[résolu] serveur mail : récup des mails sur un autre ordi

sylvain1970 · Le 22/04/2008, à 17:06

Bonjour,
j'ai suivi ce tuto pour installer un serveur de mail.
Tout marche bien (au passage, encore merci à M. DECLERCQ).
Par contre, les mails sont sur le serveur dans /home/user/Maildir...

Comment les récupérer à partir d'un autre ordi ?
(je préfère demander avant de trifouiler et tout casser car plus je lis de tuto/explication, moins j'arrive à savoir quoi installer et où - serveur ou ordi).

précision : le serveur accepte ssh avec login+clé

Merci.

Dernière modification par sylvain1970 (Le 24/04/2008, à 18:06)

B@rtounet · Le 22/04/2008, à 18:40

En montant tout simplement un webmail, ou bien un serveur imap, pour te connecter directement avec un client de messagerie imap

sylvain1970 · Le 22/04/2008, à 18:49

Merci de ta réponse.
Je ne comprends pas bien.
le serveur imap est installé sur le serveur et est opérationnel.
sur l'ordi sur lequel je souhaite récupérer les mails du serveur, je dois aussi installer un serveur imap pour récupérer les mails ?
Ou alors, sur quel PC dois-je installer un webmail, serveur ou ordi ?
(désolé, je me suis noyé en lisant beaucoup de doc sur le sujet, du coup c'est confus dans ma tête).
Merci.

Uggy · Le 22/04/2008, à 20:20

Si tes mails arrivent dans /home/user/Maildir... et que tu as installé un serveur POP(s) ou IMAP(s) alors il suffit de configurer ton client (par exemple thunderbird) pour aller chercher les mails sur ton serveur...

sylvain1970 · Le 23/04/2008, à 07:57

Bonjour,
çà marche sur le serveur (récup des mails avec thunderbird) mais pas sur l'autre ordi en réseau (connexion refusée).

Uggy · Le 23/04/2008, à 12:20

conf/logs serveur pop/imap

sylvain1970 · Le 23/04/2008, à 12:59

Bonjour,
sur le serveur, c'est fonctionnel (postfix+imap : ce tuto) :
si je lance thunderbird avec mon compte, je récupère les mails de mon compte (5 comptes utilisateurs sur le serveur).

sur l'ordi sur lequel je souhaiterai récupérer les mails, thunderbird refuse de se connecter au serveur. je ne fais que lancer thunderbird (pas d'autres installations concernant la lecture des mails). Je dois peut-être installer quelque chose sur l'ordi pour récupérer les mails sur le serveur mais je ne sais pas quoi.

je peux, à partir de l'ordi me connecter sur le serveur en ssh (c'est fonctionnel). Le serveur et l'ordi sont sur un réseau local.
voilà où j'en suis.

je posterai postconf -n ce soir si tu en a besoin (je ne suis pas chez moi à cette heure-ci).
Merci.

Dernière modification par sylvain1970 (Le 23/04/2008, à 13:01)

Uggy · Le 23/04/2008, à 14:29

Oublie le "postconf -n" car tu as un probleme POP/IMAP et non pas SMTP.

Que donne un:
"sudo netstat -alpen --inet" ?

Encore une fois:
Quelle est la conf de ton serveur IMAP/POP ?
Quels sont les logs générés par ton serveur POP/IMAP?

sylvain1970 · Le 23/04/2008, à 15:26

Merci de ta réponse.

Quelle est la conf de ton serveur IMAP/POP ?

je n'ai pas de conf imap (Il n'y a rien à configurer pour courier-imap. Il faut juste s'assurer qu'il est lancé - d'après le tuto d'installation).

Pour procmail, c'est le fichier du tuto (nomdedomaine modifié) auquel j'ai rajouté l'option (que l'on m'a donnée sur le forum) :
DROPPRIVS=yes
afin que les mails aient les droits de l'utilisateur.

Quels sont les logs générés par ton serveur POP/IMAP?

aucune indication de connexion de l'ordi sur le serveur dans /var/log/mail.log (c'est bien là qu'il faut regarder ?).

pour netstat -alpen --inet, je le mets ce soir.
Merci.

sylvain1970 · Le 23/04/2008, à 20:35

sudo netstat -alpen --inet :

