Re: [Mailman-Users] List email pre-approval
Could this be the problem: When searching for an Approve/Approved header, the first non-whitespace line of the body of the message is also checked, if the body has a MIME type of text/plain. Can your mailclient add the Approve line as a header? On Sat, 2003-02-22 at 21:40, Steve Sterling wrote: With Majordomo, you could pre-approve a message to the list, say from an otherwise unsubscribed user or to a moderated list. I tried with my mailman, but it treats the Approved: password first line as normal message body. Somewhere, I remember seeing that Mailman supports such things, but can't find any documentation on syntax, etc. Can anyone point me the right direction, or is that not a feature? Steve -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] htdig patches and information leakage
At 11:53 22/02/2003, Rupa Schomaker wrote: One can choose to search any archive (even private ones) by constructing the URL correctly. If Short mode one can find subjects for the private list. In Long mode one can find excerpts from the private list. Viewing the actual message requires logging in. I'm addressing the issue raised above in the context of the #444884 patch on sourceforge. If you were not referring to that patch to integrate htdig with MM thanks anyway for highlighting a potential problem. In normal use this problem does not arise as access to the search form for a private list archive is from the list's TOC page which requires authentication by CGI script private.py to access. Also search results are links which go via the CGI script htdig.py which enforces the same rules as private.py But it is possible for a malicious user to bypass the search form on a private list's archive TOC page (and thus avoid logon via the MM private.py CGI script) and construct a URL which will get them search results from a private list's htdig indexes. Thus leakage via the page returned by htsearch, rather than the pages which links on that page point to, is possible. It seems to me that a better solution is to use a proxy cgi-bin program for htsearch that first checks to see if the list is private and if so do the same auth check that the htdig does (just error if not authened) or actually ask for login info... If the user is authenticated or if it is a public list, then just exec the htsearch cgi program. I'll post a revised version of patch #444884 tomorrow that deals with the issue you've raised and provides an update path for existing installations using the patch. -- -rupa -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
auto unsub vs auto no-mail Re: [Mailman-Users] Questions
At 04:51 PM 2/22/03, Jon Carnes wrote: On Fri, 2003-02-21 at 22:59, [EMAIL PROTECTED] wrote: 1. Can this program delete the wrong addresses automatically, where as with aol you have to do it manually? Nothing deletes a wrong address automatically, but if the address bounces too often then Mailman will automatically move the address over to No Mail so that it no longer sends mail to the address. Is this strictly so, under 2.1 (or 2.1.1)? Our list-owners get notices like this: Subject: WIT-L unsubscribe notification To: [EMAIL PROTECTED] [EMAIL PROTECTED] has been removed from WIT-L. And when we look at the membership roster for that list, the address in question will be just gone, not No Mail. In fact our list owners would prefer to only have automatic no-mail, not automatic complete removal. That way they can look into the problem and either correct the address or reactivate it if it was only a temporary problem (though exceeding MM's grace period, I guess). I can't seem to find the settings to turn off automatic full-unsubscribe, while retaining automatic no-mail and owner notification. Short of turning off bounce-processing altogether, that is. Here are the settings under Bounce Processing from one of our lists, where I was trying to prevent full-unsubscribe by trickery with the timing (that is, the combination of bounce_info_stale_after and bounce_you_are_disabled_warnings_interval). Suggestions for better ways of getting this result will be much appreciated. Maybe just raise the threshhold way up? (But the list owners do want to be alerted to bad addresses...) Here are the current settings: bounce_processing: Yes bounce_score_threshold: 5.0 bounce_info_stale_after: 7 bounce_you_are_disabled_warnings: 10 bounce_you_are_disabled_warnings_interval: 8 bounce_unrecognized_goes_to_list_owner: Yes bounce_notify_owner_on_disable: Yes bounce_notify_owner_on_removal: Yes Thanks for your help, Mitch Marks -- Mitchell Marks CUIP Tech Coordinatorhttp://cuip.uchicago.edu CUIP: Chicago Public Schools / Univ. of Chicago Internet Project 5640 S Ellis Ave AAC-045, Univ of Chgo, Chgo IL 60637 Telephone: Ofc 773-702-6041 Fax 702-8212 Home (v.m. only, ok any time) 241-7166 Email: Primary address: [EMAIL PROTECTED] Alternate UofC addresses (use especially to report problems with cuip.uchicago.edu): [EMAIL PROTECTED] and [EMAIL PROTECTED] Off-campus (ISP) address: [EMAIL PROTECTED] The incandescent Dawggies And the flu-o-rescent Katz With their looking-glassy futures And those Samsonited pasts -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Help
1) When we do a test mail and send to the list ( the list is 3 email addresses at screenriter.com) our other screenwriter.com addresses never receive the mail. 2) When we subscribe from the web browser, we receive the email but when the subscriber confirms, he never gets a confirmation email and his name is never in the viewable list. The only names in the list are the three that we put in using the mass list function. Can you tell what is wrong? or what we're doing wrong? Are you sure it's configured properly? we're on a solaris computer at verio .net and we interface with our g4 macintosh using system 9.2.2 thank you for your help -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
FW: [Mailman-Users] List email pre-approval
Thanks to all who have responded. To the questions posed back: a) The pre-approved messages are all text, and the mime-type is set to plain text in the header (I checked on one to be sure!). They are generated from a mailer routine on a website, so are consistent (don't vary from user to user). b) I don't see a parameter I can use in the mailer ASP that will add a line to the header. Will check, as I can appreciate that would be a better way to do it. b) The Approved: password is the first line in the body, which under Majordomo would be stripped. There is no whitespace before the A in approved. The true body of the message then follows on the 2nd line in the message body (no blank line between). c) the password is the Administrator's password for this list. d)Maybe the format of the approval command I am using is incorrect. It is Approved: password . This worked under MajorDomo. Should I use Approve or approve or no colon or no whitespace after the colon or ?? Thanks again to all who have offered help. We will solve this. Main thing, I have confirmation from you all that Mailman should perform this function if I get the format/syntax correct. Steve -Original Message- From: JC Dill [mailto:[EMAIL PROTECTED] Sent: Sunday, February 23, 2003 10:00 AM To: Steve Sterling Cc: Jon Carnes; Mailman users Mailing list Subject: Re: [Mailman-Users] List email pre-approval On Sat, 2003-02-22 at 21:40, Steve Sterling wrote: With Majordomo, you could pre-approve a message to the list, say from an otherwise unsubscribed user or to a moderated list. I tried with my mailman, but it treats the Approved: password first line as normal message body. Somewhere, I remember seeing that Mailman supports such things, but can't find any documentation on syntax, etc. Jon Carnes wrote: Could this be the problem: When searching for an Approve/Approved header, the first non-whitespace line of the body of the message is also checked, if the body has a MIME type of text/plain. Can your mailclient add the Approve line as a header? I suspect the problem is due to sending the message with formatted text (not MIME type text/plain) and *also* using the Approved line as the first line in the body of the message. If you need for non-subscribers to be able to send formatted posts from a client that won't allow adding an Approved header, you can just specify approved posters. The option is found under Privacy Options, Sender Filters, at: ~mailman/admin/listname/privacy/sender Then any message from one of the approved email addresses will be sent on without requiring further approval. ***Warning*** If an email virus which uses email addresses found on a victim's computer manages to grab one of these approved addresses and use it as the From and also coincidentally grabs your mailing list submission address and uses it as the To, your list will accept the virus laden email and distribute the virus to your whole list. This coincidence is not unlikely, since both addresses will be found together in the inbox or address book of your subscribers. One infected subscriber can then infect your whole list. (I have a friend who has a large newsletter list and who has been repeatedly falsely accused of spreading viruses when a virus forged her list address as the From and then sent the virus *directly* to a list subscriber (her subscribers also often know each other directly, thus one subscriber who has the list address in her address book will also have another subscriber's address in her address book too). She is sticking with the Approved header to ensure that it will be more difficult for a virus to manage to forge her approved address and send to her list submission address.) If this list is a distribution list (not a discussion list), you may want to hide the sender address, so that the automatically approved submission addresses are not disclosed to the list recepients. This is the last item under General List Personality at: ~/mailman/admin/listname/general jc -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Help
Check your Mail logs (and the Mailman logs). Sounds like you are running a virtual domain and the Mail setup is not yet working properly. A common problem is to setup a catch-all address for a domain and all mail ends up going there (as opposed to going to one of the Mailman aliases or one of the local users). Good Luck - Jon Carnes On Sat, 2003-02-22 at 16:11, Screenwriters Online wrote: 1) When we do a test mail and send to the list ( the list is 3 email addresses at screenriter.com) our other screenwriter.com addresses never receive the mail. 2) When we subscribe from the web browser, we receive the email but when the subscriber confirms, he never gets a confirmation email and his name is never in the viewable list. The only names in the list are the three that we put in using the mass list function. Can you tell what is wrong? or what we're doing wrong? Are you sure it's configured properly? we're on a solaris computer at verio .net and we interface with our g4 macintosh using system 9.2.2 thank you for your help -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/jonc%40nc.rr.com -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Changing the Member Options Page???
Hello, I have changed the listinfo and user options page from the admin interface, however there is another page I need to change but I can't find the template anywhere. If you go to the listinfo page and click the Unsubscribe or edit options button with nothing in the box, you get a page titled: listname list: member options login page How can I modify this page? [Please CC replies to [EMAIL PROTECTED] Thanks! --ian -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Changing the Member Options Page???
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ian Chilton wrote: I have changed the listinfo and user options page from the admin interface, however there is another page I need to change but I can't find the template anywhere. If you go to the listinfo page and click the Unsubscribe or edit options button with nothing in the box, you get a page titled: listname list: member options login page How can I modify this page? I don't think you can modify this from a simple template. I believe that you'll need to edit ~mailman/Mailman/Cgi/options.py to make changes here. Of course, if I'm mistaken I'm sure that one of the more knowledgeable folks here will set me straight. - -- Todd OpenPGP - KeyID: 0xD654075A | URL: www.pobox.com/~tmz/pgp In America, anybody can be president. That's one of the risks you take. -- Adlai Stevenson (1900-1965) -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) Comment: When crypto is outlawed bayl bhgynjf jvyy unir cevinpl. iD8DBQE+WTnzuv+09NZUB1oRAtWzAJ4iyFiw/J4T6i2UMTJ6H9iTfoLcowCg+Lbq Yc/uhnAQPzCJ+xrJk8MmZjY= =McqM -END PGP SIGNATURE- -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Upgrade from 2.0.x to 2.1.1-- incorrect padding error.
Upgrade from 2.0.x to 2.1.1 has caused the following error during sending digests i suppose. There is a bug about base64 already open. Am I running into the same thing here? As a side note does anyone else think that Mailman has reached a state of perfection in terms of usability/features? I can't imagine it being too much better. Thanks, sumeet.: [EMAIL PROTECTED] root]# /usr/bin/python -S /var/mailman/cron/senddigests Traceback (most recent call last): File /var/mailman/cron/senddigests, line 94, in ? main() File /var/mailman/cron/senddigests, line 86, in main mlist.send_digest_now() File /list/Mailman/Digester.py, line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File /list/Mailman/Handlers/ToDigest.py, line 123, in send_digests send_i18n_digests(mlist, mboxfp) File /list/Mailman/Handlers/ToDigest.py, line 295, in send_i18n_digests msg = scrubber(mlist, msg) File /list/Mailman/Handlers/Scrubber.py, line 252, in process payload = part.get_payload(decode=1) File /list//pythonlib/email/Message.py, line 189, in get_payload return Utils._bdecode(payload) File /list//pythonlib/email/Utils.py, line 75, in _bdecode value = base64.decodestring(s) File /usr/lib/python2.2/base64.py, line 44, in decodestring return binascii.a2b_base64(s) binascii.Error: Incorrect padding Sending relevent logs: Feb 23 11:27:47 2003 (24968) SHUNTING: 1046028467.287553+80336bf6d6db1c808bd7e3bceaa7256b5c4ff 419 Feb 23 11:36:38 2003 (24968) Uncaught runner exception: Incorrect padding Feb 23 11:36:38 2003 (24968) Traceback (most recent call last): File /list//Mailman/Queue/Runner.py, line 105, in _oneloop self._onefile(msg, msgdata) File /list//Mailman/Queue/Runner.py, line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /list//Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /list//Mailman/Queue/IncomingRunner.py, line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File /list//Mailman/Handlers/ToDigest.py, line 82, in process send_digests(mlist, mboxfp) File /list//Mailman/Handlers/ToDigest.py, line 123, in send_digests send_i18n_digests(mlist, mboxfp) File /list//Mailman/Handlers/ToDigest.py, line 295, in send_i18n_digests msg = scrubber(mlist, msg) File /list//Mailman/Handlers/Scrubber.py, line 252, in process payload = part.get_payload(decode=1) File /list//pythonlib/email/Message.py, line 189, in get_payload return Utils._bdecode(payload) File /list//pythonlib/email/Utils.py, line 75, in _bdecode value = base64.decodestring(s) File /usr/src/build/143041-i386/install/usr/lib/python2.2/base64.py, line 44, in decodestr ing return binascii.a2b_base64(s) Error: Incorrect padding Also saw this right under it, but don't think it's related: Feb 23 12:41:11 2003 admin(18322): admin(18322): [- Mailman Version: 2.1.1 -] admin(18322): [- Traceback --] admin(18322): Traceback (most recent call last): admin(18322): File /list/scripts/driver, line 87, in run_main admin(18322): main() admin(18322): File /list/Mailman/Cgi/confirm.py, line 146, in main admin(18322): heldmsg_confirm(mlist, doc, cookie) admin(18322): File /list/Mailman/Cgi/confirm.py, line 590, in heldmsg_confirm admin(18322): ign, sender, msgsubject, ign, ign, ign = mlist.GetRecord(id) admin(18322): File /list/Mailman/ListAdmin.py, line 170, in GetRecord admin(18322): type, data = self.__db[id] admin(18322): KeyError: 1 admin(18322): [- Python Information -] admin(18322): sys.version = 2.2.1 (#1, Aug 30 2002, 12:15:30) [GCC 3.2 20020822 (Red Hat Linux Rawhide 3.2-4)] admin(18322): sys.executable = /usr/bin/python admin(18322): sys.prefix = /usr admin(18322): sys.exec_prefix = /usr admin(18322): sys.path= /usr admin(18322): sys.platform= linux2 admin(18322): [- Environment Variables -] admin(18322): CONTENT_LENGTH: 69 admin(18322): CONTENT_TYPE: application/x-www-form-urlencoded admin(18322): HTTP_COOKIE: ops+admin=2802006961b4583e7328003437643234313634396466613 6316665373033646534393466373437343766326335313566643635; mailman+admin=28020069482e593e732 800303262323139363935666239363036633734663864363135613637643862323738343 86364633433 admin(18322): SCRIPT_FILENAME: /var/mailman/cgi-bin/confirm admin(18322): PYTHONPATH: /list admin(18322): SERVER_SOFTWARE: Apache/2.0.40 (Red Hat Linux) admin(18322): SERVER_ADMIN: [EMAIL PROTECTED] admin(18322): SCRIPT_NAME: /mailman/confirm admin(18322): SERVER_SIGNATURE: addressApache/2.0.40 Server at mailman.vmware.com Port 80 /address admin(18322): admin(18322): REQUEST_METHOD: POST admin(18322): HTTP_HOST: mailman.vmware.com admin(18322): PATH_INFO: /mailman admin(18322): SERVER_PROTOCOL: HTTP/1.1 admin(18322): QUERY_STRING:
Example of bad line break in subject header was Re: [Mailman-Users] Upgrade from 2.0.x to 2.1.1-- incorrect padding error.
I'm enclosing below the full headers from Sumeet P's recent message, as they reached me. This shows the formatting problem discussed last week, mentioned on the Mailman-Users list by Sarah from NOW and seconded by me, and also turned over a little on the Developers list. The discussion on Developers included requests for an example that would reproduce the problem. I don't know if this one will show the same behavior if re-tried on another installation, but here we can at least see it happening someplace we can observe in common. (In case this gets mangled on the way back through, the Subject header as I've received it and pasted below is: first line [Mailman-Users] then second line a Tab and the rest Upgrade from 2.0.x to 2.1.1-- incorrect padding error. ) I've installed the recommended Headers.py patch (and checked that it is /this/ headers.py that is being used), and I thought briefly that the problem was solved for my installation -- but it isn't. I'll quote a subject string that I've seen problems with, but note that whether it's reproducible seems to depend on what list it's going through. Here's the example: [CUIP Activity] NSPTECH 2097 Alex Wilson Wednesday 2003-01-15 OS install/Printer Install. It breaks after the list tag [CUIP Activity], and so do test messages with longish subjects that go through that list. But if I send a message with that same header through a Test list (or any of several others), it doesn't break funny. I'm trying to figure out the differences between the lists, but haven't managed to make the error happen in the Test list by fiddling with Language Options and Personalization. I'm close to ready to just suppress all wrapping in Subjects if that would cure this oddity. Would that be a disaster waiting to happen? How hard would it be (I don't know much about the Mailman python code)? Thanks, Mitch Marks P.S. The point was made in the Developers discussion that Eudora's handling of the newlines in the summary windows may not accord to the relevant standard. Would someone who can speak to this fairly authoritatively feel like sending a report/suggestion in Qualcomm's direction? This is indeed only bothering Eudora users here. (Including me...) The headers for the example passing through Mailman-Users: At 03:23 PM 2/23/03, Sumeet wrote: X-Originating-IP: [65.113.40.130] From: Sumeet [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Sun, 23 Feb 2003 13:23:58 -0800 X-Mailer: Microsoft Outlook Express 5.50.4522.1200 X-OriginalArrivalTime: 23 Feb 2003 21:23:59.0699 (UTC) FILETIME=[E14D2A30:01C2DB81] X-Spam-Status: No, hits=1.4 required=5.0 tests=BODY_PYTHON_ZOPE,FORGED_HOTMAIL_RCVD,FROM_BIGISP,LARGE_HEX,SPAM_PHRAS E_00_01,USER_AGENT_OE X-Spam-Level: * Subject: [Mailman-Users] Upgrade from 2.0.x to 2.1.1-- incorrect padding error. X-BeenThere: [EMAIL PROTECTED] X-Mailman-Version: 2.1.1 List-Id: Mailman mailing list management users mailman-users.python.org List-Unsubscribe: http://mail.python.org/mailman/listinfo/mailman-users, mailto:[EMAIL PROTECTED] List-Archive: http://mail.python.org/pipermail/mailman-users List-Post: mailto:[EMAIL PROTECTED] List-Help: mailto:[EMAIL PROTECTED] List-Subscribe: http://mail.python.org/mailman/listinfo/mailman-users, mailto:[EMAIL PROTECTED] Sender: [EMAIL PROTECTED] -- Mitchell Marks CUIP Tech Coordinatorhttp://cuip.uchicago.edu CUIP: Chicago Public Schools / Univ. of Chicago Internet Project 5640 S Ellis Ave AAC-045, Univ of Chgo, Chgo IL 60637 Telephone: Ofc 773-702-6041 Fax 702-8212 Home (v.m. only, ok any time) 241-7166 Email: Primary address: [EMAIL PROTECTED] Alternate UofC addresses (use especially to report problems with cuip.uchicago.edu): [EMAIL PROTECTED] and [EMAIL PROTECTED] Off-campus (ISP) address: [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] newsletter
Is there a way to keep the email address of a sender from showing up anywhere in the headers of the resulting email? I've got a newsletter with everyone moderated except for one user, who I'd like to be able to post to the list. But if his email address shows up in the email, someone else could forge it and be able to spam the list, couldn't they? Unless there's a way to hide the sender's email address. Is there a better way to handle this without requiring someone to approve a message through the web interface? Thanks, Curt -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Upgrade from 2.0.x to 2.1.1-- incorrect paddingerror.
Try this patch. http://sourceforge.net/tracker/download.php?group_id=103atid=300103file_id=43139aid=670167 Tokio Sumeet wrote: Upgrade from 2.0.x to 2.1.1 has caused the following error during sending digests i suppose. There is a bug about base64 already open. Am I running into the same thing here? As a side note does anyone else think that Mailman has reached a state of perfection in terms of usability/features? I can't imagine it being too much better. Thanks, sumeet.: [EMAIL PROTECTED] root]# /usr/bin/python -S /var/mailman/cron/senddigests Traceback (most recent call last): File /var/mailman/cron/senddigests, line 94, in ? main() File /var/mailman/cron/senddigests, line 86, in main mlist.send_digest_now() File /list/Mailman/Digester.py, line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File /list/Mailman/Handlers/ToDigest.py, line 123, in send_digests send_i18n_digests(mlist, mboxfp) File /list/Mailman/Handlers/ToDigest.py, line 295, in send_i18n_digests msg = scrubber(mlist, msg) File /list/Mailman/Handlers/Scrubber.py, line 252, in process payload = part.get_payload(decode=1) File /list//pythonlib/email/Message.py, line 189, in get_payload return Utils._bdecode(payload) File /list//pythonlib/email/Utils.py, line 75, in _bdecode value = base64.decodestring(s) File /usr/lib/python2.2/base64.py, line 44, in decodestring return binascii.a2b_base64(s) binascii.Error: Incorrect padding Sending relevent logs: Feb 23 11:27:47 2003 (24968) SHUNTING: 1046028467.287553+80336bf6d6db1c808bd7e3bceaa7256b5c4ff 419 Feb 23 11:36:38 2003 (24968) Uncaught runner exception: Incorrect padding Feb 23 11:36:38 2003 (24968) Traceback (most recent call last): File /list//Mailman/Queue/Runner.py, line 105, in _oneloop self._onefile(msg, msgdata) File /list//Mailman/Queue/Runner.py, line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /list//Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /list//Mailman/Queue/IncomingRunner.py, line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File /list//Mailman/Handlers/ToDigest.py, line 82, in process send_digests(mlist, mboxfp) File /list//Mailman/Handlers/ToDigest.py, line 123, in send_digests send_i18n_digests(mlist, mboxfp) File /list//Mailman/Handlers/ToDigest.py, line 295, in send_i18n_digests msg = scrubber(mlist, msg) File /list//Mailman/Handlers/Scrubber.py, line 252, in process payload = part.get_payload(decode=1) File /list//pythonlib/email/Message.py, line 189, in get_payload return Utils._bdecode(payload) File /list//pythonlib/email/Utils.py, line 75, in _bdecode value = base64.decodestring(s) File /usr/src/build/143041-i386/install/usr/lib/python2.2/base64.py, line 44, in decodestr ing return binascii.a2b_base64(s) Error: Incorrect padding -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Archiving doesn't work under Mac OS X 10.1
Editing the sources in the indicated manner (plus adjusting the level
of indentation of the remaining part of the function) indeed works.
Editing i18n.py in the install directory doesn't suffice, however - it
is necessary to edit the file in the distribution directory and then do
a 'make install'. Anyway, thanks for the pointer!
However, should Mailman really require that strptime is defined? As it
is now, archiving doesn't work _at_all_ in Mailman 2.x under Mac OS X
10.1.
/ Peter
On lördag, feb 22, 2003, at 22:36 Europe/Stockholm, Jon Carnes wrote:
The function is used only once in Mailman, inside i18n.py
year, mon, day, hh, mm, ss, wday, ydat, dst = time.strptime(date)
You could easily replace this line of code with a small block that does
the same thing but without referencing the strptime function.
In fact, looking at the code, it looks like there is already an
existing
block that would do this for you... Try deleting the 4 lines of code
that I marked with an *
if isinstance(date, StringType):
try:
*year, mon, day, hh, mm, ss, wday, ydat, dst =
time.strptime(date)
*tzname = time.tzname[dst and 1 or 0]
*except ValueError:
*try:
wday, mon, day, hms, year = date.split()
hh, mm, ss = hms.split(':')
year = int(year)
day = int(day)
hh = int(hh)
mm = int(mm)
ss = int(ss)
except ValueError:
return date
===
If that works then you won't need the time.strptime function at all.
Good Luck - Jon
BTW: good detective work tracing down the lack of strptime function in
Max OSX v10.1!
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Upgrade from 2.0.x to 2.1.1-- incorrectpaddingerror.
i clearly don't know what i'm doing. I did a patch -p1 yourfile on
/tmp/mailman.2.1.1/Mailman/Handlers/Scrubber.py when it asked me for which
file and then recompiled. Can you tell me exactly how to apply this patch?
Thanks alot. I then got:
[EMAIL PROTECTED] mailman-2.1.1]# python -S /list/cron/senddigests
Traceback (most recent call last):
File /list/cron/senddigests, line 94, in ?
main()
File /list/cron/senddigests, line 86, in main
mlist.send_digest_now()
File /list/Mailman/Digester.py, line 60, in send_digest_now
ToDigest.send_digests(self, mboxfp)
File /list/Mailman/Handlers/ToDigest.py, line 123, in send_digests
send_i18n_digests(mlist, mboxfp)
File /list/Mailman/Handlers/ToDigest.py, line 295, in send_i18n_digests
msg = scrubber(mlist, msg)
File /list/Mailman/Handlers/Scrubber.py, line 320, in process
if not t.endswith('\n'):
AttributeError: 'NoneType' object has no attribute 'endswith'
- Original Message -
From: Tokio Kikuchi [EMAIL PROTECTED]
To: Sumeet [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Sunday, February 23, 2003 4:07 PM
Subject: Re: [Mailman-Users] Upgrade from 2.0.x to 2.1.1-- incorrect
paddingerror.
Try this patch.
http://sourceforge.net/tracker/download.php?group_id=103atid=300103file_id
=43139aid=670167
Tokio
Sumeet wrote:
Upgrade from 2.0.x to 2.1.1 has caused the following error during
sending
digests i suppose. There is a bug about base64 already open. Am I
running
into the same thing here?
As a side note does anyone else think that Mailman has reached a state
of
perfection in terms of usability/features? I can't imagine it being too
much
better.
Thanks, sumeet.:
[EMAIL PROTECTED] root]# /usr/bin/python -S /var/mailman/cron/senddigests
Traceback (most recent call last):
File /var/mailman/cron/senddigests, line 94, in ?
main()
File /var/mailman/cron/senddigests, line 86, in main
mlist.send_digest_now()
File /list/Mailman/Digester.py, line 60, in send_digest_now
ToDigest.send_digests(self, mboxfp)
File /list/Mailman/Handlers/ToDigest.py, line 123, in send_digests
send_i18n_digests(mlist, mboxfp)
File /list/Mailman/Handlers/ToDigest.py, line 295, in
send_i18n_digests
msg = scrubber(mlist, msg)
File /list/Mailman/Handlers/Scrubber.py, line 252, in process
payload = part.get_payload(decode=1)
File /list//pythonlib/email/Message.py, line 189, in get_payload
return Utils._bdecode(payload)
File /list//pythonlib/email/Utils.py, line 75, in _bdecode
value = base64.decodestring(s)
File /usr/lib/python2.2/base64.py, line 44, in decodestring
return binascii.a2b_base64(s)
binascii.Error: Incorrect padding
Sending relevent logs:
Feb 23 11:27:47 2003 (24968) SHUNTING:
1046028467.287553+80336bf6d6db1c808bd7e3bceaa7256b5c4ff
419
Feb 23 11:36:38 2003 (24968) Uncaught runner exception: Incorrect
padding
Feb 23 11:36:38 2003 (24968) Traceback (most recent call last):
File /list//Mailman/Queue/Runner.py, line 105, in _oneloop
self._onefile(msg, msgdata)
File /list//Mailman/Queue/Runner.py, line 155, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /list//Mailman/Queue/IncomingRunner.py, line 130, in _dispose
more = self._dopipeline(mlist, msg, msgdata, pipeline)
File /list//Mailman/Queue/IncomingRunner.py, line 153, in
_dopipeline
sys.modules[modname].process(mlist, msg, msgdata)
File /list//Mailman/Handlers/ToDigest.py, line 82, in process
send_digests(mlist, mboxfp)
File /list//Mailman/Handlers/ToDigest.py, line 123, in send_digests
send_i18n_digests(mlist, mboxfp)
File /list//Mailman/Handlers/ToDigest.py, line 295, in
send_i18n_digests
msg = scrubber(mlist, msg)
File /list//Mailman/Handlers/Scrubber.py, line 252, in process
payload = part.get_payload(decode=1)
File /list//pythonlib/email/Message.py, line 189, in get_payload
return Utils._bdecode(payload)
File /list//pythonlib/email/Utils.py, line 75, in _bdecode
value = base64.decodestring(s)
File /usr/src/build/143041-i386/install/usr/lib/python2.2/base64.py,
line 44, in decodestr
ing
return binascii.a2b_base64(s)
Error: Incorrect padding
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Upgrade from 2.0.x to 2.1.1-- incorrectpaddingerror.
I have now uploaded a new patch to fix this error.
Please backout the last patch by mv Scrubber.py.orig Scrubber.py
and apply new patch like this
% patch Scrubber.py.patch.030224.txt
in source/Mailman/Handlers
Then, make install and restart mailman qrunners.
Tokio
sumeet wrote:
i clearly don't know what i'm doing. I did a patch -p1 yourfile on
/tmp/mailman.2.1.1/Mailman/Handlers/Scrubber.py when it asked me for which
file and then recompiled. Can you tell me exactly how to apply this patch?
Thanks alot. I then got:
[EMAIL PROTECTED] mailman-2.1.1]# python -S /list/cron/senddigests
Traceback (most recent call last):
File /list/cron/senddigests, line 94, in ?
main()
File /list/cron/senddigests, line 86, in main
mlist.send_digest_now()
File /list/Mailman/Digester.py, line 60, in send_digest_now
ToDigest.send_digests(self, mboxfp)
File /list/Mailman/Handlers/ToDigest.py, line 123, in send_digests
send_i18n_digests(mlist, mboxfp)
File /list/Mailman/Handlers/ToDigest.py, line 295, in send_i18n_digests
msg = scrubber(mlist, msg)
File /list/Mailman/Handlers/Scrubber.py, line 320, in process
if not t.endswith('\n'):
AttributeError: 'NoneType' object has no attribute 'endswith'
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Upgrade from 2.0.x to 2.1.1-- incorrectpaddingerror.
Oops, I forgot to add pointers.
http://sourceforge.net/tracker/index.php?func=detailaid=670167group_id=103atid=300103
http://sourceforge.net/tracker/download.php?group_id=103atid=300103file_id=43266aid=670167
Tokio Kikuchi wrote:
I have now uploaded a new patch to fix this error.
Please backout the last patch by mv Scrubber.py.orig Scrubber.py
and apply new patch like this
% patch Scrubber.py.patch.030224.txt
in source/Mailman/Handlers
Then, make install and restart mailman qrunners.
Tokio
sumeet wrote:
i clearly don't know what i'm doing. I did a patch -p1 yourfile on
/tmp/mailman.2.1.1/Mailman/Handlers/Scrubber.py when it asked me for
which
file and then recompiled. Can you tell me exactly how to apply this
patch?
Thanks alot. I then got:
[EMAIL PROTECTED] mailman-2.1.1]# python -S /list/cron/senddigests
Traceback (most recent call last):
File /list/cron/senddigests, line 94, in ?
main()
File /list/cron/senddigests, line 86, in main
mlist.send_digest_now()
File /list/Mailman/Digester.py, line 60, in send_digest_now
ToDigest.send_digests(self, mboxfp)
File /list/Mailman/Handlers/ToDigest.py, line 123, in send_digests
send_i18n_digests(mlist, mboxfp)
File /list/Mailman/Handlers/ToDigest.py, line 295, in
send_i18n_digests
msg = scrubber(mlist, msg)
File /list/Mailman/Handlers/Scrubber.py, line 320, in process
if not t.endswith('\n'):
AttributeError: 'NoneType' object has no attribute 'endswith'
--
Mailman-Users mailing list
[EMAIL PROTECTED]
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/
This message was sent to: [EMAIL PROTECTED]
Unsubscribe or change your options at
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: Example of bad line break in subject header was Re:[Mailman-Users]Upgrade from 2.0.x to 2.1.1-- incorrect padding error.
Hi, I've uploaded a new patch. Please try. http://sourceforge.net/tracker/?func=detailaid=687338group_id=25568atid=384680 http://sourceforge.net/tracker/download.php?group_id=25568atid=384680file_id=43260aid=687338 I also recommend to use my version of CookHeaders.py. Looks like it's complicated by more stable than CVS. http://sourceforge.net/tracker/?func=detailaid=601117group_id=103atid=300103 http://sourceforge.net/tracker/download.php?group_id=103atid=300103file_id=42418aid=601117 Tokio Mitchell Marks wrote: I'm enclosing below the full headers from Sumeet P's recent message, as they reached me. This shows the formatting problem discussed last week, mentioned on the Mailman-Users list by Sarah from NOW and seconded by me, and also turned over a little on the Developers list. snip -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: Example of bad line break in subject header wasRe:[Mailman-Users]Upgrade from 2.0.x to 2.1.1-- incorrect padding error.
Wow! Thanks for the really quick turnaround. I appreciate all the help. Also can someone point out the edicate here. I notice many people top posting so i do too. Is that OK? And should I direct my emails to the sender and list? Thanks again. Unfortunately I only got 6 lines down: 18:37:[EMAIL PROTECTED] python -S ~mailman/cron/senddigests Traceback (most recent call last): File /var/mailman/cron/senddigests, line 94, in ? main() File /var/mailman/cron/senddigests, line 86, in main mlist.send_digest_now() File /list/Mailman/Digester.py, line 60, in send_digest_now ToDigest.send_digests(self, mboxfp) File /list/Mailman/Handlers/ToDigest.py, line 123, in send_digests send_i18n_digests(mlist, mboxfp) File /list/Mailman/Handlers/ToDigest.py, line 295, in send_i18n_digests msg = scrubber(mlist, msg) File /list/Mailman/Handlers/Scrubber.py, line 326, in process msg.set_payload(sep.join(text), charset) TypeError: sequence item 2: expected string, NoneType found - Original Message - From: Tokio Kikuchi [EMAIL PROTECTED] To: Mitchell Marks [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] Sent: Sunday, February 23, 2003 5:48 PM Subject: Re: Example of bad line break in subject header was Re:[Mailman-Users]Upgrade from 2.0.x to 2.1.1-- incorrect padding error. Hi, I've uploaded a new patch. Please try. http://sourceforge.net/tracker/?func=detailaid=687338group_id=25568atid=3 84680 http://sourceforge.net/tracker/download.php?group_id=25568atid=384680file_ id=43260aid=687338 I also recommend to use my version of CookHeaders.py. Looks like it's complicated by more stable than CVS. http://sourceforge.net/tracker/?func=detailaid=601117group_id=103atid=300 103 http://sourceforge.net/tracker/download.php?group_id=103atid=300103file_id =42418aid=601117 Tokio Mitchell Marks wrote: I'm enclosing below the full headers from Sumeet P's recent message, as they reached me. This shows the formatting problem discussed last week, mentioned on the Mailman-Users list by Sarah from NOW and seconded by me, and also turned over a little on the Developers list. snip -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/sumeetp%40hotmail.com -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Help with user_optionsurl
Forgive me if I am missing the obvious. I asked this last week and did not see any replies but since I still have not figured it out, I thought I should ask again. I want to personalize the footers in the messages of my lists as described in a post by Jon Carnes on 2/1 and repeated on 2/20 but I find that the variable user_optionsurl uses the hostname from /etc/hosts and not the one that is configured using DEFAULT_URL_HOST or DEFAULT_EMAIL_HOST within mm_cfg.py. Is there a way to change that so that it reflects the preferred hostname? If there is not I will change the name in /etc/hosts but I am trying to avoid that. Paul -- Paul Kleeberg [EMAIL PROTECTED] -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Creating a Broadcast list
I need to create a list ion which no-one can post but the list admin. So I created the list, set it to all users are moderated, moderated posts are rejected, etc. But what is preventing someone from spoofing the list admin's return address and posting to the list? -- ...when you're no longer searching for beauty or love, just some kind of life with the edges taken off. When you can't even define what it is that you're frightened of; this song will be here. -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] further 2.0.x to 2.1.1 issues
looking at this change it kinda breaks the subject line into parts. smart wrapping or something which breaks people's procmail rules. Note the self imposed indentation. do you think it's possible to have the same behaviour as in mailman 2.0? In 2.0 Subject lines are displayed as they show up. Alternatively does anyone have info on migrating from 2.1 to 2.0? thanks sumeet. example: Subject: [build-notify] This an example of broken subject headers. It will break my procmail. -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
