OVH Community, votre nouvel espace communautaire.

Multiple Redirections via un Alias Postfix


jhonbauwens
12/01/2015, 14h16
J'aimerai savoir à quoi servent ces lignes qu'on commente. Elles sont peut-être appelées ailleurs!

Digi12
12/01/2015, 10h29
Bonjour,
Etant moi aussi en R3 j'avais exactement le même problème.
Cette solution fonctionne à merveille.
Merci à vous tous

jicao
10/01/2015, 17h31
J'ai trouvé ça sur la mailing liste (exactement le même problème que nous, je suppose que c'est pareil pour tout le monde sur la R3...)
La piste de Gregory et du no_address_mappings semble la bonne, voici ce que j'ai fais dans le master.cf de postfix (/etc/postfix/master.cf) et qui semble fonctionner (nota : les # pour commenter les lignes et revenir vite en arrière) :

...
-o smtpd_sender_restrictions=
-o smtpd_recipient_restrictions=permit_mynetworks,rej ect
# -o receive_override_options=no_address_mappings
-o smtpd_data_restrictions=reject_unauth_pipelining
-o smtpd_end_of_data_restrictions=
-o smtpd_restriction_classes=
-o mynetworks=127.0.0.0/8
-o smtpd_error_sleep_time=0
-o smtpd_soft_error_limit=1001
-o smtpd_hard_error_limit=1000
-o smtpd_client_connection_count_limit=0
-o smtpd_client_connection_rate_limit=0
# -o receive_override_options=no_header_body_checks,no_ unknown_recipient_checks,no_milters,no_address_map pings
-o receive_override_options=no_header_body_checks,no_ unknown_recipient_checks,no_milters
-o local_header_rewrite_clients=
...

Relancer postfix ensuite bien entendu

Jacques Vernay

----[ Le 09/10/2013 11:15 - Gregory Fardel a écrit ]----
Salut,

Première réaction : j'ai envie de dire est-ce qu'on peut ajouter une adresse
externe comme alias ?

Ou alors, serait-ce un problème de address mapping avec postfix (j'ai déjà
eu ce soucis, il s'agit du paramètre no_address_mapping dans master.cf).
J'avais quelques soucis avec le filtre amavis / spam assassin, en supprimant
le no_address_mapping, ça avait résolu mon souci de "user unknown".

Redis nous si tu as trouvé quelque chose de ce côté-là.

Amicalement,


Gregory
-----Message d'origine-----
De : Florent Portais [mailto:florent@pixiblack.com]
Envoyé : mercredi 9 octobre 2013 10:54
À : release@ml.ovh.net
Objet : [release] [R3] email alias : Diagnostic-Code: x-unix; user unknown

Bonjour,

J'ai un soucis d'e.mail sur mon KS sur R3 à jour.
Lorsque je tente d'envoyer un mail depuis mon domaine 1 (theblacklines.com)
vers une boite mail alias
d'un autre domaine sur le même serveur (cet alias renvoi vers une boite
gmail) le mail ne passe pas.


eporting-MTA: dns; ns1.theblacklines.com
X-Postfix-Queue-ID: 640D011B14E
X-Postfix-Sender: rfc822; florent@theblacklines.com
Arrival-Date: Wed, 9 Oct 2013 10:47:25 +0200 (CEST)

Final-Recipient: rfc822; contact@doyleairence.com
Original-Recipient: rfc822;contact@doyleairence.com
Action: failed
Status: 5.1.1
Diagnostic-Code: x-unix; user unknown

Bizarre.



---------------------------------------------------------------------
Desinscription: envoyez un message a: release-unsubscribe@ml.ovh.net
Pour obtenir de l'aide, ecrivez a: release-help@ml.ovh.net


---------------------------------------------------------------------
Desinscription: envoyez un message a: release-unsubscribe@ml.ovh.net
Pour obtenir de l'aide, ecrivez a: release-help@ml.ovh.net
Je suis sur mon iphone, désolé pour la forme de cette réponse
Je ne pourrai testé ça que lundi au bureau donc tiens moi au courant Jhon

jhonbauwens
10/01/2015, 17h03
Si c'est exactement ce que j'ai indiqué @jicao )

jicao
09/01/2015, 16h20
Salut,

