Mailman 3 January 2000 - Mailman-Users

Posting-Filter is broken in 1.1 !?
by Aaron Optimizer Digulla 03 Jan '00

03 Jan '00

I have reported these bugs several *months* ago and still got no feedback about them :-( Is anyone ever fixing bugs ? Ok, here they are again: 1. Some posts are held no matter if the poster is subscribed or in the posters list (this is a different bug than #2 !!). 2. Some posts are held because Mailman uses the "Sender:" header item added by Netscape (Mailman should ignore it). 3. When I have a list with the policy "Only subscribed posters can post" set to "Yes" and I set this option to "No", then all posts must be approved manually ! No one can post anymore :-( Is anyone working on these bugs ? If so, can this person please contact me ASAP so we can fix them ? Thanks, -- Dipl. Inf. (FH) Aaron "Optimizer" Digulla "(to) optimize: Make a program faster by improving the algorithms rather than by buying a faster machine."

4 4

Host name this list prefers
by blurr＠txraves.org 03 Jan '00

03 Jan '00

i changed "Host name this list prefers" from www.txraves.org to just txraves.org because i have disabled mail for www.txraves.org -however- i'm still getting administrative emails sent to @www.txraves.org and its choking since i disabled mail for that... i grep'd all the config.db files for www.txraves.org and this is a sample of what i get: Do Whatchya Like # grep -r www.txraves.org lists/* Binary file lists/developers/config.db matches Binary file lists/developers/config.db.last matches Binary file lists/everyone/config.db matches Binary file lists/everyone/config.db.last matches can someone tell me how i can remove -all- references to the old host name from the config.db files? thanks --- -] jordan -] blurr(a)txraves.org -] http://www.txraves.org/~blurr . .. ... s p r e a d t h a v i b e ... .. .

1 0

RH 6.1 Wrapper Erros, Users sent monthy reminders (set not to)
by Garret Krampe 03 Jan '00

03 Jan '00

/var/log/maillog reports: Jan 2 04:19:07 office sendmail[19766]: EAA19766: from=<max_mk(a)yahoo.com>, size=1328, class=0, pri=31328, nrcpts=1, msgid=<20000101201857.25103.qmail(a)web306.mail.yahoo.com>, proto=SMTP, relay=web306.mail.yahoo.com [128.11.68.237] Jan 2 04:19:07 office sendmail[19767]: EAA19767: clone EAA19766, owner=vtun-admin Jan 2 04:19:08 office sendmail[19767]: EAA19767: to="|/home/mailman/mail/wrapper post vtun", delay=00:00:05, xdelay=00:00:01, mailer=prog, stat=Sent Jan 2 04:19:12 office sendmail[19783]: EAA19783: from=<vtun-admin(a)office.satix.net>, size=1885, class=-60, pri=259885, nrcpts=5, msgid=<20000101201857.25103.qmail(a)web306.mail.yahoo.com>, proto=ESMTP, relay=mail@localhost [127.0.0.1] Jan 2 04:19:14 office sendmail[19791]: EAA19791: from=<vtun-admin(a)office.satix.net>, size=1885, class=-60, pri=349885, nrcpts=8, msgid=<20000101201857.25103.qmail(a)web306.mail.yahoo.com>, proto=ESMTP, relay=mail@localhost [127.0.0.1] Jan 2 04:19:14 office sendmail[19790]: EAA19790: from=<vtun-admin(a)office.satix.net>, size=1885, class=-60, pri=379885, nrcpts=9, msgid=<20000101201857.25103.qmail(a)web306.mail.yahoo.com>, proto=ESMTP, relay=mail@localhost [127.0.0.1] Jan 2 04:19:18 office sendmail[19789]: EAA19789: from=<vtun-admin(a)office.satix.net>, size=1885, class=-60, pri=319885, nrcpts=7, msgid=<20000101201857.25103.qmail(a)web306.mail.yahoo.com>, proto=ESMTP, relay=mail@localhost [127.0.0.1] Jan 2 04:19:27 office sendmail[19793]: EAA19783: to=<greg(a)d0gz.net>, delay=00:00:17, xdelay=00:00:15, mailer=esmtp, relay=mail.d0gz.net. [209.48.54.253], stat=Sent (PAA12956 Message accepted for delivery) Also ... I have a list of 3,000 users that should NOT have got mail ! They all did ! "send monthly reminders=no" this happened at 2AM on Jan 1 2000 ... Is this a bugzilla ? Now I browse to the URL and get ... Bug in Mailman version 1.0b9 We're sorry, we hit a bug! If you would like to help us identify the problem, please email a copy of this page to the webmaster for this site with a description of what happened. Thanks! Traceback: Traceback (innermost last): File "/home/mailman/scripts/driver", line 85, in run_main logger = StampedLogger('error', File "/home/mailman/Mailman/Logging/StampedLogger.py", line 48, in __init__ Logger.__init__(self, category, nofail, immediate) File "/home/mailman/Mailman/Logging/Logger.py", line 40, in __init__ self.__get_f() File "/home/mailman/Mailman/Logging/Logger.py", line 63, in __get_f reraise() File "/home/mailman/Mailman/Logging/Logger.py", line 55, in __get_f f = self.__fp = open(self.__filename, 'a+') IOError: (13, 'Permission denied') Environment variables: Variable Value DOCUMENT_ROOT /home/httpd/html HTTP_ACCEPT_ENCODING gzip REMOTE_HOST 203.38.12.10 SERVER_PORT 80 PATH_TRANSLATED /home/httpd/html/vtun REMOTE_ADDR 203.38.12.10 SERVER_SOFTWARE Apache/1.2.6 Red Hat GATEWAY_INTERFACE CGI/1.1 HTTP_ACCEPT_LANGUAGE en REMOTE_PORT 2502 SERVER_NAME office.satix.net HTTP_CONNECTION Keep-Alive HTTP_USER_AGENT Mozilla/4.6 [en] (X11; I; Linux 2.2.5-22 i686) HTTP_ACCEPT_CHARSET iso-8859-1,*,utf-8 HTTP_ACCEPT image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, image/png, */* REQUEST_URI /mailman/listinfo/vtun PATH /sbin:/usr/sbin:/bin:/usr/bin QUERY_STRING SERVER_PROTOCOL HTTP/1.0 PATH_INFO /vtun HTTP_HOST office.satix.net REQUEST_METHOD GET SCRIPT_NAME /mailman/listinfo SERVER_ADMIN garret(a)stix.net SCRIPT_FILENAME /home/mailman/cgi-bin/listinfo PYTHONPATH /home/mailman HTTP_REFERER http://office.satix.net/mailman/listinfo -- Regards, Garret Krampe (Managing Director) --------------------- SATIX Pty Ltd. http://www.satix.net --------------------- ACN 090 976 015 Western Australia "The Satellite Internet Exchange" --------------------- (08) 6278 2649 0412 303 504 Mobile ICQ 11 25 26 11 garret(a)satix.net

1 0

Question about encoding of subject line
by Feng-Cheng Chang 03 Jan '00

03 Jan '00

Hello, I'm currently using mailman under a mainly Chinese e-mail environment. The reflector works great when forwarding the mail to all users. The problem is the mail archiver. When a mail with a Chinese subject line comes in, the archive web page shows the subject like this: [Test] =?big5?B?pKSk5Q==?= Is there any way to solve this problem? I don't think make all users using English subjects is practical...... I have two machines setting up for mailman: 1. Linux (Debian slink) Python 1.5.1 mailman 1.0rc2 2. Linux (Debian potato) Python 1.5.2 mailman 1.1 Both of them have the same problem. If you have any information to solve the problem, please tell me. Thank you. Feng-Cheng

1 0

Y2k bug?
by Paul Tomblin 03 Jan '00

03 Jan '00

I just noticed about 10 of these in my log: Jan 01 10:59:13 2000 post: Traceback (innermost last): post: File "/usr/home/mailman/Mailman/Archiver/Archiver.py", line 237, in Arch iveMail post: h.processUnixMailbox(f, HyperArch.Article) post: File "/usr/home/mailman/Mailman/Archiver/pipermail.py", line 385, in pro cessUnixMailbox post: a=articleClass(m, self.sequence) # Create an article object post: File "/usr/home/mailman/Mailman/Archiver/HyperArch.py", line 242, in __i nit__ post: date=time.mktime(date)-tzoffset post: ValueError: year out of range (00-99, 1900-*) Is this a Y2K error in mailman, or is somebody sending me email with an invalid date? If the latter, will the person sending it get an appropriate bounceback so they can fix it? -- Paul Tomblin, not speaking for anybody. SETI@Home: Finally a *good* way to impress Jodie Foster http://www.setiathome.ssl.berkeley.edu/

1 0

Re: [Mailman-Users] Monthly Reminder Bounce Mail Bomb
by J C Lawrence 02 Jan '00

02 Jan '00

On Sun, 02 Jan 2000 00:06:40 -0500 John A Martin <jam(a)jamux.com> wrote: > How do folks get list owners to delete bad addresses rather than > just mark them "no mail"? I have the list configured to remove them itself. > How do experienced mailman-owners handle bouncing reminders? I use a procmail rule which matches bounces, shovels them off to their own folder, and then have a couple bits of script foo-ery to delete all but the possibly interesting ones (ie almost all of them). > Do experienced mailman-owners encourage reminders? I certainly do. > Is the subscriber account mechanism mentioned on this list likely > to show up any time soon and will it make the bouncing reminders > more manageable? I suspect that it won't change bounce handling in the slightest. Aside: I suspect your real problem is that you were not prepared either personally or at a software level for large mail volumes and did not have built and were not ready to built tools to automate your bounce handlingg for you. If you change that and get yourself into the position where you can handle a couple thousand messages a day (my normal load) as easy as you would handle a couple dozen thousand messages -- which is areally just a question of software automation -- these sorts of problems aren't problems any more but just nudges that you need to tweak things a bit more. Now in your case I suspect that you were manually processing the bounces and unsubscribing them. I had a similar situation on one of my lists where I ran the list as NOMAIL-on-bounce while I got used to MailMan's bounce handling, and then later wanted to move over. My process was simple: 1) I posted to the list that everybody who was set nomail (typically done so that they could post from multiple accounts), to also set themselves as HIDDEN. (Aside: I don't expose the membership lists, ever, so the HIDDEN flag is meaningless). 2) A week later I removed all NOMAIL flags that weren't accompanied by HIDDEN flags and set the list to unsubscribe bouncers. 3) A few days after taht I watched all the automatic unsubscribes roll in and paid them no mind other than letting procmail autofile them to a folder on a per-list basis. Were I not to have hat the ability to mess with the membership base that way (ie I wasn't the list owner, just thge list host), I suspect I would have begged a "pain of a software upgrade" (a white lie), and just removed everybodies NOMAIL flags, posted to the list that this had happened, and then let the MailMan handle it as per normal with unsubscribe-on-bounce. Note: I currently get around 250-300 bounces per day that MailMan doesn't handle yet. I ignore 'em and let procmail file and delete the old ones automatically. -- J C Lawrence Home: claw(a)kanga.nu ----------(*) Other: coder(a)kanga.nu --=| A man is as sane as he is dangerous to his environment |=--

