On 03/19/2010 04:38 AM, Wietse Venema wrote: > In the mean time, it would help if you could provide verbose (smtpd > AND cleanup) logging for a failed session. Please include information
We're trying to get the logging information. Versions we've seen this on
include:
postfix-2.5.9
postfix-2.5.1
pymilter-0.9.3 (with libmilter 8.14)
pymilter-0.8.6 (which I believe was against libmilter 8.13)
milter protocols: 2, 3, 4, and 6.
Postfix relevant configs:
milter_content_timeout = 3000 # tried 300, 600, and 3000
milter_default_action = accept # newly added to see if it helps
milter_protocol = 6
milter_connect_macros = b j _ {daemon_name} {if_name} {if_addr}
smtpd_milters = inet:127.0.0.1:2092
The milter is configured as:
socketname = 'inet:2092'
Milter.factory = OurMilter
Milter.set_flags(Milter.ADDHDRS)
Milter.runmilter('ourmilter', socketname, 240)
The problem with trying to reproduce it is, we can't really reproduce it at
will yet. As I've said before, this mail server has maybe 5 thousand users,
only something like 3 users are seeing this problem.
So, we're still trying to work on information to allow us to reproduce it,
so far only the customers involved can reproduce it.
So, I'd say don't spend too much time on trying to reproduce it -- that's
our job. :-) We were just hoping there was something obvious in the
configuration or similar.
Thanks,
Sean
--
Sean Reifschneider, Member of Technical Staff <j...@tummy.com>
tummy.com, ltd. - Linux Consulting since 1995: Ask me about High Availability
signature.asc
Description: OpenPGP digital signature
