Mailman 3 August 2001 - Mailman-Developers

change PREFIX and VAR-PREFIX directory ...
by Do-Risika RAFIEFERANTSIARONJY 08 Aug '01

08 Aug '01

Hello, Is it possible to change the PREFIX directory after an installation ? In fact, I installed mailman through apt-get/debian and want now to change the --prefix and the --var-prefix directory into /var/mailman. Can I add this line below in mm_cfg.py to do that ? or is there another way ? PREFIX = '/var/mailman' Thanx. -- Do-Risika RAFIEFERANTSIARONJY mailto:do-risika@simicro-internet.mg ~~~~~~~~~~~~~~~~ Simicro Internet Email : simicro(a)simicro.mg Web : http://www.simicro.mg Tel : 261 20 22 648 83 (GMT +3) Fax : 261 20 22 661 83

1 0

2.0.3 email interface custom who command on closed list
by Ben Burnett 08 Aug '01

08 Aug '01

Has anyone hacked the who command for the email interface to work with a closed list? I'm looking for something like: who <password> where password is the list admin password and will also allow the site admin password. If not, maybe I'll give it a go. I'd rather not reinvent the wheel though. Thanks, Ben PS I searched the archives and didn't see anything relevant using the terms: who command closed list. If anyone has ideas for other terms I'm all ears.

1 0

current cvs: no mailman.mo for big5?
by Dan Mick 08 Aug '01

08 Aug '01

The build of the current CVS fails because there's no .mo file corresponding to messages/big5/LC_MESSAGES/mailman.po. The rest of the .mo files are in CVS. Is this something that I can create, somehow, or does Barry have to? Totally-new-to-Python-and-Mailman-I18N'ly yours, Dan

1 0

$12 Investment...$10,000 Return!!!
by ddusa 07 Aug '01

07 Aug '01

THIS IS THE SUPER FAST ONE!!!!! While you're waiting for the others to work, this little gem will put $10,00 in your pockett in as little as two weeks!!..I guarantee it!! Your only cost is a couple hours of your time and $10 or $20. That's it. THE GIFTING CLUB (please take two min. to read this) If you want to make several thousand dollars really quick, then please take two minutes to read and understand the program I am sharing with you. No this is not what you think. You do not have to send $5 to five people to buy a report, receipt, or get their mailing list. Nor will you need to invest more money later to get things going. THIS IS THE FASTEST EASIEST PROGRAM YOU"VE EVER SEEN Complete this in a couple hours and you'll never forget the day you received it. If you are doing other programs, by all means stay with them. The more the merrier...please read on. First, there are only three levels, not four, five or even nine like some other programs. This three level program is much more realistic and much, much faster because it is so easy. The response to this program is VERY HIGH and VERY FAST!! You receive your money in a couple weeks, not a couple months. TRUE STORY: Cindy Allen ran this summation four times last year. The first time she received $3,000 in two weeks and $7,000 the next three weeks. When this program is continued, as it should be, EVERYONE PROFITS!! Don't be afraid to gift a stranger. There's an old saying that gifts will come back to you ten fold. THE DETAILS: You only need to mail out 20 copies, not 200 or more like other programs. Mail them to friends, relatives, poeple who send you their programs, people who you know will continue the process. Even if you're now in another program, stay with it by all means, but do yourself a favor, do this one as well!! It is very simple and takes a very small ( $10 to $20 ) investment. This will be big before the others even trickle in. Just give ONE person $5. That's it!! Follow the simple instructions and in a couple weeks you'll have $10,000 because most people will respond to the low investment high speed and huge profit potential. So lets's help each other by keeping it going!! 1. On a blank piece of paper write your name, address, and email address LEGIBLY and wrap it around a FIVE dollar bill. Send it to the FIRST person on the list below ( #1 ). ONLY THAT PERSON ON THE LIST GETS YOUR NAME AND A $5 BILL!! 2. Retype the list, REMOVE the FIRST NAME ( #1 ) from the list. Move the other two names up and add your name in the ( #3 ) position. 3. If you're using snail mail, make however many copies you're sending out, ( at least 20 ) and send them out today!!! If you're using email, make your initial mailing now and save it. Every time you recieve an opportunity letter, mail them this. There is no more to do. When your name reaches the first position, it will be your turn to collect all your gifts. Can you do it?? Of course you can. Get creative. Each time you recieve a "Get Rich Quick" or "MLM" offer in the mail or your email, respond with THIS LETTER. Your name will climb to the #1 position at dizzying rates. Some of you may want to purchase mailing lists or send out hundreds or even thousands of letters. That's great. The sky really is the limit with this unique GIFTING CLUB. ACT FAST AND GET PAID FAST! Honesty and Integrity make this plan work. Send $5 to the first name only. Remove that name and move the other two up one position. Add your name to position ( #3 ). Copy names and addresses EXACTLY. #1. Daniel Weaver, P.O. Box 7, Clarksburg, MO 65025 #2. S. Denyer, P.O. Box 406, Triangle, VA 22172 #3. Bayberry Store, 114 S. Main #305, Fond du Lac, WI 54935 This is a one time mailing so no need to remove. If you wish we will remove your name from our data base. Type remove in the subject line and email ddusa(a)ziplip.com .

