| |||||||||||||||||||||||||||||||
|
> > Exchange really should NOT be allowing client connections to sit idle > > > for 12 hours tying up resources. What prehistoric version of the > > > software are these sites running? > > > > Running server 2003 & exchange 2003 nothing outdated there... > The double-spacing really makes it hard to read and reply to your mail properly, can you try to turn that off? > > - Disable PIPELINING to Exchange (smtp_discard_ehlo_keywords) > > if Exchange PIPELINING is buggy. > > Will try this now... > > So create smtp_discard_ehlo_keyword_address_maps = hash:/etc/postfix/mapname Easier to turn it off globally for a dedicated transport: main.cf: # Use "cdb" if available default_database_type = hash indexed = ${default_database_type}:${config_directory}/ disable_pipelining = PIPELINING, silent-discard transport_maps = ${indexed}transport master.cf: smtplite unix - - n - - smtp -o smtp_discard_ehlo_keywords=$disable_pipelining transport: example.com smtplite > And in the mapname file put: > > Client-domain.com pipelining No, this only works for IP addresses, but the transport based approach above works for domains. > I only see the 3 options of: pipelining, starttls, auth in the doc I see, > should it bee nopipelining? No it should be "pipelining", because this is a *discard* keywords list. -- Viktor. Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the "Reply-To" header. To unsubscribe from the postfix-users list, visit http://www.postfix.org/lists.html or click the link below: <mailto:majordomo?body=unsubscribe%20postfix-users> If my response solves your problem, the best way to thank me is to not send an "it worked, thanks" follow-up. If you must respond, please put "It worked, thanks" in the "Subject" so I can delete these quickly.
| ||||||||||||||||||||||||||||||
© 2004-2008 readlist.com