On 2/15/22 17:53, billy noah wrote:
Sorry, the reason I cited earlier must have been from before they were added and approved. Apparently the reason has changed to "Message has implicit destination" which I'm guessing it's due to BCC. I changed "require_explicit_destination" to "No". Thanks for your help.
If it is in fact a BCC, and you want to accept it, You did the right thing. However it could be the case the your user is sending posts to an alternate address. E.g, the list is l...@example.com, but mail to l...@mail.example.com will also be delivered to the list. For this example, adding l...@mail.example.com to the list's Privacy options... -> Recipient filters -> acceptable_aliases may be a better solution.
-- Mark Sapiro <m...@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 To unsubscribe send an email to mailman-users-le...@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