Jhon es-tu sur que ce problème n'est pas juste lié aux mails internes a ton serveur ?
est-ce qu'un mail envoyé de hotmail ou gmail par exemple ne fonctionne-t-il pas ?
(Moi je viens de remarquer que c'était juste mes boites internes qui ne pouvaient pas communiquer...)

Bonne soirée.

Nowwhat
09/01/2015, 15h36
Citation Envoyé par jhonbauwens
@nowwhat

Sauf que j'ai pas la meme chose dans dovecot /etc/dovecot/dovecot-sql.conf.ext

Code:
password_query = SELECT username as user, password, concat('/var/mail/',domain,'/',local_part,'/') as userdb_home, 500 as userdb_uid, 101 as userdb_gid, CONCAT('dirsize:storage=', ROUND(quota/1024)) AS userdb_quota_rule from mailbox where username='%n@%d' and domain="%d" and active=1
Ca, j'appelle ça un bon début !

T'as le "query" :
SELECT username as user, password, concat('/var/mail/',domain,'/',local_part,'/') as userdb_home, 500 as userdb_uid, 101 as userdb_gid, CONCAT('dirsize:storage=', ROUND(quota/1024)) AS userdb_quota_rule from mailbox where username='%n@%d' and domain="%d" and active=1

T'as la posibilité de basculer postfix en mode debug - dovecot aussi https://www.google.fr/search?q=postf...Cssl&oq=&gs_l=
Histoire de vérifier ces variables:
%n
%d
Pour voir si la reqête est bien formé.

De l'autre coté, c'est possibile de bascule MySQL pour que les requetes sont loggé .... (Go Google pour les détails)
Pour voir si la reqête est bien formé.

Puis, t'as phpmyadmin pour que tu exécute cette requete manuellement,
Il suffit de rempacer les %n et %d (2 fois) avec des vrais valuers existantes.

jicao
09/01/2015, 12h57
Salut,

J'ai exactement le même problème que toi Jhon...

Tout le monde sur le net semble pointé /etc/dovecot/dovecot-sql.conf.ext, mais je n'ai aucune idée de quoi changé dans la conf de la Release 3...

Merci.

jhonbauwens
08/01/2015, 16h43
@nowwhat

Sauf que j'ai pas la meme chose dans dovecot /etc/dovecot/dovecot-sql.conf.ext

Code:
password_query = SELECT username as user, password, concat('/var/mail/',domain,'/',local_part,'/') as userdb_home, 500 as userdb_uid, 101 as userdb_gid, CONCAT('dirsize:storage=', ROUND(quota/1024)) AS userdb_quota_rule from mailbox where username='%n@%d' and domain="%d" and active=1

Nowwhat
08/01/2015, 15h38
Ah.
Jan 8 16:23:56 ns339929 dovecot: auth: sql(test@faver.be): Unknown user
C'est là ou nous chemins nous séparent.
Je n'utilise pas dovecot mais Courier ....
Il s'agit d'un erreur dans le paramétrage de Dovecot ....
Quoi faire ??

Google (!) dovecot: auth: sql( ): Unknown user => Bingo !!

Cherche sur cette page le premier occurrence de unknown user (utilise Ctrl-F + unknown user)
Tu trouve un soucis posté par :
No dovecot/imap in ps
Submitted by Michael on Sat, 04/12/2014 - 21:13
Quelques lignes plus tard t'as une solution.

jhonbauwens
08/01/2015, 15h23
Voici pour le feedback avec TAIL

Code:
Jan  8 16:23:56 ns339929 postfix/qmgr[4590]: AACBE101079: from=, size=4285, nrcpt=1 (queue active)
Jan  8 16:23:56 ns339929 amavis[21941]: (21941-15) Passed CLEAN {RelayedInbound}, [109.128.83.149]:58530 [109.128.83.149]  -> , Message-ID: , mail_id: bpoe54o-tGfh, Hits: -1.892, size: 3678, queued_as: AACBE101079, dkim_sd=default:faver.be, 659 ms
Jan  8 16:23:56 ns339929 postfix/smtp[4742]: DF368101078: to=, relay=127.0.0.1[127.0.0.1]:10024, delay=0.91, delays=0.23/0.02/0/0.66, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as AACBE101079)
Jan  8 16:23:56 ns339929 postfix/qmgr[4590]: DF368101078: removed
Jan  8 16:23:56 ns339929 dovecot: auth: sql(test@faver.be): Unknown user
Jan  8 16:23:56 ns339929 postfix/pipe[4746]: AACBE101079: to=, relay=dovecot, delay=0.12, delays=0.05/0.02/0/0.05, dsn=5.1.1, status=bounced (user unknown)

