[Resolu]Problème postfix !!!!

azzurri · Le 08/08/2007, à 17:40

Bonjour à tous,

J'ai un petit problème avec postfix j'explique :

je l'ai installé, configuré, tout, aucune erreur...:cool:
(pour info j'ai installé courier comme serveur imap)
du coup j'ai installé thunderbird pour recevoir et envoyer des mails.:P

Mais le problème vient du fait j'envoie avec thunderbird mais je ne reçois rien et dans les log j'ai ceci :

Aug 8 17:32:22 server postfix/local[13165]: 0C4661780B: to=<portable@maison.lan>, relay=local, delay=0.21, delays=0.16/0.02/0/0.02, dsn=2.0.0, status=sent (delivered to mailbox)
Aug 8 17:32:22 server postfix/qmgr[12915]: 0C4661780B: removed
Aug 8 17:32:22 server postfix/smtpd[13161]: disconnect from localhost[127.0.0.1]

La ligne du removed me semble bizarre !!!!!!

un petit coup de pouce serait la bienvenue merci d'avance

NooP · Le 08/08/2007, à 17:43

Le 'remove' est normal.. Postfix te dit simplement qu'il a supprimé le message de sa Queue étant donné qu'il l'a délivré à ta mailbox.
Ensuite, pour pouvoir recevoir tes mails, il faut configurer ton client de courrier. Il me semble que le démon IMAP ne fonctionne plus en 'normal' mais seulement en SSL (port 993)

azzurri · Le 08/08/2007, à 17:47

NooP a écrit :

Le 'remove' est normal.. Postfix te dit simplement qu'il a supprimé le message de sa Queue étant donné qu'il l'a délivré à ta mailbox.
Ensuite, pour pouvoir recevoir tes mails, il faut configurer ton client de courrier. Il me semble que le démon IMAP ne fonctionne plus en 'normal' mais seulement en SSL (port 993)

Bizarre car je viens juste de vérifier la config du serveur imap et dans le fichier de conf il indique bien le port 143 (port imap).....:/

NooP · Le 08/08/2007, à 17:54

Heu !
Je n'ai jamais trouvé de fichier de configuration pour imap ...
Quel IMAP as tu installé ? Il en existe plusieurs.

Le mien (uw-imapd), je le fait tourner à l'aide de xinetd à l'aide du fichier de config suivant :

/etc/xinetd.d/imaps

service imaps
{
        disable         = no
        socket_type     = stream
        wait            = no
        user            = root
        server          = /usr/sbin/imapd
        log_on_success  += DURATION USERID
        log_on_failure  += USERID
}

Dernière modification par NooP (Le 08/08/2007, à 17:56)

azzurri · Le 08/08/2007, à 18:05

Comme serveur imap j'ai courier-imap...

NooP · Le 08/08/2007, à 18:12

Je vais pas pouvoir t'aider, je n'ai jamais testé courier-imap.
Désolé.

toniotonio · Le 08/08/2007, à 22:41

il faut la conf de courier et celle de postfix (postconf -n)

et un peu plus de logs

azzurri · Le 09/08/2007, à 10:14

Voici la conf de postfix :

alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
inet_interfaces = all
inet_protocols = all
mailbox_size_limit = 0
mydestination = maison.lan, localhost, localhost.localdomain, localhost
myhostname = server.maison.lan
mynetworks = 127.0.0.0/8
myorigin = /etc/mailname
recipient_delimiter = +
relayhost =
smtp_tls_session_cache_database = btree:${queue_directory}/smtp_scache
smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key
smtpd_tls_session_cache_database = btree:${queue_directory}/smtpd_scache
smtpd_use_tls = yes

Et celle de courier-imap :

##VERSION: $Id: imapd.dist.in,v 1.38 2006/02/24 02:15:07 mrsam Exp $
#
# imapd created from imapd.dist by sysconftool
#
# Do not alter lines that begin with ##, they are used when upgrading
# this configuration.
#
# Copyright 1998 - 2006 Double Precision, Inc. See COPYING for
# distribution information.
#
# This configuration file sets various options for the Courier-IMAP server
# when used with the couriertcpd server.
# A lot of the stuff here is documented in the manual page for couriertcpd.
#
# NOTE - do not use \ to split long variable contents on multiple lines.
# This will break the default imapd.rc script, which parses this file.
#
##NAME: ADDRESS:0
#
# Address to listen on, can be set to a single IP address.
#
# ADDRESS=127.0.0.1

ADDRESS=0

##NAME: PORT:1
#
# Port numbers that connections are accepted on. The default is 143,
# the standard IMAP port.
#
# Multiple port numbers can be separated by commas. When multiple port
# numbers are used it is possible to select a specific IP address for a
# given port as "ip.port". For example, "127.0.0.1.900,192.68.0.1.900"
# accepts connections on port 900 on IP addresses 127.0.0.1 and 192.68.0.1
# The previous ADDRESS setting is a default for ports that do not have
# a specified IP address.

PORT=143

##NAME: AUTHSERVICE:0
#
# It's possible to authenticate using a different 'service' parameter
# depending on the connection's port. This only works with authentication
# modules that use the 'service' parameter, such as PAM. Example:
#
# AUTHSERVICE143=imap
# AUTHSERVICE993=imaps

##NAME: MAXDAEMONS:0
#
# Maximum number of IMAP servers started
#

MAXDAEMONS=40

##NAME: MAXPERIP:0
#
# Maximum number of connections to accept from the same IP address

MAXPERIP=20

##NAME: PIDFILE:0
#
# File where couriertcpd will save its process ID
#

PIDFILE=/var/run/courier/imapd.pid

##NAME: TCPDOPTS:0
#
# Miscellaneous couriertcpd options that shouldn't be changed.
#

TCPDOPTS="-nodnslookup -noidentlookup"

##NAME: LOGGEROPTS:0
#
# courierlogger(1) options.
#

LOGGEROPTS="-name=imapd"

##NAME: DEFDOMAIN:0
#
# Optional default domain. If the username does not contain the
# first character of DEFDOMAIN, then it is appended to the username.
# If DEFDOMAIN and DOMAINSEP are both set, then DEFDOMAIN is appended
# only if the username does not contain any character from DOMAINSEP.
# You can set different default domains based on the the interface IP
# address using the -access and -accesslocal options of couriertcpd(1).

#DEFDOMAIN="@maison.lan"
##NAME: IMAP_CAPABILITY:1
#
# IMAP_CAPABILITY specifies what most of the response should be to the
# CAPABILITY command.
#
# If you have properly configured Courier to use CRAM-MD5, CRAM-SHA1, or
# CRAM-SHA256 authentication (see INSTALL), set IMAP_CAPABILITY as follows:
#
# IMAP_CAPABILITY="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA AUTH=CRAM-MD5 AUTH=CRAM-SHA1 AUTH=CRAM-SHA256 IDLE"
#

IMAP_CAPABILITY="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE"

##NAME: KEYWORDS_CAPABILITY:0
#
# IMAP_KEYWORDS=1 enables custom IMAP keywords. Set this option to 0 to
# disable custom keywords.

IMAP_KEYWORDS=1

##NAME: ACL_CAPABILITY:0
#
# IMAP_ACL=1 enables IMAP ACL extension. Set this option to 0 to
# disable ACL capabilities announce.

IMAP_ACL=1

##NAME: SMAP1_CAPABILITY:0
#
# EXPERIMENTAL
#
# To enable the experimental "Simple Mail Access Protocol" extensions,
# uncomment the following setting.
#
# SMAP_CAPABILITY=SMAP1

##NAME: IMAP_CAPABILITY_ORIG:2
#
# For use by webadmin

IMAP_CAPABILITY_ORIG="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA AUTH=CRAM-MD5 AUTH=CRAM-SHA1 AUTH=CRAM-SHA256 IDLE"

##NAME: IMAP_PROXY:0
#
# Enable proxying. See README.proxy
IMAP_PROXY=0

##NAME: PROXY_HOSTNAME:0
#
# Override value from gethostname() when checking if a proxy connection is
# required.
#
# PROXY_HOSTNAME=

##NAME: IMAP_PROXY_FOREIGN:0
#
# Proxying to non-Courier servers. Re-sends the CAPABILITY command after
# logging in to the remote server. May not work with all IMAP clients.

IMAP_PROXY_FOREIGN=0

##NAME: IMAP_IDLE_TIMEOUT:0
#
# This setting controls how often
# the server polls for changes to the folder, in IDLE mode (in seconds).

IMAP_IDLE_TIMEOUT=60

##NAME: IMAP_CAPABILITY_TLS:0
#
# The following setting will advertise SASL PLAIN authentication after
# STARTTLS is established. If you want to allow SASL PLAIN authentication
# with or without TLS then just comment this out, and add AUTH=PLAIN to
# IMAP_CAPABILITY

IMAP_CAPABILITY_TLS="$IMAP_CAPABILITY AUTH=PLAIN"

##NAME: IMAP_TLS_ORIG:0
#
# For use by webadmin

IMAP_CAPABILITY_TLS_ORIG="$IMAP_CAPABILITY_ORIG AUTH=PLAIN"

##NAME: IMAP_DISABLETHREADSORT:0
#
# Set IMAP_DISABLETHREADSORT to disable the THREAD and SORT commands -
# server side sorting and threading.
#
# Those capabilities will still be advertised, but the server will reject
# them. Set this option if you want to disable all the extra load from
# server-side threading and sorting. Not advertising those capabilities
# will simply result in the clients reading the entire folder, and sorting
# it on the client side. That will still put some load on the server.
# advertising these capabilities, but rejecting the commands, will stop this
# silliness.
#

IMAP_DISABLETHREADSORT=0

##NAME: IMAP_CHECK_ALL_FOLDERS:0
#
# Set IMAP_CHECK_ALL_FOLDERS to 1 if you want the server to check for new
# mail in every folder. Not all IMAP clients use the IMAP's new mail
# indicator, but some do. Normally new mail is checked only in INBOX,
# because it is a comparatively time consuming operation, and it would be
# a complete waste of time unless mail filters are used to deliver
# mail directly to folders.
#
# When IMAP clients are used which support new mail indication, and when
# mail filters are used to sort incoming mail into folders, setting
# IMAP_CHECK_ALL_FOLDERS to 1 will allow IMAP clients to announce new
# mail in folders. Note that this will result in slightly more load on the
# server.
#

IMAP_CHECK_ALL_FOLDERS=0

##NAME: IMAP_OBSOLETE_CLIENT:0
#
# Set IMAP_OBSOLETE_CLIENT if your IMAP client expects \\NoInferiors to mean
# what \\HasNoChildren really means.

IMAP_OBSOLETE_CLIENT=0

##NAME: IMAP_UMASK:0
#
# IMAP_UMASK sets the umask of the server process. The value of IMAP_UMASK is
# simply passed to the "umask" command. The default value is 022.
#
# This feature is mostly useful for shared folders, where the file permissions
# of the messages may be important.

IMAP_UMASK=022

##NAME: IMAP_ULIMITD:0
#
# IMAP_ULIMITD sets the maximum size of the data segment of the server
# process. The value of IMAP_ULIMITD is simply passed to the "ulimit -d"
# command (or ulimit -v). The argument to ulimi sets the upper limit on the
# size of the data segment of the server process, in kilobytes. The default
# value of 65536 sets a very generous limit of 64 megabytes, which should
# be more than plenty for anyone.
#
# This feature is used as an additional safety check that should stop
# any potential denial-of-service attacks that exploit any kind of
# a memory leak to exhaust all the available memory on the server.
# It is theoretically possible that obscenely huge folders will also
# result in the server running out of memory when doing server-side
# sorting (by my calculations you have to have at least 100,000 messages
# in a single folder, for that to happen).

IMAP_ULIMITD=65536

##NAME: IMAP_USELOCKS:0
#
# Setting IMAP_USELOCKS to 1 will use dot-locking to support concurrent
# multiple access to the same folder. This incurs slight additional
# overhead. Concurrent multiple access will still work without this setting,
# however occasionally a minor race condition may result in an IMAP client
# downloading the same message twice, or a keyword update will fail.
#
# IMAP_USELOCKS=1 is strongly recommended when shared folders are used.

IMAP_USELOCKS=1

##NAME: IMAP_SHAREDINDEXFILE:0
#
# The index of all accessible folders. Do not change this setting unless
# you know what you're doing. See README.sharedfolders for additional
# information.

IMAP_SHAREDINDEXFILE=/etc/courier/shared/index

##NAME: IMAP_ENHANCEDIDLE:0
#
# If Courier was compiled with the File Alteration Monitor, setting
# IMAP_ENHANCEDIDLE to 1 enables enhanced IDLE mode, where multiple
# clients may open the same folder concurrently, and receive updates to
# folder contents in realtime. See the imapd(8) man page for additional
# information.
#
# IMPORTANT: IMAP_USELOCKS *MUST* also be set to 1, and IDLE must be included
# in the IMAP_CAPABILITY list.
#

IMAP_ENHANCEDIDLE=0

##NAME: IMAP_TRASHFOLDERNAME:0
#
# The name of the magic trash Folder. For MSOE compatibility,
# you can set IMAP_TRASHFOLDERNAME="Deleted Items".
#
# IMPORTANT: If you change this, you must also change IMAP_EMPTYTRASH

IMAP_TRASHFOLDERNAME=Trash

##NAME: IMAP_EMPTYTRASH:0
#
# The following setting is optional, and causes messages from the given
# folder to be automatically deleted after the given number of days.
# IMAP_EMPTYTRASH is a comma-separated list of folder:days. The default
# setting, below, purges 7 day old messages from the Trash folder.
# Another useful setting would be:
#
# IMAP_EMPTYTRASH=Trash:7,Sent:30
#
# This would also delete messages from the Sent folder (presumably copies
# of sent mail) after 30 days. This is a global setting that is applied to
# every mail account, and is probably useful in a controlled, corporate
# environment.
#
# Important: the purging is controlled by CTIME, not MTIME (the file time
# as shown by ls). It is perfectly ordinary to see stuff in Trash that's
# a year old. That's the file modification time, MTIME, that's displayed.
# This is generally when the message was originally delivered to this
# mailbox. Purging is controlled by a different timestamp, CTIME, which is
# changed when the file is moved to the Trash folder (and at other times too).
#
# You might want to disable this setting in certain situations - it results
# in a stat() of every file in each folder, at login and logout.
#

IMAP_EMPTYTRASH=Trash:7

##NAME: IMAP_MOVE_EXPUNGE_TO_TRASH:0
#
# Set IMAP_MOVE_EXPUNGE_TO_TRASH to move expunged messages to Trash. This
# effectively allows an undo of message deletion by fishing the deleted
# mail from trash. Trash can be manually expunged as usually, and mail
# will get automatically expunged from Trash according to IMAP_EMPTYTRASH.
#
# NOTE: shared folders are still expunged as usual. Shared folders are
# not affected.
#

IMAP_MOVE_EXPUNGE_TO_TRASH=0

##NAME: OUTBOX:0
#
# The next set of options deal with the "Outbox" enhancement.
# Uncomment the following setting to create a special folder, named
# INBOX.Outbox
#
# OUTBOX=.Outbox

##NAME: SENDMAIL:0
#
# If OUTBOX is defined, mail can be sent via the IMAP connection by copying
# a message to the INBOX.Outbox folder. For all practical matters,
# INBOX.Outbox looks and behaves just like any other IMAP folder. If this
# folder doesn't exist it must be created by the IMAP mail client, just
# like any other IMAP folder. The kicker: any message copied or moved to
# this folder is will be E-mailed by the Courier-IMAP server, by running
# the SENDMAIL program. Therefore, messages copied or moved to this
# folder must be well-formed RFC-2822 messages, with the recipient list
# specified in the To:, Cc:, and Bcc: headers. Courier-IMAP relies on
# SENDMAIL to read the recipient list from these headers (and delete the Bcc:
# header) by running the command "$SENDMAIL -oi -t -f $SENDER", with the
# message piped on standard input. $SENDER will be the return address
# of the message, which is set by the authentication module.
#
# DO NOT MODIFY SENDMAIL, below, unless you know what you're doing.
#

SENDMAIL=/usr/sbin/sendmail

##NAME: HEADERFROM:0
#
# For administrative and oversight purposes, the return address, $SENDER
# will also be saved in the X-IMAP-Sender mail header. This header gets
# added to the sent E-mail (but it doesn't get saved in the copy of the
# message that's saved in the folder)
#
# WARNING - By enabling OUTBOX above, *every* IMAP mail client will receive
# the magic OUTBOX treatment. Therefore advance LARTing is in order for
# _all_ of your lusers, until every one of them is aware of this. Otherwise if
# OUTBOX is left at its default setting - a folder name that might be used
# accidentally - some people may be in for a rude surprise. You can redefine
# the name of the magic folder by changing OUTBOX, above. You should do that
# and pick a less-obvious name. Perhaps brand it with your organizational
# name ( OUTBOX=.WidgetsAndSonsOutbox )

HEADERFROM=X-IMAP-Sender

##NAME: OUTBOX_MULTIPLE_SEND:0
#
# Remove the following comment to allow a COPY of more than one message to
# the Outbox, at a time.
#
# OUTBOX_MULTIPLE_SEND=1

##NAME: IMAPDSTART:0
#
# IMAPDSTART is not used directly. Rather, this is a convenient flag to
# be read by your system startup script in /etc/rc.d, like this:
#
# . /etc/courier/imapd
#
# case x$IMAPDSTART in
# x[yY]*)
# /usr/lib/courier/imapd.rc start
# ;;
# esac
#
# The default setting is going to be NO, so you'll have to manually flip
# it to yes.

IMAPDSTART=YES

##NAME: MAILDIRPATH:0
#
# MAILDIRPATH - directory name of the maildir directory.
#
MAILDIRPATH=Maildir

Il faut savoir que je n'ai pas touché à la conf de courier car elle me semblait correct:/

Merci de votre aide:)

