Page 1 of 1

Bounce Management again

Posted: Thu May 31, 2007 12:09 pm
by trax
Hello,

my bounce management does not work.
Not with the bav.rc, not from my maillog.

I did everything from the manual and everything suggested in this forum.
But without success.

Here is my configuration:

/etc/mail/mailertable

Code: Select all

mx.company.de    procmail:/home/openemm/conf/bav/bav.rc
/etc/mail/relay-domains

Code: Select all

mx.company.de
/etc/mail/local-host-names

Code: Select all

mx.company.de
openemm.company.de
/etc/mail/linux.mc

Code: Select all

divert(-1)

include(`/usr/share/sendmail/m4/cf.m4')
divert(0)dnl
VERSIONID(`@(#)Setup for SuSE Linux     8.12.11-0.5 (SuSE Linux) 2004/04/02')dnl

OSTYPE(`suse-linux')dnl

undefine(`confHOST_STATUS_DIRECTORY')dnl
FEATURE(`always_add_domain')dnl


DOMAIN(`generic')dnl

MAILER(`local')dnl
MAILER(`smtp')dnl
MAILER(`procmail')dnl
MAILER(`uucp')dnl
MAILER(`bsmtp')dnl
MAILER(`fido')dnl

LOCAL_CONFIG

INPUT_MAIL_FILTER(`bav',`S=unix:/home/openemm/var/run/bav.sock,F=T')dnl
bav.conf

Code: Select all

@mx.company.de     accept:rid=local
@openemm.company.de        accept:rid=local
ext_1@mx.company.de        accept:rid=1,cid=1
/var/log/maillog
-rw-r--r-- 1 root root 60742 May 31 00:46 maillog

Code: Select all

May 31 00:44:52 server sendmail[5385]: STARTTLS=client, relay=mail.wiesel.de., version=TLSv1/SSLv3, verify=FAIL, cipher=DHE-RSA-AES256-SHA, bits=256/256
May 31 00:44:52 server sendmail[5385]: 00000600000000001: to=<test@wiesel.de>, delay=00:00:53, xdelay=00:00:03, mailer=esmtp, pri=0, relay=mail.wiesel.de. [80.190.209.47], dsn=5.0.0, stat=Service unavailable
May 31 00:44:59 server sendmail[5385]: 00000600000000002: to=<usertest@usertest.de>, delay=00:01:00, xdelay=00:00:07, mailer=esmtp, pri=0, relay=mail.usertest.de. [217.110.29.107], dsn=2.0.0, stat=Sent (- Requested mail action okay, completed)
May 31 00:45:00 server sendmail[5385]: STARTTLS=client, relay=mxa.mail.widexs.nl., version=TLSv1/SSLv3, verify=FAIL, cipher=AES256-SHA, bits=256/256
May 31 00:45:00 server sendmail[5385]: 00000600000000004: to=<test@test.nl>, delay=00:01:01, xdelay=00:00:01, mailer=esmtp, pri=0, relay=mxa.mail.widexs.nl. [213.206.122.195], dsn=5.1.1, stat=User unknown
E-Mails go out. I only got Problems with the bounce management.

There is no Milter-Tag in the maillog. It seems like, procmail does not recieve the messages (?).
But why is my maillog not scanned, too?

There are no error-messages in my openemm-logs (as far as I can see).


Please help me. I spendet so many hours an that. I changed my Server from debian to Suse. But no success.

...

Posted: Fri Jun 01, 2007 12:21 pm
by christian.lang
I also had problems with the bounce management and in my case the problem was related to the issue that I had included the openemm Maildomain (bounce.yourcompany.com as described in the manuals) in the /etc/mail/local-host-names
As far as i found out because of this sendmail tried to send the mail to local users and didn't care about the mailertable.

So in your case if mx.yourcompany.com is only used for OpenEMM Mailings I would recommend you trying to delete this entry from the local-host-names file.

best regards,

Christian

Posted: Fri Jun 01, 2007 9:22 pm
by trax
Thanks Christian, but unfortunatly this was not the solution.

No bouncing recognized at any way.


Other ideas?

Posted: Sat Jun 02, 2007 12:47 am
by trax
After hours I got the following error notice in my maillog when I restart OpenEMM:

Code: Select all

daemon could not open control socket /var/run/sendmail/control: Executable files not allowed
I solved it by deleting the control-file.

I think the problem is, there are no mails bouncing.
No shown in the maillog, not in /var/mail/root

If i send a E-Mail manually to ext_@mx.company.de the Milter add: header: X-AGNLoop: set is shown in the maillog und the postmaster notification is in /var/mail/root.

Any ideas????

...

Posted: Mon Jun 04, 2007 8:07 am
by christian.lang
If you think that there are no emails bouncing you could try the following:
Create a (Test-) Mailinglist, Manually add a recipient with an email address which you know that doesn't exist and send out a mailing to that list.

Posted: Mon Jun 04, 2007 10:48 am
by trax
Hello Christian

That's what i did.

I created a mailinglist with recipients that do not exist.

In my maillog is that noitified:
May 31 00:44:52 server sendmail[5385]: STARTTLS=client, relay=mail.wiesel.de., version=TLSv1/SSLv3, verify=FAIL, cipher=DHE-RSA-AES256-SHA, bits=256/256
May 31 00:44:52 server sendmail[5385]: 00000600000000001: to=<test@wiesel.de>, delay=00:00:53, xdelay=00:00:03, mailer=esmtp, pri=0, relay=mail.wiesel.de. [80.190.209.47], dsn=5.0.0, stat=Service unavailable
May 31 00:44:59 server sendmail[5385]: 00000600000000002: to=<usertest@usertest.de>, delay=00:01:00, xdelay=00:00:07, mailer=esmtp, pri=0, relay=mail.usertest.de. [217.110.29.107], dsn=2.0.0, stat=Sent (- Requested mail action okay, completed)
May 31 00:45:00 server sendmail[5385]: STARTTLS=client, relay=mxa.mail.widexs.nl., version=TLSv1/SSLv3, verify=FAIL, cipher=AES256-SHA, bits=256/256
May 31 00:45:00 server sendmail[5385]: 00000600000000004: to=<test@test.nl>, delay=00:01:01, xdelay=00:00:01, mailer=esmtp, pri=0, relay=mxa.mail.widexs.nl. [213.206.122.195], dsn=5.1.1, stat=User unknown

But as you can see, there are no postmaster-notifications comming back to the server, that the bav.rc could regocnize this.

Why the srtlscan cant read these failures from the maillog (the second bounce filter method) is unclear too.

....

Posted: Mon Jun 04, 2007 8:46 pm
by christian.lang
um ... sorry :roll:

Concerning slrtscan: Is the process running?
As far as i know the following processes should be up & running for OpenEMM:

Code: Select all

python /home/openemm/bin/scripts/bav-update.py
python /home/openemm/bin/scripts/bav-trigger.py
python /home/openemm/bin/scripts/bavd.py
/home/openemm/bin/bav -L INFO
python /home/openemm/bin/scripts/update.py bounce account
python /home/openemm/bin/scripts/pickdist.py
[b]python /home/openemm/bin/scripts/slrtscn.py[/b]
perl /home/openemm/bin/wrapper.pl [...]
*+lots of sendmail processes*
in /home/openemm/var/log/[currentdate]-openemm-slrtscn.log there should be marks which should show you wether slrtscan is running.

--------------

Second thing: Which emailadress did you define as sender of your test-mailing?
something@mx.company.de ?

Posted: Mon Jun 04, 2007 8:55 pm
by trax
Every process is running.

The log is fine - as every other OpenEMM-Log.


I do use the mail adress ext_1@mx.company.de

I also tried root@mx.company.de


The really strange this is, there are no incoming bounce messages from other servers.

I tried to send emails to not existing adresses. But no Postmaster DAEMON notices.

...

Posted: Mon Jun 04, 2007 9:29 pm
by christian.lang
First of all regardless which sender adress you use bounce management using the logfile SHOULD work. Unfortunately I do not have any experience in python therefore i am unable to check, what slrtscan really does :(

I am sorry but for the moment i have no idea where to look into :(

Posted: Mon Jun 04, 2007 10:50 pm
by trax
Me, too - that's the problem :?

I think, slrtscan looks at the maillog and tries to find Bounces there.

Bav looks into the DAEMON notifications itself using procmail.

Why not one of both works: no idea.

...

Posted: Tue Jun 05, 2007 9:18 am
by christian.lang
i don't know whether this is relevant for slrtscan: have you set mailloop_domain in the company_tbl ?

Posted: Tue Jun 05, 2007 8:36 pm
by trax
Unfortunatly: yes, I did:

mx.company.de