Recipient email address is possibly incorrect on antispam gateway

Hi,

A sender always encounters problem on

This is a delivery failure notification message indicating that an email you addressed to email address :
--xxxx@xxxxxx.com

could not be delivered. The problem appears to be :
-- Recipient email address is possibly incorrect

Additional information follows :
-- Transaction failed

Any idea ?
-------------------------------------------------------------------------------

as1 postfix/smtpd[27122]: warning: TLS library problem: 27122:error:14094416:SSL routines:ssl3_read_bytes:sslv3 alert certificate unknown:s3_pkt.c:1472:SSL alert number 46:

as1 postfix/smtpd[29111]: warning: proxy inet:127.0.0.1:10020 rejected "RCPT TO:<xxx@xxxx.com>": "554 Transaction failed"
AXISHKAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Tomas ValentaIT ManagerCommented:
Hi,
from the log it looks like the foreign mail system rejected your message but error message is common mesage.
Can turn on diagnostic log and give me SMTP transaction info for this message, please ?
In this log we can see real smtp To, what type of connection the servers negotiate and also reason of closing
transmission.
Scott SilvaNetwork AdministratorCommented:
If your user is anything like my users, they have a bad address in autocomplete, but keep trying to use it... Then they try and blame it on the server...
AXISHKAuthor Commented:
On exchange smtp receive log, there is no entry for those missing emails.

On our Antispam gateway, only the following is logged.
"as1 postfix/smtpd[29111]: warning: proxy inet:127.0.0.1:10020 rejected "RCPT TO:<xxx@xxxx.com>": "554 Transaction failed"

Can Exchange smtp log can record all incoming connection, not match it is success or fail ?

Thx
IT Pros Agree: AI and Machine Learning Key

We’d all like to think our company’s data is well protected, but when you ask IT professionals they admit the data probably is not as safe as it could be.

Tomas ValentaIT ManagerCommented:
SO as I understand now you have internal Exchange server which deliver messages to your mail gateway.
The error message is on this mail gateway and the flow of the message is Exchange server -> mail gateway -> foreign system.
On mail gateway the system is receiving message from Exchange on some port, then internal flow on mail gateway
between smtp server and antispam engine and than final delivery out. It looks like (based on port 127.0.0.1 which is local loopback address) the problem could be internal in mail gateway.
Turn on diagnostics logging of SMTP server in Exchange - http://exchangepedia.com/2007/05/exchange-server-2007-logging-smtp-protocol-activity.html to be sure the e-mail address and other part of transmission are OK.
Next step will depend on result - Exchange server issue or mail gateway issue.
AXISHKAuthor Commented:
The problem is on the incoming emails.

Sender -> Anti-spam gateway --> Exchange 2010

SMTP log for receiving has been turned on. However, missing emails can be shown on the log.

Thx
Scott SilvaNetwork AdministratorCommented:
Does your gateway have some sort of user verification?
Mine uses LDAP to look up users before passing on the mail... Could yours have a manually created list that isn't getting updated? Or one created by a cron job that is failing to update?
AXISHKAuthor Commented:
No such setup.

Actually, can LDAP vertify incoming sender from public internet ? Only sender with my home domain should check LDAP, Otherwise, it shoudln't or it will block other domains to pass through, correct ?

Thx
Scott SilvaNetwork AdministratorCommented:
Actually there are filters that do "callback" verification, but it is a depreciated practice if I remember correctly.

Also some filters will verify if a senders domain has a valid MX address, some will verify other aspects of the sender.

So these are messages coming into your organization, and getting stopped at the filter? Or they make it to the exchange server and then disappear?
AXISHKAuthor Commented:
Bypass the gateway and all mails can deliver to Exchange within missing. Already reported to vendor but seem like it takes time to resolve...  They are still investigating.

Is there any apps that can accept mails and a decision to route to diferent hop based on email domain ? They may be a quick temporary solutoin.

Thx
Tomas ValentaIT ManagerCommented:
OK, it is possible to turn on temporary debug logging on IMSVA (Logs\Settings - Log Files - Application log detail level - DEBUG)
and ask your partner to send the same problematic message again, please ?
AXISHKAuthor Commented:
The setting was setup to DEBUG.

How to get the log for investigation ?

Thx
Tomas ValentaIT ManagerCommented:
the log files are stored in /opt/trend/imss/log.
Go to the Logs\Query in IMSVA console and here try at first Message tracking type
and type query and result you can export to the csv file. In Admin guide on page 25-5
you can find examples of queries.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux

From novice to tech pro — start learning today.