1 0

suggestion for sending monthly reminders
by Marc MERLIN 07 Aug '01

07 Aug '01

So, I have the problem that I obviously get a bunch of bounces every month when the mailing list membership Emails leave. The envelope sender is test-admin(a)lists.sf.net while the header sender is mailman-owner(a)lists.sf.net. Of course, we get a bunch of bounces at the header sender address from MTAs and stupid autoresponders that don't respect basic mail protocols (i.e. automated bounces always go to the envelope sender) Some people have however written back saying that their autoresponder is safe, and that it's ok to bounce back to the header sender as long as the original receipient was listed in To: or Cc: I happen to disagree with that, but unfortunately I've never found an RFC to support my side of the argument. In the meantime, I've written this: http://marc.merlins.org/netrants/autoresponders.txt I am currently unsubscribing on sight any person who bounces back to the header sender because I do not want to see loops on my lists, but I thought that it might be a bit more civil if I sent the membership reminder with a To: field of <mailmanlistsubscriber(a)lists.sf.net> so that if anyone still bounces a mail like this, they can really be removed, and even in some automated way. I had a quick look at the mailman code, and apparently mailpasswd calls other functions so I didn't find a quick way to hack that. 1) Do people agree that optionally not listing the receipient of the reminder in monthly password reminders could be a good thing? 2) I'd also add the receipient in the subject line (i.e. "Password reminder for foobar(a)provider.tld" as many broken autoresponders don't bounce the body and bounce from another address so you have no clue where the bounce came from (they usually are nice enough to leave the subject line mostly intact, so that's sometimes the only way to see who is bouncing) 3) Is there a quick way to hack that in the mm source? Thanks, Marc -- Microsoft is to operating systems & security .... .... what McDonalds is to gourmet cooking Home page: http://marc.merlins.org/ | Finger marc_f(a)merlins.org for PGP key

2 2

First? or Last?
by Kevinmk＠usa.com 07 Aug '01

07 Aug '01

Hello, Are you looking for your first Internet business...or your last? If it's your first, wouldn't you like it to be your last? Your last should be like going home....it should be the one that allows you to double your full time income on a part time basis, is stable, will be there for your heirs, and give you the lifestyle you dream of. May I have your permission to send you a URL link to show you an internet run, rapidly expanding leg in a company that has a 16 year track record, 15 years of double digit growth, no inventory to buy or sell, and whose successful representative have nearly all found this to be the "last" business they needed? Just reply to this letter with "show me" in the subject line and I'll send the link along. (If you'd like to receive additional info by snail mail, please include your full name, address, and phone in the body.) Best Regards, Kevin *To be removed from this list please reply with REMOVE as the Subject*