Connexions Internet actives (serveurs et établies)
Proto Recv-Q Send-Q Adresse locale Adresse distante Etat Utilisatr Inode PID/Program name
tcp 0 0 0.0.0.0:44839 0.0.0.0:* LISTEN 0 21691 6018/FahCore_a1.exe
tcp 0 0 0.0.0.0:55207 0.0.0.0:* LISTEN 0 21685 6019/FahCore_a1.exe
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 112 17575 5453/mysqld
tcp 0 0 127.0.0.1:143 0.0.0.0:* LISTEN 0 18177 5908/couriertcpd
tcp 0 0 127.0.0.1:783 0.0.0.0:* LISTEN 0 17799 5521/spamd.pid
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 19155 6466/apache2
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 17413 5372/cupsd
tcp 0 0 0.0.0.0:38680 0.0.0.0:* LISTEN 0 21694 6017/FahCore_a1.exe
tcp 0 0 0.0.0.0:25 0.0.0.0:* LISTEN 0 18348 6020/master
tcp 0 0 0.0.0.0:45407 0.0.0.0:* LISTEN 0 21688 6016/FahCore_a1.exe
tcp 232600 0 127.0.1.1:43857 127.0.1.1:55207 ESTABLISHED0 21697 6016/FahCore_a1.exe
tcp 0 232600 127.0.1.1:55207 127.0.1.1:43857 ESTABLISHED0 21702 6019/FahCore_a1.exe
tcp 0 0 192.168.0.2:36143 63.245.213.32:443 TIME_WAIT 0 0 -
tcp 0 0 127.0.1.1:45407 127.0.1.1:60907 ESTABLISHED0 21703 6016/FahCore_a1.exe
tcp 0 0 192.168.0.2:42012 213.95.41.13:80 ESTABLISHED1000 81721 11307/firefox-bin
tcp 0 0 192.168.0.2:50112 91.189.88.197:80 ESTABLISHED0 77065 10927/wget
tcp 0 0 127.0.1.1:56700 127.0.1.1:38680 ESTABLISHED0 21699 6018/FahCore_a1.exe
tcp 0 0 127.0.1.1:38680 127.0.1.1:56700 ESTABLISHED0 21704 6017/FahCore_a1.exe
tcp 0 0 192.168.0.2:42018 213.95.41.13:80 ESTABLISHED1000 81744 11307/firefox-bin
tcp 0 0 192.168.0.2:36144 63.245.213.32:443 TIME_WAIT 0 0 -
tcp 0 0 192.168.0.2:42017 213.95.41.13:80 ESTABLISHED1000 81743 11307/firefox-bin
tcp 0 0 127.0.1.1:44839 127.0.1.1:49266 ESTABLISHED0 21701 6018/FahCore_a1.exe
tcp 0 0 192.168.0.2:42014 213.95.41.13:80 ESTABLISHED1000 81723 11307/firefox-bin
tcp 0 0 127.0.1.1:49266 127.0.1.1:44839 ESTABLISHED0 21700 6019/FahCore_a1.exe
tcp 0 0 127.0.1.1:60907 127.0.1.1:45407 ESTABLISHED0 21698 6017/FahCore_a1.exe
udp 0 0 0.0.0.0:32770 0.0.0.0:* 106 17344 5320/avahi-daemon:
udp 0 0 0.0.0.0:68 0.0.0.0:* 100 14512 4417/dhclient3
udp 0 0 0.0.0.0:5353 0.0.0.0:* 106 17343 5320/avahi-daemon:
udp 0 0 192.168.0.2:123 0.0.0.0:* 0 19081 6390/ntpd
udp 0 0 127.0.0.1:123 0.0.0.0:* 0 19080 6390/ntpd
udp 0 0 0.0.0.0:123 0.0.0.0:* 0 19075 6390/ntpd
raw 0 0 0.0.0.0:6 0.0.0.0:* 7 0 20507 6592/portsentry
raw 0 0 0.0.0.0:17 0.0.0.0:* 7 0 21559 6596/portsentry

Merci.

Uggy · Le 24/04/2008, à 00:16

sylvain1970 a écrit :

tcp 0 0 127.0.0.1:143 0.0.0.0:* LISTEN 0 18177 5908/couriertcpd