stopher · Le 09/08/2007, à 10:25

Salut ..

J'ai testé , mais pas longtemps , Courier-imap et pop ... apres l'on m'a conseillé d'utiliser dovecot ... bref ..

Pour courier-imap , voici la conf de base qui fonctione sans probleme :

ADDRESS=0
AUTHMODULES="authdaemon"
IMAP_CAPABILITY="IMAP4rev1 UIDPLUS CHILDREN NAMESPACE THREAD=ORDEREDSUBJECT THREAD=REFERENCES SORT QUOTA IDLE"
IMAP_EMPTYTRASH=Trash:7
IMAP_IDLE_TIMEOUT=60
IMAP_TRASHFOLDERNAME=Trash
MAILDIRPATH=Maildir
MAXDAEMONS=40
MAXPERIP=4
PIDFILE=/var/run/courier/imapd.pid
PORT=143
SENDMAIL=/usr/sbin/sendmail
TCPDOPTS="-nodnslookup -noidentlookup"
IMAPDSTART=YES

Voilà , il n'y avait que ça dans mon fichier de conf .. et ca fonctionnait bien .. je n'ai pas eu le temps de tester d'autres options..

toniotonio · Le 09/08/2007, à 10:26

en fait postfix livre le courier dans /var/spool/mail en style mbox.

