Grant,
Thank you very much... your advice appears to be spot on...
I've added a header_check to my postfix configuration on my mailman
server to prune the headers from my internal gateway before they are
passed to mailman.
something like
/^Received: from localhost/ IGNORE
/^Received: from mygateway.mydomain.com/ IGNORE
that appears to help a lot ...
Thanks!
Ted Targosz
On 25/5/2010 11:19 AM, Grant Taylor wrote:
Ted Targosz wrote:
so I was wondering if anyone else had encountered this and knew of a
workaround (besides bypassing the gateway)
I've not run in to this my self (with Mailman). But what you say
makes perfect sense.
If you are not pruning Received: headers as you pass your messages in
to Mailman, they may be counted as extra headers contributing to the
loop detection cludge.
So, you might want to make sure that you aren't artificially raising
your hop count with the Received: headers of the messages coming in to
Mailman.
Grant. . . .
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
http://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:
http://mail.python.org/mailman/options/mailman-users/tedtarg%40jobstreet.com
--
Ted Targosz
Business Development/Operations Manager
Jobstreet.com
Phone: 604-6445131 (Mayang Mall)
Mobile Phone: 6012-2063600
Fax: 604-6428653
email: tedt...@jobstreet.com
skype ID: tedtarg
------------------------------------------------------
Mailman-Users mailing list Mailman-Users@python.org
http://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:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
