<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hello Andrew,<br><br>The issue comes up when doing immediate forwarding. That is, a people setup an email address to forward to some other address that they actually check (whether that be because the other address is old and rarely used anymore, or because they don't receive enough traffic to check that address very often or some other reason). Therefore, they receive email and have immediate forwarding setup via virtual aliases. This immediate forwarding, if disarmed, will get rejected if the email is DKIM signed. The only solution I can see currently is to disable disarming, but it would be nice to have the ability to disable it only in cases where there is a DKIM signature present.<br><br> Lev<br><br><div>From: andrew@topdog.za.net<br>Subject: Re: Mailscanner and Base64<br>Date: Sun, 12 Jul 2015 00:53:43 +0200<br>To: mailscanner@lists.mailscanner.info<br><br><pre> <br>On 11 Jul 2015, at 11:55 PM, Lev Nagdimunov <levnagdimunov0@hotmail.com> wrote:<br> <br>> An option to not disarm only when the email is DKIM signed would be great but that's a feature request and not a bug like I thought.<br> <br>I would think disarming still trumps signing, your destination server should not be performing<br>DKIM checks in any case.<br> <br>For outbound messages you should not have an issue as messages should only be signed<br>after they have been processed by MailScanner<br> <br>- Andrew<br> <br></pre><br>--
MailScanner mailing list
mailscanner@lists.mailscanner.info
http://lists.mailscanner.info/listinfo/mailscanner</div> </div></body>
</html>