Re: [Mailman-Users] footer
If you have the ability to patch your Mailman installation, you could add a new variable name (like mlist.fortune) to the ALLOWEDS array in Mailman/Gui/Digest.py and then use the 'withlist' command to set this variable to a new value every so often, and include it in the msg_footer field in your admin interface. Or you could do a more direct brutal patch to search replace a magic string of your choosing (__FORTUNE__ etc) with the output of a random fortune command, right in NonDigest.py . I don't know of any way to do what you want without patching Mailman. -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] spam filtering
--On Wednesday, January 29, 2003 3:47 PM -0800 Robin Rowe [EMAIL PROTECTED] wrote: Can anyone answer my question as asked? Is it possible to use the mailman spam filtering capabilities on message bodies as well as headers? At the risk of garnering another that's not exactly what I asked, a 2.1 patch was posted to Sourceforge to allow this, a couple of months ago. -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] 2nd request: migrating a list from 1.1 to 2.1 hosts?
There seem to be some other threads capturing people's attention, but Barry has logged in and sent mail a couple of times :), so I'm assuming this fell through the cracks. I have some lists on a host running MM1.1, and a new host running MM2.1. I need to move the 1.1 lists over to the new host. Is there a robust way to do this? -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] 2nd request: migrating a list from 1.1 to 2.1hosts?
--On Tuesday, January 28, 2003 5:44 PM -0500 Matthew Davis [EMAIL PROTECTED] wrote: -[ From mailman-2.1/UPGRADING ]- UPGRADING FROM 1.x to 2.x [...] Yes, I read that document (and I've used its advice in the past), unfortunately it doesn't cover my present situation because I'm not really upgrading any existing installation of Mailman. The 1.1 host is going to stay 1.1, and the 2.1 host is already running. I just want to migrate some lists from one to the other. I seem to have a couple of options which I will label A and 2. :) A: Clone the MM1.1 directory somewhere (on either the original or new host) and then upgrade that clone to 2.1. Copy the resulting config into the real 2.1 tree as a new list. (I should probably pre-create the migrated lists on the 2.1 host first, so I can do selective file overwrites without missing some of the structure. The upgraded clone directory can be deleted afterwards. 2: Create a 'template list' on the 2.1 host and dump the configs to text using dumpdb. Back-migrate dumpdb to the 1.1 host and use it to dump the 1.1 list to text. Extract just the member info from the 1.1 dump. Edit it to change numeric flag values (they seem to have changed a bit - no pun intended). Insert the modified member info into the template 2.1 dumps - the rest can be recreated in a few minutes. Use my 'loaddb' add-on to rebuild a working marshal from the modified dump. Go to the admin interface for that list and change list names, policies etc, as needed. A lot can be cut-n-pasted from the two hosts with two browser windows. I hope that the developer(s) understand that with the continued spread of Mailman, situations were listowners need to *migrate*, rather than upgrading in place, will be more common. It would be great to have some kind of robust export capability that was more or less version independent. -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Migrating from 1.1 on one machine to 2.1 on another?
I looked through all the docs and list archives for an answer to this, but didn't find one, so here goes. I have several large active lists on Host A that's running Mailman 1.1. I have a new server, Host B, that's more powerful and the new home, etc, etc, and already has a few active lists running under the latest Mailman 2.1. I want to move the busy lists from Host A/1.1 over to Host B/2.1. I can't just do a list_members and mass add, because there's all sort of flags people have set. I tried running the 2.1 'dumpdb' against the 1.1 config.db and it does produce a readable listing, but I doubt it's importable straight to 2.1. Does anybody have experience with this? Any code that helps? Thanks. I get the Digest, so feel free to Cc or Bcc me on any reply if you want me to see it quicker. -- 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: archive@jab.org Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Re: Web Mail Agents Generate Suspicious Headers?
As Mike says, look at the Privacy options. SquirrelMail is exceptionally well-behaved (I use it myself and recommend it) so I am surprised to see its mails rejected. However, because it is web based and (in the default configuration) runs sendmail to send messages, there is one header you might well see: X-Authentication-Warning: sample.com: apache set sender to [EMAIL PROTECTED] using -f and I suppose someone might be filtering for that. -- 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
[Mailman-Users] is private mail being redirected here?
I am seeing what appears to be a series of one-sided answer posts from [EMAIL PROTECTED] quoting messages that have not previously appeared on the mailman-users list. If this person is redirecting private responses to the list without the correspondent's permission, that's considered rude Net behavior and they should cease. If there is some other technical explanation, perhaps it's a Mailman issue. -- 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
Re: [Mailman-Users] Re: Editability of messages
I will definitely issue an editing patch for 2.1 when it goes gold. Since this is one of their we don't think you should WANT to do this hot-buttons, like controlling the List-* headers, I don't want to issue patches for prerelease versions and encourage them to do any counter-engineering. --On Monday, April 15, 2002 2:09 PM -0700 Marc MERLIN [EMAIL PROTECTED] wrote: On Mon, Apr 15, 2002 at 07:55:01AM -0400, Tom Neff wrote: Billie R. McNamara [EMAIL PROTECTED] wrote: We are using version 2.0.8 for a moderated list. But, we aren't able to edit messages before approving them (for example, to delete just one inappropriate word). How can we do this? There is a FAQ entry that wants you to hand edit various spool files, but you can patch 2.0.8 to allow message editing. I think the patch will be necessary for mailman 2.1, it unfortunately stores the message on disk in a database format, making hand editing on the mm server not that easy. -- 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
Re: [Mailman-Users] Re: Editability of messages
It's difficult to edit message bodies with encoded MIME parts, although one can still edit the headers. For plain text messages, I have found the 2.0.8 patch (which simply places headers and body in separate editable textareas) to be usable. It sure would be nice if someone would make a better textarea editor for Mozilla though! -- 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
[Mailman-Users] Re: Editability of messages
Billie R. McNamara [EMAIL PROTECTED] wrote: We are using version 2.0.8 for a moderated list. But, we aren't able to edit messages before approving them (for example, to delete just one inappropriate word). How can we do this? There is a FAQ entry that wants you to hand edit various spool files, but you can patch 2.0.8 to allow message editing. First, increase ADMINDB_PAGE_TEXT_LIMIT in Mailman/Defaults.py from the default of 4096 to something bigger like 32768 or -1 for unlimited (a huge submission may render slowly in the browser!). Then apply the patch at http://www.panix.com/~tneff/mailman20_edit_patch.gz and you're in business. -- 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
[Mailman-Users] Re: Removing those extra List-* headers
David [EMAIL PROTECTED] wrote: Actually itis the only product that my host offers for mailing lists. It is a damn good program in all respects other than the programmers decision to force this on us and wrongfully cite it as following the standards. The standards make it optional not forced. Hell I like Mailman but just wisk they would change that and stop telling us things that are not true when we ask how to make it work the way we want. Look, I completely agree with you about this major gotcha with Mailman, that its otherwise terrifically brilliant coders happen to have some ideological hobbyhorses they ride - there is no use arguing with them about it. The good news is it's open source, so you can patch your installation as needed. I was concerned to read you were unable to patch out the List-*: behavior. What happened when you tried? Here's a one-byte patch that does it. Assuming you're running Mailman 2.0.8/9, just edit the file $base/Mailman/Handlers/CookHeaders.py and look down at the bottom, where you see an area of code that looks like this: # First we delete any pre-existing headers because the RFC permist only # one copy of each, and we want to be sure it's ours. for h, v in headers.items(): del msg[h] # Wrap these lines if they are too long. 78 character width probably # shouldn't be hardcoded. The adding of 2 is for the colon-space # separator. if len(h) + 2 + len(v) 78: v = string.join(string.split(v, ', '), ',\n\t') msg[h] = v Just change that very last line quoted above to say #msg[h] = v in other words, comment the line out. Save that file, rerun Mailman and you should be all set. -- 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
Re: [Mailman-Users] Re: how to remove List-* headers
--On Friday, March 29, 2002 9:30 PM -0500 Ron Jarrell [EMAIL PROTECTED] wrote: In 2.1 you can go into mm_cfg.py and break RFC2369 compliance by setting ALLOW_RFC2369_OVERRIDES to 1. That'll enable a policy at your site that list owners can turn it off, which will cause the cgi scripts to display that as an option for them. Quite the contrary, RFC2369 says Implementing these fields will be optional. Therefore, by adding a manager's option for those headers instead of trying to force them on everyone, Mailman 2.1 has finally been brought into RFC2369 compliance. Thanks for the reminder on this environment variable, I hadn't reviewed that part of the 2.1 config yet. My patch works under 2.0.8 and similar versions. -- 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
[Mailman-Users] Re: stripping Received: headers
Dan Wilder [EMAIL PROTECTED] wrote: Be aware that not having [Received:] headers will make troubleshooting certain kinds of subscriber problems more difficult. Not an issue for announce-only lists, and maybe not so much an issue for moderated lists, but for others, keep a copy. The simplest way to keep a copy is just to add a file to the alias entry when you create the list, e.g. mylist: /var/spool/lists/mylist,|/home/mailman2/mail/wrapper post mylist Even better would be to keep a big Received Chronicle: mylist: |/usr/local/bin/reformail -c -X Message-Id: -X Received: |sort /var/spool/lists/mylist_recvd,|/usr/local/bin/reformail -I Received: | /home/mailman2/mail/wrapper post mylist That file would contain just the message ID's (or you could use From:) followed by their Received: lines. Tracking down a problem would be relatively easy. You can use one of the log rotater programs to swap these out when they get too big. -- 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
[Mailman-Users] Re: stripping Received: headers
Dmitry Barabanov [EMAIL PROTECTED] wrote: is there any easy way to strip Received: headers from messages that mailman sends to subscribers? There are utilities that are distributed with 'procmail' and/or 'maildrop' that are very useful for this sort of thing, in particular 'formail' and 'reformail'. You can use them to add, remove, and extract headers, and do all sorts of things to scandalize the Mailman developers. :) Procmail: http://www.procmail.org/ Maildrop: http://www.flounder.net/~mrsam/maildrop/ -- 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
