I'm having a similar problem, also using 2.1.18-1. Posts from a Yahoo
user are bouncing on redelivery to him.
Jun 13 18:55:00 host postfix/smtp[15681]: 912BD520AB:
to=<u...@yahoo.com>, relay=mta5.am0.yahoodns.net[98.138.112.33]:25,
delay=1.2, delays=0.05/0/0.25/0.92, dsn=5.7.9, status=bounced (host
mta5.am0.yahoodns.net[98.138.112.33] said: 554 5.7.9 Message not
accepted for policy reasons. See
http://postmaster.yahoo.com/errors/postmaster-28.html (in reply to
end of DATA command))
I don't have a GLOBAL_PIPELINE in mm_cfg.py.
host mailman # grep PIPELINE Mailman/mm_cfg.py
host mailman # bin/withlist Test-list2
Loading list test-list2 (unlocked)
The variable `m' is the test-list2 MailList instance
>>> m.pipeline
Traceback (most recent call last):
File "<console>", line 1, in <module>
File "/usr/lib64/mailman/Mailman/MailList.py", line 146, in
__getattr__
raise AttributeError, name
AttributeError: pipeline
>>>
Finalizing
host mailman #
General Options
from_is_list is Munge From
anonymous_list is No
Privacy Options --> Sender Filters
dmarc_moderation_action is Munge From
dmarc_quarantine_moderation_action is Yes
The GLOBAL_PIPELINE in Defaults.py looks ok to me:
GLOBAL_PIPELINE = [
# These are the modules that do tasks common to all delivery paths.
'SpamDetect',
'Approve',
'Replybot',
'Moderate',
'Hold',
'MimeDel',
'Scrubber',
'Emergency',
'Tagger',
'CalcRecips',
'AvoidDuplicates',
'Cleanse',
'CleanseDKIM',
'CookHeaders',
# And now we send the message to the digest mbox file, and to the
arch and
# news queues. Runners will provide further processing of the message,
# specific to those delivery paths.
'ToDigest',
'ToArchive',
'ToUsenet',
# Now we'll do a few extra things specific to the member delivery
# (outgoing) path, finally leaving the message in the outgoing queue.
'AfterDelivery',
'Acknowledge',
'WrapMessage',
'ToOutgoing',
]
Any ideas what I could try?
Thanks
glen
On 06/12/2014 02:19 PM, Mark Sapiro wrote:
On 06/12/2014 01:41 PM, Peter Knowles wrote:
When I set the option to "reject" it rejects properly as expected. But
when it's set to "munge from" it sends it out as if "Accept" was chosen.
Then the problem almost certainly has to be the pipeline. There is a new
WrapMessage handler that must be in the pipeline.
Do you have a GLOBAL_PIPELINE setting in mm_cfg.py? If so, look at the
setting in Defaults.py and make sure it contains the WrapMessage entry
in the right place.
If not, try
bin/withlist LISTNAME
and then at the prompt enter m.pipeline. Does that return a value rather
than AttributeError?
------------------------------------------------------
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/archive%40jab.org
