Hi - I'm trying out PMG with on-premises Exchange prior to a potential production deployment. Please excuse newbie questions...
Is it possible to bounce incoming mail for unknown Exchange/AD recipients and recipient aliases BEFORE any spam processing (with an 'unknown recipient' message)?
And then, only once that process is performed, do spam protection processing ONLY for known recipients?
Currently, incoming messages to appear to be accepted and queued and only then checked for valid (exchange) recipient. Does this tell a sender that 'we are thinking about this' before finally returning a reject?
When I was using ScrolloutF1 there was a feature to test (using AD/LDAP lookup) for valid recipients (and rejecting if not valid) before any queuing or spam processing. This would seem to reduce the overhead of queuing before a decision for unknowns?
the initial response is:
: CCB1E1818DA: to=<unknown@[obfuscated].com>, relay=172.16.10.12[172.16.10.12]:25, delay=5, delays=0/0.01/0/5, dsn=2.1.5, status=deliverable (250 2.1.5 Recipient OK)
...which is potentially misleading?
Only after that initial response
: 181B29646493FEDF7AD: accept mail to <unknown@[obfuscated].com> (90B96181BD6) (rule: default-accept)
: 181B29646493FEDF7AD: processing time: 3.728 seconds (3.634, 0.025, 0)
: proxy-accept: END-OF-MESSAGE: 250 2.5.0 OK (181B29646493FEDF7AD); from=<[obfuscated]@outlook.com> to=<unknown@[obfuscated].com> proto=ESMTP helo=<EUR05-AM6-obe.outbound.protection.outlook.com>
: disconnect from mail-am6eur05olkn2087.outbound.protection.outlook.com[40.92.91.87] ehlo=1 mail=1 rcpt=1 bdat=1 quit=1 commands=5
: 90B96181BD6: to=<unknown@[obfuscated].com>, relay=172.16.10.12[172.16.10.12]:25, delay=5.1, delays=0.05/0/0/5, dsn=5.1.10, status=bounced (host 172.16.10.12[172.16.10.12] said: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup (in reply to end of DATA command))
: 90B96181BD6: removed
Also, it is possible to tailor the polite 'I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.' that also includes alot of detail about internal addressing and process to something more terse?
Thanks
Is it possible to bounce incoming mail for unknown Exchange/AD recipients and recipient aliases BEFORE any spam processing (with an 'unknown recipient' message)?
And then, only once that process is performed, do spam protection processing ONLY for known recipients?
Currently, incoming messages to appear to be accepted and queued and only then checked for valid (exchange) recipient. Does this tell a sender that 'we are thinking about this' before finally returning a reject?
When I was using ScrolloutF1 there was a feature to test (using AD/LDAP lookup) for valid recipients (and rejecting if not valid) before any queuing or spam processing. This would seem to reduce the overhead of queuing before a decision for unknowns?
the initial response is:
: CCB1E1818DA: to=<unknown@[obfuscated].com>, relay=172.16.10.12[172.16.10.12]:25, delay=5, delays=0/0.01/0/5, dsn=2.1.5, status=deliverable (250 2.1.5 Recipient OK)
...which is potentially misleading?
Only after that initial response
: 181B29646493FEDF7AD: accept mail to <unknown@[obfuscated].com> (90B96181BD6) (rule: default-accept)
: 181B29646493FEDF7AD: processing time: 3.728 seconds (3.634, 0.025, 0)
: proxy-accept: END-OF-MESSAGE: 250 2.5.0 OK (181B29646493FEDF7AD); from=<[obfuscated]@outlook.com> to=<unknown@[obfuscated].com> proto=ESMTP helo=<EUR05-AM6-obe.outbound.protection.outlook.com>
: disconnect from mail-am6eur05olkn2087.outbound.protection.outlook.com[40.92.91.87] ehlo=1 mail=1 rcpt=1 bdat=1 quit=1 commands=5
: 90B96181BD6: to=<unknown@[obfuscated].com>, relay=172.16.10.12[172.16.10.12]:25, delay=5.1, delays=0.05/0/0/5, dsn=5.1.10, status=bounced (host 172.16.10.12[172.16.10.12] said: 550 5.1.10 RESOLVER.ADR.RecipientNotFound; Recipient not found by SMTP address lookup (in reply to end of DATA command))
: 90B96181BD6: removed
Also, it is possible to tailor the polite 'I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.' that also includes alot of detail about internal addressing and process to something more terse?
Thanks
Last edited: