Re: [Mailman-Users] Mailman-Users Digest, Vol 57, Issue 27
You could set the reply address to the list address - in the web interface. It's shown as deprecated - but works well for me. Jon 2008/11/17 [EMAIL PROTECTED] Send Mailman-Users mailing list submissions to mailman-users@python.org To subscribe or unsubscribe via the World Wide Web, visit http://mail.python.org/mailman/listinfo/mailman-users or, via email, send a message with subject or body 'help' to [EMAIL PROTECTED] You can reach the person managing the list at [EMAIL PROTECTED] When replying, please edit your Subject line so it is more specific than Re: Contents of Mailman-Users digest... Today's Topics: 1. listname-bounces@ (Michael Welch) -- Forwarded message -- From: Michael Welch [EMAIL PROTECTED] To: mailman-users@python.org Date: Sun, 16 Nov 2008 20:42:45 -0800 Subject: [Mailman-Users] listname-bounces@ Hi friends, hoping you can help me out. I am having to do too much work running our lists. Apparently, list members not as knowledgeable as I are looking in the headers for our list address, and accidentally end up using the wrong address. In the header there are at least three instances of the address: [EMAIL PROTECTED] Sender: Return-Path Errors-To: All contain an address that can be too easily mistaken for the list address. That means I end up having to do personal contact with way too many people to let them know that they did not use the correct address, so they need to resend. I notice that this list does not show me the real address in those headers, but rather something like: Sender: [EMAIL PROTECTED] So I would guess that the list admin for this listserver rarely sees users mistaking the Sender: header for the correct address. I am getting pretty tired of this. How can I fix it? This is a hosted list at dreamhost, so I cannot run any commands. If there is an easy cure, I can probably get the host to do it (it would probably have to apply to all their hosted lists, not just mine), but is there something I can do about this? - - - - - - - - - - - - Michael Welch, volunteer Redwood Alliance PO Box 293 Arcata, CA 95518 707-822-7884 [EMAIL PROTECTED] www.redwoodalliance.org -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ -- Jon -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Please trim your replies and edit your subject lines: (was: Re: Mailman-Users Digest, Vol 57, Issue 27)
Jon Hind wrote: You could set the reply address to the list address - in the web interface. It's shown as deprecated - but works well for me. If you're going to reply to a message from one of the digests, please make sure to trim your reply to include just the relevant text and to edit the subject line to match that of the message you replying to. Thank you. -- Brad Knowles [EMAIL PROTECTED] Member of the Python.org Postmaster Team Co-Moderator of the mailman-users and mailman-developers mailing lists -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] listname-bounces@
Michael Welch wrote: That means I end up having to do personal contact with way too many people to let them know that they did not use the correct address, so they need to resend. I notice that this list does not show me the real address in those headers, but rather something like: Sender: [EMAIL PROTECTED] So I would guess that the list admin for this listserver rarely sees users mistaking the Sender: header for the correct address. We get a few people who send to mailman-users-owner thinking that they're posting to the whole list, but I disabuse them of that notion. Over the several years I've been acting as one of the co-owners of this list, I don't recall getting any messages being sent by users to mailman-users-bounces. I am getting pretty tired of this. How can I fix it? You can set up an auto-responder. For the web admin page for your mailing list, go to the Auto-responder section. From there, you can set the auto-responder message for all posts that are sent to the list, and there's a separate auto-responder message that you can create for all messages sent to listname-owner, which should also include all messages sent to listname-bounces. Make sure you check the settings of the various related radio-buttons for these automatic responses, and change them to be more appropriate for your situation if they are not correct. -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] appearance of member list (2.1.9)
Hi, normally (?) the member list shows all members from A to Z at one page. I have seen a list, where a kind of tabs is above it with links A...Z, and only the members with one of these letters are listet at one page. It seems to be not very useful to me, I'd like to change it to the normal appearance. Is it possible? I am not the admin of the server, therefore I can only use the admin frontend. Thanks for hints, Ralph -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] listname-bounces@
Brad Knowles [EMAIL PROTECTED] wrote in reply, in part: Over the several years I've been acting as one of the co-owners of this list, I don't recall getting any messages being sent by users to mailman-users-bounces. I have some Mailman lists, and if a recipient does a reply-all from a BlackBerry device, then the -bounces address is included in the reply. -- Barry S. Finkel Computing and Information Systems Division Argonne National Laboratory Phone:+1 (630) 252-7277 9700 South Cass Avenue Facsimile:+1 (630) 252-4601 Building 222, Room D209 Internet: [EMAIL PROTECTED] Argonne, IL 60439-4828 IBMMAIL: I1004994 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] One private archive not appearing online
The index.html is blank! Not sure how long it's been that way. Is there a way to generate or create a new one? Mark Sapiro wrote: Jewel wrote: I have one list which won't display online the archives. I don't receive any web page error, it's just blank. I also have confirmed the archives are listed in the directory and that I can view them from the command line. I have the correct permissions. What is the content of archives/private/LISTNAME/index.html? Are you just looking at http://www.example.com/mailman/private/LISTNAME, or are you also trying other things such as http://www.example.com/mailman/private/LISTNAME/2008-October? -- Jewel Makda Student Computer Services Coordinator -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] listname-bounces@
Brad Knowles wrote at 09:09 AM 11/17/2008: Michael Welch wrote: That means I end up having to do personal contact with way too many people to let them know that they did not use the correct address, so they need to resend. I notice that this list does not show me the real address in those headers, but rather something like: Sender: [EMAIL PROTECTED] So I would guess that the list admin for this listserver rarely sees users mistaking the Sender: header for the correct address. We get a few people who send to mailman-users-owner thinking that they're posting to the whole list, but I disabuse them of that notion. Over the several years I've been acting as one of the co-owners of this list, I don't recall getting any messages being sent by users to mailman-users-bounces. Right, that must be because this list's Sender: header does not look like a real email address. I wonder why ours are different. I am getting pretty tired of this. How can I fix it? You can set up an auto-responder. For the web admin page for your mailing list, go to the Auto-responder section. From there, you can set the auto-responder message for all posts that are sent to the list, and there's a separate auto-responder message that you can create for all messages sent to listname-owner, which should also include all messages sent to listname-bounces. That does not work, I assume because the message to -owner is coming from -bounces and not from the original list member. So an autoresponder would be sent back to -bounces, which might actually create an endless loop (though I imagine Mailman traps for that). - - - - - - - - - - - - Michael Welch, volunteer Redwood Alliance PO Box 293 Arcata, CA 95518 707-822-7884 [EMAIL PROTECTED] www.redwoodalliance.org -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] listname-bounces@
Michael Welch wrote: That does not work, I assume because the message to -owner is coming from -bounces and not from the original list member. So an autoresponder would be sent back to -bounces, which might actually create an endless loop (though I imagine Mailman traps for that). You are correct, Mailman should trap for that. This means that there's no harm in testing out the feature yourself, just to see what happens. If it works, you're done. If not, then no harm should be done, and we can explore other possibilities. -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] listname-bounces@
Hi Brad. I did test it, hence That does not work. But I do appreciate the reminder, because I had intended to populate that particular autoresponder. Brad Knowles wrote at 11:09 AM 11/17/2008: Michael Welch wrote: That does not work, I assume because the message to -owner is coming from -bounces and not from the original list member. So an autoresponder would be sent back to -bounces, which might actually create an endless loop (though I imagine Mailman traps for that). You are correct, Mailman should trap for that. This means that there's no harm in testing out the feature yourself, just to see what happens. If it works, you're done. If not, then no harm should be done, and we can explore other possibilities. - - - - - - - - - - - - Michael Welch, volunteer Redwood Alliance PO Box 293 Arcata, CA 95518 707-822-7884 [EMAIL PROTECTED] www.redwoodalliance.org -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] listname-bounces@
Michael Welch wrote: Hi Brad. I did test it, hence That does not work. Ahh, sorry. It wasn't clear to me that you had actually tested it or not. My bad. But I do appreciate the reminder, because I had intended to populate that particular autoresponder. And thanks to your note, I have more fully populated the auto-responder for mailman-users-owner and mailman-users-request, too. I'm sorry this has not yet solved your problem, but I do appreciate the opportunity to improve our own configuration even more. Thanks! -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Securing My Mailman Lists
Hello all, I have inherited a Mac Xserve server running Mailman from a support person that is no longer employed at our school. I have changed the Admin password on the server, and also changed (or thought I did) the Admin passwords for the Mailman lists as well. The old admin password is still working for theses lists. How can I completely remove this old password? Any help is appreciated. Jeff -- Jeff Bernier E-mail Administrator Rhode Island School of Design 401.454.6168 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] listname-bounces@
Michael Welch writes: Right, that must be because this list's Sender: header does not look like a real email address. I wonder why ours are different. It's one of the VERP settings. While true VERP is done by the MTA, not by agents like Mailman, the basic idea is the same: to personalize various fields in the message so that the original that elicited a reply (including a bounce) can be identified. IIRC there are two. One which enables VERP for various administrative messages which allows occasional checking for bounces, the other enables it for all messages. I believe this is possible on a per-list basis. You want the latter. The downside is performance, which is why VERP off is the default. Each message has to be composed individually, which increases the processor load a bit. This is probably negligible. More important, each message has to be sent individually, which can dramatically slow down processing if you have any large groups of members served by a single receiving MTA. (It is possible to specify multiple recipients for a single message; the receiving MTA will fetch it from the network once, then distribute copies. Sort of like you fax a handout to the meeting organizer, and he makes Xeroxes for all the attendees. Much more efficient than faxing one to each attendee!) I'm still on Mailman 2.1.5 which doesn't seem to have this feature, or maybe it's only available through the command line interface. If it sounds like what you need, say so and I'm sure somebody will tell you where the setting can be made. Note that this configuration may be disabled or objectionable to your ISP because of the possible impact on performance. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] listname-bounces@
Stephen J. Turnbull wrote: The downside is performance, which is why VERP off is the default. That and the fact that not all MTAs support VERP at all, and some of the ones that do support VERP don't support it by default. So, we leave this option turned off by default. I'm still on Mailman 2.1.5 which doesn't seem to have this feature, or maybe it's only available through the command line interface. VERP is available on Mailman 2.1.5, but it does have to be enabled in the configuration file, before you can actually see the option in the web admin UI for your list(s). Which is actually the problem here, since the OP is on a shared server and they're not likely to allow him to enable VERP since doing so would make everyone else capable of doing the same thing, and that would probably just *bury* the server performance. -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] listname-bounces@
Stephen J. Turnbull wrote: It's one of the VERP settings. While true VERP is done by the MTA, not by agents like Mailman, the basic idea is the same: to personalize various fields in the message so that the original that elicited a reply (including a bounce) can be identified. Um... Please explain what you mean by ... true VERP is done by the MTA Are you thinking of SRS? I'm not aware of any thing else at the MTA level that will alter the SMTP Envelope sender (MAIL FROM:). As far as RFC 822 headers, that is almost completely up to the MSA. About the only thing that the MTA does is insert (or append) a header if it does not already exist. IIRC there are two. One which enables VERP for various administrative messages which allows occasional checking for bounces, the other enables it for all messages. I believe this is possible on a per-list basis. You want the latter. I think you are thinking of the Non-digest delivery option Personalize and its possible values: No, Yes, and Full Personalization. Yes these are per-list settings. The downside is performance, which is why VERP off is the default. Each message has to be composed individually, which increases the processor load a bit. This is probably negligible. More important, each message has to be sent individually, which can dramatically slow down processing if you have any large groups of members served by a single receiving MTA. (It is possible to specify multiple recipients for a single message; the receiving MTA will fetch it from the network once, then distribute copies. Sort of like you fax a handout to the meeting organizer, and he makes Xeroxes for all the attendees. Much more efficient than faxing one to each attendee!) Correct. However, (IMHO) it does help make your message appear to be less spammy in nature. If you receive two questionable messages, one with your email address listed in the To: / CC: header(s) and one with out it, you are far more likely to consider the one that does not list your email address as spam than the one that does have your email address. Similarly with the use of the name in the email address with Full Personalization. Grant. . . . -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] spam gatewayed from Usenet to mail bypasses our spam filters
With the help of the python.org postmasters I figured something out about spam on the [EMAIL PROTECTED] mailing list over the weekend. I was confused that some seemingly obvious spams made it through to the mailing list subscribers. Then I noticed that it didn't appear these spams had even seen the spam filter. The headers the filter adds were missing and I could never find their Message-Id's in the spam filter's logs. Mailman operates the bidirectional gateway between the Usenet newsgroup comp.lang.python and the [EMAIL PROTECTED] mailing list. When it sees a Usenet message on the one side it distributes the posting directly to its subscribers, and vice versa. Because Usenet postings don't arrive by email the spam filtering we have in place (which occurs before Mailman sees a mail message) is not done. Mailman happily passes such unfiltered mail on to the list. I still haven't figured out quite how to solve the problem. In theory we could use some other tool to perform the gateway operation. Instead of passing Usenet postings directly to Mailman it would mail them to [EMAIL PROTECTED] where they would get the spam filter treatment before Mailman sees them. I'm still thinking about the full ramifications of that. It might be easier to get Mailman's news-to-mail gateway to mail incoming Usenet messages to the list address instead of directly distributing them to the subscribers though. I don't believe Mailman does that out of the box (but I would love to be wrong here). Has anyone tried implementing that? If so, got a patch or a recipe for how to configure Mailman to operate this way? Thanks, -- Skip Montanaro - [EMAIL PROTECTED] - http://smontanaro.dyndns.org/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] listname-bounces@
Brad Knowles writes: VERP is available on Mailman 2.1.5, but it does have to be enabled in the configuration file, before you can actually see the option in the web admin UI for your list(s). OK, so that probably was a deliberate decision and won't fly on his ISP. Which is actually the problem here, since the OP is on a shared server and they're not likely to allow him to enable VERP since doing so would make everyone else capable of doing the same thing, and that would probably just *bury* the server performance. Well, maybe if it's not advertised and he asks pretty please with whipped cream and cherries on top and promises cross my heart and hope to die to keep it secret, the List Czar at the ISP will change it only for his list(s) from the CLI. Weak, I know, but it *could* work Good luck! -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] spam gatewayed from Usenet to mail bypasses our spam filters
[EMAIL PROTECTED] writes: I still haven't figured out quite how to solve the problem. In theory we could use some other tool to perform the gateway operation. Instead of passing Usenet postings directly to Mailman it would mail them to [EMAIL PROTECTED] where they would get the spam filter treatment before Mailman sees them. I'm still thinking about the full ramifications of that. Well, you want to watch out for greylisting. But running them through SpamBayes from Mailman should be trivial. You could also add (with a slight performance hit) a Handler that calls out to SpamBayes, SpamAssassin, etc, only when the MTA didn't already do that, or only when the message's from_usenet flag is set. It might be easier to get Mailman's news-to-mail gateway to mail incoming Usenet messages to the list address instead of directly distributing them to the subscribers though. That's probably not a great idea as ToUsenet comes pretty late in the pipeline. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] spam gatewayed from Usenet to mail bypasses our spam filters
on 11/17/08 11:20 PM, [EMAIL PROTECTED] said: It might be easier to get Mailman's news-to-mail gateway to mail incoming Usenet messages to the list address instead of directly distributing them to the subscribers though. I don't believe Mailman does that out of the box (but I would love to be wrong here). Has anyone tried implementing that? If so, got a patch or a recipe for how to configure Mailman to operate this way? Ironically, we run an external news-to-mail gateway at ntp.org, based on the long-existing standard tools in the INN toolbox. We do this because Mailman generates it's own message-ids when it gateways the articles from news to mail, and the news reading public for ntp.org complained violently. The mail-to-news gateway from INN re-uses the same message-id as was originally contained within the news posting, so when people refer to a given message-id, it's always the same regardless of whether or not they are using mail or news. This is related to FAQ 4.59 at http://wiki.list.org/pages/viewpage.action?pageId=4030712. If we implemented a proper server-side read/post interface for Mailman, we could fix a lot of other USENET gateway problems, too. For one thing, we would no longer need high watermarks for article numbers, we would instead track whether or not we've seen a given message (and therefore whether or not it needs to be gatewayed) based on whether we've seen that message-id within our lifetime window, and any articles older than the lifetime window would get ignored. A server-side implementation would also allow us to directly feed outgoing articles to news routing servers, potentially bypassing a large news reader server infrastructure and being both more robust and more efficient. And we could take feeds from multiple upstream news routing servers, too. But as I said recently on this mailing list, I'm not a programmer and I don't have the necessary skills to write a proper server-side interface for USENET news to be incorporated into Mailman. So, I let this issue drop a few years ago when I first brought it up, although it does seem to come back up every so often. -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] spam gatewayed from Usenet to mail bypasses our spam filters
on 11/18/08 1:28 AM, Stephen J. Turnbull said: Well, you want to watch out for greylisting. But running them through SpamBayes from Mailman should be trivial. You could also add (with a slight performance hit) a Handler that calls out to SpamBayes, SpamAssassin, etc, only when the MTA didn't already do that, or only when the message's from_usenet flag is set. We've got more to the anti-spam processing for our mail server infrastructure than just SpamBayes. We've got several components whose function I only know about slightly in passing, and they all have an impact on the incoming mail traffic. We wouldn't be doing them if they didn't have an impact. I am a fan of SpamAssassin in general, but it is not part of that toolkit. I'm not sure how much some of those other components are specifically tied into postfix, and may be of limited use with any other program. And of course the host-level firewalling we're doing to reject connections from the worst abusers operates at a completely different level. There's a lot to be said for the simplicity of just having all this traffic handled via e-mail, just like all the other bi-directional traffic we're doing. We will have to be careful about loops, however. We wouldn't want to gateway the same thousand-articles-plus per day many times over. -- Brad Knowles [EMAIL PROTECTED] LinkedIn Profile: http://tinyurl.com/y8kpxu -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] The Mysterious Disappearing Disk Space (fwd)
Greetings, I have looked through the archives for something similar to my issue, and I noticed that by searching on disk full, I get similar reports beginning in roughly July of 08. As with these other reports, I have noticed *tremendous* disappearing space. When I tried to find the actual files, I was unsuccessful. Interestingly, if I stop mailman and then restart it, the missing space miraculously reappears! So, now that the background is over with, here's where I find myself (besides just looking stupid): (1) Yesterday I enabled VERP, and it appeared to be working well, At the time I turned on VERP, I had around 5gb of free space (which would take about two weeks to disappear before VERP). (2) Around 2pm today, the disk was full, and mailman died. (3) My inkling of something being wrong was this on the web interface: Bug in Mailman version 2.1.11rc2 We're sorry, we hit a bug! Please inform the webmaster for this site of this problem. Printing of traceback and other system information has been explicitly inhibited, but the webmaster can find this information in the Mailman error logs. (4) Upon looking at the system in response to the above missive, I checked and saw the system ws out of space again. I did what I always do - shut down mailman (which usually drops ~5gb of missing space, and then restart it. Everything before today has come up roses doing this. (5) There is nothing in any of the logs that indicate why this message is continuing to poke fun at me. (6) I have looked through the various manuals, pdfs, etc, and cannot find anything about explicitly enabling logging so that I can get a better handle on this. Oddly, as a mailman user since around 2001, this is the first real problem Ive had: Great platform!!! Mediocre admin though, and one begging for help as well. All the best, //Alif -- Yours, J.A. Terranson sysadmin_at_mfn.org 0xpgp_key_mgmt_is_broken-dont_bother -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
