Hi Eric,
I have followed the page indicated and I am now getting
lock file errors.
supervise: fatal: unable to acquire smtp/supervise/lock: temporary failure
supervise: fatal: unable to acquire send/supervise/lock: temporary failure
supervise: fatal: unable to acquire log/supervise/lock: temporary failure
supervise: fatal: unable to acquire log/supervise/lock: temporary failure
supervise: fatal: unable to acquire log/supervise/lock: temporary failure
supervise: fatal: unable to acquire submission/supervise/lock: temporary failure
Sorry, I cannot see what happened. Any ideas please?
regards
Tony White
On 26/5/25 02:00, Eric Broch wrote:
If you are on the latest qmail you can set up smtp transaction logging to a separate file. It will tell you exactly
what's going on (http://wiki.qmailtoaster.org/index.php?title=Fail2ban).
In order to log SMTPTX (transactions) do the following:
1) # qmailctl stop
2) Add 'SMTP_DEBUG="1"' to /etc/tcprules.d/tcp.smtp
3) Replace contents of '/var/qmail/supervise/smtp/log/run' script with below to log transactions to different file:#!/bin/sh LOGSIZE=`cat /var/qmail/control/logsize` LOGCOUNT=`cat /var/qmail/control/logcount` exec /usr/bin/setuidgid
qmaill \ /usr/bin/multilog t s$LOGSIZE n$LOGCOUNT \ '-*' '+@* server:[*' '+@* client:[*' /var/log/qmail/smtptx \ '+*'
'-@* server:[*' '-@* client:[*' /var/log/qmail/smtp 2>&1
4) # qmailctl start && qmailctl cdb
5) # tail -f /var/log/qmail/smtptx/current | tai64nlocal
On 5/25/2025 9:00 AM, Tony White wrote:
There has been a growing number of this entry in the log
file that I have not been able to explain...
2025-05-26 00:58:05.642949500 CHKUSER accepted sender: from <[email protected]::> remote
<net149.233.188-137.ertelecom.ru:unknown:188.233.149.137> rcpt <> : sender accepted
Yet manually testing the server it will not accept an empty rctp to.
regards
Tony White
On 26/5/25 00:40, Tony White wrote:
Hi Folks,
Is there a way to not accept empty rcpt to (no sender email)?
--
regards
Tony White