jhonbauwens
08/01/2015, 15h13
@nowwhat les mails envoyé à partir de l'extérieur du serveur arrivent bien sur les deux adresses emails!! Le problème de deamon: unknown user c'est quand on envoie un mail à partir d'un domaine existant sur le serveur !!

Le retour de postmap est niquel aussi:

Code:
[root@xxxxxxx ~]# postmap -q test@domain.be mysql:/etc/postfix/sql/mysql_virtual_alias_maps.cf
jhon@faver.be, fabien@faver.be

Nowwhat
08/01/2015, 13h19
Citation Envoyé par Nowwhat
Dè que j'ai un peu de temps, je paramètre un
/etc/postfix/sql/mysql_virtual_alias_maps.cf
moi même avec sa table.
Suis con.
J'ai déjà dans mon main.cf ceci:
virtual_alias_maps = proxy:mysql:/etc/postfix/mysql-virtual_forwardings.cf, proxy:mysql:/etc/postfix/mysql-virtual_email2email.cf
Prenons le premier:
Voici mon /etc/postfix/mysql-virtual_forwardings.cf:
user = mail
password = motdepasse
dbname = mail
hosts = 127.0.0.1
query = SELECT destination FROM forwardings WHERE source='%s'
J'ai modifié un mes mes tables (la table nommé "forwardings") le champs "destination" en:
un-mail-a-moi@un-domaine-a-moi.tld, un-autre-mail-a-moi@un-autre-domaine...hez-orange.tld
Puis je m'adresse un mail (venant d'un gmail à moi) un mail vers le mail marqué dans "source" dans la table "forwardings".
Surprise.
J'ai reçu ce mail sur
un-mail-a-moi@un-domaine-a-moi.tld
et sur
un-autre-mail-a-moi@un-autre-domaine-a-moi-chez-orange.tld

Donc, ça marche !!

- - - Mise à jour - - -

Citation Envoyé par jhonbauwens
...
Code:
postmap: fatal: open database /etc/postfix/sql/mysql_virtual_alias_maps.cf.db: No such file or directory
Ma faute.
C'est
postmap -q test@domain.be mysql:/etc/postfix/sql/mysql_virtual_alias_maps.cf

jhonbauwens
08/01/2015, 12h44
@nowwhat

Ta requête SQL renvoie jhon@faver.be, fabien@faver.be

Ce qui est totalement logique.

Je teste le master.cf tout de suite et te reviens avec les logs!

Pour la commande postmap:

Code:
postmap: fatal: open database /etc/postfix/sql/mysql_virtual_alias_maps.cf.db: No such file or directory

Nowwhat
08/01/2015, 11h40
Citation Envoyé par jhonbauwens
@anyvie il est à 1 depuis le début!
ne colle pas avec
address goto domain created modified active
test@domain.be jhon@domain.be, fabien@domain.be domain.be 2015-01-07 02:20:10 2015-01-07 0
'active' est sur '0'.

Si-dessus, c'est un extrait de la table "alias" ?

T’as testé la requête MySQL ??

