Mailman 3 Search results for "ezmlm" - Mailman-Users

Re: [Mailman-Users] Large lists and Postfix

by bruce＠hams.com

From: Dan Delaney <Dionysos(a)Dionysia.org> > Thanks. So, considering the claims made about ezmlm for qmail, does > that have anything to do with ezmlm, or is it qmail that's making > mlm so fast? Ezmlm is a very lightweight mailing list manager, and it adds essentially no overhead to that of qmail. Mailman would add some more overhead, but still not enough to be significant. However, the main overhead of mailing lists is their overhead on _your_time_ to manage them, not the computer. Mailman is very good about reducing _that_ overhead, much better than ezmlm. Ezmlm's main advantage is that it uses the qmail "percent hack" to get reliable information about bounces - the "envelope from" address is different for each recepient, and you can tell who a bouncing message was addressed to by the address the bounce comes to. For example, mail to me would have an envelope From something like this: balloons-owner-bruce%hams.com(a)lists.hams.com If my address bounces, the bounce mail goes to that address, a qmail default rule catches it, and ezmlm decodes bruce%hams.com and realizes that I've had a bounce. It doesn't have to look at the bounce message at all, just the address it goes to. When I get sick of watching undecoded bounces go by, I'll add that "percent hack" feature to Mailman. Thanks Bruce

25 years, 9 months

relaying spam using mailing lists

by Gadi Evron

A friend of mine just wrote about what happened to an ezmlm mailing list he runs, and how it was recently used to relay spam (quoted below). All mailing list managers return bounces of some sort, for subscriptions, unsubscriptions, moderation, etc. (*configuration dependent*), some just quote the subject line though, as an example. Do we risk blocking by black lists for allowing mailing list bounces? Do we in blacklists block spam in bounces? We all see spam bouncing off our lists, how do we distinguish what's what? Especially if these are bounces themselves? How would mailman be vulnerable, if at all? Thanks go to Ellen from spamcop for the help. ----- People tend to think of SPAMers are a bunch of monkeys, i.e. know nothing, utilize off the shelf tools, and completely un-imaginative. I tend to differ, especially after what I saw happen… It began about 3 months ago, our ezmlm mailing list was starting to get a lot of bounces, and when I say a lot, I mean a lot. The number quickly risen to more than 100 per hour, all of them bounces caused by malformed ezmlm requests. These bounces weren’t ordinary, their body was composed of a SPAMed email. You would ask your self, why would someone use ezmlm to bounce emails? well you take our security oriented mailing-list, which has its credibility (both the IP address of the mail server’s credibility and the email address’s credibility) and you utilize it for your spamming needs. In addition, ezmlm will bounce almost any email it receives without thinking, and not only bounce it, but also include the entire incoming email, in our case the SPAM content. Making it a nice to use SPAM relay. After several weeks, our mail server was starting to get blocked by SpamCop, and others which regard bouncing email SPAM as regular SPAM. Several days ago, we decided to put an end to this shenanigan, we patched - yes changed the source code, as ezmlm doesn’t support the suppression of bouncing emails - ezmlm to stop it from sending back emails whenever something bad has happened, and low and behold a few hours after the change was put into place, our ezmlm was no longer being used to relay SPAM. The only option I can conclude from this is that the SPAMers use some-kind of technique (maybe even “SPAM” themselves) to detect whether it is still useful to use your SPAM relay for their needs, in this case our ezmlm configuration, and when it is no longer useful, they “conserve” their bandwidth and move on to their next target. ----- http://blogs.securiteam.com/index.php/archives/353 Gadi.

18 years, 9 months

Email command in Mailman to get by e-mail a message (like ezmlm has)

by Ricardo Dias Marques

