ISPConfig (sieve) messages redirect causes an SPF fail at the original sender

Hello, please help me.

1. For my mailbox [email protected], in the mailbox configuration in ISPConfig, I set the redirect of incoming messages to my second personal e-mail [email protected]
2. I receive email messages from [email protected] to my address [email protected] with redirect also to [email protected]

The problem is that I was contacted by [email protected], that the IP address of my server is filling him with DMARC reports due to SPF softfail and that he says that my server is spoofing his mail by sending mails on his behalf.

I noticed that ISPConfig manages the sieve file and adds this line to it:

redirect [email protected]

But apparently this method is not friendly to the SPF of the original sender. Apparently the redirect doesn't forward the messages correctly to be SPF compliant.

How to solve this please?

 

Search for mail SRS

 

I've made 2 tutorials on how to implement SRS in ISPConfig a while back.

https://forum.howtoforge.com/thread...heme-in-an-ispconfig-mailserver-part-1.89827/
https://forum.howtoforge.com/thread...heme-in-an-ispconfig-mailserver-part-2.89828/

 

That seems very complicated to me.

Couldn't the solution be one of the following two simple solutions?

• https://doc.dovecot.org/settings/pigeonhole/#pigeonhole_setting-sieve_redirect_envelope_from
• https://doc.dovecot.org/configuration_manual/sieve/configuring_auto_forward_sender_address/

 

Looks to me like it should work.
On the condition the mail is resigned by DKIM.
Otherwise you would have worked around your SPF issue but created a new DKIM issue.

I agree with @till about the implications rewriting the sender would have doing it this way.
That's why SRS is invented.

 

how is it possible for ispconfig to not add my dmarc after i have set a spf record i still get the eroor ther is no active spf record

 

I wrote answer to your other hijacked thread with the same question.