<div dir="auto">Thanks Shawn<div dir="auto"><br></div><div dir="auto">I discovered after the mail was sent to the list, that my mailwatch installation was a bit old.</div><div dir="auto">After upgrading to the current version of mailwatch I saw that the procedure has changed and releasing doesn't reproduce this problem.</div><div dir="auto"><br></div><div dir="auto">Thanks anyway!</div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Nov 27, 2018, 17:45 Shawn Iverson via MailScanner <<a href="mailto:mailscanner@lists.mailscanner.info">mailscanner@lists.mailscanner.info</a> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">George,<div><br></div><div>Indeed, Exchange does not out of the box accept email that is re-sent with the same message ID.</div><div><br></div><div>MailScanner, though, does not release quarantined messages, it just stores them in quarantine based on your rules. MailWatch is releasing the messages, not MailScanner, and it is probably using the sendmail command to do that, which means the message content is being released as-is.</div><div><br></div><div>You may want to reach out to the MailWatch team and see if they can assist you. In theory, it should be possible to modify the Message ID on the fly. I'm fairly certain that MailWatch is currently not doing that.</div></div><br><div class="gmail_quote"><div dir="ltr">On Mon, Nov 26, 2018 at 8:57 PM George Papamichelakis <<a href="mailto:gpapamichelakis@gmail.com" target="_blank" rel="noreferrer">gpapamichelakis@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><br><div>Hi all,</div><div><br></div><div>I have this scenario and I wonder how do you people cope with it (if you do) :</div><div><br></div><div>I have a postfix as a primary MX for a domain with some system users and an exchange server behind with some additional users. Normally when I release a quarantined message (mostly due to filename restrictions) the exchange users did not receive this email with the released attachment but the postfix (linux) system users did (exchange implements deduplication by default I guess). In the way I had to implement on dovecot a global sieve sieve filter which also adds deduplication . Now when I release a message no user gets the released message because it has the same ID as the one blocked in the first place. One way to address this is to modify the global sieve script to not discard the duplicate messages but to store them in a folder for the user to see , but this breaks the reason why the action was implemented in the first place.</div><div>A second way to bypass this restriction is to release the message in an alternative user and then this user to FWD to the original recipients, but this is also awkward. </div><div> I wonder how likely it is to be able to modify the messageID of the released quarantined message in order to bypass this ?</div><div><br></div><div>I use mailwatch to view and release quarantined messages.</div><div><br></div><div>Thanks for any suggestions</div><div>GP</div></div>
<br>
<br>
-- <br>
MailScanner mailing list<br>
<a href="mailto:mailscanner@lists.mailscanner.info" target="_blank" rel="noreferrer">mailscanner@lists.mailscanner.info</a><br>
<a href="http://lists.mailscanner.info/mailman/listinfo/mailscanner" rel="noreferrer noreferrer" target="_blank">http://lists.mailscanner.info/mailman/listinfo/mailscanner</a><br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="m_-463301728019788484gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr">Shawn Iverson, CETL<div>Director of Technology</div><div>Rush County Schools</div><div>765-932-3901 option 7</div><div><a href="mailto:iversons@rushville.k12.in.us" target="_blank" rel="noreferrer">iversons@rushville.k12.in.us</a></div><div><br></div><div><img src="https://docs.google.com/uc?export=download&id=0Bw5iD0ToYvs_cy1OZFNIZ0drYVU&revid=0Bw5iD0ToYvs_UitIcHVIWkJVVTl2VGpxVUE0d0FQcHBIRXk4PQ" width="96" height="96" style="font-size:12.8px"><img src="https://docs.google.com/uc?export=download&id=0Bw5iD0ToYvs_Zkh4eEs3R01yWXc&revid=0Bw5iD0ToYvs_QWpBK2Y2ajJtYjhOMDRFekZwK2xOamk5Q3Y0PQ" width="89" height="96"></div><div><img src="https://docs.google.com/uc?export=download&id=1aBrlQou4gjB04FY-twHN_0Dn3GHVNxqa&revid=0Bw5iD0ToYvs_RnQ0eDhHcm95WHBFdkNRbXhQRXpoYkR6SEEwPQ" style="font-size:12.8px"><br></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
<br>
<br>
-- <br>
MailScanner mailing list<br>
<a href="mailto:mailscanner@lists.mailscanner.info" target="_blank" rel="noreferrer">mailscanner@lists.mailscanner.info</a><br>
<a href="http://lists.mailscanner.info/mailman/listinfo/mailscanner" rel="noreferrer noreferrer" target="_blank">http://lists.mailscanner.info/mailman/listinfo/mailscanner</a><br>
<br>
</blockquote></div>