Mailman 3 September 2004 - Mailman-Users

Shunting - Where Did they Go?
by Lloyd F. Tennison Sept. 2, 2004

Sept. 2, 2004

I am re-asking this as it seems I am not the only one with this problem and none of use received an answer. I had a problem and my MTA restart itself automatically. Mailman threw the following error:(SMTP log) Aug 27 04:38:41 2004 (26555) All recipients refused: please run connect() first Aug 27 04:38:41 2004 (26555) All recipients refused: please run connect() first Aug 27 04:38:41 2004 (26555) All recipients refused: please run connect() first For the remainder of the list - about 20,000 emails. I saw files (about six) in the shunt folder. I waited a couple of hours since I thought Mailman would retry (I also stopped and started Mailman) but to no avail. I saw the "unshunt" command and ran it. No errors and it removed the files from the shunt queue - but then nothing happened again. No pick up wgere left off, no nothing. Tried restarting, even recompiling and restarting, but no difference. Since I am assuming they are gone and the only way to recover if to extract sent ones from the log file - what do I do if this ever happens again? Thanks. Lloyd F. Tennison lloyd_tennison(a)whoever.com No trees were harmed in the transmission of this message. However, a rather large number of electrons were temporarily inconvenienced.

1 0

Editing out English / US from HTML render
by demo Sept. 2, 2004

Sept. 2, 2004

Yup, I know it sounds petty and I guess it is just a Scottish thing - or about any reminder of any Imperial Force especially in these rabid Bush/Blair dogs of war days - but; How can I edit off the constant " English / US " references when I am only using one language so that I, and my users, never have to see it? May be " International " would be a better thing to put? [ Been through all the templates ] USUK indeed. Thanks, MA

1 0

Using mailman with dial-up Internet access
by The Admirable Crichton Sept. 2, 2004

Sept. 2, 2004

I understand that it's perfectly possible to use mailman on a server that has only dial-up access to the Internet. However, I'd like to get a firm grasp of the downsides of doing this before I go to the effort of installing it. My setup is this: Linux box running Fetchmail, Postfix, Procmail, Qpopper, Apache. This sits on a LAN and access the net through an ISDN router. My plan was to have list messages go to a POP server at my hosting provided from where I would download them with Fetchmail, which would then forward them to user 'mailman' on this server. Any problem with that? Now, obviously I'm going to lose the web-based features for users, so it's going to be an email-only system. What I'd like to know is how much of a loss that would really be. I can get a list of the features I'd be missing from the manuals etc - what I really want to know is how important people feel this is - ie, a subjective response. Am I really crippling the system this way (and would therefore be better off opening a group on Yahoo), or would I be losing only moderately useful features? All informed opinions would be gratefully received. -- The Admirable Crichton "Born to serve . . ."

1 0

Scripting newlist gives weird errors!
by hesco＠greens.org Sept. 1, 2004

Sept. 1, 2004

