[Mailman-Users] Configuring Mailman as an announce list

Hi, Can someone please remind me how to configure mailman so that subscriber cannot post to it, only those registered in [Sender filters] List of non-member addresses whose postings should be automatically accepted. I have By default, should new list member postings be moderated? No Action

Re: [Mailman-Users] Configuring Mailman as an announce list

Thanks Mark and Brad. Found both Python and GNU FAQs, and found the answer, nice and clear. Thanks Geoff Mark Sapiro said the following on 17/01/2007 10:48 AM: Geoff Deering wrote: Can someone please remind me how to configure mailman so that subscriber cannot post to it, only those

Re: [Mailman-Users] Problems with Subject Generated via Invites

Paul Tomblin said the following on 14/01/2007 3:12 PM: The problem as I see it is that people who only configure lists through a web interface are unlikely to have the knowledge of the mail transport agent (MTA) to know if setting VERP_CONFIRMATIONS will work or not. It's only if you're an

[Mailman-Users] Problems with Subject Generated via Invites

such as 'confirm 33f514b7210cb6bea0cdfd9fa0a1d273b5266177' . At first glance it looks like any old spammer phishing for login information. Is it possible to modify the mass mailout subscribe/invite so there is a custom subject header? Geoff Deering

Re: [Mailman-Users] Problems with Subject Generated via Invites

10:56 AM: Geoff Deering wrote: . At first glance it looks like any old spammer phishing for login information. Is it possible to modify the mass mailout subscribe/invite so there is a custom subject header? If you set VERP_CONFIRMATIONS = Yes in mm_cfg.py, the subject

Re: [Mailman-Users] Problems with Subject Generated via Invites

Mark Sapiro said the following on 14/01/2007 11:55 AM: I agree, but in the case of VERP_CONFIRMATIONS, this is a site setting. It defaults to No rather than Yes, because that is the 'safer' setting because some MTA's will not be configured to handle the reply address with confirmation token

[Mailman-Users] Auto-discard notifications - Logging original headers for Spam tracing

Hi, Is there a log or any way of logging the original spam emails sent to lists so that the original headers can be used for spam tracing and reporting through the likes of spamcop.net? Regards Geoff -- Mailman-Users mailing list

Re: [Mailman-Users] Auto-discard notifications - Logging originalheaders for Spam tracing

Mark Sapiro wrote: Geoff Deering wrote: Is there a log or any way of logging the original spam emails sent to lists so that the original headers can be used for spam tracing and reporting through the likes of spamcop.net? Not without modifying the code. If you want this info

Re: [Mailman-Users] subscription request as recieved, but nothing further happens (randomly)

Mark Sapiro wrote: Geoff Deering wrote: I have Mailman 2.16 installed on a server. It seems to behaving erratically by only subscribing people randomly, some subscriptions are processed without problems. I can't find what is happening with the failed attempts to subscribe. It's

Re: [Mailman-Users] subscription request as recieved, but nothing further happens (randomly)

Patrick Siglin wrote: Mine sits on a subdomain. I was having a similar problem which turned out to be a wrong setting on my dns server on the primary. I think the dns is okay, just that on the default install it seems to be looking for an SMTP server on the sub domain. Also I am not

[Mailman-Users] subscription request as recieved, but nothing further happens (randomly)

Hi, I have Mailman 2.16 installed on a server. It seems to behaving erratically by only subscribing people randomly, some subscriptions are processed without problems. I can't find what is happening with the failed attempts to subscribe. It's acknowledging the subscription request as