Le démon n'ecoute que sur l'interface localhost.
Il faut faire écouter le démon sur ton IP 192.168.0.2 (ou sur toutes les interfaces 0.0.0.0) pour qu'on puisse y accéder depuis une autre machine.

Ca ce fait probablement par une option de la conf.
(je ne connais pas courier et comme il n'y a pas de conf dans le post..)

Dernière modification par Uggy (Le 24/04/2008, à 00:19)

sylvain1970 · Le 24/04/2008, à 09:35

Bonjour,
merci de ton aide.
je n'ai pas mis de fichier de conf tout simplement parce que je ne savais pas où ni qui chercher.
J'ai donc cherché tous les fichiers courier et dans /etc/courier/imapd, il y a un paramètre ADDRESS=127.0.0.1.
A la lecture de ce fichier, j'ai commenté cette ligne et modifié :
PORT=143 en
PORT=127.0.0.1.143,192.168.0.2.143 (si je mets 0.0.0.0.143, il ne fonctionne plus, pareil si je mets 0.0.0.0 en adresse).
Enfin, maintenant il écoute sur 127.0.0.1 et 192.168.0.2 :

tcp 0 0 127.0.0.1:143 0.0.0.0:* LISTEN 0 169665 22650/couriertcpd
tcp 0 0 192.168.0.2:143 0.0.0.0:* LISTEN 0 169664 22650/couriertcpd

Quel est l'intérêt du local ?

Je verrai ce soir pour la récup de mail sur l'autre ordi.
Merci.

PS : le fichier en question :

##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="@example.com"

##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

Uggy · Le 24/04/2008, à 11:05

Quelle surprise.. il y a un fichier de conf finalement...

Vu le fichier j'aurais envire de dire que "ADDRESS=0" permettrait d'ecouter sur ta vraie IP.
sinon met que PORT=192.168.0.2.143
(sans le 127.0.0.1)

sylvain1970 · Le 24/04/2008, à 11:13

Grâce à toi, je l'ai trouvé (le fichier de conf).
J'ai essayé ADDRESS=0, mais çà ne fonctionne pas (pas de courrier avec netstat.....).
J'ai mis que 192.168.0.2.143.
Merci.

sylvain1970 · Le 24/04/2008, à 18:06

Merci Uggy, çà marche !

Uggy · Le 24/04/2008, à 19:09

Cool

Ubuntu-fr

Navigation

Liens de recherche

Annonce

#1 Le 22/04/2008, à 17:06

[résolu] serveur mail : récup des mails sur un autre ordi

#2 Le 22/04/2008, à 18:40

Re : [résolu] serveur mail : récup des mails sur un autre ordi

#3 Le 22/04/2008, à 18:49

Re : [résolu] serveur mail : récup des mails sur un autre ordi

#4 Le 22/04/2008, à 20:20

Re : [résolu] serveur mail : récup des mails sur un autre ordi

#5 Le 23/04/2008, à 07:57

Re : [résolu] serveur mail : récup des mails sur un autre ordi

#6 Le 23/04/2008, à 12:20

Re : [résolu] serveur mail : récup des mails sur un autre ordi

#7 Le 23/04/2008, à 12:59

Re : [résolu] serveur mail : récup des mails sur un autre ordi

#8 Le 23/04/2008, à 14:29

Re : [résolu] serveur mail : récup des mails sur un autre ordi

#9 Le 23/04/2008, à 15:26

Re : [résolu] serveur mail : récup des mails sur un autre ordi

#10 Le 23/04/2008, à 20:35

Re : [résolu] serveur mail : récup des mails sur un autre ordi

#11 Le 24/04/2008, à 00:16

Re : [résolu] serveur mail : récup des mails sur un autre ordi

#12 Le 24/04/2008, à 09:35

Re : [résolu] serveur mail : récup des mails sur un autre ordi

#13 Le 24/04/2008, à 11:05

Re : [résolu] serveur mail : récup des mails sur un autre ordi

#14 Le 24/04/2008, à 11:13

Re : [résolu] serveur mail : récup des mails sur un autre ordi

#15 Le 24/04/2008, à 18:06

Re : [résolu] serveur mail : récup des mails sur un autre ordi

#16 Le 24/04/2008, à 19:09

Re : [résolu] serveur mail : récup des mails sur un autre ordi

Pied de page des forums