| Peux-tu poster ton named.conf ?
Le fichier named.root.hints est la liste des serveurs racine pour faire une recherche à partir de la racine d'internet. | 2 tira, le 20 nov 2008 à 10:40:30Bonjour,voici mon fichier named.conf:
//
// Sample named.conf BIND DNS server 'named' configuration file
// for the Red Hat BIND distribution.
//
// See the BIND Administrator's Reference Manual (ARM) for details, in:
// file:///usr/share/doc/bind-*/arm/Bv9ARM.html
// Also see the BIND Configuration GUI : /usr/bin/system-config-bind and
// its manual.
//
options
{
/* make named use port 53 for the source of all queries, to allow
* firewalls to block all ports except 53:
*/
query-source port 53;
query-source-v6 port 53;
// Put files that named is allowed to write in the data/ directory:
directory "/var/named"; // the default
dump-file "data/cache_dump.db";
statistics-file "data/named_stats.txt";
memstatistics-file "data/named_mem_stats.txt";
};
logging
{
/* If you want to enable debugging, eg. using the 'rndc trace' command,
* named will try to write the 'named.run' file in the $directory (/var/named).
* By default, SELinux policy does not allow named to modify the /var/named directory,
* so put the default debug log file in data/ :
*/
channel default_debug {
file "data/named.run";
severity dynamic;
};
};
//
// All BIND 9 zones are in a "view", which allow different zones to be served
// to different types of client addresses, and for options to be set for groups
// of zones.
//
// By default, if named.conf contains no "view" clauses, all zones are in the
// "default" view, which matches all clients.
//
// If named.conf contains any "view" clause, then all zones MUST be in a view;
// so it is recommended to start off using views to avoid having to restructure
// your configuration files in the future.
//
view "localhost_resolver"
{
/* This view sets up named to be a localhost resolver ( caching only nameserver ).
* If all you want is a caching-only nameserver, then you need only define this view:
*/
match-clients { localhost; };
match-destinations { localhost; };
recursion yes;
# all views must contain the root hints zone:
include "/etc/named.root.hints";
/* these are zones that contain definitions for all the localhost
* names and addresses, as recommended in RFC1912 - these names should
* ONLY be served to localhost clients:
*/
include "/etc/named.rfc1912.zones";
};
view "internal"
{
/* This view will contain zones you want to serve only to "internal" clients
that connect via your directly attached LAN interfaces - "localnets" .
*/
match-clients { localnets; };
match-destinations { localnets; };
recursion yes;
// all views must contain the root hints zone:
include "/etc/named.root.hints";
// include "named.rfc1912.zones";
// you should not serve your rfc1912 names to non-localhost clients.
// These are your "authoritative" internal zones, and would probably
// also be included in the "localhost_resolver" view above :
zone "my.internal.zone" {
type master;
file "my.internal.zone.db";
};
zone "my.slave.internal.zone" {
type slave;
file "slaves/my.slave.internal.zone.db";
masters { /* put master nameserver IPs here */ 127.0.0.1; } ;
// put slave zones in the slaves/ directory so named can update them
};
zone "my.ddns.internal.zone" {
type master;
allow-update { key ddns_key; };
file "slaves/my.ddns.internal.zone.db";
// put dynamically updateable zones in the slaves/ directory so named can update them
};
};
zone "aster.sn" IN {
type master;
allow-update { none; };
file "aster.zone";
};
key ddns_key
{
algorithm hmac-md5;
secret "use /usr/sbin/dns-keygen to generate TSIG keys";
};
view "external"
{
/* This view will contain zones you want to serve only to "external" clients
* that have addresses that are not on your directly attached LAN interface subnets:
*/
match-clients { !localnets; !localhost; };
match-destinations { !localnets; !localhost; };
recursion no;
// you'd probably want to deny recursion to external clients, so you don't
// end up providing free DNS service to all takers
// all views must contain the root hints zone:
include "/etc/named.root.hints";
// These are your "authoritative" external zones, and would probably
// contain entries for just your web and mail servers:
zone "my.external.zone" {
type master;
file "my.external.zone.db";
};
};
132,1 Bas
1,1 Haut | Il va falloir que tu nettoies tout ça, si tu compte mettre tes fichiers dans un répertoire dédié, ce qui a mon avis est une excellente idée.
Tout au long du fichier tu as des includes vers des fichiers dans /etc
Range tous ces fichiers dans ton répertoire (en général /var/named),
puis change les includes de façon appropriée.
Dans l'install, quelque part, tu dois avoir le fichier hints ( named.root.hints )
il faut aussi que ce fichier soit correctement déclaré. | 6 tira, le 24 nov 2008 à 15:39:57Bonjour,excusez-moi pour tt ce silence j'etais un peu souffrante.
Maintenant j'ai réinstallé mon OS mais c'est toujours la mem distribution (fc6);dans le rep /etc/ j'ai les fichiers named.caching_nameserver.conf
[root@aster-server ~]# vim /etc/named.caching-nameserver.conf
//
// named.caching-nameserver.conf
//
// Provided by Red Hat caching-nameserver package to configure the
// ISC BIND named(8) DNS server as a caching only nameserver
// (as a localhost DNS resolver only).
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
// DO NOT EDIT THIS FILE - use system-config-bind or an editor
// to create named.conf - edits to this file will be lost on
// caching-nameserver package upgrade.
//
options {
listen-on port 53 { 127.0.0.1; };
listen-on-v6 port 53 { ::1; };
directory "/var/named";
dump-file "/var/named/data/cache_dump.db";
statistics-file "/var/named/data/named_stats.txt";
memstatistics-file "/var/named/data/named_mem_stats.txt";
query-source port 53;
query-source-v6 port 53;
allow-query { localhost; };
};
logging {
channel default_debug {
file "data/named.run";
severity dynamic;
};
};
view localhost_resolver {
match-clients { localhost; };
match-destinations { localhost; };
recursion yes;
include "/etc/named.rfc1912.zones";
};
et named.rfc1912.zones
[root@aster-server ~]# vim /etc/named.rfc1912.zones
// named.rfc1912.zones:
//
// Provided by Red Hat caching-nameserver package
//
// ISC BIND named zone configuration for zones recommended by
// RFC 1912 section 4.1 : localhost TLDs and address zones
//
// See /usr/share/doc/bind*/sample/ for example named configuration files.
//
zone "." IN {
type hint;
file "named.ca";
};
zone "localdomain" IN {
type master;
file "localdomain.zone";
allow-update { none; };
};
zone "aster.com" IN {
type master;
file "aster.com.zone";
allow-update { none; };
};
zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};
zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};
zone "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa" IN {
type master;
file "named.ip6.local";
allow-update { none; };
};
zone "255.in-addr.arpa" IN {
type master;
file "named.broadcast";
allow-update { none; };
};
zone "0.in-addr.arpa" IN {
type master;
file "named.zero";
allow-update { none; };
};
mon domaine s'appelle aster.com
voici mon fichier aster.com.zone
$TTL 86400
aster.com. IN SOA aster-server.aster.com. root.aster.com. (
42 ; serial (d. adams)
3H ; refresh
15M ; retry
1W ; expiry
1D ) ; minimum
aster.com. IN NS aster-server.aster.com.
aster-server.aster.com. IN A 127.0.0.1
www.aster.com. IN CNAME aster-server.aster.com.
aster.com. IN MX 1 aster-server.aster.com.
~
~
~
~
~
~
~
~
~
~
Puis je lance les commandes suivantes:
[root@aster-server ~]# /etc/init.d/named restart
Arrêt de named : [ OK ]
Démarrage de named : [ OK ]
[root@aster-server ~]# nslookup
> aster.com
Server: 127.0.0.1
Address: 127.0.0.1#53
** server can't find aster.com: SERVFAIL
il n'affiche pas l'enregistrement MX ni le nom complet de la machine et pourtant je l'ai bien précisé dans le fichier aster.com.zone .
Maintenant je travaille en local c'est à dire j'utilise l'@ 127.0.0.1 et ma machine s'appelle aster-server.Si vous pouvez me repondre le plus vite que possible car mon principal but c'est de mettre en place un serveur de messagerie | Ce que je vois, comme problème : tu as défini ta zone comme suit :
aster.com. IN NS aster-server.aster.com.
aster-server.aster.com. IN A 127.0.0.1
www.aster.com. IN CNAME aster-server.aster.com.
aster.com. IN MX 1 aster-server.aster.com.
Donc tu définis :
un nameserver pour aster.com
une IP 127.0.0.1 pour aster-server.aster.com
un cname vers aster-server.aster.com pour www.aster.com
et un MX vers aster-server.aster.com pour aster.com
Mais tu demandes l'IP de aster.com dans ton nslookup.
Il n'y en a pas de défini dans la zone...
Essaye de définir (par exemple) :
@ IN A 10.10.10.10
également : utilises plutôt la commande DIG pour tes interrogation, nslookup est obsolete.
dig MX aster.com
dig aster-server.aster.com
dig NS aster.com
dig aster.com
| 8 tira, le 26 nov 2008 à 11:40:22Bonjour,et merci encore pour votre disponibilité
voilà ce que j'ai comme résultat
[root@localhost named]# /etc/init.d/named restart
Arrêt de named :
Démarrage de named : [ OK ]
[root@localhost named]# nslookup
> aster.com
Server: 212.217.0.1
Address: 212.217.0.1#53
Non-authoritative answer:
Name: aster.com
Address: 66.11.237.12
>
et pourtant mon fichier /etc/resolv.conf contient ceci:
; generated by /sbin/dhclient-script
search aster.com
nameserver 10.10.10.10
nameserver 212.217.0.1
~
~
~
et avec la commande set type=any j'ai ceci :
> set type=any
> aster.com
Server: 212.217.0.1
Address: 212.217.0.1#53
Non-authoritative answer:
aster.com nameserver = ns2.everydns.net.
aster.com nameserver = ns3.everydns.net.
aster.com nameserver = ns1.everydns.net.
aster.com nameserver = ns4.everydns.net.
Authoritative answers can be found from:
aster.com nameserver = ns4.everydns.net.
aster.com nameserver = ns1.everydns.net.
aster.com nameserver = ns2.everydns.net.
aster.com nameserver = ns3.everydns.net.
> |
| 9 tira, le 26 nov 2008 à 11:52:38Ah j'ai oublié de vous montrer ce que j'obtiens avec la commande dig
[root@localhost named]# /etc/init.d/named restart
Arrêt de named : [ OK ]
Démarrage de named : [ OK ]
[root@localhost named]# dig aster.com
; <<>> DiG 9.2.4 <<>> aster.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18888
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 0
;; QUESTION SECTION:
;aster.com. IN A
;; ANSWER SECTION:
aster.com. 3600 IN A 66.11.237.12
;; AUTHORITY SECTION:
aster.com. 86400 IN NS ns3.everydns.net.
aster.com. 86400 IN NS ns1.everydns.net.
aster.com. 86400 IN NS ns4.everydns.net.
aster.com. 86400 IN NS ns2.everydns.net.
;; Query time: 2536 msec
;; SERVER: 212.217.0.1#53(212.217.0.1)
;; WHEN: Wed Nov 26 12:09:13 2008
;; MSG SIZE rcvd: 127
[root@localhost named]#
et je vois nulle part où on precise le mx | Ce que je comprend pas, tu définies un DNS sur localhost, càd ta machine locale, mais les DNS qui ont autorité sur le domaine sont ns1.everydns.net, ns2.everydns.net, ns3.everydns.net, et ns4.everydns.net. C'est normal qu'ils ne te répondent pas ce que tu mets en local, à moins que tu sois sur un des ns?.everydns.net...
Si tu veux le local, il faut mettre 127.0.0.1 dans ton resolv.conf, mais dans ce cas, il n'ira pas voir les ns?.eveydns.net | 11 tira, le 28 nov 2008 à 14:50:36Bonjour et merci encore pour tout l'aide que vous m'apporter,je vous avez dit que mon objectif etait de mettre en place en serveur de messagerie et pour cela j'ai installé les paquets:
[root@aster-server ~]# rpm -q sendmail
sendmail-8.14.1-4.2.fc6
[root@aster-server ~]# rpm -q sendmail-cf
sendmail-cf-8.14.1-4.2.fc6
[root@aster-server ~]# rpm -q m4
m4-1.4.5-3
et dans le ficher /etc/mail/sendmail.mc j'ai fait des modifications et voici le contenu:
[root@aster-server ~]# vim /etc/mail/sendmail.mc
divert(-1)dnl
dnl #
dnl # This is the sendmail macro config file for m4. If you make changes to
dnl # /etc/mail/sendmail.mc, you will need to regenerate the
dnl # /etc/mail/sendmail.cf file by confirming that the sendmail-cf package is
dnl # installed and then performing a
dnl #
dnl # make -C /etc/mail
dnl #
include(`/usr/share/sendmail-cf/m4/cf.m4')dnl
VERSIONID(`setup for linux')dnl
OSTYPE(`linux')dnl
dnl #
dnl # Do not advertize sendmail version.
dnl #
dnl define(`confSMTP_LOGIN_MSG', `$j Sendmail; $b')dnl
dnl #
dnl # default logging level is 9, you might want to set it higher to
dnl # debug the configuration
dnl #
dnl define(`confLOG_LEVEL', `9')dnl
dnl #
dnl # Uncomment and edit the following line if your outgoing mail needs to
dnl # be sent out through an external mail server:
dnl #
dnl define(`SMART_HOST', `smtp.your.provider')dnl
dnl #
define(`confDEF_USER_ID', ``8:12'')dnl
dnl define(`confAUTO_REBUILD')dnl
define(`confTO_CONNECT', `1m')dnl
define(`confTRY_NULL_MX_LIST', `True')dnl
define(`confDONT_PROBE_INTERFACES', `True')dnl
define(`PROCMAIL_MAILER_PATH', `/usr/bin/procmail')dnl
define(`ALIAS_FILE', `/etc/aliases')dnl
define(`STATUS_FILE', `/var/log/mail/statistics')dnl
define(`UUCP_MAILER_MAX', `2000000')dnl
define(`confUSERDB_SPEC', `/etc/mail/userdb.db')dnl
define(`confPRIVACY_FLAGS', `authwarnings,novrfy,noexpn,restrictqrun')dnl
define(`confAUTH_OPTIONS', `A')dnl
dnl #
dnl # The following allows relaying if the user authenticates, and disallows
dnl # plaintext authentication (PLAIN/LOGIN) on non-TLS links
dnl #
dnl define(`confAUTH_OPTIONS', `A p')dnl
dnl #
dnl # PLAIN is the preferred plaintext authentication method and used by
dnl # Mozilla Mail and Evolution, though Outlook Express and other MUAs do
dnl # use LOGIN. Other mechanisms should be used if the connection is not
dnl # guaranteed secure.
dnl # Please remember that saslauthd needs to be running for AUTH.
dnl #
dnl TRUST_AUTH_MECH(`EXTERNAL DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl
dnl define(`confAUTH_MECHANISMS', `EXTERNAL GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN PLAIN')dnl
dnl #
dnl # Rudimentary information on creating certificates for sendmail TLS:
dnl # cd /usr/share/ssl/certs; make sendmail.pem
dnl # Complete usage:
dnl # make -C /usr/share/ssl/certs usage
dnl #
dnl define(`confCACERT_PATH', `/etc/pki/tls/certs')dnl
dnl define(`confCACERT', `/etc/pki/tls/certs/ca-bundle.crt')dnl
dnl define(`confSERVER_CERT', `/etc/pki/tls/certs/sendmail.pem')dnl
dnl define(`confSERVER_KEY', `/etc/pki/tls/certs/sendmail.pem')dnl
dnl #
dnl # This allows sendmail to use a keyfile that is shared with OpenLDAP's
dnl # slapd, which requires the file to be readble by group ldap
dnl #
dnl define(`confDONT_BLAME_SENDMAIL', `groupreadablekeyfile')dnl
dnl #
dnl define(`confTO_QUEUEWARN', `4h')dnl
dnl define(`confTO_QUEUERETURN', `5d')dnl
dnl define(`confQUEUE_LA', `12')dnl
dnl define(`confREFUSE_LA', `18')dnl
define(`confTO_IDENT', `0')dnl
dnl FEATURE(delay_checks)dnl
FEATURE(`no_default_msa', `dnl')dnl
FEATURE(`smrsh', `/usr/sbin/smrsh')dnl
FEATURE(`mailertable', `hash -o /etc/mail/mailertable.db')dnl
FEATURE(`virtusertable', `hash -o /etc/mail/virtusertable.db')dnl
FEATURE(redirect)dnl
FEATURE(always_add_domain)dnl
FEATURE(use_cw_file)dnl
FEATURE(use_ct_file)dnl
dnl #
dnl # The following limits the number of processes sendmail can fork to accept
dnl # incoming messages or process its message queues to 20.) sendmail refuses
dnl # to accept connections once it has reached its quota of child processes.
dnl #
dnl define(`confMAX_DAEMON_CHILDREN', `20')dnl
dnl #
dnl # Limits the number of new connections per second. This caps the overhead
dnl # incurred due to forking new sendmail processes. May be useful against
dnl # DoS attacks or barrages of spam. (As mentioned below, a per-IP address
dnl # limit would be useful but is not available as an option at this writing.)
dnl #
dnl define(`confCONNECTION_RATE_THROTTLE', `3')dnl
dnl #
dnl # The -t option will retry delivery if e.g. the user runs over his quota.
dnl #
FEATURE(local_procmail, `', `procmail -t -Y -a $h -d $u')dnl
FEATURE(`access_db', `hash -T<TMPF> -o /etc/mail/access.db')dnl
FEATURE(`blacklist_recipients')dnl
EXPOSED_USER(`root')dnl
dnl #
dnl # For using Cyrus-IMAPd as POP3/IMAP server through LMTP delivery uncomment
dnl # the following 2 definitions and activate below in the MAILER section the
dnl # cyrusv2 mailer.
dnl #
define(`confLOCAL_MAILER', `cyrusv2')dnl
define(`CYRUSV2_MAILER_ARGS', `FILE /var/lib/imap/socket/lmtp')dnl
dnl #
dnl # The following causes sendmail to only listen on the IPv4 loopback address
dnl # 127.0.0.1 and not on any other network devices. Remove the loopback
dnl # address restriction to accept email from the internet or intranet.
dnl #
dnl DAEMON_OPTIONS(`Port=smtp,Addr=127.0.0.1, Name=MTA')dnl
dnl #
dnl # The following causes sendmail to additionally listen to port 587 for
dnl # mail from MUAs that authenticate. Roaming users who can't reach their
dnl # preferred sendmail daemon due to port 25 being blocked or redirected find
dnl # this useful.
dnl #
dnl DAEMON_OPTIONS(`Port=submission, Name=MSA, M=Ea')dnl
dnl #
dnl # The following causes sendmail to additionally listen to port 465, but
dnl # starting immediately in TLS mode upon connecting. Port 25 or 587 followed
dnl # by STARTTLS is preferred, but roaming clients using Outlook Express can't
dnl # do STARTTLS on ports other than 25. Mozilla Mail can ONLY use STARTTLS
dnl # and doesn't support the deprecated smtps; Evolution <1.1.1 uses smtps
dnl # when SSL is enabled-- STARTTLS support is available in version 1.1.1.
dnl #
dnl # For this to work your OpenSSL certificates must be configured.
dnl #
dnl DAEMON_OPTIONS(`Port=smtps, Name=TLSMTA, M=s')dnl
dnl #
dnl # The following causes sendmail to additionally listen on the IPv6 loopback
dnl # device. Remove the loopback address restriction listen to the network.
dnl #
dnl DAEMON_OPTIONS(`port=smtp,Addr=::1, Name=MTA-v6, Family=inet6')dnl
dnl #
dnl # enable both ipv6 and ipv4 in sendmail:
dnl #
dnl DAEMON_OPTIONS(`Name=MTA-v4, Family=inet, Name=MTA-v6, Family=inet6')
dnl #
dnl # We strongly recommend not accepting unresolvable domains if you want to
dnl # protect yourself from spam. However, the laptop and users on computers
dnl # that do not have 24x7 DNS do need this.
dnl #
FEATURE(`accept_unresolvable_domains')dnl
dnl #
dnl FEATURE(`relay_based_on_MX')dnl
dnl #
dnl # Also accept email sent to "localhost.localdomain" as local email.
dnl #
LOCAL_DOMAIN(`localhost.localdomain')dnl
dnl #
dnl # The following example makes mail from this host and any additional
dnl # specified domains appear to be sent from mydomain.com
dnl #
MASQUERADE_AS(`aster.com')dnl
dnl #
dnl # masquerade not just the headers, but the envelope as well
dnl #
FEATURE(masquerade_envelope)dnl
dnl #
dnl # masquerade not just @mydomainalias.com, but @*.mydomainalias.com as well
dnl #
dnl FEATURE(masquerade_entire_domain)dnl
dnl #
dnl MASQUERADE_DOMAIN(localhost)dnl
dnl MASQUERADE_DOMAIN(localhost.localdomain)dnl
dnl MASQUERADE_DOMAIN(mydomainalias.com)dnl
dnl MASQUERADE_DOMAIN(mydomain.lan)dnl
MAILER(smtp)dnl
MAILER(procmail)dnl
MAILER(cyrusv2)dnl
FIN
Et j'ai tappé la commandes suivantes:
[root@aster-server ~]# m4 /etc/mail/sendmail.mc > /etc/mail/sendmail.cf
[root@aster-server ~]# /etc/init.d/sendmail restart
Arrêt de sm-client : [ OK ]
Arrêt de sendmail : [ OK ]
Démarrage de sendmail : [ OK ]
Démarrage de sm-client : [ OK ]
[root@aster-server ~]# sendmail -bt -d0.1 < /dev/null
Version 8.14.1
Compiled with: DNSMAP HESIOD HES_GETMAILHOST LDAPMAP LOG MAP_REGEX
MATCHGECOS MILTER MIME7TO8 MIME8TO7 NAMED_BIND NETINET NETINET6
NETUNIX NEWDB NIS PIPELINING SASLv2 SCANF SOCKETMAP STARTTLS
TCPWRAPPERS USERDB USE_LDAP_INIT
============ SYSTEM IDENTITY (after readcf) ============
(short domain name) $w = aster-server
(canonical domain name) $j = aster-server.aster.com
(subdomain name) $m = aster.com
(node name) $k = aster-server.aster.com
========================================================
ADDRESS TEST MODE (ruleset 3 NOT automatically invoked)
Enter <ruleset> <address>
[root@aster-server ~]# hostname aster-server.aster.com
[root@aster-server ~]# vim /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 aster-server.aster.com localhost aster-server
192.168.1.110 aster-server.aster.com aster-server
192.168.1.110 www.aster.com linux.aster.com
~
~
Ensuite je crée 2 utilisateurs toto et tata par la commande adduser puis je redémarre sendmail ,et j'envoie un email
à un utilisateur qui n'est pas sur la meme machine
[root@aster-server ~]# mail ndella81@yahoo.fr
Subject: essai
teste
.
Cc: no
[root@aster-server ~]#
et pour lire le message envoyé
[root@aster-server ~]# mail -u root
No mail for root
[root@aster-server ~]#
pour la création des boites à lettre , je demarre le cyrus par :
[root@aster-server ~]# /etc/init.d/cyrus-imapd restart
Arrêt de cyrus-imapd : [ OK ]
Exportations des bases de données cyrus-imapd [ OK ]
Importation des bases de données cyrus-imapd [ OK ]
Démarrage de cyrus-imapd : [ OK ]
[root@aster-server ~]# id cyrus
uid=76(cyrus) gid=12(mail) groupes=12(mail),76(saslauth)
[root@aster-server ~]# passwd cyrus
Changing password for user cyrus.
New UNIX password:
BAD PASSWORD: it is based on a dictionary word
Retype new UNIX password:
passwd: all authentication tokens updated successfully.
[root@aster-server ~]#
[root@aster-server ~]# telnet localhost 25
Trying 127.0.0.1...
Connected to aster-server.aster.com (127.0.0.1).
Escape character is '^]'.
220 aster-server.aster.com ESMTP Sendmail 8.14.1/8.14.1; Fri, 28 Nov 2008 13:36:17 GMT
mail from:ndella81@yahoo.fr
250 2.1.0 ndella81@yahoo.fr... Sender ok
rcpt to:toto@aster-server.aster.com
250 2.1.5 toto@aster-server.aster.com... Recipient ok
data
354 Enter mail, end with "." on a line by itself
BONJOUR
.
250 2.0.0 mASDaHIE005165 Message accepted for delivery
quit
221 2.0.0 aster-server.aster.com closing connection
Connection closed by foreign host.
[root@aster-server ~]#
ET POUR CRÉÉR DESBOITES DE toto et tata
voici ce que cela donne:
[root@aster-server ~]# cyradm
cyradm> cm user.toto
createmailbox: no connection to server
cyradm>
ET POURTANT Je pensais que Sendmail et cyrus-imapd ont été correctement configuré et
et en cours d'exécution. Donc, je suis encore confus.
S'il vous plaît AIDEZ-MOI |
|
|
|
|
|
|
|
Astus configurer dns windows 2008