Hello: I'm developing a script to automate list creation, particularly alias creation. I'm running into weird errors. All clues are appreciated. Using the mm scripts at a command line as intended seems to work fine. But when I try to call it from a script, it hangs and fails to return cleanly so my script can continue to execute. bash-2.05$ newlist testy hesco(a)greens.org qwerty To finish creating your mailing list, you must edit your /etc/aliases (or equivalent) file by adding the following lines, and possibly running the `newaliases' program: ## testy mailing list testy: "|/home/mailman/mail/mailman post testy" testy-admin: "|/home/mailman/mail/mailman admin testy" testy-bounces: "|/home/mailman/mail/mailman bounces testy" testy-confirm: "|/home/mailman/mail/mailman confirm testy" testy-join: "|/home/mailman/mail/mailman join testy" testy-leave: "|/home/mailman/mail/mailman leave testy" testy-owner: "|/home/mailman/mail/mailman owner testy" testy-request: "|/home/mailman/mail/mailman request testy" testy-subscribe: "|/home/mailman/mail/mailman subscribe testy" testy-unsubscribe: "|/home/mailman/mail/mailman unsubscribe testy" Hit enter to notify testy owner... bash-2.05$ I get the newlist email and everything works as intended. The only problem is that I am not root on this machine. So I have a script set up to install my new aliases, which is run by root crontab on 15 minute intervals. It sweeps them out of aliases.tmp and puts them in /etc/mail/aliases. And I will need to create over a hundred-fifty lists in a couple of weeks which will only be used for a couple of months. So, I'm trying to automate this as much as possible, especially all that alias creation. First the strange errors I get from the python newlist script, then the perl script which invokes newlist to generate these errors. bash-2.05$ ./nl.pl testier hesco(a)greens.org qwerty List = testier Admin = hesco(a)greens.org Password = qwerty Create List Command: /home/mailman/bin/newlist testier hesco(a)greens.org qwerty ^CTraceback (most recent call last): File "/home/mailman/bin/newlist", line 219, in ? bash-2.05$ main() File "/home/mailman/bin/newlist", line 191, in main sys.stdin.readline() KeyboardInterrupt bash-2.05$ The new aliases got created and put into temporary storage. Running $result = `$createlist`; the list got created in the file system. I can browse to the listinfo page. But the email never shows up for the new list's administrator. And the script hangs, instead of successfully completing, so it can re-iterate on the next list it must produce. Only ^C^C breaks it out of its holding pattern on the errors reported above. My test lists started out being called simply test. Only banging my head against this one for the last two hours got them renamed testy and finally testier. #!/usr/local/bin/perl use strict; my ($NEWLIST, $newaliases, $createlist, $result, $args, $usage); my ($newlist, $admin, $pw); $result = `cd /usr/home/hesco`; $NEWLIST = "/home/mailman/bin/newlist"; $usage = usage(); $newlist = $ARGV[0]; $admin = $ARGV[1]; $pw = $ARGV[2]; print "List = $newlist \nAdmin = $admin \nPassword = $pw \n\n"; if (!$newlist || !$admin || !$pw) { print "$usage \n"; exit; return 0; } else { $createlist = "$NEWLIST $newlist $admin $pw"; print "Create List Command: ".$createlist."\n"; $newaliases = newaliases(); # print $newaliases; $result = `/bin/echo \"$newaliases\" >> aliases.tmp`; $result = `$createlist`; print "List created and aliases prepared. \n"; print "Run sudo installaliases.sh to activate aliases and list."; print "\n\n"; exit 1; # return true } sub usage() { $usage = "Usage: ,/nl.pl newlistname admin-email admin-pw \n\n"; return $usage; } sub newaliases() { $newaliases = qq{ \#\# $newlist mailing list $newlist: \\\"|/usr/local/mailman/mail/mailman post $newlist\\\" $newlist-admin: \\\"|/usr/local/mailman/mail/mailman admin $newlist\\\" $newlist-bounces: \\\"|/usr/local/mailman/mail/mailman bounces $newlist\\\" $newlist-confirm: \\\"|/usr/local/mailman/mail/mailman confirm $newlist\\\" $newlist-join: \\\"|/usr/local/mailman/mail/mailman join $newlist\\\" $newlist-leave: \\\"|/usr/local/mailman/mail/mailman leave $newlist\\\" $newlist-owner: \\\"|/usr/local/mailman/mail/mailman owner $newlist\\\" $newlist-request: \\\"|/usr/local/mailman/mail/mailman request $newlist\\\" $newlist-subscribe: \\\"|/usr/local/mailman/mail/mailman subscribe $newlist\\\" $newlist-unsubscribe: \\\"|/usr/local/mailman/mail/mailman unsubscribe $newlist\\\" \n }; return $newaliases; } # END newaliases

5 7

Re: [Mailman-Users] All AOL members not receiving emails
by Paul H Byerly Sept. 1, 2004

