Mailman 3 April 2003 - Mailman-Developers

Re: [Mailman-Developers] Re: Reply-To munging & member_aliases
by Alan K. Stebbens 22 Apr '03

22 Apr '03

TN> The per-member patch that I WOULD like to see added is member_aliases - TN> a list of alternate addresses under which a given member posts. "Address TN> creep" is a daily plague, and it's not adequately answered by creating TN> nomail "ghost members" or stuffing the accept_these_nonmembers pool, TN> because when people leave things get out of sync. If the per-user TN> options screen allowed both user and admin to edit an alias list, and if TN> we wrote a little add_member_alias script, things would go a lot easier. I agree with this suggestion. If you check out "www.topica.com", the following functionality is provided: a. multiple addresses per person b. when a person is subscribed to a list, a submission from *any* of a that person's email aliases is acceptable c. for each subscriber, each list has a designated *primary* distribution address -- one of the subscriber's email aliases I was thinking of hacking Mailman to support this functionality, but was going to first ask if it might already be "in the works". Is it? -- Best regards, Alan K. Stebbens <aks(a)stebbens.org> (Voice/Fax: +1.866.579.0801) Wear me as a seal upon your heart, as a seal upon your arm; for love is strong as death, passion cruel as the grave; it blazes up like blazing fire, fiercer than any flame. -- [Song of Solomon 8:6 (NEB)]

1 0

SMTPServerDisconnected bug
by Michael Meltzer 22 Apr '03

22 Apr '03

I just updated my system, it is a FreeBSD 4.8-stable(Thursday) plus full ports with python 2.2.2, after the upgrade mailman started refusing to deliver any messages, it started with a 2.0.13b4 install that's been good for months and I also tried a clean install of 2.1.1(also reinstalled python 2.2.2 a few times after reading the archives), it a hard failure that happens with all messages. Right now I got the list working using the sendmail method but would like to stop that. Frankly I think it a problem with python 2.2.2 and FreeBSD 4.8-stable, the "latest and greatest", I am not sure of what to do next(not on any python lists). Maybe this might be a heads up of things to come. Any one have an idea what's up, is this a know bug/patch(python/mailman/FreeBSD) or any ideas of a workaround/fix. Happy to supply any information or run any tests, looking for some help please. MJM File "/home/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop self._onefile(msg, msgdata) File "/home/mailman/Mailman/Queue/Runner.py", line 155, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File "/home/mailman/Mailman/Queue/OutgoingRunner.py", line 61, in _dispose self._func(mlist, msg, msgdata) File "/home/mailman/Mailman/Handlers/SMTPDirect.py", line 150, in process conn.quit() File "/home/mailman/Mailman/Handlers/SMTPDirect.py", line 80, in quit self.__conn.quit() File "/usr/local/lib/python2.2/smtplib.py", line 702, in quit self.docmd("quit") File "/usr/local/lib/python2.2/smtplib.py", line 357, in docmd self.putcmd(cmd,args) File "/usr/local/lib/python2.2/smtplib.py", line 313, in putcmd self.send(str) File "/usr/local/lib/python2.2/smtplib.py", line 305, in send raise SMTPServerDisconnected('please run connect() first') SMTPServerDisconnected: please run connect() first Apr 12 03:26:19 2003 (46119) SHUNTING: 1050132199.892874+1248b43fe8a0fd5c91e64db7d3aeed2735c6cbf2

2 6

Re: Reply-To munging & member_aliases
by Tom Neff 22 Apr '03

22 Apr '03

Reality check: Most mailers today already theoretically give users some kind of option over where a reply goes. The problems arise because in the real world, users pay no attention to that stuff. They barely know how to hit Send. So what in the world would delude us into thinking that if we introduced some kind of per-member Reply-To: option, these people would know or bother to use it? They'll never touch it! The only people who will change it are the people who are already savvy enough to direct their replies correctly without it. Also, on lists of the COMET-ANNOUNCE-L variety, where the admin has specifically set a reply policy or reply address, it seems positively harmful to allow individual members to override it. I do not see the usefulness of this per-member patch. The per-member patch that I WOULD like to see added is member_aliases - a list of alternate addresses under which a given member posts. "Address creep" is a daily plague, and it's not adequately answered by creating nomail "ghost members" or stuffing the accept_these_nonmembers pool, because when people leave things get out of sync. If the per-user options screen allowed both user and admin to edit an alias list, and if we wrote a little add_member_alias script, things would go a lot easier.