Hello, I think this is my post to the Mailman Users mailing list. Hi everyone! :) I supposed this would be a FAQ, but I can't find it in Mailman's web site. My question is: "Is there any email command (or other way) that allows you to be e-mailed a past message (or messages) that was sent to a Mailman managed mailing list?" Browsing the Mailman list archives, I could only find a reference from September 2002 (almost 7 years ago!) from a user (Fernan Aguero) asking the same thing, but not getting a reply: [Mailman-Users] add to whishlist? http://mail.python.org/pipermail/mailman-users/2002-September/022243.html I know that ezmlm has a "-get" command for doing this: EZMAN-0.32: ezmlm Commands http://www.ezmlm.org/ezman/ezman5.html >From that page: ---------------------------------------- -get Get a message or range of messages from the archive. Without argument it returns the messages since the latest digest. To retrieve a range of messages, use list-get.123_234@host(*). At most 100 messages are returned. Without ezmlm-idx, individual messages can still be retrieved by sending mail to list-get.123@host. ---------------------------------------- By reading the list of Mailman commands available in the following web page, it seems that Mailman (still) hasn't a command for doing that: Can I use email commands to interact with the Mailman server? http://www.washington.edu/computing/mailman/faqs/mailman.email.html Am I right? Is there some reason for not including this "get" message functionality in Mailman? Thanks in advance! :) Cheers, Ricardo Dias Marques lists AT ricmarques DOT net

15 years, 5 months

Re: [Mailman-Users] Large lists and Postfix

by Dave Sill

bruce(a)hams.com wrote: >However, the main overhead of mailing lists is their overhead on >_your_time_ to manage them, not the computer. Mailman is very good >about reducing _that_ overhead, much better than ezmlm. I'm a long-time majordomo user who's evaluating alternatives including ezmlm, mailman, and listar. I'd appreciate an explanation of how mailman is better at reducing the list manager's overhead than ezmlm. >Ezmlm's main advantage is that it uses the qmail "percent hack" to get Actually, it's called "VERP" (Variable Envelope Return Path), not "percent hack". The "percenthack" qmail configuration variable turns on user%host@relay style relaying. But your explanation is, otherwise, accurate. >If my address bounces, the bounce mail goes to that address, a qmail default >rule catches it, and ezmlm decodes bruce%hams.com and realizes that I've >had a bounce. It doesn't have to look at the bounce message at all, just >the address it goes to. Right, and the neat thing about this from the user's point of view is that ezmlm keeps track of which messages each recipient bounces so if the problem is temporary, it tells them and they can retrieve the messages from the archive. >When I get sick of watching undecoded bounces go by, I'll add that "percent >hack" feature to Mailman. You really need VERP support in the MTA, otherwise you'll have to inject a copy of each message to each recipient. Right now, qmail is the only MTA I've aware of that does VERP. Venema wants to add it as an option to Postfix, though. -Dave

25 years, 9 months

Re: [Mailman-Users] Moving to mailman from ezmlm

by Jon Carnes

On Mon, 2003-11-03 at 05:21, Daniel S. Reichenbach wrote: > Hi, > > we are currently testing Mailman on our development systems and > really like it. Great work! Right now we use Qmail with the > combination of vpopmail / ezmlm to run our mailing lists. > > We manage a lot of lists for Open Source projects and as of this > mail we are near to 1GB of archived mails. Is there any kind of > script to migrate vom ezmlm to mailman? Especially converting > the archives to mailman would be a great thing. > > Greetings, > Daniel > -- Pipermail (the archiver used in Mailman) creates its html archives from an Mbox style mailbox file. If ezmlm has a similar format, then it's easily done. There are some posts in the Archives about this, so you might want to look there for further information. Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Good Luck - Jon Carnes

21 years, 1 month

Re: [Mailman-Users] Large lists and Postfix

by Dave Sill

bruce(a)hams.com wrote: >Simply because the web interface is excellent, and it allows the user >to do most of their own management easily, I agree that mailman's web interface is excellent. And given the choice between an MLM with an e-mail only interface, and one with a good web interface, too, I'd usually prefer the latter. Unfortunately, it's not always practical for the list server to be co-located with a web server. For example, we have two list servers: one for internal use, and one for internal+external use. The internal server happens to also be our main internal web server. (Yay!) But implementing new CGI's on this system is an exercise in frustration. First you have to request an account on the development system. Then you have to implement and test the CGI on the development system using a CGI wrapper. If you need something python installed on both the development and production systems, that's additional work and delay. (Boo!) The public list server is also an FTP and netnews server, but it's not a web server. It's already got its hands full, so I'm not keen to run a web server there too, but even if I did, I'd have to essentially get a license to run it. More work, paperwork, and delay. So for my immediate need, the web interface is not important. The MLM has to "win" on the basis of its e-mail interface alone. >and the confirmation system >avoids problems with malicious subscription. Majordomo (optionally) and ezmlm (automatically) do this, too. I'm sure listar does, too. This is a must-have feature, these days. >Users don't in general >want to bother the manager if they can solve their own problem with a >button click. Yes, I know other list servers have these features as >optional packages, but in Mailman they are well-integrated. My qmail+majordomo+bounceman set-up requires *very* little owner intervention. The major remaining problem area is people who can't remember their subscription address and therefore can't unsubscribe. Does Mailman have any better way of handling this? That doesn't require the use of the web interface? >Mailman seems to have the best features. I really like the way that >Mailman figures out what host URL it's being called from and presents the >appropriate list choices for that URL. I have the same mailman instance >running on several virtual web sites, and it does not display the lists >of one virtual site when called with another virtual site's host name. Virtual list servers aren't a plus me at the moment. >Ezmlm is too minimal. Are you talking about ezmlm, or ezmlm-idx? Plain old ezmlm is pretty minimal, but the idx package makes it pretty complete--and practically everyone running ezmlm is using ezmlm-idx. It has no web interface, but I like the way it does some things, like moderated lists, especially with multiple moderators. -Dave