1 0

deleting mail from archive
by paolo pumilia 02 Jan '00

02 Jan '00

Is there a proper way to delete a message from the mailing list archive? Thank you for your help Pol

1 0

Monthly Reminder Bounce Mail Bomb
by John A. Martin 02 Jan '00

02 Jan '00

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 It seems that absent Y2K excitement several of the list owners/administrators at a Mailman 1.1 site conspired instead to mail bomb the mailman-owner by leaving all the bouncing subscription addresses in their lists "no mail" rather than removing them. Though having just completed their conversion from listproc the list administrators were already astute enough to see that mailman-owner would be the only target bombed because Mailman sends the reminders as mailman-owner even when there be only a single list mentioned in the reminder. The bomb would in this instance have been far less effective were reminders mentioning but a single list sent as the owner of the pertinent list. In fact one wonders if the individual list owners were subject to receiving the bounces even just for the reminders mentioning but a single list they might be deterred from the prank. As it is there seems to be little motivation for the list owners to remove bouncing subscriptions as long as they can shield themselves from normal bounces by using "no mail" and be totally immune from the bounces they bomb the mailman-owner with at reminder time. At first this new mailman-owner thought he could deflect the bounces to the list owner(s) by looking at the body of the bounce. But a substantial proportion of bounces did not include the body of the original message and a fair number did not even include the original header. Because the lists had been converted to mailman within the last couple of weeks grepping the current mailman subscribe log told where to deflect the bounces. A few that had been munged by relays and what not took some extra work but it also allowed deflecting one bounce to more than one list when the same bad address was subscribed to several lists that didn't do reminders. Doing this manually took about 14 hours to dispose of about 800 bounces. 620 were from one list with 1618 subscribers and 100 from a list of 438 the remaining 60 bounces were from a handful of lists totaling about 150 subscribers. (The site has about 22,000 subscribers in 50 lists with the largest having 7200 subscribers.) With something over 36 percent of the reminders bouncing one wonders what large mailman sites do? In this case all the reminders went out with a "List-Id" header field referring to the first list (a test list) created by mailman which had nothing whatever to do with any of the reminders sent. What would it hurt to construct a header field showing each list mentioned in the reminder? That might make it easier to do something sensible with the bouncing reminders that include at least the header intact, no? How do folks get list owners to delete bad addresses rather than just mark them "no mail"? How do experienced mailman-owners handle bouncing reminders? Do experienced mailman-owners encourage reminders? Is the subscriber account mechanism mentioned on this list likely to show up any time soon and will it make the bouncing reminders more manageable? jam -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.0 (GNU/Linux) Comment: By Mailcrypt 3.5.4 and Gnu Privacy Guard <http://www.gnupg.org/> iD8DBQE4btyeUEvv1b/iXy8RAlRCAJ9kXk0a7gclvJcts2yGPkOh4jJZ6gCeOhmR T5EYkJisk1WKf8x9eXGb/0U= =FWVn -----END PGP SIGNATURE-----

1 0