Mailman 3 September 2003 - Mailman-Users

mysterious behaviour
by Duke Sept. 29, 2003

Sept. 29, 2003

I'm running a list where all new users receive a digest by default (I actually submitted a bug about this because they're not set to digest by default when mass subscribing, but that's not really what this is about.) I have the crontab (edited with crontab -e mailman) set to send the digests at 11pm (23:00) every day. However, on this particular list, digests are not being made, and the messages are being sent out to the users as they come in. I went over every user and manually set their digest option (135 users, someone please fix that bug! ;) I also have "digestable" set to "yes". I'm running 2 other lists that aren't having this problem. I looked in the list directory, and there isn't even a digest.mbox being created. Also, what's this attachment scrubbing all about? All the attachments coming through are being scrubbed, but I don't want attachments to be touched at all. I set "filter_content" to "no", but attachments are still being scrubbed. Relating to attachments and html, is there a way I can allow attachments to come through, but have html tags stripped? I see some messages coming through saying "an html attachment was scrubbed..." The message is intact w/out html tags, so what's going on there? Is part of the html stripping process to scrub the attachments, or is the html attachment being scrubbed because all attachments are being scrubbed? Also, is it possible to permit only one user to send attachments (or would this have undesirable effects, such as with html emails?) Basically what I'd like is digests sent at 23:00hrs, html stripped, attachments not scrubbed. I'm using Mailman 2.1.1 (installed by hand), Postfix 2.0.11, Linux kernel 2.4.22, Gentoo Linux distribution, Apache 2.0.47. Thank you in advance! -- Matt. (btw, re: new release 2.1.3, there's no info in the UPGRADING file about going from 2.1.x to 2.1.y.)

1 0

flood of unsubs may be heading your way
by JC Dill Sept. 29, 2003

Sept. 29, 2003

In the default mailman install, a subscription is automatically disabled when mail starts repeatedly bouncing. The subscriber is then emailed a reminder every 4 weeks telling them that they are disabled and that they can re-enable their subscription. After 5 weeks the account is removed (unsubscribed). 5 weeks ago many email boxes started to overflow with virus laden email. So if you notice a sudden flurry of unsubscribes from your mailman hosted lists, it's probably just those inactive email addresses finally being removed from your list roster, 5 weeks later. jc

1 0

Removing Icons
by Atkins, Brian Sept. 29, 2003

Sept. 29, 2003

I'm looking to remove the mailman and other icons that show up at the bottom of the general info, archives, and admin page. I'm not up on Python yet. Has anyone attempted this before? Been successful? Brian

1 0

Is there a patch which improves bulk mailing?
by Wayne Spivak Sept. 29, 2003

Sept. 29, 2003

I have two lists, each with 20,000 names on them. The algorithm Mailman uses, to created the list e-mail, is inefficient. There was a program that was used in conjunction with Majordomo called Bulk-mailer which did a tremendous job. In effect, it bundled addresses based on domain name, and let you limit how many domain names were sent in the same e-mail. This way, on a 20K list, maybe 500 e-mails would go out, but they would do it in a fraction of the time Mailman currently does it (it takes about 6 - 10 hours). Thanks.

1 0

setting as announce-only
by Chris Sept. 29, 2003

Sept. 29, 2003

Hi there, I've created a monster - I moved people from an announcement only list run by a different script to Mailman with posting privilege - and people started screaming! I guess some people don't want to see other postings. How do I set the Mailman so only I have posting privilege? I'd really appreciate your help - I don't want to loose about 1,000 subscribers and also want to reach them all (unlike other script). Thank you, Chris Gozdzik ________________________________________ -Divining Mind Radiesthetic Supplies Quality Pendulums and Divining Rods http://diviningmind.com

1 0

RELEASED Mailman 2.1.3
by barry＠python.org Sept. 29, 2003

Sept. 29, 2003

