[SOLVED] Bounce/Alias problem

Use this forum for all questions related to bounce management of OpenEMM

Moderator: moderator

sal
Posts: 3
Joined: Wed Sep 07, 2011 10:48 am

[SOLVED] Bounce/Alias problem

Post by sal »

Hello,

this is my first time setting up OpenEMM, but i have a little bit former experience with mail servers in general.

"Everything" is working (at least i think so) except the alias i created in /home/openemm/conf/bav/bav.conf-local. I created a bounce filter in OpenEMM ("Forward incoming emails" to my address on another server), which got ext_1@mailing.sub.domain.de as "sender address". If i send a mail to this address it will be successfully forwarded to my address.

Code: Select all

Sep  6 20:17:27 staging sm-mta[12378]: p86IHPSb012378: from=<privateaddress@fastmail.fm>, size=1438, class=0, nrcpts=1, msgid=<4E6663B3.70608@fastmail.fm>, proto=ESMTP, daemon=MTA-v4, relay=out4.smtp.messagingengine.com [66.111.4.28]
Sep  6 20:17:27 staging sm-mta[12378]: p86IHPSb012378: Milter add: header: X-AGNMailloop: from=<privateaddress@fastmail.fm>,rid=1,cid=1,fwd=sal@domain.de,to=<ext_1@mailing.sub.domain.de>
Sep  6 20:17:27 staging sm-mta[12378]: p86IHPSb012378: Milter add: header: X-AGNLoop: set
Sep  6 20:17:27 staging sendmail[12388]: p86IHR5K012388: from=openemm, size=1756, class=0, nrcpts=1, msgid=<4E6663B3.70608@fastmail.fm>, relay=openemm@localhost
Sep  6 20:17:27 staging sm-mta[12389]: p86IHRUb012389: from=<openemm@staging.sub.domain.de>, size=1876, class=0, nrcpts=1, msgid=<4E6663B3.70608@fastmail.fm>, proto=ESMTP, daemon=MTA-v4, relay=localhost [127.0.0.1]
Sep  6 20:17:27 staging sendmail[12388]: p86IHR5K012388: to=sal@domain.de, ctladdr=openemm (1001/1001), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=31756, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (p86IHRUb012389 Message accepted for delivery)
Sep  6 20:17:27 staging sm-mta[12381]: p86IHPSb012378: to=<ext_1@mailing.sub.domain.de>, delay=00:00:01, xdelay=00:00:00, mailer=procmail, pri=121438, relay=/home/openemm/conf/bav/bav.rc, dsn=2.0.0, stat=Sent
Sep  6 20:17:28 staging sm-mta[12392]: p86IHRUb012389: to=<sal@domain.de>, ctladdr=<openemm@staging.sub.domain.de> (1001/1001), delay=00:00:01, xdelay=00:00:01, mailer=esmtp, pri=121876, relay=mxa.expurgate.net. [195.190.135.25], dsn=2.0.0, stat=Sent (OK id=expurgator14/1315333047-00004F47-7158D2C5/0-0/0-14)
Now i want to use another address for sending emails and created a bav.conf-local as described in the installation manual.

Code: Select all

openemm@staging ~ $ cat conf/bav/bav.conf-local 
news@mailing.sub.domain.de alias:ext_1@mailing.sub.domain.de 
But if i try to send a mail to that adress it fails, telling me that the user is unknown:

Code: Select all

Sep  6 20:17:45 staging sm-mta[12393]: p86IHhG5012393: Milter: to=<news@mailing.sub.domain.de>, reject=550 5.1.1 No such user
Sep  6 20:17:45 staging sm-mta[12393]: p86IHhG5012393: from=<privateaddress@fastmail.fm>, size=1464, class=0, nrcpts=0, proto=ESMTP, daemon=MTA-v4, relay=out4.smtp.messagingengine.com [66.111.4.28]
I checked ~openemm/var/spool/bav/bav.conf, which seems to be ok.

Code: Select all

openemm@staging ~ $ cat ./var/spool/bav/bav.conf
@localhost      accept:rid=local
@staging.sub.domain.de     accept:rid=local
@newsletter.sub.domain.de  accept:rid=local
@staging.sub.domain.de     accept:rid=local
ext_1@mailing.sub.domain.de        accept:rid=1,cid=1,fwd=sal@domain.de
news@mailing.sub.domain.de alias:ext_1@mailing.sub.domain.de 

Since the "No such user"-Message is prefixed with Milter, i think that bav is not correctly handling the alias or did i configure something wrong ? Any help is appreciated.

Here comes the rest of my config. The server (Ubuntu 10.04 LTS 64bit) itself thinks it is staging.sub.domain.de.

Code: Select all

openemm@staging ~ $ cat /etc/hosts
# IPv4
127.0.0.1 localhost
74.36.111.12   staging.sub.domain.de staging
OpenEMM (Tomcat) is configured to use newsletter.sub.domain.de, e.g. "system.url=http://newsletter.sub.domain.de".
But for the mail-relay i use another domain which is not local for the sendmail daemon.

DNS Setup:

Code: Select all

staging.sub.domain.de. 600	IN	A	74.36.111.12
newsletter.sub.domain.de. 600 IN	A	74.36.111.12
mailing.sub.domain.de. 600	IN	A	74.36.111.12
mailing.sub.domain.de. 600	IN	MX	10 mailing.sub.domain.de.
Sendmail Setup:

Code: Select all

openemm@staging /etc/mail $ cat relay-domains 
mailing.sub.domain.de

Code: Select all

openemm@staging /etc/mail $ cat local-host-names 
localhost
staging.sub.domain.de
newsletter.sub.domain.de

Code: Select all

openemm@staging /etc/mail $ cat mailertable
mailing.sub.domain.de      procmail:/home/openemm/conf/bav/bav.rc
In sendmail.mc i added the following lines where they belong and changed the DEAMON_OPTIONS, so that the MTA also listens on the external interface (that works obviously):

Code: Select all

FEATURE(`mailertable', `hash -o /etc/mail/mailertable.db')dnl
MAILER(`procmail')dnl
INPUT_MAIL_FILTER(`bav', `S=unix:/home/openemm/var/run/bav.sock, F=T')dnl
I think that's all, that could influence the bounce management.
Thanks in advance for any hints and advice!
Stephan
Last edited by sal on Wed Sep 07, 2011 6:22 pm, edited 1 time in total.
sal
Posts: 3
Joined: Wed Sep 07, 2011 10:48 am

Re: Bounce/Alias problem

Post by sal »

Just solved the issue myself: I had a space at the end of the alias-definition, which is not really visible in the posting (only by c&p) !

Let's visualize it, just in case anybody else makes the same stupid little mistake:

Code: Select all

news@mailing.sub.domain.de alias:ext_1@mailing.sub.domain.deSPACE
Stephan
maschoff
Site Admin
Posts: 2596
Joined: Thu Aug 03, 2006 10:20 am
Location: Munich, Germany
Contact:

Re: [SOLVED] Bounce/Alias problem

Post by maschoff »

Thanks for posting the solution!
OpenEMM Maintainer
rootsys6
Posts: 1
Joined: Tue Feb 17, 2015 7:58 am

Re: [SOLVED] Bounce/Alias problem

Post by rootsys6 »

Our hunch: Your mail forwarding changes the sender address of the bounce which means that the bounce management can not detect that the incoming mail is a automatically generated bounce reply. If this is the case, we see two possibilities:
Post Reply