<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Segoe UI";
panose-1:2 11 5 2 4 2 4 2 2 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:10.5pt;
font-family:"Segoe UI",sans-serif;}
span.E-postmall19
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=SV link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='mso-fareast-language:EN-US'>He of course meant the From: MIME sender. This can fail in a SPF check if identity aligment is set to strict.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'>Rewriting the From: heasder is one way to solve it, another way which preserves the original message in full, is to encapsulate the original message ina new message/rfc822 container where the new outer container, does have the rewritten details.<o:p></o:p></span></p><p class=MsoNormal><span style='mso-fareast-language:EN-US'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b>Från:</b> dovecot-bounces@dovecot.org <dovecot-bounces@dovecot.org> <b>För </b>Scott Q.<br><b>Skickat:</b> den 25 oktober 2020 17:02<br><b>Till:</b> Marc Roos <m.roos@f1-outsourcing.eu>; dovecot <dovecot@dovecot.org><br><b>Ämne:</b> Re: forwarding email with sieve of spf domains<o:p></o:p></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Segoe UI",sans-serif'>There's no ambiguity here, if you send a message, you are the sender. The envelope from should be yours.<o:p></o:p></span></p><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Segoe UI",sans-serif'><o:p> </o:p></span></p></div><div><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Segoe UI",sans-serif'><br>On Sunday, 25/10/2020 at 11:48 Marc Roos wrote:<o:p></o:p></span></p><blockquote style='border:none;border-left:solid #22437F 1.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-right:0cm'><p class=MsoNormal><span style='font-size:10.5pt;font-family:"Segoe UI",sans-serif'>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">https://tools.ietf.org/html/rfc5228#section-4.2</a><o:p></o:p></span></p></blockquote></div></div></body></html>