atom feed16 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: courier tmp d...
FromSent OnAttachments
Jan MachAug 10, 2000 2:42 am 
Jan MachAug 10, 2000 4:57 am 
Jan MachAug 10, 2000 7:03 am 
Jan MachAug 10, 2000 9:08 am 
Jan MachAug 10, 2000 10:16 am 
Jan MachAug 11, 2000 6:36 am 
Jan MachAug 18, 2000 6:57 am 
Jan MachSep 1, 2000 4:04 am 
Jan MachSep 1, 2000 5:22 am 
Jan MachSep 1, 2000 10:48 am 
Honza MachSep 2, 2000 8:10 am 
Honza MachSep 2, 2000 11:41 am 
Honza MachSep 2, 2000 1:21 pm 
Jason HaarSep 3, 2000 1:45 pm 
Jason HaarSep 3, 2000 5:53 pm 
Jason HaarSep 3, 2000 9:26 pm 
Subject:Re: [courier-users] Re: courier tmp directory - with some diagnostic
From:Jason Haar (Jaso@trimble.co.nz)
Date:Sep 3, 2000 5:53:45 pm
List:net.sourceforge.lists.courier-users

On Sun, Sep 03, 2000 at 08:16:44PM -0400, Sam Varshavchik wrote:

You will find many fixed upper resource limits in Courier. Overall, the system design is oriented to limiting all sorts of potential sources of denial of service attacks. Allowing the system an unlimited period of time to receive a single message is just asking for trouble.

Wow - that's come as a bit of a shock. What's wrong with setting up similar timeout options to sendmail and qmail, and setting some "sane" huge timeout for a connection - like 12hours? Even I could live with that :-)

FYI, in all the years I've run mail servers, I've never seen SMTP sessions under Qmail or Sendmail hang on for days on end because of such "troublesome" timeout settings...

-- Cheers

Jason Haar

Unix/Network Specialist, Trimble NZ Phone: +64 3 9635 377 Fax: +64 3 9635 417