[Mailman-Developers] [ mailman-Bugs-663593 ] Traceback when changing email address
Bugs item #663593, was opened at 2003-01-07 11:04 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663593&group_id=103 Category: Web/CGI Group: 2.1 (stable) Status: Open Resolution: None Priority: 5 Submitted By: Daniel Buchmann (avalon) Assigned to: Nobody/Anonymous (nobody) Summary: Traceback when changing email address Initial Comment: I got this traceback when trying to change a member's email address on his options page. His name contained a non-ASCII character, which is probably why this happened. Traceback (most recent call last): File "/home/mailman/scripts/driver", line 87, in run_main main() File "/home/mailman/Mailman/Cgi/options.py", line 269, in main if membername and membername <> oldname: UnicodeError: ASCII decoding error: ordinal not in range(128) -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663593&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Bugs-663675 ] Administrative interface vs. non-standardHTTP ports
Bugs item #663675, was opened at 2003-01-07 11:02
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663675&group_id=103
Category: Web/CGI
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Submitted By: Fabricio Chalub (chalub)
Assigned to: Nobody/Anonymous (nobody)
Summary: Administrative interface vs. non-standard HTTP ports
Initial Comment:
I still find that mailman's administrative interface
behaves incorrectly on HTTPDs running on non-standard
ports. It simply discards the port information out of
the URL, despite DEFAULT_URL* settings.
On some pages, the URL to the FORM ACTION is relative
(eg, the "General Options" form) while others, it is
absolute (eg, the "Membership list").
Looking around the source, I've found lines like this
(on Mailman/Cgi/admin.py)
adminurl = mlist.GetScriptURL('admin', absolute=1)
Changing the value of ABSOLUTE to 0 solved the problem,
and I've found it pretty harmless. Any specific reason
for the ABSOLUTE=1 setting?
--
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=663675&group_id=103
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Patches-645513 ] qmail VERP-enabled delivery handler
Patches item #645513, was opened at 2002-11-29 15:58 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 Category: mail delivery Group: Mailman 2.1 Status: Open Resolution: None Priority: 5 Submitted By: Colin Palmer (tzs) Assigned to: Nobody/Anonymous (nobody) Summary: qmail VERP-enabled delivery handler Initial Comment: This is based on Peter D. Gray's popen-avoiding Sendmail.py module, tweaked so it can use qmail-inject instead of sendmail and ask qmail to do VERP when the message is delivered, which is much faster than getting Mailman to do it at message injection time. You'll need the following in mm_cfg.py: DELIVERY_MODULE = 'Qmail' SENDMAIL_CMD = '/var/qmail/bin/qmail-inject' DO_QMAIL_VERP = 1 -- >Comment By: Colin Palmer (tzs) Date: 2003-01-08 09:46 Message: Logged In: YES user_id=658762 Oops, should have been comparing it's function with 'SMTPDirect' as well as 'Sendmail'... this version should work a lot better. It doesn't support personalisation or mailman-generated VERP headers, but should do everything else now. Read the the comments at the top of the module for things that need to be in mm_cfg.py for it to work. -- Comment By: Ed Lau (edlau) Date: 2002-12-25 13:32 Message: Logged In: YES user_id=675094 Running as listed except DO_QMAIL_VERP = 0, messages don't appear to have the footer tacked on at the bottom. Everything else (header-wise) seems there. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=300103&aid=645513&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] [ mailman-Feature Requests-232489 ] RFE: Option to drop implicitdestination messages
Feature Requests item #232489, was opened at 2001-02-15 19:06 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=232489&group_id=103 Category: configuring/installing Group: None Status: Open Resolution: None Priority: 4 Submitted By: Karsten Thygesen (karthy) Assigned to: Nobody/Anonymous (nobody) Summary: RFE: Option to drop implicit destination messages Initial Comment: Many lists receive huge loads of spam with iimplicit destination (BCc). I would like an option to bounce their postings with information about, that implicit destinations is not allowed and then _not_ inform the administrator of the list. As admin, it is not unusual to receive more than 30 administrative mails pr. list pr. day. When running many lists, this can be quite a burden. -- Comment By: Ken Yap (ken_yap) Date: 2003-01-10 12:28 Message: Logged In: YES user_id=23461 Is this implemented in the latest release? Anybody know? Anyway I found a way around it. I send all admin mail to a webmail mailbox which I check perhaps once a few months. I'm so sick of getting reminded to delete spam that I don't care if some silly subscriber doesn't know the posting rules. -- Comment By: Nobody/Anonymous (nobody) Date: 2002-08-05 00:49 Message: Logged In: NO I second this. For a public list this option is de rigeur. I admin a couple of lists, and with only a couple of exceptions, ALL MAIL with implicit destinations were spam. It's a burden on the admin to have to discard these. To add injury to insult, mailman insists on reminding me every couple of hours to deal with the spam. I don't know why you people didn't think of this long ago. Please, please, please, implement this option, and let the list admin decide if this is the default policy for the list. I have suffered enough. I am capable of implementing the changes required and would have done so, but these are sourceforge lists beyond my control. I asked sourceforge to implement this option and they said it was up to the developers. -- Comment By: Nobody/Anonymous (nobody) Date: 2001-08-14 22:20 Message: Logged In: NO We're getting flooded with this as well on the EROS project lists. I don't think an autorespond is a good idea, but a silent discard would be EXTREMELY useful. It's annoying enough that I've been trying to find the time to dig in to the code... -- Comment By: Thomas Wouters (twouters) Date: 2001-03-03 10:52 Message: Logged In: YES user_id=34209 Moved to feature requests. Could possibly be incorporated into the autoresponder. Note, however, that bouncing spam is usually not a good idea: the from address (both of them) are almost always fake, and sometimes end up in the mailbox(es) of innocent people. I have seen a lot of uucp nodes suffer under that kind of flooding. -- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350103&aid=232489&group_id=103 ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
[Mailman-Developers] What's wrong with the mailman-users archive?
Hi, As of 0900 JST (+0900), http://mail.python.org/pipermail/mailman-users/2003-January/date.html shows 12 messages archived but it also says there are 311 messages. Looks like all the messages before Wed Jan 8 13:55:56 EST 2003 (in January 2003) are gone ! What happened ? Tokio ___ Mailman-Developers mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-developers