4 4

suppressing appending of generic welcome message
by Heiko Rommel 22 Apr '03

22 Apr '03

Hi, when sending welcome messages to new subscribees I need a way to suppress the automatically appended " To post to this list, send your email to: alist(a)suse.de General information about the mailing list is at: ... " for some lists. I need this because the mail list (web) server is on an internal network. However, I'd like to make some lists available to the public (via email only). Is there currently a way to accompish that ? Heiko Rommel SuSE Linux AG

1 0

Re: Mailman-Developers English (USA)
by Charlie Clark 22 Apr '03

22 Apr '03

Barry was (w)riting: > Since John, Ken, and I are all American, I think it's only mildly > surprising <wink> that all the source code human readable text, and the > en templates are written in American English. I think there's an oxymoron in there somewhere! as American English != human readable <wink>. Going back to what the real problem with the "language" selection is: a conflation of user interface elements (user-language settings) and the code-page settings. The two things need to be kept separate and both should be configurable. We just had an "interesting" situation where a UTF-8 body gets a plain text MIME attachment for the footer and as we couldn't find a way in Mailman to enforce UTF-8 for the whole mail had to find a work-around outside of Mailman, ie. insert the footer in body. Being able to set the code page for a list would seem to make sense. What are the lists thoughts on this issue? Charlie

1 0

Removing .mo files from cvs
by Barry Warsaw 22 Apr '03

22 Apr '03

I'm strongly considering removing .mo files from cvs and the tar.gz file, possibly for Mailman 2.1.2. - The files can easily be created at build time, even if gettext doesn't exist. We have a pure-Python version of msgfmt - It cuts out about 4MB uncompressed from the tar file - Having .mos makes creating patches more difficult. - It should greatly speed up cvs update. I'd like to know if anybody has objections to this. It would actually make the translation teams job easier since you won't have to worry about building or checking in the .mo files. I have this working in an unchecked in snapshot. Before I commit it I wanted to see if anybody has major objections or can see any flaws. -Barry

3 3

virtual problem with latest CVS
by Mentor Cana 21 Apr '03

21 Apr '03

Hi, I'm trying to setup a virtual domain and it seems like I've gotten the virtual e-mail host to be properly recognized. However, the %(web_page_url) variable still does not get replaced by the virtual host URL. As a result, I'm also not getting the test list with the virtual domain to show on the virtual listinfo (or admin) pages for the virtual domain. I think I've made the proper changes in the mm_cfg.py for the virtual domains. I have the following entries: POSTFIX_STYLE_VIRTUAL_DOMAINS = ['virtual.domain'] add_virtualhost('www.virtual.domain', 'virtual.domain') add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) VIRTUAL_HOST_OVERVIEW = 1 Have I done something wrong? What am I missing? Any help will be greatly appreciated. thanks, Mentor

1 0

Mailman 2.1.2
by Barry Warsaw 21 Apr '03

21 Apr '03

Mailman 2.1.2 is essentially in place in cvs under the Release_2_1_2 tag. I'm going to run this snapshot on python.org until tomorrow, then I'll make the release. Enjoy, -Barry

1 0

Removing add_members -c
by Barry Warsaw 19 Apr '03

19 Apr '03

In bug # 659011, Jost Krieger writes about a privacy leak when using add_members -c. This has prompted me to believe that -c / --changes-msg is an anachronism that should just be removed. While I usually don't like to do this for micro releases, I think in this case it's justified. I won't (yet) delete the convert.txt files, since folks might still want to refer to these. But I'll delete them with the next full release. -Barry http://sourceforge.net/tracker/index.php?func=detail&aid=659011&group_id=10…

1 0

Implicit destination default action RFE
by Todd Green 19 Apr '03

19 Apr '03

Ok, this is driving me bonkers. We get a ton of spam that is sent to our lists as implicit destinations. There is no way to automatically discard these messages under Mailman 2.1.1 (Python 2.2.2 on Solaris9) As an RFE, could a feature be added along the lines of the default handler for posts from non-members so that you can select what do to with mail for implicit destinations? i.e. Under Privacy -> Recipient Filters Action to take for postings to implicit destinations for which no explicit action is defined. (Details for generic_implicit_action) [ ] Accept [ ] Hold [ ] Reject [ ] Discard Right now the there is no option and all mail is held. Thanks, Todd

4 4