[Mailman-Users] Sevier Issue with mails, are these compromised?
Hello all, I have recently shifted my site and mailing list on Hostgator server here in India. Today, I've got an E-Mail from them saying that as per the mail policy, our members can send 500 mails per hour but we are exceeding the number of mails a day! While the fact is we have around 360 members and we send hardly 50 to 60 messages in entire day of 24:00. so, I am unable to understand what's wrong with us. Are some of our mails account got hacked and compromised? Hostgator team has send me the number of messages and Email addresses sent from: -- sayeverything-boun...@sayeverything.org: 11,655 mailman-boun...@sayeverything.org: 4 sayev...@in6.hostgator.in: 2 modera...@sayeverything.org: 1 They also send me some Random recipient addresses. Please advise me, what it looks like, problem with some mailman setting at our end? any issue with the technicality of my service provider? or as I suspect, are above mail accounts being misused? Thanks, Amit Bhatt -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Sevier Issue with mails, are these compromised?
On Mon, 14 May 2012, Amit Bhatt wrote: Today, I've got an E-Mail from them saying that as per the mail policy, our members can send 500 mails per hour but we are exceeding the number of mails a day! While the fact is we have around 360 members and we send hardly 50 to 60 messages in entire day of 24:00. so, I am unable to understand what's wrong with us. Are some of our mails account got hacked and compromised? I suspect you don't understand how emails are counted. Each list message to each recipinet probably counts as one email. If I'm understanding you correctly, your are sending 50 to 60 messages per day to 360 users. 50 times 360 is 18,000 outgoing messages per day. Hostgator team has send me the number of messages and Email addresses sent from: -- sayeverything-boun...@sayeverything.org: 11,655 That fits with my assumption above. -- Larry Stone lston...@stonejongleux.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Sevier Issue with mails, are these compromised?
So, does it mean that we cannot run our mailman with hosting provider like Hostgator? If this is the case, who is good service provider where our mailing list can work properly without such interruption. Regards, Amit Bhatt - Original Message - From: Larry Stone lston...@stonejongleux.com To: Mailman-Users@python.org Sent: Monday, May 14, 2012 10:11 PM Subject: Re: [Mailman-Users] Sevier Issue with mails, are these compromised? On Mon, 14 May 2012, Amit Bhatt wrote: Today, I've got an E-Mail from them saying that as per the mail policy, our members can send 500 mails per hour but we are exceeding the number of mails a day! While the fact is we have around 360 members and we send hardly 50 to 60 messages in entire day of 24:00. so, I am unable to understand what's wrong with us. Are some of our mails account got hacked and compromised? I suspect you don't understand how emails are counted. Each list message to each recipinet probably counts as one email. If I'm understanding you correctly, your are sending 50 to 60 messages per day to 360 users. 50 times 360 is 18,000 outgoing messages per day. Hostgator team has send me the number of messages and Email addresses sent from: -- sayeverything-boun...@sayeverything.org: 11,655 That fits with my assumption above. -- Larry Stone lston...@stonejongleux.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/misterbhatt%40gmail.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Sevier Issue with mails, are these compromised?
On 5/14/2012 1:21 PM, Amit Bhatt wrote: So, does it mean that we cannot run our mailman with hosting provider like Hostgator? If this is the case, who is good service provider where our mailing list can work properly without such interruption. Regards, Amit Bhatt - Original Message - From: Larry Stone lston...@stonejongleux.com To: Mailman-Users@python.org Sent: Monday, May 14, 2012 10:11 PM Subject: Re: [Mailman-Users] Sevier Issue with mails, are these compromised? On Mon, 14 May 2012, Amit Bhatt wrote: Today, I've got an E-Mail from them saying that as per the mail policy, our members can send 500 mails per hour but we are exceeding the number of mails a day! While the fact is we have around 360 members and we send hardly 50 to 60 messages in entire day of 24:00. so, I am unable to understand what's wrong with us. Are some of our mails account got hacked and compromised? I suspect you don't understand how emails are counted. Each list message to each recipinet probably counts as one email. If I'm understanding you correctly, your are sending 50 to 60 messages per day to 360 users. 50 times 360 is 18,000 outgoing messages per day. Hostgator team has send me the number of messages and Email addresses sent from: -- sayeverything-boun...@sayeverything.org: 11,655 That fits with my assumption above. -- Larry Stone lston...@stonejongleux.com -- Hi Amit: You will not be able to use that mailman list with Hostgator due to their email limits. I recommend you to check out our mailman hosting services at http://www.mailmanhost.com. We have a number of clients from Hostgator and Bluehost who use us to host their mailman lists since we do not impose any limits on our mailman clients. Please let me know if you have any questions. -- Brian Carpenter Owner | EMWD dotList br...@emwd.com | http://www.emwd.com | http://www.mailmanhost.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] How do I default to HTML, not plain text emails?
On 5/14/2012 11:36 AM, David wrote: There is an old discussion in this list's archives on this topic at http://mail.python.org/pipermail/mailman-users/2005-April/044342.html. Unfortunately, it didn't help me. The problem, as I understand it, is that when you change the digest setting, it also affects the non-digest setting. That is not correct. The ONLY thing affected by the plain/MIME setting is the format of the user's digest. The archived thread didn't resolve or clarify this for me. We are experiencing this problem now. Our problem: Set the following option to plain. Note that this is a digest option, not a non-digest option. When receiving digests, which format is default? Plain (Edit mime_is_default_digest) Then set the following option to regular: Which delivery mode is the default for new users? Regular (Edit digest_is_default) Now add a new member to the list. What happens is that the new member is set to non-digest and plain text defaults. Yes, but the 'plain' setting, while displayed, does not affect this user in any way as it only affects digests. If you now change mime_is_default_digest to MIME and add a new member, the new member is set to non-digest and rich text defaults. There's another misunderstanding. MIME does not mean rich text or HTML. It only means that MIME format digests are sent as MIME Content-Type: multipart/digest with each digested message contained in it's own message/rfc822 sub-part, whereas 'plain' format digests are 'flattened in to a single text/plain message with those parts that can't be rendered as plain text removed and stored aside, a process called 'scrubbing'. So the digest option is changing the default settings for non-digest new members. This is both confusing and limiting. It is a digest option that affects only digest subscribers, but every subscriber has the bit that controls that option, whether or not it is relevant to their subscription at this time. I'm sorry you find this confusing. Have you looked at the list member manual at http://www.list.org/mailman-member/index.html? We want digest emails sent out in plain format by default. But we want the non-digest option with rich text to be the default for all new users. There doesn't seem to be a way to achieve this. Hopefully, there is a setting I'm overlooking. Every non-digest subscriber receives the same message which is the message as sent by the poster with possible addition of msg_header and/or msg_footer and possible content removed by content filtering if enabled. The plain/MIME setting does not affect this. Mailman does not in any way 'convert' a plain text message to HTML or rich text. If you want HTML messages to be delivered to list members, you have to a) post HTML or multipart/alternative with an HTML part, and b) make sure content filtering passes everything you want. I think my off list exchange with Terry Earley got your content filtering settings to the point where they were passing what you wanted. Then, depending on their MUAs, MIME digest subscribers may also see the same rich text messages as all non-digest subscribers. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Error accessing admin pages, AttributeError: local_name
Hello, I'm using the mailman vhost branch (is this the 'best' thing to use to do multi-domain mailing list hosting?) When I enter /mailman/admin/2030 it first asks for the password, after that I get an error page 'Bug in Mailman version 2.1.14' This happens on all the lists, but it did used to work but I'm not sure what has happened to break it now. The Error log can be seen at http://pastebin.com/KZKMwCap Help appreciated! Thanks Andrew. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Error accessing admin pages, AttributeError: local_name
Andrew H wrote: I'm using the mailman vhost branch (is this the 'best' thing to use to do multi-domain mailing list hosting?) The recommended best practice for Mailman 2.1.x is to run a separate Mailman instance per domain. The vhost branch may be the second choice alternative. When I enter /mailman/admin/2030 it first asks for the password, after that I get an error page 'Bug in Mailman version 2.1.14' This happens on all the lists, but it did used to work but I'm not sure what has happened to break it now. What broke it is setting OWNERS_CAN_DELETE_THEIR_OWN_LISTS = Yes in mm_cfg.py. It's definitely a bug in the vhost branch. It's fixed (I hope) in rev. 852 of the branch. See http://bazaar.launchpad.net/~msapiro/mailman/vhost/revision/852 for the fix. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Spam filters
So my mailing lists are getting hit by spam that goes to the lists since it claims to be from some poor subscriber whose email got hijacked. But to be more general, what are some of the current best practices to filter out spam in a postfix mailman environment on Linux? mjb. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Ubuntu release of Mailman
Lindsay Haisley writes: It's probably just as easy to bypass the precompiled Ubuntu package and work straight from the Mailman distribution. If I have issues, which are ususally creative problems with Python, I'd much rather work with the Mailman devs than with Canonical :-) We do like to hear we're easy to work with! The distros (and that includes even Gentoo and Arch, to some degree) do have their place, but it's not in the specialized mission-critical components of the system. Depending on your application, you may want to apply that even to the kernel and libc, but most of the time there's a long list of highly complex and widely used components (kernel, libc, Apache, ...) that the distros do quite well enough, and you rarely if ever run into issues (whether software bugs or admin PEBKAC). But when you do run into issues, whether a need for customization or a bug, it help a lot to be using something as close to upstream's recommended configuration as possible. That's why many projects (not just Mailman) recommend building from source. (Yeah, I know you know this, Lindsay. It's worth repeating occasionally, though. This automatically-triggered recording was brought to you by the FLUFL's Fluffy Support Brigade and the Mailman Devs. :-) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] Spam filters
Mark J Bradakis writes: So my mailing lists are getting hit by spam that goes to the lists since it claims to be from some poor subscriber whose email got hijacked. But to be more general, what are some of the current best practices to filter out spam in a postfix mailman environment on Linux? Run SpamAssassin or similar as a milter from Postfix. One hint that may help is that on many lists there's a short list of keywords that allow you to whitelist content when they appear in a text/* part. Eg, on Python lists, almost no spam contains the word python (except perhaps in the greeting Dear python-l...@python.com). SpamAssassin and similar filters allow you to add rules for this kind of thing. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Re: [Mailman-Users] Ubuntu release of Mailman
On Tue, 2012-05-15 at 11:54 +0900, Stephen J. Turnbull wrote: But when you do run into issues, whether a need for customization or a bug, it help a lot to be using something as close to upstream's recommended configuration as possible. That's why many projects (not just Mailman) recommend building from source. (Yeah, I know you know this, Lindsay. It's worth repeating occasionally, though. This automatically-triggered recording was brought to you by the FLUFL's Fluffy Support Brigade and the Mailman Devs. :-) Heh!! Yeah, the Mailman developers seem to be a very focused and friendly bunch. Brad Knowles is a friend of mine here in Austin, as we're both members of Austin's Unix professional society. There's also the fact that I've bent Mailman to my will in a couple of departments, forcing it to deal intelligently with PHP and Namazu. As you point out, it's always easiest to start as far upstream as possible when one does this sort of thing. I've moved away from Gentoo for my servers. It's just too much hassle and takes too long to deal with building from source for _everything_, so I let Canonical handle the big stuff and use Ubuntu server on my newest server, and Linux Mint on my favorite desktop. I'm 70 years old. I just don't have the bandwidth, or the time, to learn everything I need to know to keep up with all the dirty details of the ever increasing complexity of a modern Linux installation. -- Lindsay Haisley | The only unchanging certainty FMP Computer Services |is the certainty of change 512-259-1190 | http://www.fmp.com| - Ancient wisdom, all cultures -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