courier-imap lui fonctionne en Maildir, un tout autre style de boite email.

il faut donc specifier a postfix de livrer de cette facon

ajoute au main.cf

home_mailbox = Maildir/

puis tu fais un postfix reload

Dernière modification par toniotonio (Le 09/08/2007, à 10:27)

stopher · Le 09/08/2007, à 10:32

A oui en effet ... ca ne peut pas fonctionner !!

Juste pour l'info , pour le format mailbox tous les messages d'une boite sont stokés dans un fichier texte unique , alors que le format Maildir met en place une arborescence de repertoires particuliere et cree un fichier par message .

azzurri · Le 09/08/2007, à 10:51

En effet postfix livre bien les mails en /var/spool/mail/$USER.

En rajoutant la ligne :
home_mailbox = Maildir/

cela n'a aucun effet, le courier est toujours livré dans /var/spool/mail mais la piste de recherche est la bonne si vous trouvez des solutions POSTER !!!

toniotonio · Le 09/08/2007, à 10:54

as tu rechargé postfix ?
poste un postconf -n et les logs d'une livraison

poste aussi un
ls -la /var/spool/mail

et un

ls -la /home/ton user/Maildir

Dernière modification par toniotonio (Le 09/08/2007, à 10:58)

azzurri · Le 09/08/2007, à 11:13

