[Mailman-Users] Adding a Disclaimer
How do i add a disclaimer within the mailing list. Is there options to add something like this. Is there any suggestions? 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
Re: [Mailman-Users] Adding a Disclaimer
Kim Moodley sent the message below at 02:40 2/8/2007: How do i add a disclaimer within the mailing list. Is there options to add something like this. Is there any suggestions? End original message. - You could add that text to the footer. It seems like the logical place to put it. In the web interface for the list under Non-digest options, edit the msg_footer setting. Under the digest settings, edit the text of digest_footer. 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
[Mailman-Users] Blocking particular domains
hi I had few basic questions about user management in Mailman 1. How do I know when a user registered himself with a mailing list? 2. How do I block particular email ids/emails from a particular domain from becoming subscribers of a list? -- -- B.G. Mahesh http://www.greynium.com/ http://www.oneindia.in/ http://www.click.in/ - Free Indian Classifieds -- 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] mailman user account and login
On 2/4/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: The mailman installation manual seems to imply that the mailman account should be added with no ability to log in to it. I translated what appeared to me to be the sense of the line given to Solaris. As with most daemon accounts.. However, after having gone through several fire drills of resetting file owner from root to mailman, I've set the account up with the directory /usr/local/mailman and NP in the /etc/shadow file. This allows me to su - mailman from root, but not to get a login from anywhere else. This is the same setup as is used for other Solaris blind accounts. I don't see any reason that this would cause alarm. For caveat, see below... Is there any real reason not to use the account this way? I'm aware that Mailman security is based on group identity, not user, but external programs such as htdig running under cron need to have uid mailman in files it writes to or to be set up as a mailman-uid program. My personal preference is to set the needed uid's in the mailman runtime tree. The main concern with this type of setup is that someone might be able to exploit a vulnerability in mailman or htdig or whatever to obtain a login shell for the users they run as. If that login shell is /bin/false, well, they can just do whatever they want (i.e., nothing at all) with that. If it's bash, well- that's another story altogether. Please note: The mailman user shouldn't *need* a valid shell for programs to be running with its privileges. If there's not a reason you need to login (either via su or something else), you're probably better off giving mailman an invalid shell. -- - Patrick Bogen -- 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] Blocking particular domains
BG Mahesh wrote: 1. How do I know when a user registered himself with a mailing list? General Options-admin_notify_mchanges = yes 2. How do I block particular email ids/emails from a particular domain from becoming subscribers of a list? Privacy options...-Subscription rules-ban_list -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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] Moderated postings return error on reason_notice()
Hi, I got a system crush on my linux server, and after I did rescue everything, the following weird problem has appeared. There is no problem with postings of nonmoderated members, but whenever a moderated member sends mail to a list, the message gets lost and following log appears in 'log/error'. Thanks for help. Onur. Feb 08 18:53:37 2007 (1904) Uncaught runner exception: unbound method reason_notice() must be called with ModeratedMemberPost instance as first argument (got nothing instead) Feb 08 18:53:37 2007 (1904) Traceback (most recent call last): File /var/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop self._onefile(msg, msgdata) File /var/mailman/Mailman/Queue/Runner.py, line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /var/mailman/Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /var/mailman/Mailman/Queue/IncomingRunner.py, line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File /var/mailman/Mailman/Handlers/Moderate.py, line 67, in process ModeratedMemberPost) File /var/mailman/Mailman/Handlers/Hold.py, line 216, in hold_for_approval reason = Utils.wrap(exc.reason_notice()) TypeError: unbound method reason_notice() must be called with ModeratedMemberPost instance as first argument (got nothing instead) - Access over 1 million songs - Yahoo! Music Unlimited. -- 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 subscriptions are 'frozen'
I searched the archives for this issue and did not find any relevant messages, so I was hoping someone could help me. We've been running mailman 2.1.4 on Solaris for about 2 years and in the last week the subscription confirmations have seemingly stopped being sent to users. In looking at the subscription log, it's only been able to process 11 new subscriptions today, vs. 5000 pending ones. Now, the 5000+ subscription requests seems odd, since that would match the total number of subscribers to all lists, so I assume those are attempts by spam-subscribers. Do we need to dump out the confirmation queue? Does mailman eventually get full of bad (spam) sign-up attempts? Thanks, Derek -- Derek Cicero Program Manager Solaris Kernel Group, Software Division -- 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] Attachment URL's not working
I've noticed that when I send e-mails with attachments (for example, either an HTML message sent from my gmail account or an attached jpeg) to my test list, I get the following footer blah message -- next part -- An HTML attachment was scrubbed... URL: http://lists.myexamples1.org/pipermail/bylaws/attachments/20070208/866= c1be7/attachment.html The first part of the URL is clickable, the second is not. If I actually combine the two portions of the URL into http://lists.myexamples1.org/pipermail/bylaws/attachments/20070208/866=c1be7/attachment.html and feed it through my web browser, I receive a 404 not found error. On my Apache webserver, this is the appropriate log entry: [Thu Feb 08 10:23:51 2007] [error] [client 128.32.226.135] File does not exist: /var/lib/mailman/archives/public/bylaws/attachments/20070208/866=c1be7 However, if I combine the two halves of the URL and remove the equal sign, so it looks like http://lists.myexamples1.org/pipermail/bylaws/attachments/20070208/866c1be7/attachment.html, then it works. How do I fix my footers so that no equal sign gets injected into the attachment URL, and that the entire URL is clickable? I'm using the following setup: Ubuntu 6.0.6 Mailman 2.1.5 (from Ubuntu repository) Thanks for any help. Michael _ Check out all that glitters with the MSN Entertainment Guide to the Academy Awards® http://movies.msn.com/movies/oscars2007/?icid=ncoscartagline2 -- 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] Attachment URL's not working
Michael Lee wrote: I've noticed that when I send e-mails with attachments (for example, either an HTML message sent from my gmail account or an attached jpeg) to my test list, I get the following footer blah message -- next part -- An HTML attachment was scrubbed... URL: http://lists.myexamples1.org/pipermail/bylaws/attachments/20070208/866= c1be7/attachment.html The first part of the URL is clickable, the second is not. snip How do I fix my footers so that no equal sign gets injected into the attachment URL, and that the entire URL is clickable? This is not a Mailman issue. Apparently, the message you receive is quoted-printable encoded. Among other things, quoted-printable encoding allows long lines to be split by adding an '=' just before the new-line that splits the long line. I.e., the line abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvwxyzabcdefghijkl could be split in a quoted-printable encoding into abcdefghijklmnopqrstuvwxyzabcdefghijklm= nopqrstuvwxyzabcdefghijkl and the user agent that renders the message is supposed to drop the = and the immediately following newline, thus rejoining the two pieces into one long line. Either your MUA (mail client) is not properly understanding the quoted-printable encoding or some other agent in the delivery path from Mailman to you has munged the message. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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] [OT] Adding a Disclaimer
Kim Moodley wrote: How do i add a disclaimer within the mailing list. Is there options to add something like this. Is there any suggestions? Has one of these ever, in any country, stood up in court? I did some research and couldn't find anything conclusive... -- Jay Chandler Network Administrator, Chapman University 714.628.7249 / [EMAIL PROTECTED] Today's Excuse: Too many interrupts -- 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] Mailing List subscriptions are 'frozen'
Derek Cicero wrote: We've been running mailman 2.1.4 on Solaris for about 2 years and in the last week the subscription confirmations have seemingly stopped being sent to users. What is the setting for Privacy options...-Subscription rules-subscribe_policy? Is VirginRunner running? See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.014.htp section 1)b). In looking at the subscription log, it's only been able to process 11 new subscriptions today, vs. 5000 pending ones. Now, the 5000+ subscription requests seems odd, since that would match the total number of subscribers to all lists, so I assume those are attempts by spam-subscribers. What do the log entries say? Do we need to dump out the confirmation queue? Does mailman eventually get full of bad (spam) sign-up attempts? The confirmation cookies expire after mm_cfg.PENDING_REQUEST_LIFE (default 3 days) and are removed. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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] Moderated postings return error on reason_notice()
M. Onur ERGiN wrote: I got a system crush on my linux server, and after I did rescue everything, the following weird problem has appeared. There is no problem with postings of nonmoderated members, but whenever a moderated member sends mail to a list, the message gets lost and following log appears in 'log/error'. snip Feb 08 18:53:37 2007 (1904) Uncaught runner exception: unbound method reason_notice() must be called with ModeratedMemberPost instance as first argument (got nothing instead) Feb 08 18:53:37 2007 (1904) Traceback (most recent call last): File /var/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop self._onefile(msg, msgdata) File /var/mailman/Mailman/Queue/Runner.py, line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /var/mailman/Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /var/mailman/Mailman/Queue/IncomingRunner.py, line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File /var/mailman/Mailman/Handlers/Moderate.py, line 67, in process ModeratedMemberPost) File /var/mailman/Mailman/Handlers/Hold.py, line 216, in hold_for_approval reason = Utils.wrap(exc.reason_notice()) TypeError: unbound method reason_notice() must be called with ModeratedMemberPost instance as first argument (got nothing instead) It seems you probably didn't rescue everything properly. This error in the hold_for_approval() function in Hold.py should not be occurring unless you wound up post-rescue using a pre 2.1.9 Mailman with Python 2.5 At the point of the exception exc is a class ModeratedMemberPost instead of an instance of that class, yet the beginning of hold_for_approval() has if isinstance(exc, ClassType) or isinstance(exc, type(type)): # Go ahead and instantiate it now. exc = exc() or pre Mailman 2.1.9 if type(exc) is ClassType: # Go ahead and instantiate it now. exc = exc() This should render the exception 'impossible' unless you are using a pre 2.1.9 Mailman with Python 2.1.5. If so, I think this is an incompatability. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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] Challenge/response
I have a client who is concerned about his list subscriber addresses being spoofed. In other words someone who knows the addresses of people on the list can set up a mail server and spoof the subscriber so he can post nasty things to the list. He would like to set up a challenge/response mechanism so that when [EMAIL PROTECTED] posts to the list, [EMAIL PROTECTED] gets sent a copy of the message and must confirm that he/she was the sender before it gets posted. I don¹t see any configuration in Mailman for this. Is it possible? BTW, searching the archives at mail-arcihve.com gets a 404 error. -- 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] Moderated postings return error on reason_notice()
Right, I have Mailman 2.1.7 and Python 2.5. Now, should I change the version of Python or Mailman? or, is there anything else better that you could suggest? Thanks, Onur. Mark Sapiro [EMAIL PROTECTED] wrote: M. Onur ERGiN wrote: I got a system crush on my linux server, and after I did rescue everything, the following weird problem has appeared. There is no problem with postings of nonmoderated members, but whenever a moderated member sends mail to a list, the message gets lost and following log appears in 'log/error'. Feb 08 18:53:37 2007 (1904) Uncaught runner exception: unbound method reason_notice() must be called with ModeratedMemberPost instance as first argument (got nothing instead) Feb 08 18:53:37 2007 (1904) Traceback (most recent call last): File /var/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop self._onefile(msg, msgdata) File /var/mailman/Mailman/Queue/Runner.py, line 167, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /var/mailman/Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /var/mailman/Mailman/Queue/IncomingRunner.py, line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File /var/mailman/Mailman/Handlers/Moderate.py, line 67, in process ModeratedMemberPost) File /var/mailman/Mailman/Handlers/Hold.py, line 216, in hold_for_approval reason = Utils.wrap(exc.reason_notice()) TypeError: unbound method reason_notice() must be called with ModeratedMemberPost instance as first argument (got nothing instead) It seems you probably didn't rescue everything properly. This error in the hold_for_approval() function in Hold.py should not be occurring unless you wound up post-rescue using a pre 2.1.9 Mailman with Python 2.5 At the point of the exception exc is a class ModeratedMemberPost instead of an instance of that class, yet the beginning of hold_for_approval() has if isinstance(exc, ClassType) or isinstance(exc, type(type)): # Go ahead and instantiate it now. exc = exc() or pre Mailman 2.1.9 if type(exc) is ClassType: # Go ahead and instantiate it now. exc = exc() This should render the exception 'impossible' unless you are using a pre 2.1.9 Mailman with Python 2.1.5. If so, I think this is an incompatability. -- Mark SapiroThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan - Food fight? Enjoy some healthy debate in the Yahoo! Answers Food Drink QA. -- 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] Challenge/response
On 2/8/07, Bob Morse [EMAIL PROTECTED] wrote: I have a client who is concerned about his list subscriber addresses being spoofed. In other words someone who knows the addresses of people on the list can set up a mail server and spoof the subscriber so he can post nasty things to the list. He would like to set up a challenge/response mechanism so that when [EMAIL PROTECTED] posts to the list, [EMAIL PROTECTED] gets sent a copy of the message and must confirm that he/she was the sender before it gets posted. I don¹t see any configuration in Mailman for this. Is it possible? So far as I know, this isn't possible in Mailman. You'd have to modify the code.. If you think you're up to it, other folk should be able to give you some pointers as to the best way to do this. -- - Patrick Bogen -- 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] Moderated postings return error on reason_notice()
On 2/8/07, M. Onur ERGiN [EMAIL PROTECTED] wrote: Right, I have Mailman 2.1.7 and Python 2.5. Now, should I change the version of Python or Mailman? or, is there anything else better that you could suggest? Upgrading to the newest Mailman is always a good choice. -- - Patrick Bogen -- 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] Moderated postings return error on reason_notice()
Patrick Bogen wrote: On 2/8/07, M. Onur ERGiN [EMAIL PROTECTED] wrote: Right, I have Mailman 2.1.7 and Python 2.5. Now, should I change the version of Python or Mailman? or, is there anything else better that you could suggest? Upgrading to the newest Mailman is always a good choice. Agreed! There are at least 3 modules in pre 2.1.9 Mailman that are not compatable with Python 2.5. The best bet is to upgrade Mailman to 2.1.9, but for your immediate problem, you could download the following three modules from sourceforge and copy them to your installation and restart mailman. The modules/versions you need are: http://mailman.svn.sourceforge.net/viewvc/mailman/branches/Release_2_1-maint/mailman/Mailman/SecurityManager.py?revision=7963pathrev=7963 http://mailman.svn.sourceforge.net/viewvc/mailman/branches/Release_2_1-maint/mailman/Mailman/Utils.py?revision=7963pathrev=7963 and http://mailman.svn.sourceforge.net/viewvc/mailman/branches/Release_2_1-maint/mailman/Mailman/Handlers/Hold.py?revision=7963 -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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] Challenge/response
Bob Morse wrote: BTW, searching the archives at mail-arcihve.com gets a 404 error. I see that too, but that is a www.mail-archive.com issue. We can't do anything about it. See http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq01.018.htp for info on searching http://mail.python.org/pipermail/mailman-users/ with Google. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- 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] Challenge/response
At 1:40 PM -0800 2/8/07, Bob Morse wrote: He would like to set up a challenge/response mechanism so that when [EMAIL PROTECTED] posts to the list, [EMAIL PROTECTED] gets sent a copy of the message and must confirm that he/she was the sender before it gets posted. I don't see any configuration in Mailman for this. Is it possible? Challenge/response is one of the most vile inventions that has ever been applied to the concept of Internet e-mail. I would violently oppose any integration of such features into any project I was involved with. At the very least, you would have to be very, very careful how such a system was created, so as to avoid the problem where the cure is far worse than any possible disease that you might have. -- Brad Knowles [EMAIL PROTECTED], Consultant Author Co-author of SAGE Booklet #15 Internet Postmaster: Duties and Responsibilities Founding Member and Platinum Individual Sponsor of LOPSA: http://www.lopsa.org Papers: http://tinyurl.com/tj6q4 LinkedIn Profile: http://tinyurl.com/y8kpxu -- 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] Challenge/response
Quoting Brad Knowles ([EMAIL PROTECTED]): At 1:40 PM -0800 2/8/07, Bob Morse wrote: He would like to set up a challenge/response mechanism so that when [EMAIL PROTECTED] posts to the list, [EMAIL PROTECTED] gets sent a copy of the message and must confirm that he/she was the sender before it gets posted. I don't see any configuration in Mailman for this. Is it possible? Challenge/response is one of the most vile inventions that has ever been applied to the concept of Internet e-mail. I would violently oppose any integration of such features into any project I was involved with. Somebody should integrate PGP signing into Mailman (as an option) so that you could set it up so when you subscribe to a list you give it your public key, and you can't post to the list unless the message is PGP signed by that key. rant Digital signatures on email is something that is extremely overdue. PGP signatures have been grafted on in a half-assed way, but someday either no mail will travel unless it's been correctly signed or email will disappear as a viable means of communication because of the spam problem. /rant -- Paul Tomblin [EMAIL PROTECTED] http://blog.xcski.com/ Belligerent Design: The theory that life was put on this planet by an external sentient force just to piss me off. - Lore Brand Comics -- 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] Challenge/response
Brad Knowles writes: Challenge/response is one of the most vile inventions that has ever been applied to the concept of Internet e-mail. *chuckle* I wouldn't go so far, since the spam that evoked it is far worse, but I'm steadfastly opposed to challenge-response. If you absolutely *must* do this thing, be prepared to get violent responses and to lose mail from people that you'd really like to get mail from. Now that you're properly warned, I believe that there is a description of how to integrate TMDA, a popular Python-based challenge-response system, into Mailman in the Mailman FAQ wizard. If not, I suppose there would be one on the TMDA home page. -- 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] Challenge/response
I have a client who is concerned about his list subscriber addresses being spoofed. In other words someone who knows the addresses of people on the list can set up a mail server and spoof the subscriber so he can post nasty things to the list. He would like to set up a challenge/response mechanism so that when [EMAIL PROTECTED] posts to the list, [EMAIL PROTECTED] gets sent a copy of the message and must confirm that he/she was the sender before it gets posted. I don¹t see any configuration in Mailman for this. Is it possible? Challenge-response is a well-known spam relay issue, and very undesirable. Mailman privacy options allow you to force moderation of mail purportedly coming from specific addresses You should also investigate methods using your MTA or adding a filter to the mailman address input, and not even think about challenge-response. Hank -- 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