Ouvre phpmyadmin (utilise comme login "mailadmin" et le mot de passe.
Sélectionne la base "mail" si ce n'est pas déjà fait.
Exécute cette requête SQL:
SELECT goto FROM alias WHERE address='test@domain.be' AND active = '1'
Ça retourne quoi ?

Dè que j'ai un peu de temps, je paramètre un
/etc/postfix/sql/mysql_virtual_alias_maps.cf
moi même avec sa table.

Histoire de voir comment postfix va réagir quand il reçoit une réponse comme:
un-mail@domaine.tld, un-autre-mail@autre-domaine.tld
Autre test:
Utilise la commande 'postmap'.
Par exemple:
Code:
postmap -q test@domain.be mysql:/etc/postfix/sql/mysql_virtual_alias_maps.cf
Ça retourne quoi ?

édit.
Mieux encore.
Ouvre /etc/postfix/master.cf
Localise:
Code:
virtual   unix  -       n       n       -       -       virtual
Change le en
Code:
virtual   unix  -       n       n       -       -       virtual -v
Sauvegarde.
Puis
Code:
postfix reload
Lance un
Code:
tail -f /var/log/mail.log
(/var/log/mail.log est chez moi le log de postfix, peut être le chemin est ailluers chez toi).

Lance un mail venant de l'extérieur vers ton "test@domain.be"
Observe le log

jhonbauwens
08/01/2015, 11h23
@anyvie il est à 1 depuis le début!

anyvie
08/01/2015, 10h20
Dans ta BDD, active est à 0 :

address goto domain created modified active
test@domain.be jhon@domain.be, fabien@domain.be domain.be 2015-01-07 02:20:10 2015-01-07 0
Met le à 1 et ça devrait aller mieux.


EDIT pour réponse ci-dessous :
Dans ce que tu as collé au dessus (voir quote), il est à 0

jhonbauwens
07/01/2015, 12h15
@fritz2cat j'ai bien recu ton mail! Le problème vient donc des adresses locales! Les mails envoyés à partir d'une adresse existante sur le serveur!

@nowwhat ils sont tous écrit de la même manière à savoir:

Code:
user = mailadmin
password = ********
hosts = localhost
dbname = mail
query = SELECT goto FROM alias WHERE address='%s' AND active = '1'
C'est cool, on avance, merci les gars!

Nowwhat
07/01/2015, 07h41
Le doc http://www.postfix.org/virtual.5.html précise bien:

Code:
       /etc/postfix/main.cf:
           virtual_alias_maps = hash:/etc/postfix/virtual

       Note:  some  systems use dbm databases instead of hash.  See the output
       from "postconf -m" for available database types.

       /etc/postfix/virtual:
           virtual-alias.domain     anything (right-hand content does not matter)
           postmaster@virtual-alias.domain  postmaster
           user1@virtual-alias.domain       address1
           user2@virtual-alias.domain       address2, address3
Là ou ça devient intéressant est de savoir COMMENT ces fichiers de sélection ont été écrit:
Code:
/etc/postfix/sql/mysql_virtual_alias_maps.cf
/etc/postfix/sql/mysql_virtual_alias_domain_maps.cf
/etc/postfix/sql/mysql_virtual_alias_domain_catchall_maps.cf
/etc/postfix/sql/mysql_virtual_mailing.cf
Ces fichiers sont 'imposés' par le R3 ..... ( donc personne peut savoir ce qui se passe - sauf toi - sache que le plupart qui communiquent ici n'ont pas de R3 car trop de contraintes )

T'as pas plus des détails concernant ces fichiers ?

Exemple, QUI te dit que un résultat (multiple adresses mails, séparées par des virgules), est possible ? Peut être la requête dans un de ces fichiers ".cf" ne le permet pas (comme résultat) - ou, plus probable encore, ils envoient un résultat erroné donc postfix pleure ....

fritz2cat
07/01/2015, 06h35
Je t'ai envoyé un test est il a été accepté par ton serveur.
A=@ P=.
Jan 7 07:32:22 b1 postfix/smtp[18751]: 66304E0133: to=, relay=mailPfaverPbe[37.187.166.234]:25, delay=2.5, delays=0.41/0.02/1.7/0.41, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as 8B7721010E9)

jhonbauwens
07/01/2015, 01h20
@Newwhat

Voici dans la table alias la ligne de l'alias qui devrait fonctionné

Code:
address           	goto	                                                       domain	         created	                                modified	                       active
test@domain.be	jhon@domain.be, fabien@domain.be      domain.be	2015-01-07 02:20:10	2015-01-07 02:20:10	1

Mais toujours:

Code:
This is the mail system at host ns339929.ip-37-187-166.eu. 

I'm sorry to have to inform you that your message could not 
be delivered to one or more recipients. It's attached below. 

For further assistance, please send mail to postmaster. 

If you do so, please include this problem report. You can 
delete your own text from the attached returned message. 

The mail system 

: user unknown 
Go
Et l'attachement de deamon:

Code:
Reporting-MTA: dns; ns339929.ip-37-187-166.eu
X-Postfix-Queue-ID: 92FE310107D
X-Postfix-Sender: rfc822; jhon@domain.be
Arrival-Date: Wed,  7 Jan 2015 02:27:48 +0100 (CET)

Final-Recipient: rfc822; test@domain.be
Original-Recipient: rfc822;test@domain.be
Action: failed
Status: 5.1.1
Diagnostic-Code: x-unix; user unknown
Dans la mysql ca semble niquel, les deux emails de l'alias sont biens séparé par une virgule...

Merci !!

Nowwhat
03/01/2015, 16h50
J'ai cru comprendre que t'as bien du voir:
virtual_alias_maps = mysql:/etc/postfix/sql/mysql_virtual_alias_maps.cf, mysql:/etc/postfix/sql/mysql_virtual_alias_domain_maps.cf, mysql:/etc/postfix/sql/mysql_virtual_alias_domain_catchall_maps.cf, mysql:/etc/postfix/sql/mysql_virtual_mailing.cf
dans ton main.cf.
C'est ce "virtual_alias_maps" qui 'map les aliases'.
Ouvre :
/etc/postfix/sql/mysql_virtual_alias_maps.cf
/etc/postfix/sql/mysql_virtual_alias_domain_maps.cf
/etc/postfix/sql/mysql_virtual_alias_domain_catchall_maps.cf
/etc/postfix/sql/mysql_virtual_mailing.cf
qui te donne exactement la base et table dans laquelle tes alaises sont stocké.
Après; un coup de phpmyadmin pour voir a de plus près.

Sache que rien est vraiment standard, car il s'agit d'un R3.

jhonbauwens
03/01/2015, 13h30
UP

Merciii

jhonbauwens
16/12/2014, 16h55
@Nowwhat

J'ai retiré les premières lignes de commentaires car trop de caractères

Code:
# LOCAL PATHNAME INFORMATION
#
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
#
queue_directory = /var/spool/postfix

# The command_directory parameter specifies the location of all
# postXXX commands.
#
command_directory = /usr/sbin

# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
#
daemon_directory = /usr/libexec/postfix

# The data_directory parameter specifies the location of Postfix-writable
# data files (caches, random numbers). This directory must be owned
# by the mail_owner account (see below).
#
data_directory = /var/lib/postfix

# QUEUE AND PROCESS OWNERSHIP
#
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes.  Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM.  In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
#
mail_owner = postfix

# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#
#default_privs = nobody

# INTERNET HOST AND DOMAIN NAMES
# 
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#
myhostname = ns339929.ip-37-187-166.eu 

# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#
mydomain = localdomain

# SENDING MAIL
# 
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites.  If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# user@that.users.mailhost.
#
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#
#myorigin = $myhostname
myorigin = $mydomain

# RECEIVING MAIL

# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on.  By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
#
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
#
# Note: you need to stop/start Postfix when this parameter changes.
#
inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost
#inet_interfaces = localhost

# Enable IPv4, and IPv6 if supported
inet_protocols = all

# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
#
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4

# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
#
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
#
# The default is $myhostname + localhost.$mydomain.  On a mail domain
# gateway, you should also include $mydomain.
#
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
#
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
#
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
#
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
#
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#
mydestination = localhost.$mydomain, localhost, localhost.localdomain 
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
#	mail.$mydomain, www.$mydomain, ftp.$mydomain

# REJECTING MAIL FOR UNKNOWN LOCAL USERS
#
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
#
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
#
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
#
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
#
# - You define $mydestination domain recipients in files other than
#   /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
#   For example, you define $mydestination domain recipients in    
#   the $virtual_mailbox_maps files.
#
# - You redefine the local delivery agent in master.cf.
#
# - You redefine the "local_transport" setting in main.cf.
#
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
#   feature of the Postfix local delivery agent (see local(8)).
#
# Details are described in the LOCAL_RECIPIENT_README file.
#
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
#
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a user@domain.tld address.
# 
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
local_recipient_maps = unix:passwd.byname

# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
#
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
#
unknown_local_recipient_reject_code = 550

# TRUST AND RELAY CONTROL

# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
#
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix.  See the smtpd_recipient_restrictions parameter
# in postconf(5).
#
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
#
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# 
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network.  Instead, specify an explicit
# mynetworks list by hand, as described below.
#  
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
# 
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host

# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
#
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
#
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#
mynetworks = 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table

# The relay_domains parameter restricts what destinations this system will
# relay mail to.  See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
#
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
#   subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# 
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# 
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace.  Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
#
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#
#relay_domains = list.localhost, list.localhost.localdomain
#transport_maps = hash:/etc/postfix/transport
#mailman_destination_recipient_limit = 1
# INTERNET OR INTRANET

# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
#
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
#
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
#
# If you're connected via UUCP, see also the default_transport parameter.
#
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]

