Mailman 3 January 2007 - Mailman-coders

[ mailman-Feature Requests-673265 ] Post confirmation + moderation
by SourceForge.net Jan. 5, 2007

Jan. 5, 2007

Feature Requests item #673265, was opened at 2003-01-23 19:39 Message generated for change (Comment added) made by tpetazzoni You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=673265&group_i… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Samuel Tardieu (samtardieu) Assigned to: Nobody/Anonymous (nobody) Summary: Post confirmation + moderation Initial Comment: The following scheme (implemented by me for Sympa as a scenario some time ago) leads to a spam-free mailing-list with almost no work from the moderator. When a mail arrive and should be held for any reason (sender not in subscriber list, list not in to: or cc:, too many recipients), ask the alleged sender to confirm its post then hold it for moderation when the sender confirms its intention to post. This way, spam (whose confirmation request will almost never be answered) is not presented to the moderators, while mail sent by humans will. It would be great to have this feature in mailman. ---------------------------------------------------------------------- Comment By: Thomas Petazzoni (tpetazzoni) Date: 2007-01-06 08:40 Message: Logged In: YES user_id=1145572 Originator: NO I also really would like to see this feature implemented in Mailman. I'm the mailing list moderator of several lists managed by Mailman, and I'm really bored by all the spam I have to delete from the administrative interface. Of course, I could configure the lists to drop e-mails from non-members, but as some of my lists target a public that doesn't really understand the way mailing lists work, I prefer to keep the solution of moderating valid e-mails by hand. Having a mechanism where a e-mail would be send to the sender asking for confirmation would be nice. Sympa has this feature for a long time, but I'd really prefer sticking with Mailman, I like it better. ---------------------------------------------------------------------- Comment By: James Andrewartha (watha) Date: 2006-11-13 03:48 Message: Logged In: YES user_id=460267 http://viewmtn.angrygoats.net/revision/diff/dfedaca2816739f4f052d21247f6877… has an implementation for this, although there's a few other features mixed into the diff as well. ---------------------------------------------------------------------- Comment By: Lucas Nussbaum (lnu) Date: 2006-11-11 11:52 Message: Logged In: YES user_id=527142 Also, this could be implemented in a greylist-like way: the sender would have to confirm his first post, and then, its mails would get auto-accepted for a few hours/days. ---------------------------------------------------------------------- Comment By: Lucas Nussbaum (lnu) Date: 2006-11-11 11:34 Message: Logged In: YES user_id=527142 Hi, This feature would really be great to have in mailman. Additionnally, a web-based confirmation interface could be added, with an image-based confirmation, to prevent robots from auto-confirming their posts. Is it planned ? I'm a bit concerned by the fact that this feature request was posted more than 3 years ago. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=673265&group_i…

1 0

[ mailman-Bugs-1628753 ] Outbound messages have domain fubar'd
by SourceForge.net Jan. 5, 2007

Jan. 5, 2007

Bugs item #1628753, was opened at 2007-01-05 06:18 Message generated for change (Comment added) made by msapiro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1628753&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Michael Reynolds (wshs) Assigned to: Nobody/Anonymous (nobody) Summary: Outbound messages have domain fubar'd Initial Comment: This is using a port install of mailman in FreeBSD, with version 2.1.9_1. When sending messages to users, either triggered by the web interface, or a message from a user to a mailman controlled email address, while using qmail with the included qmail-to-mailman script, the following errors litter my logs: 2007-01-05 07:53:25.924843500 info msg 5348160: bytes 1233 from <sirv-bounces(a)lists.delinked.us> qp 98922 uid 89 2007-01-05 07:53:25.961231500 starting delivery 17: msg 5348160 to remote munged(a)gmail.comyes Note the 'gmail.comyes'. A 'yes' is appended to every outbound message's target domain, thus making delivery impossible. I spent a few days thinking it was something I messed up, so I went through my entire system setup checking everything that could influence mail. I then discovered the problem is specific to mailman. Not sure what info I can provide to help, but I'd be willing to supply upon request. I am using FreeBSD 5.5, Python 2.5. ---------------------------------------------------------------------- >Comment By: Mark Sapiro (msapiro) Date: 2007-01-05 07:11 Message: Logged In: YES user_id=1123998 Originator: NO There are many people using Mailman 2.1.9 and probably several using the FreeBSD port. This is the first report of this issue. It may have something to do with Python 2.5 or perhaps the combination of the FreeBSD port and Python 2.5. The following is an interactive Python snippet (Python responses other than prompts omitted) that sends mail in exactly the same way as Mailman does. If you have changed the assignments of SMTPHOST and/or SMTPPORT in mm_cfg.py, change them here too. Try this and see if the problem exists with it. If so, the problem is with Python, not Mailman. >>> import smtplib >>> msg = """Subject: Test Message ... Message-Id: <some-id(a)nowhere.example.com> ... From: poster(a)example.com ... To: you ... ... The body ... """ >>> rcpts = ['user1(a)example.com', 'userb(a)example.com'] >>> env = 'list-bounces(a)example.com' >>> SMTPHOST = 'localhost' >>> SMTPPORT = 0 >>> x = smtplib.SMTP() >>> x.set_debuglevel(1) >>> x.connect(SMTPHOST, SMTPPORT) >>> x.sendmail(env, rcpts, msg) >>> x.quit() ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1628753&group_…

1 0

[ mailman-Bugs-1628753 ] Outbound messages have domain fubar'd
by SourceForge.net Jan. 5, 2007

Jan. 5, 2007

Bugs item #1628753, was opened at 2007-01-05 09:18 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1628753&group_… Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: mail delivery Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Michael Reynolds (wshs) Assigned to: Nobody/Anonymous (nobody) Summary: Outbound messages have domain fubar'd Initial Comment: This is using a port install of mailman in FreeBSD, with version 2.1.9_1. When sending messages to users, either triggered by the web interface, or a message from a user to a mailman controlled email address, while using qmail with the included qmail-to-mailman script, the following errors litter my logs: 2007-01-05 07:53:25.924843500 info msg 5348160: bytes 1233 from <sirv-bounces(a)lists.delinked.us> qp 98922 uid 89 2007-01-05 07:53:25.961231500 starting delivery 17: msg 5348160 to remote munged(a)gmail.comyes Note the 'gmail.comyes'. A 'yes' is appended to every outbound message's target domain, thus making delivery impossible. I spent a few days thinking it was something I messed up, so I went through my entire system setup checking everything that could influence mail. I then discovered the problem is specific to mailman. Not sure what info I can provide to help, but I'd be willing to supply upon request. I am using FreeBSD 5.5, Python 2.5. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1628753&group_…

1 0

OK
by Juhani Ollikainen Dec. 31, 2006

Dec. 31, 2006

Juhani Ollikainen e-mail. juhani.ollikaineneen(a)dnainternet.net ad.jo(a)dnainternet.net

1 0