Oui bien sur j'ai rechargé postfix.

Voici le résultat de postconf -n

alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
home_mailbox = Maildir/
inet_interfaces = all
inet_protocols = all
mailbox_size_limit = 0
mydestination = maison.lan, localhost, localhost.localdomain, localhost
myhostname = server.maison.lan
mynetworks = 127.0.0.0/8
myorigin = /etc/mailname
recipient_delimiter = +
relayhost =
smtp_tls_session_cache_database = btree:${queue_directory}/smtp_scache
smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)
smtpd_tls_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file = /etc/ssl/private/ssl-cert-snakeoil.key
smtpd_tls_session_cache_database = btree:${queue_directory}/smtpd_scache
smtpd_use_tls = yes

le résultat de ls -la /var/spool/mail :

lrwxrwxrwx 1 root root 7 2007-05-05 15:07 /var/spool/mail -> ../mail

et le résultat de ls -la /home/MONUSER/Maildir :

drwx------ 12 azzurri azzurri 4096 2007-08-08 17:30 .
drwxr-xr-x 29 azzurri azzurri 4096 2007-08-09 10:05 ..
drwx------  2 azzurri azzurri 4096 2007-08-08 16:24 courierimapkeywords
-rw-r--r--  1 azzurri azzurri   11 2007-08-08 17:30 courierimapsubscribed
-rw-r--r--  1 azzurri azzurri   15 2007-08-08 16:24 courierimapuiddb
drwx------  2 azzurri azzurri 4096 2007-08-08 16:22 cur
drwx------  5 azzurri azzurri 4096 2007-08-08 16:24 .Drafts
drwx------  5 azzurri azzurri 4096 2007-08-08 16:24 .junkmail
drwx------  2 azzurri azzurri 4096 2007-08-08 16:22 new
drwx------  5 azzurri azzurri 4096 2007-08-08 16:24 .Queue
drwx------  6 azzurri azzurri 4096 2007-08-08 17:30 .Sent
drwx------  2 azzurri azzurri 4096 2007-08-09 11:08 tmp
drwx------  6 azzurri azzurri 4096 2007-08-08 17:10 .Trash
drwx------  5 azzurri azzurri 4096 2007-08-08 16:24 .virus

