Quarantine release and Dedpuplication

[George Papamichelakis]

Thanks Shawn

I discovered after the mail was sent to the list, that my mailwatch
installation was a bit old.
After upgrading to the current version of mailwatch I saw that the
procedure has changed and releasing doesn't reproduce this problem.

Thanks anyway!

On Tue, Nov 27, 2018, 17:45 Shawn Iverson via MailScanner <
mailscanner at lists.mailscanner.info wrote:

> George,
>
> Indeed, Exchange does not out of the box accept email that is re-sent with
> the same message ID.
>
> 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.
>
> 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.
>
> On Mon, Nov 26, 2018 at 8:57 PM George Papamichelakis <
> gpapamichelakis at gmail.com> wrote:
>
>>
>> Hi all,
>>
>> I have this scenario and I wonder how do you people cope with it (if you
>> do) :
>>
>> 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.
>> 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.
>>  I wonder how likely it is to be able to modify the messageID of the
>> released quarantined message in order to bypass this ?
>>
>> I use mailwatch to view and release quarantined messages.
>>
>> Thanks for any suggestions
>> GP
>>
>>
>> --
>> MailScanner mailing list
>> mailscanner at lists.mailscanner.info
>> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>>
>>
>
> --
> Shawn Iverson, CETL
> Director of Technology
> Rush County Schools
> 765-932-3901 option 7
> iversons at rushville.k12.in.us
>
>
>
>
> --
> MailScanner mailing list
> mailscanner at lists.mailscanner.info
> http://lists.mailscanner.info/mailman/listinfo/mailscanner
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mailscanner.info/pipermail/mailscanner/attachments/20181127/b262fec6/attachment.html>