On 12/15/2017 12:27 PM, Steve Atkins wrote:
https://github.com/imapsync/imapsync or _maybe_
https://github.com/wrzlbrmft/imapcopy
If the destination system is dovecot then they should probably use dsync.
If the destination system is a Large Webmail Provider then they should probably use the
I wonder if it would ever work to allow a server to forward a message
while including headers that indicate the message had signs of spam. It
would only work in the negative direction (this message is spam, but not
this message is ham).
I kind of think of in the way the courts do with
On 7/25/2017 8:14 AM, Vladimir Dubrovin via mailop wrote:
STARTTLS is opportunistic and doesn't protect against active
Man-in-the-Middle. In case of TLS problems it falls back to plain text.
Interestingly, that's not always the case now. We typoed the cert on
one of our list servers earlier
On 2/10/2017 3:14 AM, Klaus Ethgen wrote:
Never, never ever tell that to your users. Forward is the better idea
for that. Sure, you have to handle the spam yourself.
The challenge that we run into as mail providers is handling the the
mail that we are uncertain about. On a consolidated mail