Sinon au niveau des log j'ai un truc bizarre :

dans mail.err (éloquant !!!) :

Aug  9 11:04:17 server postfix/local[7597]: fatal: gethostbyname: Success

et une autre erreur :

Aug  9 11:12:07 server postfix/smtpd[7837]: connect from portable.maison.lan[192.168.1.101]
Aug  9 11:12:07 server postfix/smtpd[7837]: D45A51782C: client=portable.maison.lan[192.168.1.101]
Aug  9 11:12:07 server postfix/cleanup[7841]: D45A51782C: message-id=<46BADA70.2020707@maison.lan>
Aug  9 11:12:07 server postfix/qmgr[7574]: D45A51782C: from=<portable@maison.lan>, size=524, nrcpt=1 (queue active)
Aug  9 11:12:07 server postfix/smtpd[7837]: disconnect from portable.maison.lan[192.168.1.101]
Aug  9 11:12:07 server postfix/local[7842]: fatal: gethostbyname: Success
Aug  9 11:12:08 server postfix/qmgr[7574]: warning: premature end-of-input on private/local socket while reading input attribute name
Aug  9 11:12:08 server postfix/qmgr[7574]: warning: private/local socket: malformed response
Aug  9 11:12:08 server postfix/qmgr[7574]: warning: transport local failure -- see a previous warning/fatal/panic logfile record for the problem description
Aug  9 11:12:08 server postfix/master[4252]: warning: process /usr/lib/postfix/local pid 7842 exit status 1
Aug  9 11:12:08 server postfix/master[4252]: warning: /usr/lib/postfix/local: bad command startup -- throttling
Aug  9 11:12:09 server postfix/qmgr[7574]: D45A51782C: to=<azzurri@maison.lan>, relay=none, delay=1.1, delays=0.07/1.1/0/0, dsn=4.3.0, status=deferred (unknown mail transport error)

