[courier-users] Re: deferred status received on working courier server (certain received emails are not getting through from certain domains)

[brian]

Sorry it took so long to reply.
Your saying that I shouldn't accept mail then bounce it?
I am using maildrop to filter out certain phrases and if the messages contains those phrases then bounce the message. I do output the decisions made by maildrop for each message it handles. However I took a look at the maildrop logs and I cannot find any emails received from hipersoft.com. Meaning that those emails sent to me did not even reach maildrop. So I don't understand why courierlocal is automatically deferring the messages. Since the message is deferred my client doesn't even realize that the message didn't get to me and just assumes that I received the messages, which is bad.
My question is why does it deferr messages from this particular hipersoft.com mail web server? It has a valid MX record? I don't even get a reason why the message was deffered while other messages get through.
Roland Schneider writes:

--brian wrote on 21.10.2002 10:44 -0700:

Oct 21 10:11:01 localhost courierlocal:
id=0001EE47.3DACE2A9.000043B0,from=<[EMAIL PROTECTED]>,addr=<briann@aut
horityserver.com>,status: deferred

Oct 21 09:55:59 localhost courierlocal:
id=0001EE4D.3DB0752C.00000988,from=<[EMAIL PROTECTED]>,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=<[EMAIL PROTECTED]>

Oct 21 09:45:21 localhost courieresmtp:
id=0001EE6A.3DB0C5E1.00000F25,from=<>,addr=<[EMAIL PROTECTED]>: Connection
timed out Oct 21 09:45:21 localhost courieresmtp:
id=0001EE6A.3DB0C5E1.00000F25,from=<>,addr=<[EMAIL PROTECTED]>,status:
deferred

thats your server busy sending back bounces to the (possibly forged)
senders [EMAIL PROTECTED] and [EMAIL PROTECTED]

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

-------------------------------------------------------
This sf.net emial is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ad.doubleclick.net/clk;4699841;7576298;k?
http://www.sun.com/javavote
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

-------------------------------------------------------
This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users