Cheers,
I am evaluating PMG to deploy to our customers. Target systems are Exchange SE.
I set up a test drive where I evaluate several functions. One I absolutely need is recipient verification. Exchange rejects mails for non-existing recipients. This should also be reflected to the PMG. I activated:
450 4.1.1 <honk.honk@xyz.de>: Recipient address rejected: unverified address: Address verification in progress; from=<test@test.de> to=<honk.honk@xyz.de> proto=ESMTP helo=<VHUD-01>
So far so good.
Next log entry is:
from=<double-bounce@pmg-0.dmzxyz.com>, size=263, nrcpt=1 (queue active)
to=<honk.honk@xyz.de>, relay=192.168.110.8[192.168.110.8]:25, delay=18, delays=0.01/0.04/0.04/18, dsn=2.1.5, status=deliverable (250 2.1.5 Recipient OK)
IP address is the one of the exchange server.
When sending again to the recipient the message is bounced by Exchange:
0E6DB50121D: to=<honk.honk@xyz.de>, relay=192.168.110.8[192.168.110.8]:25, delay=24, delays=0.8/0/0.03/24, dsn=5.1.10, status=bounced (host 192.168.110.8[192.168.110.8] said: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup (in reply to end of DATA command))
The bounce is expected. However - the second log entry is not. Against what is the check performed? If I cannot check against the recipients then this would be a real showstopper - I want such mails to be rejected, not bounces to be created. Is this how it is supposed to work? If not: any hints how to get this working? I would use PMG in front of Exchange, doing all the AntiSpam stuff which currently Exchange does.
What is even worse is that a second Email sent with a nonexisting recipient is also accepted by PMG and then bounced by Exchange.
Regards,
Thomas
I am evaluating PMG to deploy to our customers. Target systems are Exchange SE.
I set up a test drive where I evaluate several functions. One I absolutely need is recipient verification. Exchange rejects mails for non-existing recipients. This should also be reflected to the PMG. I activated:
- Verify Receivers (550)
- Before Queue Filtering
450 4.1.1 <honk.honk@xyz.de>: Recipient address rejected: unverified address: Address verification in progress; from=<test@test.de> to=<honk.honk@xyz.de> proto=ESMTP helo=<VHUD-01>
So far so good.
Next log entry is:
from=<double-bounce@pmg-0.dmzxyz.com>, size=263, nrcpt=1 (queue active)
to=<honk.honk@xyz.de>, relay=192.168.110.8[192.168.110.8]:25, delay=18, delays=0.01/0.04/0.04/18, dsn=2.1.5, status=deliverable (250 2.1.5 Recipient OK)
IP address is the one of the exchange server.
When sending again to the recipient the message is bounced by Exchange:
0E6DB50121D: to=<honk.honk@xyz.de>, relay=192.168.110.8[192.168.110.8]:25, delay=24, delays=0.8/0/0.03/24, dsn=5.1.10, status=bounced (host 192.168.110.8[192.168.110.8] said: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup (in reply to end of DATA command))
The bounce is expected. However - the second log entry is not. Against what is the check performed? If I cannot check against the recipients then this would be a real showstopper - I want such mails to be rejected, not bounces to be created. Is this how it is supposed to work? If not: any hints how to get this working? I would use PMG in front of Exchange, doing all the AntiSpam stuff which currently Exchange does.
What is even worse is that a second Email sent with a nonexisting recipient is also accepted by PMG and then bounced by Exchange.
Regards,
Thomas