# REJECTING UNKNOWN RELAY USERS
#
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
#
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
#
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a user@domain.tld address.
# 
#relay_recipient_maps = hash:/etc/postfix/relay_recipients

# INPUT RATE CONTROL
#
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# 
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# 
# Specify 0 to disable the feature. Valid delays are 0..10.
# 
#in_flow_delay = 1s

# ADDRESS REWRITING
#
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.

# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
#
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.

# "USER HAS MOVED" BOUNCE MESSAGES
#
# See the discussion in the ADDRESS_REWRITING_README document.

# TRANSPORT MAP
#
# See the discussion in the ADDRESS_REWRITING_README document.

# ALIAS DATABASE
#
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
#
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# 
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
#
# It will take a minute or so before changes become visible.  Use
# "postfix reload" to eliminate the delay.
#
alias_maps = hash:/etc/aliases, hash:/etc/mailman/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases

# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi".  This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#
alias_database = hash:/etc/aliases, hash:/etc/mailman/aliases

#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
# ADDRESS EXTENSIONS (e.g., user+foo)
#
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#
recipient_delimiter = +

# DELIVERY TO MAILBOX
#
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user.  Specify
# "Maildir/" for qmail-style delivery (the / is required).
#
#home_mailbox = Mailbox
#home_mailbox = Maildir/
 
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#
#mail_spool_directory = /var/mail
#mail_spool_directory = /var/spool/mail

# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception:  delivery for root is done as $default_user.
#
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
#
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
#
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
#
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#
#mailbox_command = /usr/lib/dovecot/deliver -n -m "$EXTENSION"
#mailbox_command = /some/where/procmail -a "$EXTENSION"

# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
#
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf.  The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for    
# non-UNIX accounts with "User unknown in local recipient table".
#
#mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp

# If using the cyrus-imapd IMAP server deliver local mail to the IMAP
# server using LMTP (Local Mail Transport Protocol), this is prefered
# over the older cyrus deliver program by setting the
# mailbox_transport as below:
#
# mailbox_transport = lmtp:unix:/var/lib/imap/socket/lmtp
#
# The efficiency of LMTP delivery for cyrus-imapd can be enhanced via
# these settings.
#
# local_destination_recipient_limit = 300
# local_destination_concurrency_limit = 5
#
# Of course you should adjust these settings as appropriate for the
# capacity of the hardware you are using. The recipient limit setting
# can be used to take advantage of the single instance message store
# capability of Cyrus. The concurrency limit can be used to control
# how many simultaneous LMTP sessions will be permitted to the Cyrus
# message store. 
#
# To use the old cyrus deliver program you have to set:
#mailbox_transport = local

# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
#
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf.  The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for    
# non-UNIX accounts with "User unknown in local recipient table".
#
#fallback_transport = lmtp:unix:/var/lib/imap/socket/lmtp
#fallback_transport =

# The luser_relay parameter specifies an optional destination address
# for unknown recipients.  By default, mail for unknown@$mydestination,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
#
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
#
# luser_relay works only for the default Postfix local delivery agent.
#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for    
# non-UNIX accounts with "User unknown in local recipient table".
#
#luser_relay = $user@other.host
#luser_relay = $local@other.host
#luser_relay = admin+$local
  
# JUNK MAIL CONTROLS
# 
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.

# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
#
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
#
# For details, see "man header_checks".
#
#header_checks = regexp:/etc/postfix/header_checks

# FAST ETRN SERVICE
#
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
# 
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
# 
#fast_flush_domains = $relay_domains

# SHOW SOFTWARE VERSION OR NOT
#
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
#
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)

# PARALLEL DELIVERY TO THE SAME DESTINATION
#
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# 
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter.  The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.

#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20

# DEBUGGING CONTROL
#
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
#
debug_peer_level = 2

# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain

# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
#
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
#
debugger_command =
	 PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
	 ddd $daemon_directory/$process_name $process_id & sleep 5

# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
#
# debugger_command =
#	PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
#	echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
#	>$config_directory/$process_name.$process_id.log & sleep 5
#
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# " where  uniquely matches one of the detached
# sessions (from "screen -list").
#
# debugger_command =
#	PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
#	-dmS $process_name gdb $daemon_directory/$process_name
#	$process_id & sleep 1

