16 messages in net.sourceforge.lists.courier-users[courier-users] Re: RFC 2047 2045 COM...
FromSent OnAttachments
Christian JourdeSep 7, 2000 6:52 am 
Christian JourdeSep 13, 2000 9:16 am 
Chad Leigh, Shire.Net LLCSep 13, 2000 9:57 am 
Christian JourdeSep 13, 2000 2:19 pm 
Gordon MessmerSep 13, 2000 2:49 pm 
Christian JourdeSep 13, 2000 3:01 pm 
Michael S. FischerSep 13, 2000 4:08 pm 
Gordon MessmerSep 13, 2000 5:24 pm 
Sam VarshavchikSep 13, 2000 6:20 pm 
Jason BakerSep 14, 2000 10:10 am 
Sam VarshavchikSep 14, 2000 7:30 pm 
Christian JourdeSep 15, 2000 3:23 am 
Jan MachSep 15, 2000 6:04 am 
Christian JourdeSep 15, 2000 6:49 am 
Gordon MessmerSep 15, 2000 9:30 pm 
Michael T. BabcockSep 15, 2000 10:41 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:[courier-users] Re: RFC 2047 2045 COMPLIANCEActions...
From:Sam Varshavchik (mrs@stop.mail-abuse.org)
Date:Sep 13, 2000 6:20:38 pm
List:net.sourceforge.lists.courier-users

Gordon Messmer writes:

On Wed, 13 Sep 2000, Sam Varshavchik wrote:

One mistake that I will never make is attempt to have Courier be a jack of all trades. That's a mistake. You have to have the right tool for the right job. In certain situations other mail servers will do a better job than Courier. That's never going to change. It would be an error to try to make a shoe that fits every foot.

That's an interesting (and quite rational) statement. It begs the question: What _is_ your target audience for Courier? When do you think that another server (qmail for instance) should be used instead of Courier?

Courier's strengths are: integration of most popular mail services: SMTP, IMAP, POP3, and webmail. Only have to deal with the configuration issues once, and you get the whole package working.

Also -- a firewall situation, where you want to be able to defensively screen incoming mail. Courier has a lot of code to deal with denial of service attacks. Although, by default VRFY and EXPN is turned on, anyone attempting to do a dictionary attack against a Courier server is in for a surprise. There are also several options for installing arbitrary aggressive mail filters.

Here's an experiment: enable one of the sample mail filter that gets installed by default, "dupfilter". Then try to mailbomb any account on the Courier server, using any lame ass mailbomb proggie. That's just an example. Write your own filters to deal with your own "unique" situations.

Or, enable the "perlfilter" filter, and try to send Courier a message with a long Date: header (the most recent Lookout Express exploit).

Two examples of what can be done here.

You don't want to use Courier sometimes when speed is an absolute requirement. Depending on the kind of mail traffic, Courier can be a lot slower than Qmail pushing a large load of mail out. But, in other situations Courier will spank the monkey out of Qmail. It all depends upon your kind of mail traffic, but don't take it for granted that you'll be able to push a load of mail through, in no time at all.

I can't think of a situation where I'd recommend sendmail over Courier :-)

I don't know much about Postfix, but from what I've heard, it sounds like it's slow, and needs lots of resources.