Mailman 3 July 2003 - Mailman-Users

Re: [Mailman-Users] Subject Line Length Considered Spam
by J C Lawrence 28 Jul '03

28 Jul '03

On Mon, 28 Jul 2003 18:28:48 -0700 jsmith <jsmith(a)smittybuilt.com> wrote: > Paul, I couldn't agree with you more. But, as I exchange email with a > minimum wage worker at excite that is doing what he was told to do > (decision from someone that hasn't got a clue) I still have people > complaining. Since people can still follow the link in the email is > there a short term fix that I can implement here until I can get this > corrected with excite. =20 You don't adapt to or accommodate such stupidity, you either fix it or let it die of its own. If that's really what Excite want to do, don't encourage them by making it easier on Excite users. -- J C Lawrence ---------(*) Satan, oscillate my metallic sonatas. claw(a)kanga.nu He lived as a devil, eh? http://www.kanga.nu/~claw/ Evil is a name of a foeman, as I live.

1 0

RE: [Mailman-Users] Subject Line Length Considered Spam
by jsmith 28 Jul '03

28 Jul '03

Paul, I couldn't agree with you more. But, as I exchange email with a minimum wage worker at excite that is doing what he was told to do (decision from someone that hasn't got a clue) I still have people complaining. Since people can still follow the link in the email is there a short term fix that I can implement here until I can get this corrected with excite. The worse art of this is the fact that they gave no error back that this is what was happening. Usually if you get blacklisted for spam the error msg would say relying denied or some other useful msg to address the issue. This one did not. I happened on it by mistake. Then 2 + 2 added up about excite users complaining. So I would bet this is happening to every mailman installation that tries to send a confirmation email to excite. Any Ideas? Help? Swift kick in the butt for the obvious? I am not a programmer and it would be useless for me to start opening files trying to track down the line of code that adds that as the subject so I can modify it. Not to mention what to modify it too. Joe -----Original Message----- From: Paul H Byerly [mailto:paul@thcwd.com] Sent: Monday, July 28, 2003 6:13 PM To: mailman-users(a)python.org Subject: Re: [Mailman-Users] Subject Line Length Considered Spam jsmith wrote: >Excite is blocking any subject that has more than 22 characters due to it >looking like >commercial spam. I would bet that other ISP's will be or have already >started subject line filtering on the length as well. I am assuming you mean 22 consecutive characters without a break? The subject you gave your post would violate a 22 character limit. Even at 22 consecutive I think this is a rather short sighted, over the top and totally worthless way to try and stop spam. There are a lot of systems that depend on subject lines with long confirmation codes, including some spam programs! I would think an ISP that breaks this many systems is going to lose some customers. <>< Paul ------------------------------------------------------ Mailman-Users mailing list Mailman-Users(a)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/ This message was sent to: jsmith(a)smittybuilt.com Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/jsmith%40smittybuil t.com

1 0

Re: [Mailman-Users] Subject Line Length Considered Spam
by Paul H Byerly 28 Jul '03

28 Jul '03

jsmith wrote: >Excite is blocking any subject that has more than 22 characters due to it >looking like >commercial spam. I would bet that other ISP's will be or have already >started subject line filtering on the length as well. I am assuming you mean 22 consecutive characters without a break? The subject you gave your post would violate a 22 character limit. Even at 22 consecutive I think this is a rather short sighted, over the top and totally worthless way to try and stop spam. There are a lot of systems that depend on subject lines with long confirmation codes, including some spam programs! I would think an ISP that breaks this many systems is going to lose some customers. <>< Paul

1 0

Subject Line Length Considered Spam
by jsmith 28 Jul '03

28 Jul '03

Hello all, I have just received an email back from Excite on an issue that I am having about excite users not being able to sign up for my lists via the web. The installation is not having any errors script wise. I am experiencing a problem with the length of the subject line on posts going out and I am working on that issue with the list owners, but, I am also having the issue when a user subscribes, they get send a confirmation email with a subject line that that looks like this "confirm 101795f318ab73938580ffc26fdc7154937b62ac" Excite is blocking any subject that has more than 22 characters due to it looking like commercial spam. I would bet that other ISP's will be or have already started subject line filtering on the length as well. My question is, Is there a way to still have the confirmation email sent but not have that long subject line? Any and all help would be greatly appreciated. Joe

2 1

Re: [Mailman-Users] Gentoo, mailman and the "module named paths"
by Whit Blauvelt 28 Jul '03

28 Jul '03