I have released Mailman 2.1.3, a bug fix release which also contains support for four new languages: Ukrainian, Serbian, Euskara (Basque), and Danish. This release also contains a fix for a cross-site scripting vulnerability in the 'create' cgi script, as well as improved performance of the bounce and outgoing queue runners. I recommend all sites running versions of the 2.1.x line upgrade to the new version. The full source tarball has been made available from the usual sites (although the gnu.org sites have not yet been updated). Sorry, there is no patch available, but you should be able to install 2.1.3 over your existing 2.1.x installation. See http://sourceforge.net/project/showfiles.php?group_id=103 for links to download all the patches and the source tarballs. After installing, be sure you restart your Mailman daemon by doing a "mailmanctl restart". See also: http://www.gnu.org/software/mailman http://www.list.org (not yet updated) http://mailman.sf.net Cheers, -Barry -------------------- snip snip -------------------- 2.1.3 (28-Sep-2003) Performance, Reliability, Security - Closed a cross-site scripting exploit in the create cgi script. - Improvements in the performance of the bounce processor. Now, instead of processing each bounce immediately (which can cause severe lock contention), bounce events are queued. Every 15 minutes by default, the queued bounce events are processed en masse, on a list-per-list basis, so that each list only needs to be locked once. - When some or all of a message's recipients have temporary delivery failures, the message is moved to a "retry" queue. This queue wakes up occasionally and moves the file back to the outgoing queue for attempted redelivery. This should fix most observed OutgoingRunner 100% cpu consumption, especially for bounces to local recipients when using the Postfix MTA. - Optional support for fsync()'ing qfile data after writing. Under some catastrophic system failures (e.g. power lose), it would be possible to lose messages because the data wasn't sync'd to disk. By setting SYNC_AFTER_WRITE to True in Mailman/Queue/Switchboard.py, you can force Mailman to fsync() queue files after flushing them. The benefits are debatable for most operating environments, and you must ensure that your Python has the os.fsync() function defined before enabling this feature (it isn't, even on all Unix-like operating systems). Internationalization - New languages Ukrainian, Serbian, Danish, Euskara/Basque. - Fixes to template lookup. Lists with local overriding templates would find the wrong template. - .mo files (for internationalization) are now generated at build time instead of coming as part of the source distribution. Documentation - A first draft of member documentation by Terri Oda. There is also a Japanese translation of this manual by Ikeda Soji. Archiver / Pipermail - In the configuration variables PUBLIC_EXTERNAL_ARCHIVER, and PRIVATE_EXTERNAL_ARCHIVER, %(hostname)s has been added to the list of allowable substitution variables. - The timezone is now taken into account when figuring the posting date for an article. Scripts / Cron - Fixes to cron/disabled for NotAMemberError crashes. - New script bin/show_qfiles which prints the contents of .pck message files. New script bin/discard which can be used to mass discard held messages. - Fixes to cron/mailpasswds to account for old password-less subscriptions. - bin/list_members has grown two new options: --invalid/-i prints only the addresses in the member database that are invalid (which could have snuck in via old releases); --unicode/-u prints addresses which are stored as Unicode objects instead of as normal strings. Miscellaneous - Fixes to problems in some configurations where Python wouldn't be able to find its standard library. - Fixes to the digest which could cause MIME-losing missing newlines when parts are scrubbed via the content filters. - In the News/Mail gateway admin page, the configuration variable nntp_host can now be a name:port pair. - When messages are pulled from NNTP, the member moderation checks are short-circuited. - email 2.5.4 is included. This fixes an RFC 2231 bug, among possibly others. - Fixed some extra spaces that could appear in the List-ID header. - Fixes to ensure that invalid email addresses can't be invited. - WEB_LINK_COLOR in Defaults.py/mm_cfg.py should now work. - Fixes so that shunted message file names actually match those logged in log/errors. - An improved pending action cookie generation algorithm has been added. - Fixes to the DSN bounce detector. - The usual additional u/i, internationalization, unicode, and other miscellaneous fixes.

1 0

Removing Header from Digest Lists
by Mark T. Valites Sept. 29, 2003

Sept. 29, 2003

(Please cc me in on reply as I am no longer a list member) I'm running MailMan 2.1.2 here at my site. Lately, many of my digested list owners have been whining^hcommenting on how the message header with information on the list gets inserted into the message text before all the digested messages & leads list members to think the digest is junk. I did some quick looking around & wasn't able to find out how to disable this behavior. Some digging through the archives suggested turning off the footer for the message, but this didn't work for me either. Is there a proper way to do this? Thanks in advance, -Mark -- Mark T. Valites Unix Systems Analyst CIT - SUNY Geneseo >--))> >--))>

1 0

admin request sending 4 times
by Denis -- Sept. 29, 2003

Sept. 29, 2003

Hi, I have (since a upgrade to mailman 2.1.1-5) a problem whit the admin request waiting. All messages are send 4 times to the moderator of the list. Some can help me to resolve this problem ? Thanks Denis

1 0

list admins getting bounced
by Guillaume Rousse Sept. 29, 2003

Sept. 29, 2003

I'm both a site admin for a mailman server, and a list admin for several list hosted there. The problem is that as soon as some message posted to one of those list containing a virus is sent to me for approval, it gets refused by my university mail server, and i get unsubscribed of every mailing-list :-( There are two problems here: - for list admins, getting unsubscribed is painful - for users, getting unsubscribed for all lists whereas bounce occured only on one list is also a bit extreme What can i do ? -- What gets you promoted from one rank gets you killed in the next rank -- Murphy's New Military Laws n°17

1 0

Unable to insert header or footer in list post - Help Please
by mroberts＠dairyweb.com.au Sept. 29, 2003

Sept. 29, 2003

Dear list Email posts sent to my mailing lists do not show the header and footer in the received email. I have tried mailing with the (Unaltered from install) default setting in non-digest member settings and then with my own text inserted. Is there a switch to enable these? I am using Mailman 2.0.13-1 on Plesk 6.0.1 (I have tried an upgrade to Mailman 2.1 on a test system but the Plesk system does not allow this to work) Operating system is Redhat 7.3 Can anyone help?

1 0