Hi,
I don't think it's a problem with your qmail setup, but a problem with the remote mta.
If the recipient does not exist on the remote server, it must notify immediately the sender.
Following is a transcript for what happens when I send an email to a non-existent user from my qmail server:
Quote:
@400000004c0a865f1ca15e5c new msg 4792949
@400000004c0a865f1ca16a14 info msg 4792949: bytes 324 from <sender@qmail.mydomain.com> qp 16910 uid 1003
@400000004c0a865f20a50c4c starting delivery 48: msg 4792949 to remote recipient@remotedomain.com
@400000004c0a865f20a51804 status: local 0/10 remote 1/20
@400000004c0a865f215ac7bc delivery 48: failure: 192.168.0.1_does_not_like_recipient./Remote_host_said:_550_5.1.1_<recipient@remotedomain.com>..._User_unknown/Giving_up_on_x.x.x.x./
@400000004c0a865f215ad75c status: local 0/10 remote 0/20
@400000004c0a865f26ab0e34 bounce msg 4792949 qp 16912
@400000004c0a865f26ab19ec end msg 4792949
@400000004c0a865f26af406c new msg 4793198
@400000004c0a865f26af4454 info msg 4793198: bytes 971 from <> qp 16912 uid 1008
@400000004c0a865f2b3224c4 starting delivery 49: msg 4793198 to local sender@qmail.mydomain.com
@400000004c0a865f2b32307c status: local 1/10 remote 0/20
@400000004c0a86672749a7c4 delivery 49: success: did_1+0+1/
@400000004c0a86672749b37c status: local 0/10 remote 0/20
@400000004c0a86672749b764 end msg 4793198
|
Since in your case this takes a week to happen, I guess the remote mta tries for this period of time to deliver the message (maybe to a catch-all account?).
You can try to send another mail to the non-existent recipient and watch qmail logs to see if you get the "user unknown" notification immediately.