1 0

Re: [Mailman-Developers] sendmail
by Darrell Fuhriman 05 Aug '01

05 Aug '01

barry(a)zope.com (Barry A. Warsaw) writes: > It would be great if Mailman and Sendmail could play better together. Well, you could include my address sorting patch -- it does help sendmail's performance quite a lot. :-| The onus can't be put solely on sendmail, especially since Mailman could do something of little of little cost but great benefit. That being said, for Mailman, I run sendmail on a second port with only Mailman uses. /usr/lib/sendmail -bd -ODeliveryMode=defer \ -ODaemonPortOptions=Name=Mailman,Port=26 You could also use that to bind only to localhost. The only downside to this method is that messages won't be sent until the queue is run on the normal interval. I run only a couple of relatively low traffic lists, and like the quick turnaround, I myself got around that problem by writing a wrapper around qrunner that runs the queue when qrunner finishes, but only processes things that were put in the queue within the last N minutes (currently fifteen). -- /usr/local/bin/python -S /usr/local/mailman/cron/qrunner exec /usr/lib/sendmail `/usr/local/mailman/bin/qid` > /dev/null -- The qid program is below. The whole thing is a bit kludgey, but it does the right thing. Darrell #!/usr/local/bin/perl # in which we generate a partial sendmail queue identifier for the # current minute. We have just translated this from sendmail's # code. use Time::gmtime; @Base60Code=split('', "0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwx"); foreach $i (0 .. 15) { undef $idbuf; $gm = gmtime(time - ($i*60)); $idbuf .= $Base60Code[$gm->year() % 60]; $idbuf .= $Base60Code[$gm->mon()]; $idbuf .= $Base60Code[$gm->mday()]; $idbuf .= $Base60Code[$gm->hour()]; $idbuf .= $Base60Code[$gm->min()]; print "-qI${idbuf} "; }

1 0

Re: [Mailman-Developers] sendmail
by Dan Mick 04 Aug '01

04 Aug '01

I've come to the conclusion that 1) postfix takes the message no matter what synchronously and queues it, which eliminates a lot of the wait problems, and 2) yes, the validation step can be short-circuited with things like "mynetworks" and "relaydomains" and that set of stuff, and I think the "default" is to allow locally-originated mail to go out without sender-DNS lookups. > Is it possible to configure Postfix this way? That is: "to validate against > J. Random connection coming in to port 25 from whereever in the world, > but if the connection comes from 127.0.0.1, we want it to just basically > shut up and take the message." > > thanks, > Mentor > > On Fri, 3 Aug 2001, at 20:49 -0400, Barry A. Warsaw wrote: > > > > > >>>>> "RJ" == Ron Jarrell <jarrell(a)vt.edu> writes: > > > > RJ> Ok, so the main problem people have with sendmail and mailman > > RJ> is that using the smtpdirect approach with a busy machine > > RJ> costs too much hang time at both the MAIL FROM and the RCPT TO > > RJ> anti-relay/spam testing points, right? And what we want is a > > RJ> way to configure it to continue to validate against J. Random > > RJ> connection coming in to port 25 from whereever in the world, > > RJ> but if the connection comes from 127.0.0.1, we want it to just > > RJ> basically shut up and take the message. > > > > RJ> Does that about sum it up? > > > > Yes, I think so. It would be great if you could communicate with the > > Sendmail folks to make sure that it can be configured this way for > > Mailman sites. I'll offer to help in any way I can, so feel free to > > forward my email to them if necessary. > > > > It would be great if Mailman and Sendmail could play better together. > > > > Thanks, > > -Barry > > > > _______________________________________________ > > Mailman-Developers mailing list > > Mailman-Developers(a)python.org > > http://mail.python.org/mailman/listinfo/mailman-developers > > > > > _______________________________________________ > Mailman-Developers mailing list > Mailman-Developers(a)python.org > http://mail.python.org/mailman/listinfo/mailman-developers