Thanks Bruce. I see that mailmanctl doesn't throw those errors if I start it from /web/mailman/bin rather than /etc/init.d. (However, I still have a "Site list is missing: mailman" error to sleuth out.) Where do you run mailmanctl from? Have I missed something on setting a system variable in the INSTALL instructions, that would enable it to work from /etc/init.d as advertised with mailman not installed in the default /usr/local/mailman? Whit On Mon, Jul 28, 2003 at 02:22:43PM -0400, Bruce Embrey wrote: > Whit, > > I have mine stored in /var/mailman and it works fine. I did have to > specified it when I ran configure but other than that it has run quite > smoothly. The version I run is 2.1.1. > > Hope that helps, > > Bruce Emrbey

2 2

Gentoo, mailman and the "module named paths"
by Whit Blauvelt 28 Jul '03

28 Jul '03

Hi, I've done a manual install of mailman on a system running the current Gentoo. "mailmanctl start" gives the dreaded "No module named paths" error. I've seen the README.linux attribution of this problem to not having installed Python from tar - but Gentoo's portage system is Python-based, and its Python is a full build of 2.2.3 from tar. I can't find mention of a paths module in any of the ebuilds in Gentoo's dev-python directory (not to be confused with Debian's dev-python .deb). I don't want to reinstall Python manually, because of the risk of somehow throwing the whole Gentoo portage system out of whack. What to do? Thanks, Whit

1 2

broken List-archive header
by Joel Uckelman 28 Jul '03

28 Jul '03

Yesterday I upgraded Mailman to 2.1 and started to notice the following problem: The List-archive headers in messages coming from my lists all look like this: List-archive: </archives> while before they looked like this, e.g.: List-archive: <http://lists.ellipsis.cx/archives/hosers-talk/> What's happening to the rest of the URL? I have PUBLIC_ARCHIVE_URL set to 'http://lists.ellipsis.cx/archives/%(listna me)s/', and it *is* showing up correctly in the archive links on the list info pages. Any ideas? -- J.

1 1

Virtualhosts-related problem (i think!)
by kaMe 28 Jul '03

28 Jul '03

Hello, i have set up mailman on a machine (tatooine.domain.tld) that handles the mail of domain.tld, with qmail+vpopmail. I've created a list @tatooine.domain.tld and all works right, posts, web-administration, archives.. all. I've tryed to create a new mailin list @domain.tld, set up the .qmail- files in the /domains/domain.tld/ directory of vpopmail and this list doesnt work. In the /Mailman/Defaults.py i have: DEFAULT_EMAIL_HOST = 'tatooine.domain.tld' DEFAULT_URL_HOST = 'tatooine.domain.tld' I found in the faq wizard, about handling virtualhosts, the add_virtualhost() directive, so i've added in mm_cfg.py add_virtualhost('domain.tld') or add_virtualhost('lists.domain.tld', 'domain.tld') and run the fix_url script for the list. It doesnt work in both ways. Yes, i restarted mailman (/bin/mailmanctl restart) every time i changed something. Is there a method to see what mailman do with a mail? A complete path, from when he receive the mail from the local MTA till when he handles it? When i try to post to the list i get no logs about the post, nothing in /log/ error|smtp|post|qrunner. The MTA's logs says the mail has been submitted to mailman.. but mailman seems trash it, simply the post disappear! Thanks in advance, Simone

1 0

List admin addresses bounce
by Mark Dadgar 28 Jul '03

28 Jul '03

I'm using Mailman 2.1.2 (installed from source) and Sendmail (RedHat RPM). I have the appropriate aliases installed for each list I run (as output by Mailman during list creation) and things have been peachy keen for a year now. However, I just discovered that email to listname-admin(a)pdc-racing.net generates an "unrecognized bounce" every time, for each of my lists. And yeah, I tried putting my address in for both list admin and list moderator. Any ideas? I did a quick search through the archives and the obvious search terms returned a couple of zillion results, none of which appeared to answer my question. Thanks. - Mark -- mark(a)pdc-racing.net

1 0

Re: Mailman-Users Digest, Vol 10, Issue 77
by Nancy Roberts, Statistics Geek 28 Jul '03

28 Jul '03

It is spam, and the OLD list is open to all posters, but the new list is not, so it needs to be approved or deleted. You can either open the new list to all posters, or leave it like it is where you would need to approve (moderate) posts from non-members, so you can reject spam. You can change the list password to something you can remember easily on the passwords page. Nancy

1 0