Sept. 1, 2004

On 08:12 PM 9/1/2004, mailman-users-request(a)python.org wrote: >My AOL users have also "discovered" our mail in their SPAM folders. I run >both YahooGroups! lists and Mailman lists and it has happened to messages >from both lists as of ~8/26. I can say with confidante that our lists are still getting through to most of our AOL subscribers. Just today I got three list messages reported to AOL as spam, which only happens to mail that make it to their in box (I get a few of these a week). I also have some very chatty ladies lists, and I can assure you I'd have heard about it if they were not getting e-mail. So while there may have been changes, they have not blocked all list mail. I do have full or partial personalization on for most of these lists, which may be a factor. <>< Paul

1 0

Block attachments before testing for non-member
by Ed Greenberg Sept. 1, 2004

Sept. 1, 2004

Many things show up as "mail from non-member" which contain nothing but a forbidden attachment. Can we run through the content filter BEFORE testing for membership so that this cr*p just gets discarded? Thanks, </edg>

3 2

Making Announce Only Lists
by Joseph A. Nagy, Jr. Sept. 1, 2004

Sept. 1, 2004

I need to create an announce only list, so far I've set the moderation bit for /everyone/ on the list except for myself, what else do I need to do? -- AIM: pres CTHULHU | ICQ: 18115568 | Yahoo: pagan_prince Jabber: DarkKnightRadick(a)(jabber.org|amessage.at) | Libertarian @ Large PGP: 0x642F7BDA | < http://groups.yahoo.com/group/tennesseans-for-badnarik/ > < http://mc-luug.homelinux.org/mailman/listinfo/mc-luug >

2 1

All AOL members not receiving emails
by John Sept. 1, 2004

Sept. 1, 2004

Hello, Apologies if this has been answered elsewhere... I searched the archives and didn't find it. Did AOL make some major change affecting Mailman a couple weeks ago? I have a Mailman 2.1.5 list with 46 AOL members, all of whom appear to have stopped receiving list messages. Anyone know anything about this? We haven't gotten any bounces, but have noticed the pattern of AOL subscribers asking us why we cut them off... so we're checking all AOL subscribers on the list and so far not one is receiving. (It's possible that we'll get a bunch of confirmations later, but so far nothing...) Is there some setting we need to tweak? Have been running for years and no problems other than the usual AOL spam controls getting tweaked without the AOL subscriber's knowledge... but before it was always on a case-by-case basis and we got bounces back... Thanks, John 600 member San Diego scuba diving list

5 6

No Date: line in digest header
by Todd K. Watson Sept. 1, 2004

Sept. 1, 2004

I have searched fairly intensively looking for a previously posted answer to my question, but have not turned up anything other than a similar post to this list last year which didn't get a response (see: http://mail.python.org/pipermail/mailman-users/2003-February/026093.html) All list digests created by my install of Mailman-2.1.5 are missing the "Date:" line in the header. Each individual message within the digest has a date line in its header, but the digest itself is missing the Date line. Most MTA's and MUA's inject a Date line, but I'm using Qmail as an MTA -- which doesn't inject one. It seems that it's the job of the MUA (Mailman in this case) to create the Date: line according to RFC-2822. Any help would appreciated! Am I missing something simple here? Todd -- Todd K. Watson Senior Systems and Network Administrator Southwestern University, Georgetown, TX

3 3

E-mail configuration
by s.aslan＠zonnet.nl Sept. 1, 2004

Sept. 1, 2004

Hi, I have intall the mailman and configured it but i can't get receive email from the users. How do i need configure it? Savas -- _____________________________________________________________________ Zon Gratis ADSL. De voordelen van gratis internet met de snelheid van ADSL. Zonder abonnementskosten en zonder vast contract. Je betaalt alleen voor de tijd online. Nu zonder aansluitkosten en met gratis modem. Bestel snel op zonnet.nl.

2 3