Redirects 550'd So why no SRS method
Happy New Year!
Now to Aki, Timo, Corr, why, when setting up mail forwarding, is sieve not automatically configuring rules for SRS, it has this ability for long time, yet dovecots sieve based forwarding just creates a plain old redirect "forward" resulting in,in 2024, 99% of forwarded emails getting rejected for failing SPF because it's not enabling the require or the rules needed for successful sender rewriting.
Is this an oversight? and I suppose the bigger question is, when is it planned to be corrected to using SRS method?
Happy New Year!
Now to Aki, Timo, Corr, why, when setting up mail forwarding, is sieve not automatically configuring rules for SRS, it has this ability for long time, yet dovecots sieve based forwarding just creates a plain old redirect "forward" resulting in,in 2024, 99% of forwarded emails getting rejected for failing SPF because it's not enabling the require or the rules needed for successful sender rewriting.
Is this an oversight? and I suppose the bigger question is, when is it planned to be corrected to using SRS method?
While I would MUCH prefer SRS as you mentioned, it would dramatically save me time and effort, there is at least this option:
sieve_redirect_envelope_from = recipient
It's not SRS, but it will rewrite the sender to the recipient address. So user@gmail.com sends to user@yourdomain.tld, which redirects to whoever@gmail.com, then user@yourdomain.tld becomes the envelope sender for the message headed toward whoever@gmail.com.
It's better. It's not what I want, just better.
On 2024-01-04 07:51, Laura Steynes wrote:
Happy New Year!
Now to Aki, Timo, Corr, why, when setting up mail forwarding, is sieve not automatically configuring rules for SRS, it has this ability for long time, yet dovecots sieve based forwarding just creates a plain old redirect "forward" resulting in,in 2024, 99% of forwarded emails getting rejected for failing SPF because it's not enabling the require or the rules needed for successful sender rewriting.
Is this an oversight? and I suppose the bigger question is, when is it planned to be corrected to using SRS method?
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org
• Laura Steynes [2024-01-04 23:51]:
Happy New Year!
Now to Aki, Timo, Corr, why, when setting up mail forwarding, is sieve not automatically configuring rules for SRS, it has this ability for long time, yet dovecots sieve based forwarding just creates a plain old redirect "forward" resulting in,in 2024, 99% of forwarded emails getting rejected for failing SPF because it's not enabling the require or the rules needed for successful sender rewriting.
External forwarding in 2024 is rather fragile anyway, isn't it?
Is this an oversight? and I suppose the bigger question is, when is it planned to be corrected to using SRS method?
I'd consider this a task for the MTA doing the deliveries of the messages submitted by Dovecot to ensure that all external messages have an envelope sender which would make SPF happy (even though I see that Cyrus' Sieve gained SRS support in 2010). SRS requires coordination with the MTA listed as MX for the domain used in the SRS envelope anyway, so one might as well just do all rewriting on the MTA level.
participants (3)
-
jarland＠mxroute.com
-
Kirill Miazine
-
Laura Steynes