Hello,
I am having some problems with bounce processing working correctly. If I set a list so that a max bounce score < 1 ( .1 in this case). So, the expectation is that the subscriber's account will immediately be tagged as 'No Mail" by Bounce (B). That is not happening. In addition, the bounce logs are quite a bit leaner than I would expect and the bounces don't seem to be showing up there.
Can someone point me in the right direction? I have checked the cron and list settings and can't seem to resolve this. Stale users are not being marked disabled and are not getting unsubscribed.
On 11/19/2013 11:26 AM, Christopher Adams wrote:
I am having some problems with bounce processing working correctly. If I set a list so that a max bounce score < 1 ( .1 in this case). So, the expectation is that the subscriber's account will immediately be tagged as 'No Mail" by Bounce (B). That is not happening.
It should work. The first bounce should disable delivery by bounce. You can also set bounce_score_threshold to 0, but .1 should do the same thing.
Is bounce_processing set to Yes for the list? Are all the notifications set to Yes?
In addition, the bounce logs are quite a bit leaner than I would expect and the bounces don't seem to be showing up there.
What do you see in the MTA logs for mail which bounces?
Can someone point me in the right direction? I have checked the cron and list settings and can't seem to resolve this. Stale users are not being marked disabled and are not getting unsubscribed.
Ultimate unsubscription, assuming bounce_you_are_disabled_warnings is greater than 0 depends on cron/disabled, but if delivery is not being disabled by bounce, then removal won't occur.
Mark,
Here is a log that shows a message sent to the 'test7' list. The list is set up for bounce processing and all notifications are set to 'yes'. This is happening with the entire system, not just individual lists. It doesn't seem to be processing bounces. The bounce.log,which rotated at 4 am this morning, is currently empty. The mailman.cron has an entry that sends messages to disabled subscribers at 9 am every day.
Looking at some older bounce logs, it appears that a few entries for bounce score appear, but not as many as I would expect. Additionally, nobody is being tagged as (B) bounce in the membership list.
Nov 19 11:58:26 swiki postfix/local[17412]: 270961998422: to=< test7@mydomain.com>, relay=local, delay=0.15, delays=0.05/0/0/0.1, dsn=2.0.0, status=sent (delivered to command: /usr/local/mailman/mail/mailman post test7) Nov 19 11:58:27 swiki postfix/qmgr[6381]: 824501998422: from=< test7-bounces@mydomain.com>, size=5830, nrcpt=1 (queue active) Nov 19 11:58:27 swiki postfix/qmgr[6381]: 852721998424: from=< test7-bounces@mydomain.com>, size=5798, nrcpt=3 (queue active) Nov 19 11:58:31 swiki postfix/local[17411]: 9E66A1998437: to=< test7-bounces@mydomain.com>, relay=local, delay=0.2, delays=0.02/0/0/0.18, dsn=2.0.0, status=sent (delivered to command: /usr/local/mailman/mail/mailman bounces test7)
On Tue, Nov 19, 2013 at 12:20 PM, Mark Sapiro mark@msapiro.net wrote:
On 11/19/2013 11:26 AM, Christopher Adams wrote:
I am having some problems with bounce processing working correctly. If I set a list so that a max bounce score < 1 ( .1 in this case). So, the expectation is that the subscriber's account will immediately be tagged
as
'No Mail" by Bounce (B). That is not happening.
It should work. The first bounce should disable delivery by bounce. You can also set bounce_score_threshold to 0, but .1 should do the same thing.
Is bounce_processing set to Yes for the list? Are all the notifications set to Yes?
In addition, the bounce logs are quite a bit leaner than I would expect and the bounces don't
seem
to be showing up there.
What do you see in the MTA logs for mail which bounces?
Can someone point me in the right direction? I have checked the cron and list settings and can't seem to resolve this. Stale users are not being marked disabled and are not getting unsubscribed.
Ultimate unsubscription, assuming bounce_you_are_disabled_warnings is greater than 0 depends on cron/disabled, but if delivery is not being disabled by bounce, then removal won't occur.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/adamsca%40gmail.com
On 11/19/2013 12:59 PM, Christopher Adams wrote:
Looking at some older bounce logs, it appears that a few entries for bounce score appear, but not as many as I would expect. Additionally, nobody is being tagged as (B) bounce in the membership list.
If there is a bounce score entry in the bounce log and the score exceeds threshold, the member should be disabled.
Nov 19 11:58:31 swiki postfix/local[17411]: 9E66A1998437: to=<test7-bounces@mydomain.com mailto:test7-bounces@mydomain.com>, relay=local, delay=0.2, delays=0.02/0/0/0.18, dsn=2.0.0, status=sent (delivered to command: /usr/local/mailman/mail/mailman bounces test7)
This should result in a bounce log entry.
Is BounceRunner running? Is there anything in Mailman's error log relating to bounces? What's in Mailman's qrunner log relating to BounceRunner?
There is no bounce score entry in the bounce log for that post, or for probably any posts.
There is nothing in the error log about bounces.
The only entry in the qrunner related to BounceRunner is at 4:02 am every day:
Nov 19 04:02:36 2012 (29791) Master qrunner detected subprocess exit (pid: 27168, sig: None, sts: 2, class: BounceRunner, slice: 1/1) [restarting]
On Tue, Nov 19, 2013 at 1:25 PM, Mark Sapiro mark@msapiro.net wrote:
On 11/19/2013 12:59 PM, Christopher Adams wrote:
Looking at some older bounce logs, it appears that a few entries for bounce score appear, but not as many as I would expect. Additionally, nobody is being tagged as (B) bounce in the membership list.
If there is a bounce score entry in the bounce log and the score exceeds threshold, the member should be disabled.
Nov 19 11:58:31 swiki postfix/local[17411]: 9E66A1998437: to=<test7-bounces@mydomain.com mailto:test7-bounces@mydomain.com>, relay=local, delay=0.2, delays=0.02/0/0/0.18, dsn=2.0.0, status=sent (delivered to command: /usr/local/mailman/mail/mailman bounces test7)
This should result in a bounce log entry.
Is BounceRunner running? Is there anything in Mailman's error log relating to bounces? What's in Mailman's qrunner log relating to BounceRunner?
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
There is no bounce score entry in the bounce log. As it turns out, there has not been a bounce log generated since 11/13.
Would BounceRunner show in a list of processes. If so, I don't see it.
Here is an entry in the qrunner log related to BounceRunner:
Nov 19 04:02:36 2012 (29791) Master qrunner detected subprocess exit (pid: 27168, sig: None, sts: 2, class: BounceRunner, slice: 1/1) [restarting] /Bounce 1973,40 4
On Tue, Nov 19, 2013 at 1:25 PM, Mark Sapiro mark@msapiro.net wrote:
On 11/19/2013 12:59 PM, Christopher Adams wrote:
Looking at some older bounce logs, it appears that a few entries for bounce score appear, but not as many as I would expect. Additionally, nobody is being tagged as (B) bounce in the membership list.
If there is a bounce score entry in the bounce log and the score exceeds threshold, the member should be disabled.
Nov 19 11:58:31 swiki postfix/local[17411]: 9E66A1998437: to=<test7-bounces@mydomain.com mailto:test7-bounces@mydomain.com>, relay=local, delay=0.2, delays=0.02/0/0/0.18, dsn=2.0.0, status=sent (delivered to command: /usr/local/mailman/mail/mailman bounces test7)
This should result in a bounce log entry.
Is BounceRunner running? Is there anything in Mailman's error log relating to bounces? What's in Mailman's qrunner log relating to BounceRunner?
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 11/19/2013 03:35 PM, Christopher Adams wrote:
There is no bounce score entry in the bounce log. As it turns out, there has not been a bounce log generated since 11/13.
Would BounceRunner show in a list of processes. If so, I don't see it.
ps -fwC python
or
ps -fwu mailman
should show all the qrunners with the commands that invoked them (including the runner name).
e.g. $ ps -fwu mailman UID PID PPID C STIME TTY TIME CMD mailman 21122 1 0 Nov18 ? 00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/mailmanctl -s -q start mailman 21123 21122 0 Nov18 ? 00:00:03 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=ArchRunner:0:1 -s mailman 21124 21122 0 Nov18 ? 00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=BounceRunner:0:1 -s mailman 21125 21122 0 Nov18 ? 00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=CommandRunner:0:1 -s mailman 21126 21122 0 Nov18 ? 00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s mailman 21127 21122 0 Nov18 ? 00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=NewsRunner:0:1 -s mailman 21128 21122 0 Nov18 ? 00:00:08 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s mailman 21129 21122 0 Nov18 ? 00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=VirginRunner:0:1 -s mailman 21130 21122 0 Nov18 ? 00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=RetryRunner:0:1 -s
If BounceRunner isn't running (since 11/13?) that would explain a lot.
Here is an entry in the qrunner log related to BounceRunner:
Nov 19 04:02:36 2012 (29791) Master qrunner detected subprocess exit (pid: 27168, sig: None, sts: 2, class: BounceRunner, slice: 1/1) [restarting]
What happens daily at 04:02? Check your cron logs or /etc/cron.daily
sts: 2 could be a missing file or directory, but there should be an entry in Mailman's error log from the same time.
Are there queued bounces in the bounces queue (Mailman's qfiles/bounces/ or wherever your package puts it (e.g. /var/spool/mailman/bounces in the RedHat/CentOS package).
Mark,
I had restarted Mailman several times and still, bounce processing was not taking place and the bounce log had not been written since 11/13. Before I left last night, I restarted it and then I noticed a flurry of activity, with queued bounces being processed. I hadn't looked in the /qfiles/bounces/ until this morning. Now I see that there is nothing queued.
So, any idea of what might of happened to gum it up. Thanks for taking the time to address this issue. It seemingly has corrected itself.
On Tue, Nov 19, 2013 at 4:22 PM, Mark Sapiro mark@msapiro.net wrote:
On 11/19/2013 03:35 PM, Christopher Adams wrote:
There is no bounce score entry in the bounce log. As it turns out, there has not been a bounce log generated since 11/13.
Would BounceRunner show in a list of processes. If so, I don't see it.
ps -fwC python
or
ps -fwu mailman
should show all the qrunners with the commands that invoked them (including the runner name).
e.g. $ ps -fwu mailman UID PID PPID C STIME TTY TIME CMD mailman 21122 1 0 Nov18 ? 00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/mailmanctl -s -q start mailman 21123 21122 0 Nov18 ? 00:00:03 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=ArchRunner:0:1 -s mailman 21124 21122 0 Nov18 ? 00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=BounceRunner:0:1 -s mailman 21125 21122 0 Nov18 ? 00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=CommandRunner:0:1 -s mailman 21126 21122 0 Nov18 ? 00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s mailman 21127 21122 0 Nov18 ? 00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=NewsRunner:0:1 -s mailman 21128 21122 0 Nov18 ? 00:00:08 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s mailman 21129 21122 0 Nov18 ? 00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=VirginRunner:0:1 -s mailman 21130 21122 0 Nov18 ? 00:00:00 /usr/bin/python2.7 /usr/local/mailman/bin/qrunner --runner=RetryRunner:0:1 -s
If BounceRunner isn't running (since 11/13?) that would explain a lot.
Here is an entry in the qrunner log related to BounceRunner:
Nov 19 04:02:36 2012 (29791) Master qrunner detected subprocess exit (pid: 27168, sig: None, sts: 2, class: BounceRunner, slice: 1/1) [restarting]
What happens daily at 04:02? Check your cron logs or /etc/cron.daily
sts: 2 could be a missing file or directory, but there should be an entry in Mailman's error log from the same time.
Are there queued bounces in the bounces queue (Mailman's qfiles/bounces/ or wherever your package puts it (e.g. /var/spool/mailman/bounces in the RedHat/CentOS package).
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 11/20/2013 07:57 AM, Christopher Adams wrote:
So, any idea of what might of happened to gum it up. Thanks for taking the time to address this issue. It seemingly has corrected itself.
It appears that BounceRunner had died for some reason. To understand more, I'd need to see the full Mailman qrunner log for the entire period that things weren't working and also any Mailman error log entries from times that BounceRunner exited according to the qrunner log.
participants (2)
-
Christopher Adams -
Mark Sapiro