# INSTALL-TIME CONFIGURATION INFORMATION
#
# The following parameters are used when installing a new Postfix version.
# 
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
# 
sendmail_path = /usr/sbin/sendmail.postfix

# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
#
newaliases_path = /usr/bin/newaliases.postfix

# mailq_path: The full pathname of the Postfix mailq command.  This
# is the Sendmail-compatible mail queue listing command.
# 
mailq_path = /usr/bin/mailq.postfix

# setgid_group: The group for mail submission and queue management
# commands.  This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
#
setgid_group = postdrop

# html_directory: The location of the Postfix HTML documentation.
#
html_directory = no

# manpage_directory: The location of the Postfix on-line manual pages.
#
manpage_directory = /usr/share/man

# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
#
sample_directory = /usr/share/doc/postfix-2.6.6/samples

# readme_directory: The location of the Postfix README files.
#
readme_directory = /usr/share/doc/postfix-2.6.6/README_FILES

#smtpd_sasl_type = dovecot
#smtpd_sasl_auth_enable = yes
#smtpd_sasl_path = /var/spool/postfix/private/auth
#smtpd_recipient_restrictions=permit_sasl_authenticated, permit_mynetworks, check_relay_domains
smtpd_recipient_restrictions=check_recipient_access mysql:/etc/postfix/sql/mysql_amavis_in.cf, permit_mynetworks, reject_unauth_destination 
external_submission_restrictions=check_recipient_access mysql:/etc/postfix/sql/mysql_amavis_in.cf, permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination

virtual_mailbox_domains = mysql:/etc/postfix/sql/mysql_virtual_domains_maps.cf
virtual_mailbox_maps = mysql:/etc/postfix/sql/mysql_virtual_mailbox_maps.cf, mysql:/etc/postfix/sql/mysql_virtual_alias_domain_mailbox_maps.cf
virtual_alias_maps = mysql:/etc/postfix/sql/mysql_virtual_alias_maps.cf, mysql:/etc/postfix/sql/mysql_virtual_alias_domain_maps.cf, mysql:/etc/postfix/sql/mysql_virtual_alias_domain_catchall_maps.cf, mysql:/etc/postfix/sql/mysql_virtual_mailing.cf
virtual_mailbox_base = /var/mail/vhosts
virtual_uid_maps = static:500
virtual_gid_maps = static:101
virtual_transport = dovecot

virtual_create_maildirsize = yes
virtual_mailbox_extended = yes
virtual_mailbox_limit_maps = mysql:/etc/postfix/sql/mysql_virtual_mailbox_limit_maps.cf
virtual_mailbox_limit_override = yes
virtual_maildir_limit_message = Sorry, the user's maildir has overdrawn his diskspace quota, please try again later.
virtual_overquota_bounce = yes
transport_maps = hash:/etc/postfix/transport
#
# translate sender root to postmaster@ns339929.ip-37-187-166.eu
#
sender_canonical_maps=hash:/etc/postfix/sender_canonical

#
#  multiple recipients (to dovecot) in one mail won't work if not activated!
#
dovecot_destination_recipient_limit = 1

#
# OpenDKIM
#
smtpd_milters = inet:localhost:8891
non_smtpd_milters = inet:localhost:8891
milter_default_action = accept

#
# TLS
#
smtpd_tls_security_level = may
smtpd_tls_key_file = /etc/pki/tls/private/localhost.key
smtpd_tls_cert_file = /etc/pki/tls/certs/localhost.crt
smtpd_tls_loglevel = 1
smtpd_tls_session_cache_timeout = 3600s
smtpd_tls_session_cache_database = btree:/var/lib/postfix/smtpd_tls_cache.db
smtpd_tls_auth_only = yes
tls_random_source = dev:/dev/urandom

#
# dovecot
#
mailbox_command = /usr/libexec/dovecot/deliver

bbr18
16/12/2014, 14h36
jette un oeil sur ce fichier :
/home/ovh/www/postfixadmin/config.inc.php

Nowwhat
16/12/2014, 13h44
De mémoire, si le fichier
/etc/aliases
ou
/etc/postfix/aliases
existe, postfix l'utilise.

Pense à ceci:
Après avoir éditer ce fichier, il faut régénér la base 'aliases'.
postfix n'utilise pas le fichier texte /etc/aliases (et/ou /etc/postfix/aliases) mais un fichier binaire généré à partir de ce fichier texte.

