Hi,
I have a problem with a specific mail flow. My provider (home.pl) forwards emails to my PMG, but it doesn't support SRS. Instead, it overwrites the Envelope Sender (MAIL FROM) and X-Sieve-Redirected-From with the recipient's address.
Because of this, PMG sees every email as "internal" (sent from the domain itself). SPF always passes (checking provider's IP vs my domain), and RBLs are effectively useless.
Here is an example header (sent from user@wp.pl to user@mydomain.pl):
X-Sieve-Redirected-From: user@mydomain.pl
Return-Path: user@mydomain.pl
Authentication-Results: v496.home.net.pl; spf=pass (sender SPF authorized) smtp.mailfrom=wp.pl (client-ip=212.77.101.6; helo=mx1.wp.pl; envelope-from=user@wp.pl; receiver=<UNKNOWN>)
From: User <user@wp.pl>
To: user <user@mydomain.pl>
As you can see, the original sender address user@wp.pl only survives in the From: header.
My questions:
Best,
Artur
I have a problem with a specific mail flow. My provider (home.pl) forwards emails to my PMG, but it doesn't support SRS. Instead, it overwrites the Envelope Sender (MAIL FROM) and X-Sieve-Redirected-From with the recipient's address.
Because of this, PMG sees every email as "internal" (sent from the domain itself). SPF always passes (checking provider's IP vs my domain), and RBLs are effectively useless.
Here is an example header (sent from user@wp.pl to user@mydomain.pl):
X-Sieve-Redirected-From: user@mydomain.pl
Return-Path: user@mydomain.pl
Authentication-Results: v496.home.net.pl; spf=pass (sender SPF authorized) smtp.mailfrom=wp.pl (client-ip=212.77.101.6; helo=mx1.wp.pl; envelope-from=user@wp.pl; receiver=<UNKNOWN>)
From: User <user@wp.pl>
To: user <user@mydomain.pl>
As you can see, the original sender address user@wp.pl only survives in the From: header.
My questions:
- Can PMG be configured to use the domain from the From: header for RBL/DNSBL checks instead of the Envelope Sender?
- Is there a standard way in PMG to handle such a "broken" forwarding setup to regain filtering efficiency?
Best,
Artur