voila voila et merci toniotonio;)

toniotonio · Le 09/08/2007, à 11:20

fais voir ton /etc/hosts et le /etc/hostname

Dernière modification par toniotonio (Le 09/08/2007, à 11:21)

azzurri · Le 09/08/2007, à 11:23

Voici mon /etc/hosts :

127.0.0.1       localhost localhost.localdomain mailx.maison.lan
192.168.1.101   portable.maison.lan portable

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

et mon /etc/hostname:

server

toniotonio · Le 09/08/2007, à 11:25

postfix ne trouve pas ton domaine c'est normal...
bon deja c'est pas tres recommandé de bosser avec des domaines locaux.

ajoute maison.lan dans 127.0.0.1 et 192.168.1.101 dans ton hosts

puis fais un /etc/init.d/postfix restart (pas un reload)

Dernière modification par toniotonio (Le 09/08/2007, à 11:26)

azzurri · Le 09/08/2007, à 11:36

Je n'ai pas compris où je dois rajouter 192.168.1.101
et pourquoi dis tu qu'il n'ai pas recommandé de travailler en local ?

Mais encore une fois merci pour l'aide

toniotonio · Le 09/08/2007, à 11:40

pour le domaine local si tu ne comptes pas envoyés de mail vers l'exterieur avec ce serveur c'est ok.

desolé mon message du dessus etait pas clair:

tu modifies le /etc/hosts:

127.0.0.1       localhost localhost.localdomain mailx.maison.lan maison.lan
192.168.1.101   portable.maison.lan portable maison.lan

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

Dernière modification par toniotonio (Le 09/08/2007, à 11:41)

azzurri · Le 09/08/2007, à 11:52

Non je ne compte pas envoyé de mail à l'extérieur juste en local.

J'ai rajouté mais cela ne marche pas toujours pas possible de recevoir de mail.
J'ai toujours la même erreur :

Aug  9 11:45:31 server postfix/local[8876]: fatal: gethostbyname: Success

toniotonio · Le 09/08/2007, à 11:57

as tu relancé postfix par un /etc/init.d/postfix restart ?

poste le contenu de /etc/hosts et de /var/spool/postfix/etc/hosts

azzurri · Le 09/08/2007, à 12:05

oui je l'ai relancé.

les contenu de mon /etc/hosts et /var/spool/postfix/etc/hosts sont les mêmes :

127.0.0.1       localhost localhost.localdomain mailx.maison.lan maison.lan
192.168.1.101   portable.maison.lan portable maison.lan

# The following lines are desirable for IPv6 capable hosts
::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

toniotonio · Le 09/08/2007, à 12:36