Je t'invite à lire le manual.
Exécute
man aliases
et tout sera plus clair.

Après modif de /etc/aliases, il faut exécuter la commande
newaliases
pour que les changements sont prioses en compte.

PS: il me semble que le R3, dans tout son splendeur, utilise autre chose à coté de /etc/aliases, il stocke ces "aliases, forwarders, etc" dans une base des données. C'est un des ce foutu avantages dès qu'on paramétre un OS à partir d'un interface "graphique" : il faut tout apprendre DEUX fois, chercher dans des endroit le plus fou possible, faire des tour de pas-pas dès que tu souhaite un paramétrage un peu plus que 'normal'.
Dans ce cas, une indice doit être trouvé dans /etc/postfix/main.cf

Post ton
/etc/postfix/main.cf
ici stp.

jhonbauwens
16/12/2014, 12h20
Hello @Nowwhat,

J'ai deja cherché sur google et j'ai déja essayé avec les virgules mais rien n'y fait... Toujours

Code:
The mail system 

: user unknown
J'ai également lancé la commande:

postconf | grep 'alias'

Mais pas moyen de mettre la main sur ce fichier alias... Pas moyen de trouver ou il fait ses redirection.

J'ai même essayé un

Code:
grep -r "test@monmail.be" /etc

Nowwhat
12/12/2014, 00h53
Citation Envoyé par jhonbauwens
.....
Quelqu'un connait-il ce bug? En tout cas, pas google...
Je pense que j'ai trouvé le bug.
T'as pas installé le bon google, il faut prendre le vrai, pas ce foutu trojan.

Il est ici https://www.google.fr (ou com, pour plus de réalisme encore)

T'as testé avec ceci: Google => postfix alias multiple recipients
Le premier lien pourrait faire l'affaire.

Pour trouver ce fichier 'alias', je te propose
postconf | grep 'alias'


Attention, postfix est bien documenté, mais sache que tu utilise un 'système' de la série Rx.
Ils ont cette habitude de:
A) zéro doc - donc Google ne sais pas ce que c'est. T'as compris: zéro aide. (pour cette raison, le Rx est réservé aux experts ..... [ et eux, ils ont certainement pas envie de perdre leur temps avec un OS 'inexistant'])
Ceci est un bon exemple:
Citation Envoyé par jhonbauwens
@fritz2cat,
Il n'y a rien de bien intéressant dans /etc/alias. En tout cas rien lié aux redirections mails. Je pense que c'est ailleurs, mais je ne trouve plus le fichier de config des alias !
Il y a la façon 'normal' = utiliser ce fichier "alias".
Soit, plus poussé, postfix utilise la methode virtual, donc tout est socké dans une base MySQL (ouvre ton /etc/postfix/main.cf pour lus des détails).
Soit: ailleurs encore - les secrets de Rx sont profondes.

B) Disparaitre au bout de X temps - laissent leur utilisateurs dans un état .... disons: choquant (voir le fin de R2, ça fait qq semaines)

jhonbauwens
11/12/2014, 20h44
@fritz2cat,

Il n'y a rien de bien intéressant dans /etc/alias. En tout cas rien lié aux redirections mails. Je pense que c'est ailleurs, mais je ne trouve plus le fichier de config des alias !

fritz2cat
11/12/2014, 15h12
Montre la ligne de ton fichier /etc/alias, en masquant juste assez pour que les bots ne collectent pas les adresses e-mails dans des spam lists.

jhonbauwens
11/12/2014, 12h35
Up

jhonbauwens
04/12/2014, 12h01
Ola,

J'ai un petit soucis sur ma release 3 et je ne trouve pas la solution sur google.

En fait quand je créé un alias de boite mail pour forwarder vers mon mail principal, tout se passe bien. Mais une fois que je veux forwarder mon alias vers plus d'une boite mail, je reçois un message de deamon comme si la boite alias n'existait pas:

Code:
This is the mail system at host nsxxxxx.ip-xx-xxx-xxx.eu. 

I'm sorry to have to inform you that your message could not 
be delivered to one or more recipients. It's attached below. 

For further assistance, please send mail to postmaster. 

If you do so, please include this problem report. You can 
delete your own text from the attached returned message. 

The mail system 

: user unknown
Quelqu'un connait-il ce bug? En tout cas, pas google...

Merciiii