Dovecot - spam training through Outlook
Greetings everyone.
My dovecot mail server doesn't execute *train-spam.sh* script I set, when moving an e-mail from "Inbox" to "Junk" within Outlook.
However, it does it fine when using an online webmail client a.k.a. Roundcube Webmail.
Here are few lines from my maillog file showing the situation. Any idea would be much appreciated.
Log output of the mentioned process:
From Outlook 2016 (Move from Inbox to Junk folder) Mar 5 07:50:37 mailserver1 dovecot: imap(info@mydomain.com)<72501><uGYu6hWgeupOrFX1>: delete: box=INBOX, uid=10, msgid=016f01d5f248$45900090$d0b001b0$@test.xxx, size=3344 Mar 5 07:50:37 mailserver1 dovecot: imap(info@mydomain.com)<72501><uGYu6hWgeupOrFX1>: expunge: box=INBOX, uid=10, msgid=016f01d5f248$45900090$d0b001b0$@test.xxx, size=3344
From Roundcube Webmail (Move from Inbox to Junk folder) Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: sieve: pipe action: piped message to program `train-spam.sh' Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: sieve: left message in mailbox 'Junk' Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: copy from INBOX: box=Junk, uid=9, msgid=2eed864c2c38a690349e87dbd271e474@test.xxx, size=1214 Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: expunge: box=INBOX, uid=15, msgid=2eed864c2c38a690349e87dbd271e474@test.xxx, size=1214
Dovecot version: 2.3.9.3 running on OpenBSD 6.6
Many thanks, Özgür.
On 5.3.2020 9.00, Özgür Kazancci wrote:
Greetings everyone.
My dovecot mail server doesn't execute *train-spam.sh* script I set, when moving an e-mail from "Inbox" to "Junk" within Outlook.
However, it does it fine when using an online webmail client a.k.a. Roundcube Webmail.
Here are few lines from my maillog file showing the situation. Any idea would be much appreciated.
Log output of the mentioned process:
From Outlook 2016 (Move from Inbox to Junk folder) Mar 5 07:50:37 mailserver1 dovecot: imap(info@mydomain.com)<72501><uGYu6hWgeupOrFX1>: delete: box=INBOX, uid=10, msgid=016f01d5f248$45900090$d0b001b0$@test.xxx, size=3344 Mar 5 07:50:37 mailserver1 dovecot: imap(info@mydomain.com)<72501><uGYu6hWgeupOrFX1>: expunge: box=INBOX, uid=10, msgid=016f01d5f248$45900090$d0b001b0$@test.xxx, size=3344
From Roundcube Webmail (Move from Inbox to Junk folder) Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: sieve: pipe action: piped message to program `train-spam.sh' Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: sieve: left message in mailbox 'Junk' Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: copy from INBOX: box=Junk, uid=9, msgid=2eed864c2c38a690349e87dbd271e474@test.xxx, size=1214 Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: expunge: box=INBOX, uid=15, msgid=2eed864c2c38a690349e87dbd271e474@test.xxx, size=1214
Dovecot version: 2.3.9.3 running on OpenBSD 6.6
Many thanks, Özgür.
Hi!
Can you share your sieve script too?
Aki
Hi Aki!
Thank you for your reply.
Sure, here are the related lines within my conf files and sieve scripts: https://hastepaste.com/view/Erk8Ra
Thank you so much, Regards.
Aki Tuomi aki.tuomi@open-xchange.com, 5 Mar 2020 Per, 11:31 tarihinde şunu yazdı:
On 5.3.2020 9.00, Özgür Kazancci wrote:
Greetings everyone.
My dovecot mail server doesn't execute *train-spam.sh* script I set, when moving an e-mail from "Inbox" to "Junk" within Outlook.
However, it does it fine when using an online webmail client a.k.a. Roundcube Webmail.
Here are few lines from my maillog file showing the situation. Any idea would be much appreciated.
Log output of the mentioned process:
From Outlook 2016 (Move from Inbox to Junk folder) Mar 5 07:50:37 mailserver1 dovecot: imap(info@mydomain.com)<72501><uGYu6hWgeupOrFX1>: delete: box=INBOX, uid=10, msgid=016f01d5f248$45900090$d0b001b0$@test.xxx, size=3344 Mar 5 07:50:37 mailserver1 dovecot: imap(info@mydomain.com)<72501><uGYu6hWgeupOrFX1>: expunge: box=INBOX, uid=10, msgid=016f01d5f248$45900090$d0b001b0$@test.xxx, size=3344
From Roundcube Webmail (Move from Inbox to Junk folder) Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: sieve: pipe action: piped message to program `train-spam.sh' Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: sieve: left message in mailbox 'Junk' Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: copy from INBOX: box=Junk, uid=9, msgid=2eed864c2c38a690349e87dbd271e474@test.xxx, size=1214 Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: expunge: box=INBOX, uid=15, msgid=2eed864c2c38a690349e87dbd271e474@test.xxx, size=1214
Dovecot version: 2.3.9.3 running on OpenBSD 6.6
Many thanks, Özgür.
Hi!
Can you share your sieve script too?
Aki
Ah.
This is because you only match COPY, and outlook is doing APPEND+EXPUNGE instead.
Aki
On 5.3.2020 10.39, Özgür Kazancci wrote:
Hi Aki!
Thank you for your reply.
Sure, here are the related lines within my conf files and sieve scripts: https://hastepaste.com/view/Erk8Ra
Thank you so much, Regards.
Aki Tuomi aki.tuomi@open-xchange.com, 5 Mar 2020 Per, 11:31 tarihinde şunu yazdı:
On 5.3.2020 9.00, Özgür Kazancci wrote:
Greetings everyone.
My dovecot mail server doesn't execute *train-spam.sh* script I set, when moving an e-mail from "Inbox" to "Junk" within Outlook.
However, it does it fine when using an online webmail client a.k.a. Roundcube Webmail.
Here are few lines from my maillog file showing the situation. Any idea would be much appreciated.
Log output of the mentioned process:
From Outlook 2016 (Move from Inbox to Junk folder) Mar 5 07:50:37 mailserver1 dovecot: imap(info@mydomain.com)<72501><uGYu6hWgeupOrFX1>: delete: box=INBOX, uid=10, msgid=016f01d5f248$45900090$d0b001b0$@test.xxx, size=3344 Mar 5 07:50:37 mailserver1 dovecot: imap(info@mydomain.com)<72501><uGYu6hWgeupOrFX1>: expunge: box=INBOX, uid=10, msgid=016f01d5f248$45900090$d0b001b0$@test.xxx, size=3344
From Roundcube Webmail (Move from Inbox to Junk folder) Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: sieve: pipe action: piped message to program `train-spam.sh' Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: sieve: left message in mailbox 'Junk' Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: copy from INBOX: box=Junk, uid=9, msgid=2eed864c2c38a690349e87dbd271e474@test.xxx, size=1214 Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: expunge: box=INBOX, uid=15, msgid=2eed864c2c38a690349e87dbd271e474@test.xxx, size=1214
Dovecot version: 2.3.9.3 running on OpenBSD 6.6
Many thanks, Özgür.
Hi!
Can you share your sieve script too?
Aki
I have given up on using any spam training with Outlook because Outlook seems rebuild the mails when you touch them.
What it broke here:
- Received Headers reshuffled and useless
- x-mailer set to outlook
There are multiple bug reports about this and MS seems to have fixed it once in Outlook 2010 but broke it again sometime later.
I would be careful not to spam-report yourself with those mails since they sometimes are rewritten to originate from your hosts by outlook. Only the body seems to be preserved and even that might be re-encoded with base64.
Regards,
Claudius
On 05.03.2020 09:46, Aki Tuomi wrote:
Ah.
This is because you only match COPY, and outlook is doing APPEND+EXPUNGE instead.
Aki
On 5.3.2020 10.39, Özgür Kazancci wrote:
Hi Aki!
Thank you for your reply.
Sure, here are the related lines within my conf files and sieve scripts: https://hastepaste.com/view/Erk8Ra
Thank you so much, Regards.
Aki Tuomi aki.tuomi@open-xchange.com, 5 Mar 2020 Per, 11:31 tarihinde şunu yazdı:
On 5.3.2020 9.00, Özgür Kazancci wrote:
Greetings everyone.
My dovecot mail server doesn't execute *train-spam.sh* script I set, when moving an e-mail from "Inbox" to "Junk" within Outlook.
However, it does it fine when using an online webmail client a.k.a. Roundcube Webmail.
Here are few lines from my maillog file showing the situation. Any idea would be much appreciated.
Log output of the mentioned process:
From Outlook 2016 (Move from Inbox to Junk folder) Mar 5 07:50:37 mailserver1 dovecot: imap(info@mydomain.com)<72501><uGYu6hWgeupOrFX1>: delete: box=INBOX, uid=10, msgid=016f01d5f248$45900090$d0b001b0$@test.xxx, size=3344 Mar 5 07:50:37 mailserver1 dovecot: imap(info@mydomain.com)<72501><uGYu6hWgeupOrFX1>: expunge: box=INBOX, uid=10, msgid=016f01d5f248$45900090$d0b001b0$@test.xxx, size=3344
From Roundcube Webmail (Move from Inbox to Junk folder) Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: sieve: pipe action: piped message to program `train-spam.sh' Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: sieve: left message in mailbox 'Junk' Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: copy from INBOX: box=Junk, uid=9, msgid=2eed864c2c38a690349e87dbd271e474@test.xxx, size=1214 Mar 5 07:48:45 mailserver1 dovecot: imap(info@mydomain.com)<14673>: expunge: box=INBOX, uid=15, msgid=2eed864c2c38a690349e87dbd271e474@test.xxx, size=1214
Dovecot version: 2.3.9.3 running on OpenBSD 6.6
Many thanks, Özgür. Hi!
Can you share your sieve script too?
Aki
Say I am running some script on a user's mail account. What is the easiest way to store the log output of this script directly into a mail folder of this user? I do not want to send a message to the inbox.
On 05 Mar 2020, at 07:00, Marc Roos M.Roos@f1-outsourcing.eu wrote:
Say I am running some script on a user's mail account. What is the easiest way to store the log output of this script directly into a mail folder of this user? I do not want to send a message to the inbox.
command > /path/to/file
R dp you mean so that the log file appears as a “email” for the user?You’ll need to make a fake message and put the log file in the body, put that in the mail folder with appropriate permssionds and filename, an possibly rebuild the index.
Or, far simpler, would be to send a message to the inbox.
-- Live long enough to become a problem to your kids.
On Thu, 5 Mar 2020 12:53:32 +0100, Claudius stated:
There are multiple bug reports about this and MS seems to have fixed it once in Outlook 2010 but broke it again sometime later.
Outlook 2010 is ancient. Exactly where did you find these bug reports? Have you tried submitting a new bug report? I assume you are using the latest version of MS Outlook.
-- Gerard
On 05.03.2020 16:26, Jerry wrote:
On Thu, 5 Mar 2020 12:53:32 +0100, Claudius stated:
There are multiple bug reports about this and MS seems to have fixed it once in Outlook 2010 but broke it again sometime later. Outlook 2010 is ancient. Exactly where did you find these bug reports? Have you tried submitting a new bug report? I assume you are using the latest version of MS Outlook.
I think I was confusing it with the last working version. 2010 didn't have the issue. 2013 has/had it.
Here is the thread I bookmarked when trying to resolve this before giving up and shelving it: https://social.msdn.microsoft.com/Forums/en-US/8eafe714-8a8c-44bc-9228-d6a68...
I think nothing has been fixed as Outlook still does APPEND.
Regards,
Claudius
On Thu, 5 Mar 2020 17:08:48 +0100, Claudius stated:
On 05.03.2020 16:26, Jerry wrote:
On Thu, 5 Mar 2020 12:53:32 +0100, Claudius stated:
There are multiple bug reports about this and MS seems to have fixed it once in Outlook 2010 but broke it again sometime later. Outlook 2010 is ancient. Exactly where did you find these bug reports? Have you tried submitting a new bug report? I assume you are using the latest version of MS Outlook.
I think I was confusing it with the last working version. 2010 didn't have the issue. 2013 has/had it.
Here is the thread I bookmarked when trying to resolve this before giving up and shelving it: https://social.msdn.microsoft.com/Forums/en-US/8eafe714-8a8c-44bc-9228-d6a68...
I think nothing has been fixed as Outlook still does APPEND.
Again, these are obsoleted versions of MS Outlook. The latest official release is the 2019 version. I am actually using the beta version, but I doubt that it would make much difference. I would highly recommend updating to the latest version and then retrying the script. If it still fails, then file a bug report.
I actually read the posts in the link you supplied. The last post was in regards to Outlook 2013, and it is nearly three years old. Complaining about the the operation of an old version is like beating a dead horse.
Good luck.
-- Jerry
On 05.03.2020 17:50, Jerry wrote:
Again, these are obsoleted versions of MS Outlook. The latest official release is the 2019 version. I am actually using the beta version, but I doubt that it would make much difference. I would highly recommend updating to the latest version and then retrying the script. If it still fails, then file a bug report.
I actually read the posts in the link you supplied. The last post was in regards to Outlook 2013, and it is nearly three years old. Complaining about the the operation of an old version is like beating a dead horse.
Did you verify that the issue is gone in the new version or are you just pitching Outlook to me?
As I said we don't use it anymore. Last I saw this issue hasn't been resolved in any recent Outlook version.
Also Outlook 2013 is still supported until 2023 so I don't know what you are complaining about people complaining.
Good luck.
Thanks, same to you.
On Fri, 6 Mar 2020 14:23:09 +0100, Claudius stated:
On 05.03.2020 17:50, Jerry wrote:
Again, these are obsoleted versions of MS Outlook. The latest official release is the 2019 version. I am actually using the beta version, but I doubt that it would make much difference. I would highly recommend updating to the latest version and then retrying the script. If it still fails, then file a bug report.
I actually read the posts in the link you supplied. The last post was in regards to Outlook 2013, and it is nearly three years old. Complaining about the the operation of an old version is like beating a dead horse.
Did you verify that the issue is gone in the new version or are you just pitching Outlook to me?
Actually, I have the beta version of Outlook. However, since I don't use it in the same manner as you do, I obviously have not proof either way as 6to its behavior.
Microsoft maintains several chat forums that offer advice. I have used several of them myself. Your question might best be asked, and hopefully answered there.
As I said we don't use it anymore. Last I saw this issue hasn't been resolved in any recent Outlook version.
Also Outlook 2013 is still supported until 2023 so I don't know what you are complaining about people complaining.
I am not complaining, just pointing out that it is by no means current. Microsoft, as well as many other software authors, rarely back-ports a non-security feature unless it is a real show-stopper. This obviously is not.
Good luck.
Thanks, same to you.
-- Jerry
participants (6)
-
＠lbutlr
-
Aki Tuomi
-
Claudius
-
Jerry
-
Marc Roos
-
Özgür Kazancci