quand tu tapes hostname en ligne de commande il te donne quoi ?

et nslookup maison.lan ?

fais voir aussi le /etc/hosts.conf

un petit reboot pourrait aussi t'aider (meme sous linux des fois ca sert )

azzurri · Le 09/08/2007, à 13:37

Marrant quand je fais nslookup maison.lan :

Server:         192.168.1.102
Address:        192.168.1.102#53

*** Can't find maison.lan: No answer

Par contre quand je fais :

azzurri@server:~$ nslookup 192.168.1.102
Server:         192.168.1.102
Address:        192.168.1.102#53

102.1.168.192.in-addr.arpa      name = ns.maison.lan.
102.1.168.192.in-addr.arpa      name = mailx.maison.lan.

ça fonctionne l'adresse 192.168.1.102 est l'IP de la machine servant de dns et de serveur de mail.

Je n'ai pas de hosts.conf.

toniotonio · Le 09/08/2007, à 13:45

je voulais dire /etc/host.conf

donc tu as un serveur DNS !
c'est un bind ?
t'as la conf ?

il faut dans tous les cas que maison.lan existe dans ce dns.

Ubuntu-fr

Navigation

Liens de recherche

Annonce

#1 Le 08/08/2007, à 17:40

[Resolu]Problème postfix !!!!

#2 Le 08/08/2007, à 17:43

Re : [Resolu]Problème postfix !!!!

#3 Le 08/08/2007, à 17:47

Re : [Resolu]Problème postfix !!!!

#4 Le 08/08/2007, à 17:54

Re : [Resolu]Problème postfix !!!!

#5 Le 08/08/2007, à 18:05

Re : [Resolu]Problème postfix !!!!

#6 Le 08/08/2007, à 18:12

Re : [Resolu]Problème postfix !!!!

#7 Le 08/08/2007, à 22:41

Re : [Resolu]Problème postfix !!!!

#8 Le 09/08/2007, à 10:14

Re : [Resolu]Problème postfix !!!!

#9 Le 09/08/2007, à 10:25

Re : [Resolu]Problème postfix !!!!

#10 Le 09/08/2007, à 10:26

Re : [Resolu]Problème postfix !!!!

#11 Le 09/08/2007, à 10:32

Re : [Resolu]Problème postfix !!!!

#12 Le 09/08/2007, à 10:51

Re : [Resolu]Problème postfix !!!!

#13 Le 09/08/2007, à 10:54

Re : [Resolu]Problème postfix !!!!

#14 Le 09/08/2007, à 11:13

Re : [Resolu]Problème postfix !!!!

#15 Le 09/08/2007, à 11:20

Re : [Resolu]Problème postfix !!!!

#16 Le 09/08/2007, à 11:23

Re : [Resolu]Problème postfix !!!!

#17 Le 09/08/2007, à 11:25

Re : [Resolu]Problème postfix !!!!

#18 Le 09/08/2007, à 11:36

Re : [Resolu]Problème postfix !!!!

#19 Le 09/08/2007, à 11:40

Re : [Resolu]Problème postfix !!!!

#20 Le 09/08/2007, à 11:52

Re : [Resolu]Problème postfix !!!!

#21 Le 09/08/2007, à 11:57

Re : [Resolu]Problème postfix !!!!

#22 Le 09/08/2007, à 12:05

Re : [Resolu]Problème postfix !!!!

#23 Le 09/08/2007, à 12:36

Re : [Resolu]Problème postfix !!!!

#24 Le 09/08/2007, à 13:37

Re : [Resolu]Problème postfix !!!!

#25 Le 09/08/2007, à 13:45

Re : [Resolu]Problème postfix !!!!

Pied de page des forums