--brian wrote on 21.10.2002 10:44 -0700:
Oct 21 10:11:01 localhost courierlocal:
id=0001EE47.3DACE2A9.000043B0,from=<jmax...@hipersoft.com>,addr=<briann@aut
horityserver.com>,status: deferred
Oct 21 09:55:59 localhost courierlocal:
id=0001EE4D.3DB0752C.00000988,from=<bug-...@gnu.org>,addr=<brian@au
thorityserver.com>,status: deferred
those entries come from courierlocal, which delivers the message.
'real' bounces are all handled by courieresmtpd itself.
Guess some utility (maildrop or dotfile) returns a non-zero exitcode.
Oct 21 09:55:59 localhost courierd:
Waiting. shutdown time=none, wakeup time=Mon Oct 21 09:56:00 2002,
queuedelivering=9, inprogress=2 Other deferrals include:
,module=esmtp,host=777.net.cn,addr=<Mega...@777.net.cn>
Oct 21 09:45:21 localhost courieresmtp:
id=0001EE6A.3DB0C5E1.00000F25,from=<>,addr=<just...@xmailsex.com>: Connection
timed out Oct 21 09:45:21 localhost courieresmtp:
id=0001EE6A.3DB0C5E1.00000F25,from=<>,addr=<just...@xmailsex.com>,status:
deferred
thats your server busy sending back bounces to the (possibly forged)
senders Mega...@777.net.cn and just...@xmailsex.com.
The latter deferred messages actually have a reason why they were deferred,
but the former do not.
They have nothing in common, you need to investigate further.
The incoming spam should be rejected via esmtpaccess, dnsbl, bofh
or courierfilter, dont bounce once received and accepted and it
will be much easier to spot the 'real' problems in the logs ;)
Roland