Re: [clamsmtp-users] Problem with multiple message deliveries

[David D. <dav...@gm...>]

I did some more digging and have convinced myself that the multiple
deliveries are being caused because of the Timeout.  That's not the
root problem for this issue, but gives me a workaround.

The problem is that clamsmtpd is hitting it's 180s timeout and sends
postfix on 25 a 451, but the instance of postfix on 10025 isn't done
processing the message and when it figures itself out finishes
delivery.  Postfix on 10025 is getting hung up on some address
validation tasks that are taking longer than 3 minutes.





On Thu, Apr 23, 2009 at 11:26 PM, Alexander Moisseev
<mo...@me...> wrote:
> David DeFranco wrote:
>> My problem is that sometime Clamsmtpd is accepting, processing and
>>
>> forwarding a message successfully but is sending "451 Local Error" to
>> Postfix.  So of course Postfix retries.  Sometimes when Postfix
>> retries Clamsmtpd will send "451 Local Error" and the message will not
>> be accepted, and sometimes it is.  Sometimes this cycle will cause a
>> message to be sent 5 or 6 times before sending Postfix a 250 and
>> sometimes a duplicate message will be sent until the original message
>> times out and is NDR'd.
>
> I guess two reasons:
>
> 1. Attachment exceeds limit.
> Check StreamMaxLength option in clamd.conf.
> # Close the connection when the data size limit is exceeded.
> # The value should match your MTA's limit for a maximum attachment size.
> # Default: 10M
>
> 2. Processing of some attachements take a lot of time.
>
> Try to increase TimeOut in clamsmtpd.conf
> # Amount of time (in seconds) to wait on network IO
> # TimeOut: 180
>
> Or you may tune some options in Limits section of clamd.conf.
>
> Regards,
> Alexander
>
>
>