1 0

Two new features, partially cooked
by barry＠zope.com 04 Aug '01

04 Aug '01

I wanted to get this in now so that people can play with them. I will likely be unresponsive to email over the next week to 10 days, so apologies in advance. First, I had a brainstorm about how to do personalized email, at least for regular deliveries. I think this is essentially what people who do announce-only lists feel is missing. It's not really VERP, it's not tied into the bounce detector, and it doesn't (currently) work for digest deliveries, but it does allow you to add headers and footers which have %()s expansions personalized for each recipient. As guessed, personalized lists mean that Mailman makes a copy of the message for each recipient, so it explodes the work being done by #msgs x #recips. The details for the option (look under "Non-digest deliveries") try to explain the implications of turning this on. Note that the site administrator must explicitly enable personalized lists by setting OWNERS_CAN_ENABLE_PERSONALIZATION. Second, I've wormed around the bogus problem with password reminders coming from a random public list. Here's how it currently works: - you must create a "site list" which by default is "mailman", but which you can really give any name as long as you change MAILMAN_SITE_LIST. - For each virtual host, the password reminders look like they're coming from mailman-request@vhost, where "mailman-request" is really MAILMAN_SITE_LIST-request. - MAILMAN_OWNER is gone as a configuration variable. Wherever it was referenced before, Mailman now uses MAILMAN_SITE_LIST, with the host_name coerced to whatever vhost is appropriate (either based on the mailing list the action is being taken on, or the host name as calculated from the web request). This seems to work, and I think is better than the old approach, but it's not perfect. For one thing, MAILMAN_SITE_LIST is just a normal old list; there's nothing special about it except that it's named in MAILMAN_SITE_LIST. Second, we're relying on the, er, feature that listnames share a namespace across vhosts, so MAILMAN_SITE_LIST@vhost1 == MAILMAN_SITE_LIST@vhost2. Post MM2.1, when we have true virtual hosting, this will have to be fixed, and MAILMAN_SITE_LIST will likely be made special. Also, nothing checks to make sure this site list exists, so at the very least the installation docs will have to make it clear you need to create this list (possibly as a way to test your Mailman installation, so that could work fairly well). Anyway, neither feature is ideally implemented, but I think it's the best I can do for now. I know there'll be lots of room for improvement, but I'd like to know if you think these will work for MM2.1 as they are, or if something's fundamentally bolluxed about them. Check-ins coming soon -- I need to eat first! :) Thanks, -Barry

1 0

MM2.1 DemoList
by barry＠zope.com 04 Aug '01

04 Aug '01

I've created a demo list for Mailman 2.1. I'm going to give you the list admin password so you can go in and check out the new admin web pages. See below. A few things to note: - I am not turning on mailmanctl, nor am I installing any of the aliases. This means that the demo list cannot be abused for email, and in fact, no email can reach or leave the list. - If it turns out to be abused anyway, I'll just shut it down. Of course, I trust you guys. :) - At some point, I'll probably decommission this list, and bring up a real demo list, but you'll likely only be able to interact with it from a user point of view. - I really hope you guys will give it a look and send any suggestions or bug reports. I want to very soon start moving toward beta. There are a few more features I want to get in, but I think alpha3 will be the last alpha. I intend to be very strict about feature freeze during the (hopefully short) beta cycle. There's always a cry for more features, from myself included, but at some point you gotta stop or it'll never get released, and I think there are enough good things in the code base now that a new release is warranted. My top priorities during the beta cycle will be 1) fixing bugs; 2) adding a PyUnit test suite; 3) writing documentation; 4) integrating more languages. Enjoy, -Barry http://mail.python.org/mailman-21/admin/demolist password: demolist

6 13