We have configured a mail domain with catch-all disabled (to reject mails to unknown user accounts). However, the domain does not report any rejection to the sending relay server and instead we can see this this mail in the Axigen queue with the remark “send failure”. This is not the expected behaviour.
Why does this happen ?
Thanks.
Hello Stefano,
Yes, do not worry, catch-all is working properly.
If the catch-all is disabled for a domain (btw, this is the default setup) than if a remote server is trying to send a message to a non-exiting account from that domain than the Axigen server will reject the SMTP session and you will see this into the logs (please increase the log level for SMTP Incoming service to Protocol Level so you will get all available details).
Now, if we are discussing about a message you see into Axigen queue than I could bet that “send failure” have nothing to do with the catch-all setup but with anything else. More information you should see if you will click on show info (present at rcptList row).
Also, without having the SMTP-IN and PROCESSING log lines relevant to that message it will be very hard to understand the real cause for having the message into queue.
HTH,
Ioan
Dear Indreias,
thanks for your message. However, I can’t confirm the described behaviour.
Please find more information below :
2022-11-30 15:42:10 +0000 16 axigen SMTP-IN:0019CB23: << MAIL FROM:sender@senderdomain.com SIZE=5973
2022-11-30 15:42:10 +0000 08 axigen SMTP-IN:0019CB23: Created new queue item with id 000AAB39
2022-11-30 15:42:10 +0000 08 axigen SMTP-IN:0019CB23: SPF result for MAIL FROM <sender@senderdomain.com@senderdomain.com> issued from EHLO domain <relayserver.ourdomain.com> connected from <111.111.111.111>: Neutral (spfHeader = ‘neutral (senderdomain.com: 111.111.111.111 is neither permitted nor denied by domain of sender@senderdomain.com) client-ip=111.111.111.111; envelope-from=sender@senderdomain.com; mechanism=default; identity=mailfrom; receiver=axigen;’; spfExplanation = ‘null’)
2022-11-30 15:42:10 +0000 16 axigen SMTP-IN:0019CB23: >> 250 Sender accepted
2022-11-30 15:42:10 +0000 16 axigen SMTP-IN:0019CB23: << RCPT TO:test2@targetdomain.com
2022-11-30 15:42:10 +0000 16 axigen SMTP-IN:0019CB23: >> 250 Recipient accepted
2022-11-30 15:42:10 +0000 16 axigen SMTP-IN:0019CB23: << DATA
2022-11-30 15:42:10 +0000 16 axigen SMTP-IN:0019CB23: >> 354 Ready to receive data; remember .
2022-11-30 15:42:10 +0000 16 axigen SMTP-IN:0019CB23: << 5974 bytes and final dot read
2022-11-30 15:42:10 +0000 08 axigen SMTP-IN:0019CB23: DomainKeys verification result: no signature
2022-11-30 15:42:10 +0000 08 axigen SMTP-IN:0019CB23: DKIM verification result: good
2022-11-30 15:42:20 +0000 08 axigen SMTP-IN:0019CB23: New mail kcEE.Z/++x5DeSKaowzvavfI/4Q.gLFCTdIE2QE@mail.senderdomain.com received from relayserver.ourdomain.com (111.111.111.111) with envelope from sender@senderdomain.com, recipients=1 (test2@targetdomain.com), size=5971, enqueued with id 0AAB39
2022-11-30 15:42:20 +0000 16 axigen SMTP-IN:0019CB23: >> 250 Mail queued for delivery
2022-11-30 15:42:20 +0000 16 axigen SMTP-IN:0019CB23: << QUIT
The account test2 does not exist in targetdomain.com but it is accepted.
Below is shown “mail queued for delivery” and here is the queue entry :
cptList test2@targetdomain.com [hide info]
Fail-info: Unable to connect to 222.222.222.222: Connection timed out
Status:PROCESSED - LOCAL
MBox:INBOX
To make it even stranger, 222.222.222.222 stands for the IP of the previous (!) service provider that held the DNS entries for targetdomain.com
The domain has moved recently to a new provider where we have put Axigen in the MX record and who - apparently - is leading all incoming mail to our relay server who leads them to Axigen.
First, the message should have been rejected by Axigen before reception as our relay server first asks if the recipient exists in Axigen. Apparently Axigen said “yes” and this should not happen. Then Axigen tries to deliver this mail to an old IP and I have no idea why or where this IP might be stored.
Hello Stefano,
If your targetdomain.com domain has been recently migrated from another hosting service (via automatic migration configuration) and you left the its Migration Status Enabled than the fact that messages for accounts not present locally (like not already migrated) are routed to the configured Old Mail server SMTP server is the expected behavior.
My recommendation is to go into WebAdmin > Automatic Migration and check the displayed status for the mentioned domain.
HTH,
Ioan
Dear Indreias,
I confirm that this was the reason for the queueing, thank you for your hint !
Now Axigen sends a mail back to the sender that this account does not exist. Our mail relay uses SMTP Recipient Verification to receive information about the availability of the account and to decide by himself how to handle this case. Apparently Axigen has no SMTP Recipient Verification functionality, is this correct ?
Thanks again for your efforts !
Hello Stefano,
Yes, Axigen has no SMTP Recipient Verification functionality built in.
However, from your report I could understand that something is not correctly configured on your side as instead of sending a Non Delivery Report message Axigen should simply reject the delivery tentative (like not accepting the message at all).
BR,
Ioan
Hi Indreias,
this is our configuration :
Do you have a hint where else our configuration might be wrong ?
Thanks a lot !
Hello Stefano,
The catch-all configuration is set properly and I didn’t put the blame on it.
Please share full SMTP-IN log lines corresponding to a message that comes from an external server and have a single non existing recipient so we could trace why the message generates an NDR message from Axigen and not be rejected at session level (as expected).
HTH,
Ioan
Thanks, I have solved it by putting mails to unknown recipients into the trash of a trash account and purge it daily.