I'm using 1.03-3.3.1.qt.el8.

I actually found that setting `full-log-dir=/tmp/spamdyke-logs` in the
`spamdyke.conf` file gave me quite a lot of actionable information. I
don't know if it's exactly the same as you'd get by using `SMTP_DEBUG`,
but I found it helpful.

Thanks for your advice,

Angus



Eric Broch wrote on 1/16/23 10:03 PM:
> What version of qmail are you using?
> 
> In the later versions, <=1.03-3.3.4, you can use SMTP_DEBUG to monitor
> the SMTP transaction logged to a different file.
> 
> 
> On 1/16/2023 6:22 PM, Angus McIntyre wrote:
>> I have a qmailtoaster that's been running without problems for a while.
>> I haven't made any configuration changes, and the server is healthy,
>> with enough disk space available etc.
>>
>> Today, I noticed that certain expected messages are not getting
>> delivered. Lots of mail is still coming in without problems, but certain
>> transactions are failing silently.
>>
>> The normal pattern that I see in the logs for a healthy delivery looks
>> something like:
>>
>>    tcpserver: pid 2356283 from 123.123.123.123
>>    tcpserver: ok 2356283 s6:111.111.111.111:25 :123.123.123.123::40631
>>    CHKUSER accepted sender: from <otheru...@gmail.com::> remote <mail-
>>    qt1-f176.google.com:unknown:123.123.123.123> rcpt <> : sender accepted
>>    CHKUSER accepted any rcpt: from <otheru...@gmail.com::> remote <mail-
>>    qt1-f176.google.com:unknown:123.123.123.123> rcpt
>>    <myu...@mydomain.com> : accepted any recipient for this domain
>>    policy_check: remote otheru...@gmail.com -> local myu...@mydomain.com
>>    (UNAUTHENTICATED SENDER)
>>    policy_check: policy allows transmission
>>    simscan:[2356286]:CLEAN (-0.30/100.00):1.9436s:Re_ Some
>>    Topic:123.123.123.123:otheru...@gmail.com:myu...@mydomain.com
>>    mail recv: pid 2356286 from <otheru...@gmail.com> qp 2356287
>>
>> For the problem ones, it gets as far as:
>>
>>    CHKUSER accepted sender: from <otheru...@gmail.com::> remote <mail-
>>    qt1-f176.google.com:unknown:123.123.123.123> rcpt <> : sender accepted
>>
>> and then stops. There's no "CHKUSER accepted any rcpt" and the delivery
>> never completes.
>>
>> This doesn't seem to be connected to the actual recipient: all
>> recipients receive some mail, just not all of it. However, specific
>> incoming messages appear to fail consistently.
>>
>> Has anyone encountered this? And do you have any insight into what could
>> be causing an apparent failure between sender acceptance and recipient
>> acceptance in CHKUSER? What tests does CHKUSER perform to determine if a
>> recipient is accepted?
>>
>> Thanks for any help or suggestions,
>>
>> Angus
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
>> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>>
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Reply via email to