[Mailman-Users] Bounces not being detected
mark at msapiro.net
Sun Jun 22 01:53:52 CEST 2014
On 06/21/2014 01:24 PM, Peter Fraser wrote:
> The message I showed earlier was the postfix on the same box as mailman. Mailman should detect those bounces.
And what did that log show for the sender non-delivery notification
message generated as a result of the undeliverable message.
And was there anything in Mailman's bounce log?
And is there anything in Mailman's qfiles/bounce/ directory?
> I was just thinking based on what you said about some smtp servers getting the 5xx status from downstream servers thatthose errors would not reach mailman the way things are set up here. I hadn't considered that.
If list posts from outside your local network reach Mailman, then
bounces should too unless you have delivery to Mailman set up in some
way such that messages to LISTNAME at your.domain are delivered, but
messages to the other 9 LISTNAMEfirstname.lastname@example.org addresses are not. The 9
values of * are admin, bounces, confirm, join, leave, owner, request,
subscribe and unsubscribe, and all those addresses except 'admin' which
is a deprecated synonym for 'bounces' must be deliverable to Mailman for
Mailman to work as documented.
> So do those .pck files mean the bouncerunner is working?
No. Each heldmsg-LISTNAME-nnnn.pck file is a message to the LISTNAME
list waiting moderator action. They should all be visible in the admindb
web UI for LISTNAME. They have nothing to do with bounces.
To see if BounceRunner is running, do
ps -fAw | grep BounceRunner
If that shows nothing other than the 'grep', BounceRunner is not
running. More information may be available in Mailman's qrunner log and
possibly Mailman's error log.
Also, in that case, you may see that there are queued bounces in
Mailman's qfiles/bounce/ directory.
Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users