Once upon a time, Stephan Bosch <stephan at rename-it.nl> said:> You can check the handling of a particular message yourself using the > sieve-test tool (there is a man page for it). By specifying the `-t - > -Tlevel=matching` options, you'll get detailed information on why a > particular decision is made.Hmm, that's weird. sieve-test says it would store the message into the Spam folder (as expected), but it was definitely delivered to INBOX.> Without insight in your configuration (output from `dovecot -n`) and an > example of a message that is mishandled, I cannot tell you more.Here you go. I changed the local part of the user's email address in the spam message, and the doveadm password in the doveconf output, but that's all. http://www.cmadams.net/misc/dove/doveconf-n.txt http://www.cmadams.net/misc/dove/spam-message.txt I have three Dovecot VMs behind a pair of Dovecot director VMs; this is from the actual host that handled the delivery (all three backend hosts are showing the same issue). Users are in MySQL and mail is on NFS. There are some things configured, like managesieve, that aren't currently used. This is a new setup, migrated from Courier; I made the switch a couple of weeks ago (not my first time using Dovecot, just finally got a chance to migrate this setup). Thanks. -- Chris Adams <cma at cmadams.net>
On 5/15/2015 5:56 PM, Chris Adams wrote:> Once upon a time, Stephan Bosch <stephan at rename-it.nl> said: >> You can check the handling of a particular message yourself using the >> sieve-test tool (there is a man page for it). By specifying the `-t - >> -Tlevel=matching` options, you'll get detailed information on why a >> particular decision is made. > Hmm, that's weird. sieve-test says it would store the message into the > Spam folder (as expected), but it was definitely delivered to INBOX.BTW, did you consult your logs for any errors? If an error occurs during Sieve processing, the default behavior is to file the message into INBOX (e.g. when the Spam folder doesn't exist). Regards, Stephan.
Once upon a time, Stephan Bosch <stephan at rename-it.nl> said:> On 5/15/2015 5:56 PM, Chris Adams wrote: > > Once upon a time, Stephan Bosch <stephan at rename-it.nl> said: > >> You can check the handling of a particular message yourself using the > >> sieve-test tool (there is a man page for it). By specifying the `-t - > >> -Tlevel=matching` options, you'll get detailed information on why a > >> particular decision is made. > > Hmm, that's weird. sieve-test says it would store the message into the > > Spam folder (as expected), but it was definitely delivered to INBOX. > > BTW, did you consult your logs for any errors? If an error occurs during > Sieve processing, the default behavior is to file the message into INBOX > (e.g. when the Spam folder doesn't exist).Yes, I didn't find any errors, just the lmtp log entry for storing into INBOX. In the several cases I looked at, the Spam folder exists, is getting most spam-flagged messages filed into it, it just seems to be something about some messages (for example, got a bunch of copies of this particular spam to different users and they all went to INBOX instead of Spam). May 15 09:44:04 dovecot2 dovecot: lmtp(10157): Connect from 10.0.9.71 May 15 09:44:05 dovecot2 dovecot: lmtp(10157, localuser9 at foothills.net): MikHD8/YVVWtJwAAIYJ+iw: sieve: msgid=<438088200.476329351.0075518260474.JavaMail.root at sjmas02.lococandles.co>: stored mail into mailbox 'INBOX' May 15 09:44:05 dovecot2 dovecot: lmtp(10157): Disconnect from 10.0.9.57: Successful quit Also, if the Spam folder didn't exist, I have it set to be autocreated in the Dovecot config. I also know that Dovecot can write to the Spam folder okay, because I did a "doveadm move" to move several "X-Spam-Flag: YES" messages to the Spam folder, and that worked. -- Chris Adams <cma at cmadams.net>