atom feed23 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: RFC2045 again
FromSent OnAttachments
Chris HamiltonJul 21, 2001 9:44 am 
Ben BeuchlerJul 21, 2001 2:54 pm 
Sam VarshavchikJul 21, 2001 4:18 pm 
Ben BeuchlerJul 21, 2001 4:30 pm 
Sam VarshavchikJul 21, 2001 4:49 pm 
Greg OwenJul 21, 2001 5:48 pm 
Gordon MessmerJul 21, 2001 11:48 pm 
Lars ChristensenJul 22, 2001 1:46 am 
Bill MichellJul 22, 2001 3:30 am 
Roland SchneiderJul 22, 2001 3:56 am 
Lars ChristensenJul 22, 2001 5:56 am 
Bill MichellJul 22, 2001 6:44 am 
Alessandro VeselyJul 22, 2001 6:47 am 
Lars ChristensenJul 22, 2001 7:21 am 
Bill MichellJul 22, 2001 7:59 am 
Papo NapolitanoJul 22, 2001 2:10 pm 
Sam VarshavchikJul 22, 2001 8:37 pm 
Todd LyonsJul 24, 2001 8:16 am 
Georg LutzJul 24, 2001 3:12 pm 
Gordon MessmerJul 24, 2001 11:22 pm 
Alexei Batyr'Jul 25, 2001 1:52 am 
Oliver BlasnikJul 25, 2001 2:36 am 
Alexei Batyr'Jul 25, 2001 5:14 am 
Subject:Re: [courier-users] Re: RFC2045 again
From:Greg Owen (gow@swynwyr.com)
Date:Jul 21, 2001 5:48:47 pm
List:net.sourceforge.lists.courier-users

Sam Varshavchik wrote:

Ben Beuchler writes:

OK. I can accept that. Just curious: Aside from spam software, who/what are the prime offenders?

It's mostly spam software. This turned out to be an excellent spam

filter.

I found that bugtraq mailing list dropped me because of the 2045 checking. Presumably one of the thousands of people who post to the list uses a bad mailer, so I bounced it, so the list probed me to check, and apparently the probe failed. I don't know why it would; I thought they were running a straightforward ezmlm setup.

I'm currently running courier with 2045 checking commented out, as is described somewhere in the documentation. I wouldn't mind having that be an obscure config file option somewhere instead of requiring a special compile. I understand the reasoning behind anal checking, but I also need to receive mail from lists that have bad software posting to them.