David Newman wrote: >On 11/2/10 8:13 AM, Mark Sapiro wrote: >> >> Or, probably better, you could put >> >> spamassassin_destination_recipient_limit = 1 >> >> in main.cf to cause Postfix to pipe only one recipient at a time to the >> spamassassin handler (see man 8 pipe). > >Bingo. Your guess is correct. That one-line addition to main.cf now >allows Mailman message delivery to domain1.tld.
Actually, I think the domain1.tld non-delivery was a red herring. I think the real issue is that a post to a list with fewer than SMTP_MAX_RCPTS (default 500) members would be delivered to only one member. >I'd be glad to write this up now that it's working. To whom should I >send a draft of the changes? You can send them off list to me. >> Also note, You are doing way too much spamassassin scanning. You are >> scanning the inbound message before delivering it to Mailman, and then >> you are scanning the message again on its way from Mailman to the >> recipients. It might be better to set up a separate listener in >> Postfix on a different port and have Mailman deliver there and in >> Postfix only accept mail from Mailman (or localhost) on that port and >> bypass spamassassin for that mail. > >OK, thanks. Setting up a separate listener in Postfix via master.cf is >no problem for me, but how would I configure Mailman to deliver to that >port? Set SMTPPORT in mm_cfg.py. -- Mark Sapiro <[email protected]> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan ------------------------------------------------------ Mailman-Users mailing list [email protected] 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
