Re: [Mailman-Users] sharing administrator passwords
On 5/28/2008, Brad Knowles ([EMAIL PROTECTED]) wrote: From /usr/local/mailman/Mailman/Defaults.py: # Normally when a site administrator authenticates to a web page with the site # password, they get a cookie which authorizes them as the list admin. It # makes me nervous to hand out site auth cookies because if this cookie is # cracked or intercepted, the intruder will have access to every list on the # site. OTOH, it's dang handy to not have to re-authenticate to every list on # the site. Set this value to Yes to allow site admin cookies. ALLOW_SITE_ADMIN_COOKIES = No Sorry, guess I should have looked a little closer... but thanks... I made the change and restarted mailman, and still have to log into each list, so I'm guessing this only applies to new lists? I'll have to run a command to make it apply to existing lists? -- Best regards, Charles -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] sharing administrator passwords
On 5/29/08 6:23 AM, Charles Marcus at [EMAIL PROTECTED] wrote: On 5/28/2008, Brad Knowles ([EMAIL PROTECTED]) wrote: From /usr/local/mailman/Mailman/Defaults.py: # Normally when a site administrator authenticates to a web page with the site # password, they get a cookie which authorizes them as the list admin. It # makes me nervous to hand out site auth cookies because if this cookie is # cracked or intercepted, the intruder will have access to every list on the # site. OTOH, it's dang handy to not have to re-authenticate to every list on # the site. Set this value to Yes to allow site admin cookies. ALLOW_SITE_ADMIN_COOKIES = No Sorry, guess I should have looked a little closer... but thanks... I made the change and restarted mailman, and still have to log into each list, so I'm guessing this only applies to new lists? I'll have to run a command to make it apply to existing lists? Is your site password the same as the list admin passwords? My playing around with the feature says the site admin password must be different from the list admin password. Otherwise, it will be authenticated as the list password, not the site password, and you'll need to log into the other lists. -- Larry Stone [EMAIL PROTECTED] http://www.stonejongleux.com/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Subscription errors
Duncan Drury [EMAIL PROTECTED] wrote:
I have recently upgraded my Mailman installation to 2.1.10 and the
online subscription system that I set up stopped working completely
(users fill out a form, which generates an email, which subscribes them
to the list).
This seems to be related to the known bug in 2.1.10 and I have tried
installing the patch that has been discussed in many places - but I am
still getting the same problem. In log/error I am seeing the
following:
May 28 23:36:05 2008 (31672) Uncaught runner exception: 'NoneType' object has
no attribute 'lower'
May 28 23:36:05 2008 (31672) Traceback (most recent call last):
File /usr/local/mailman/Mailman/Queue/Runner.py, line 120, in _oneloop
self._onefile(msg, msgdata)
File /usr/local/mailman/Mailman/Queue/Runner.py, line 191, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /usr/local/mailman/Mailman/Queue/CommandRunner.py, line 241, in
_dispose
res.do_command('join')
File /usr/local/mailman/Mailman/Queue/CommandRunner.py, line 139, in
do_command
return handler.process(self, args)
File /usr/local/mailman/Mailman/Commands/cmd_subscribe.py, line 74, in
process
if digest is None and password.lower() in ('digest', 'nodigest'):
AttributeError: 'NoneType' object has no attribute 'lower'
May 28 23:36:05 2008 (31672) SHUNTING:
1212014164.9099751+f202edd394843183ffbb4f3cde5b3f52fca1038a
Perhaps I am not installing the patch correctly? I'm using the FreeBSD
port of Mailman, and haven't had to patch anything before!
Any help would be much appreciated. This has had me scratching my head
for days.
Duncan
I am not an expert in this particular patch. I did install it on a
system where I build an Ubuntu Mailman 2.1.10 package, but I have not
yet installed nor tested that package, as I am awaiting maybe more
patches.
The only thing I can suggest is that maybe the FreeBSD port has a
conflicting patch? I know that Debian/Ubuntu has changes to the
SourceForge source, so I build my package from the SourceForge source
and remove all but one Debian/Ubuntu patch (the one that places files
in the proper directories for D/U). I do not know what FreeBSD does.
--
Barry S. Finkel
Computing and Information Systems Division
Argonne National Laboratory Phone:+1 (630) 252-7277
9700 South Cass Avenue Facsimile:+1 (630) 252-4601
Building 222, Room D209 Internet: [EMAIL PROTECTED]
Argonne, IL 60439-4828 IBMMAIL: I1004994
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] slightly OT: on not becoming a spam source
On 5/28/08 8:43 PM, Larry Stone wrote: On 5/28/08 9:26 PM, David Newman at [EMAIL PROTECTED] wrote: Another is to enable VERP for your outgoing messages, this allows you to track the message ID to the individual user. That sounds very promising, thanks. Trying it now... I have all my lists VERPed for just that reason. Once I figure out who it is, they get unsubscribed with extreme prejudice (meaning they also get banned from the mail server). But you should be aware that will increase your outgoing mail load. Nothing I do is high enough frequency for that to be an issue but it can be for some people. Most of my lists are announcement lists. In fact, for some of them, the recipients aren't even aware it's a mailing list. I (as a side job) assign soccer referees for local leagues. Rather than sending out announcements to my referees with a long BCC: list, I add them to a private mailman list with VERP so they receive them with them as the To: recipient. That also lets me know who to remove when they decide that the easiest way to let me know that they're no longer interested in being notified of available games is to do a report as spam. :-( OK, I've enabled VERP but I'm no closer to isolating who's complaining in AOL-land. Possibly this is some VERP config error on my part. I added the following to mm_cfg.py and rebooted: VERP_PASSWORD_REMINDERS = Yes VERP_PERSONALIZED_DELIVERIES = Yes VERP_DELIVERY_INTERVAL = Yes VERP_CONFIRMATIONS = Yes VERP_DELIVERY_INTERVAL = 1 The next AOL feedback report contained a unique Message-ID, as always. grep'ing for that ID in /usr/local/mailman/logs tells me only that the message was delivered to 250 recipients in 65 seconds. grep'ing for that ID in /var/log/maillog produces a lot more output -- in fact, still one entry per mailing list subscriber. I've pasted one example below (addresses redacted); there are 250 of these in maillog. So, back to the original question: How to associate one message-ID with one subscriber? Many thanks dn May 29 10:01:22 mail amavis[24936]: (24936-17) Passed CLEAN, LOCAL [127.0.0.1] [ 207.178.164.26] [EMAIL PROTECTED] - [EMAIL PROTECTED], Message-ID: [EMAIL PROTECTED], mail_id : KdgO9YwQBfML, Hits: -2.403, size: 18328, queued_as: 482E25B31D5, 12089 ms May 29 10:01:22 mail postfix/cleanup[26083]: 913255B31D7: message-id=627766.373 [EMAIL PROTECTED] May 29 10:01:22 mail postfix/cleanup[31531]: BE4745B31D8: message-id=627766.373 [EMAIL PROTECTED] May 29 10:01:22 mail postfix/cleanup[26083]: D9C2E5B31D9: message-id=627766.373 [EMAIL PROTECTED] May 29 10:01:23 mail postfix/cleanup[31531]: 47F645B31DA: message-id=627766.373 [EMAIL PROTECTED] May 29 10:01:23 mail postfix/cleanup[26083]: 6E0D65B31DB: message-id=627766.373 [EMAIL PROTECTED] May 29 10:01:23 mail postfix/cleanup[31531]: 876B85B31DC: message-id=627766.373 [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] slightly OT: on not becoming a spam source
David Newman wrote: OK, I've enabled VERP but I'm no closer to isolating who's complaining in AOL-land. Possibly this is some VERP config error on my part. I added the following to mm_cfg.py and rebooted: VERP_PASSWORD_REMINDERS = Yes VERP_PERSONALIZED_DELIVERIES = Yes VERP_DELIVERY_INTERVAL = Yes VERP_CONFIRMATIONS = Yes VERP_DELIVERY_INTERVAL = 1 The next AOL feedback report contained a unique Message-ID, as always. Did you go back to the list configuration and turn on personalization? -- Brad Knowles [EMAIL PROTECTED] Member of the Python.org Postmaster Team Co-Moderator of the mailman-users and mailman-developers mailing lists -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] slightly OT: on not becoming a spam source
On 5/29/08 11:40 AM, Brad Knowles wrote: David Newman wrote: OK, I've enabled VERP but I'm no closer to isolating who's complaining in AOL-land. Possibly this is some VERP config error on my part. I added the following to mm_cfg.py and rebooted: VERP_PASSWORD_REMINDERS = Yes VERP_PERSONALIZED_DELIVERIES = Yes VERP_DELIVERY_INTERVAL = Yes VERP_CONFIRMATIONS = Yes VERP_DELIVERY_INTERVAL = 1 The next AOL feedback report contained a unique Message-ID, as always. Did you go back to the list configuration and turn on personalization? Er, no, I haven't. Where do I set that in the Web UI? thanks dn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] slightly OT: on not becoming a spam source
David Newman wrote: On 5/29/08 11:40 AM, Brad Knowles wrote: David Newman wrote: OK, I've enabled VERP but I'm no closer to isolating who's complaining in AOL-land. Possibly this is some VERP config error on my part. I added the following to mm_cfg.py and rebooted: VERP_PASSWORD_REMINDERS = Yes VERP_PERSONALIZED_DELIVERIES = Yes VERP_DELIVERY_INTERVAL = Yes VERP_CONFIRMATIONS = Yes VERP_DELIVERY_INTERVAL = 1 The next AOL feedback report contained a unique Message-ID, as always. Did you go back to the list configuration and turn on personalization? Er, no, I haven't. Where do I set that in the Web UI? End original message. - Should be in the list general options. I am not sure, but you may have to do a Mailman restart to enable it. Dragon ~~~ Venimus, Saltavimus, Bibimus (et naribus canium capti sumus) ~~~ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] slightly OT: on not becoming a spam source
At 01:53 PM 5/29/2008, David Newman wrote: On 5/29/08 11:40 AM, Brad Knowles wrote: David Newman wrote: OK, I've enabled VERP but I'm no closer to isolating who's complaining in AOL-land. Possibly this is some VERP config error on my part. I added the following to mm_cfg.py and rebooted: VERP_PASSWORD_REMINDERS = Yes VERP_PERSONALIZED_DELIVERIES = Yes VERP_DELIVERY_INTERVAL = Yes VERP_CONFIRMATIONS = Yes VERP_DELIVERY_INTERVAL = 1 The next AOL feedback report contained a unique Message-ID, as always. Did you go back to the list configuration and turn on personalization? Er, no, I haven't. Where do I set that in the Web UI? thanks dn DA: It is under Nondigest Options. Dave -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/dandrews%40visi.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp David Andrews and white cane Harry. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Selecting Topics Externally?
Hi all, We currently use Mailman at our site but do not have the administrative interface open to the public. My workaround to allow users to subscribe and unsubsribe was a CGI script that generated a command line argument to send the subcribe or unsubscribe message along with the e-mail address to mailman, using an e-mail message (it simulated the user sending an email with subscribe or unsubscribe in the subject). Pretty simple. I have a tougher job now though -- We'd like users to be able to select a topic or topics to add or remove themselves to on the mailing list. Without a built-in command line option to set topics, or being able to directly post to the mailman application (since it's behind our firewall and will only work for internal company users, not external customers), can anyone tell me if they have written a CGI application that can simulate sending these commands to mailman? I was thinking I could use an HTML form to pass the form field values to a CGI script, which could then build the proper submit logic to in turn pass the commands on to mailman (since the CGI is running our our server internally, this SHOULD work). Can anyone help me? My head is spinning here. Thanks! -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Queued mail
Is there any mailman setting that you would need to verify if you were going to shut the server down, to make sure mail is queued. We use postfix with mailman 2.1.6 Melinda Gilmore Systems Engineer The Ohio State University Enterprise Messaging/OIT 614-292-4953 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] slightly OT: on not becoming a spam source
On 5/29/08 12:09 PM, David Andrews wrote: Did you go back to the list configuration and turn on personalization? Er, no, I haven't. Where do I set that in the Web UI? thanks dn DA: It is under Nondigest Options. Sorry for being dense, but where? These are the only choices I see under nondigest options: nondigestable msg_header msg_footer scrub_nondigest and under sibling lists: regular_exclude_lists regular_include_lists dn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] slightly OT: on not becoming a spam source
It is between the first and second choices you listed. Since it isn't there, I would guess you need to stop and restart Mailman so the configuration file is reprocessed. Dave At 03:02 PM 5/29/2008, David Newman wrote: On 5/29/08 12:09 PM, David Andrews wrote: Did you go back to the list configuration and turn on personalization? Er, no, I haven't. Where do I set that in the Web UI? thanks dn DA: It is under Nondigest Options. Sorry for being dense, but where? These are the only choices I see under nondigest options: nondigestable msg_header msg_footer scrub_nondigest and under sibling lists: regular_exclude_lists regular_include_lists dn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/dandrews%40visi.com Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp David Andrews and white cane Harry. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] slightly OT: on not becoming a spam source
On Thu, 29 May 2008, David Newman wrote: Possibly this is some VERP config error on my part. I added the following to mm_cfg.py and rebooted: VERP_PASSWORD_REMINDERS = Yes VERP_PERSONALIZED_DELIVERIES = Yes VERP_DELIVERY_INTERVAL = Yes VERP_CONFIRMATIONS = Yes VERP_DELIVERY_INTERVAL = 1 You also need OWNERS_CAN_ENABLE_PERSONALIZATION = Yes Once you do that, the personalization option will appear on the appropriate admin page. You will probably need to restart httpd for it to appear. I doubt restarting the qrunners will be needed. -- Larry Stone [EMAIL PROTECTED] -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Mailing list with no archive
A mailing list that I am subscribed to, for reasons of privacy, has decided to not archive its messages. I think this is an extremely silly idea, but right now out of my control. My problem is that periodically I think I remember something useful having been posted there, and want to search the non-existant archives -- because I forget they do not exist. The first erroneous piece of information I get is 'this archive is only searchable by list members'. So I try to log in to read the list, and despite typing my correct password, things fail with 'Authorization Failed' rather than letting me discover that there were no archives to be found. So you assume you haven't reset your password for this mailing list to one of the several you are in the habit of using, and ask for a password reminder -- to find out that all of this has been a complete waste of time because your problem is that there is no archive, not that you mistyped your password. So -- is this just a bug -- should I report it -- or is this list misconfigured? I can ask the list maintainer to change things if there is a way we can avoid this. Thanks very much, Laura Creighton -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Queued mail
Melinda Gilmore wrote: Is there any mailman setting that you would need to verify if you were going to shut the server down, to make sure mail is queued. We use postfix with mailman 2.1.6 No, there is no such setting. Postfix should queue everything it can't deliver to Mailman and refuse to accept any more mail if it's own local queues are full, and the remote end should then queue the messages. Anything that can be delivered to Mailman while the Mailman queue runners are shut down will be put into a Mailman queue, to be processed once Mailman comes back up. There's queues all over the place. -- Brad Knowles [EMAIL PROTECTED] Member of the Python.org Postmaster Team Co-Moderator of the mailman-users and mailman-developers mailing lists -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] slightly OT: on not becoming a spam source
On 5/29/08 1:46 PM, Larry Stone wrote: On Thu, 29 May 2008, David Newman wrote: Possibly this is some VERP config error on my part. I added the following to mm_cfg.py and rebooted: VERP_PASSWORD_REMINDERS = Yes VERP_PERSONALIZED_DELIVERIES = Yes VERP_DELIVERY_INTERVAL = Yes VERP_CONFIRMATIONS = Yes VERP_DELIVERY_INTERVAL = 1 You also need OWNERS_CAN_ENABLE_PERSONALIZATION = Yes Once you do that, the personalization option will appear on the appropriate admin page. You will probably need to restart httpd for it to appear. I doubt restarting the qrunners will be needed. Hmmm. I must be missing something, as the system is still associating each Message-ID with all 250 list subscribers. This is in mm_cfg.py: VERP_PASSWORD_REMINDERS = Yes VERP_PERSONALIZED_DELIVERIES = Yes VERP_DELIVERY_INTERVAL = Yes VERP_CONFIRMATIONS = Yes VERP_DELIVERY_INTERVAL = 1 OWNERS_CAN_ENABLE_PERSONALIZATION = Yes and under Non-digest options, peronsalize is set to Full Personaliztion and I restarted mailman, apache, and postfix after all this. What else might be missing? many thanks dn -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] slightly OT: on not becoming a spam source
On Fri, May 30, 2008 at 12:18 AM, David Newman [EMAIL PROTECTED] wrote: Hmmm. I must be missing something, as the system is still associating each Message-ID with all 250 list subscribers. VERP has nothing to do with Message-ID, and everything to do with Return-Path and Sender: ;-) -Jim P. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