25 years, 9 months

Combining mailman and ezmlm

by Irwan Hadi

I use qmail as the MTA, and I've already installed ezmlm to serve domain list.somesite.or.id My question is, can I use mailman too, to serve the mailling list at list.somesite.or.id Because it seems mailman can give easier solution for person who just for the first time follow a mailling list. EZMLM has installed at /list and I have updated the /var/qmail/users/assign to deliver all mail addressed to list.somesite.or.id to /list BTW I read that mailman has smart detection of bounce mail o Smart bounce detection and correction o Integrated fast bulk mailing o Smart spam protection My question is, how this work, since the return-path of, for example this mailling list is Return-Path: <mailman-users-admin(a)python.org> so if mail to subscribers were bounce, then the admin will get the bounce ? ------- AFLHI 058009990407128029/089802---(102598//991024)

24 years, 8 months

migration from ezmlm

by Paul Southworth

Has anyone taken some notes on converting from qmail/ezmlm to mailman? If so, I'd like to hear from you. My biggest concern is handling the listname-subscribe and listname-unsubscribe addresses so I can avoid having to completely reeducate a large subscriber base. With ezmlm, a user can send an empty message to listname-subscribe to be added to a list, or listname-unsubscribe to be removed. From reading the mailman docs, it seems like this feature is missing. If I assume incorrectly, or if anyone has hacked it together, I'd like to hear from you. --Paul

24 years, 3 months

RE: [Mailman-Users] migration from ezmlm

by Gregory Leblanc

> -----Original Message----- > From: Paul Southworth [mailto:pauls@etext.org] > > Has anyone taken some notes on converting from qmail/ezmlm to mailman? > If so, I'd like to hear from you. > > My biggest concern is handling the listname-subscribe and > listname-unsubscribe addresses so I can avoid having to completely > reeducate a large subscriber base. With ezmlm, a user can > send an empty > message to listname-subscribe to be added to a list, or > listname-unsubscribe to be removed. From reading the mailman docs, it > seems like this feature is missing. If I assume incorrectly, > or if anyone > has hacked it together, I'd like to hear from you. Procmail is your friend. :-) As of right now Mailman doesn't have that built in, but it's easy enough to hack something on top. Just make some aliases for listname-subscribe/unsubscribe, and have procmail re-write those messages to send a message to listname-request with subscribe <email> in the message (I can't remember if it's subject or body, maybe it doesn't matter). Greg

24 years, 3 months

Re: [Mailman-Users] Auto-Responses

by Marc MERLIN

On Tue, Nov 06, 2001 at 01:26:04PM -0500, Camille K. Powell wrote: > Thanks, but I hope there's a better way. I just switched from EZMLM to > Mailmain and I never had this problem. The auto-replies used to go to the > person that posted the message, not to the list. Actually both are wrong, auto-replies are supposed to go to the envelope sender, which is the list admin address. Ezmlm is much smarter than mailman for bounce processing since it uses VERP and knows exactly which user bounced. That said, unless you have a list that does reply to munging (forcing the reply-to to the list), auto responses should never ever reach the list, whether you're using ezmlm or mailman If an auto-responder is broken to the point that it answers receipients in the To/Cc fields, you can block the sender, but neither mailman or ezmlm can do anything about it. If you are using reply-to munging, that may be another reason to consider not doing it (but the sending mail server is still at fault) 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

23 years, 1 month

Mailman-Users search results for query "ezmlm"