<html>
<head>
<style type="text/css">
body,p,td,div,span{
font-size:14px;font-family: -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, Helvetica, Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol";
};
body p{
margin:0px;
}
</style>
</head>
<body>There's no ambiguity here, if you send a message, you are the sender. The envelope from should be yours.<div><br></div><div><br>On Sunday, 25/10/2020 at 11:48 Marc Roos wrote:<br><blockquote style="border:0;border-left: 2px solid #22437f; padding:0px; margin:0px; padding-left:5px; margin-left: 5px; ">Say someone has setup spf for his domain and sends an email to a user <br>
that has in roundcube enabled the sieve forward. If the message is <br>
forwarded without altering the message headers, this could result in a <br>
message being blocked or not relayed, because sending hosts ip, is not <br>
in the spf of the from: domain.<br>
<br>
Possible solutions are:<br>
<br>
- add option if enabled, it replaces the From: with that of the email <br>
address of the sieve user. (Maybe move the original sender to the <br>
Reply-To header? Maybe exception for 'internal' forward?)<br>
- Upon processing the message, check the spf records, if they are <br>
enforced, do the above, otherwise do nothing.<br>
<br>
<br>
<a href="https://tools.ietf.org/html/rfc5228#section-4.2" target="_blank" class="normal-link">https://tools.ietf.org/html/rfc5228#section-4.2</a></blockquote></div></body></html>