[Dovecot] sieve problem email silently discard
hello folks hello Timo hello all the guru
I met a few times the problem or an email that passes through a sieve script is silently discard after delivery but never returned to the inbox
all testimonials are welcome
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x092164A7 gpg --keyserver pgp.mit.edu --recv-key 092164A7
Op 22-6-2011 3:18, ml@smtp.fakessh.eu schreef:
hello folks hello Timo hello all the guru
I met a few times the problem or an email that passes through a sieve script is silently discard after delivery but never returned to the inbox
all testimonials are welcome
We cannot say much about this problem, unless we get some more information:
What is your configuration? Provide the output of dovecot -n.
Is it reproducible somehow?
What is the Sieve script you see this behavior for? Or does it happen for all users?
Is there a specific kind of incoming message that gets discarded all the time?
Is there any error or other message in the logs that may explain this behavior?
Regards,
Stephan.
Le mercredi 22 juin 2011 10:21, Stephan Bosch a écrit :
Op 22-6-2011 3:18, ml@smtp.fakessh.eu schreef:
hello folks hello Timo hello all the guru
I met a few times the problem or an email that passes through a sieve script is silently discard after delivery but never returned to the inbox
all testimonials are welcome
We cannot say much about this problem, unless we get some more information:
- What is your configuration? Provide the output of dovecot -n.
my dovecot -n ~]# /usr/sbin/dovecot -n # 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32.2-xxxx-grs-ipv6-32 i686 CentOS release 5.6 (Final) auth_mechanisms = plain login base_dir = /var/run/dovecot/ lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = [::] log_path = /var/log/maillog log_timestamp = %Y-%m-%d %H:%M:%S login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_location = maildir:~/Maildir mail_max_userip_connections = 20 managesieve_notify_capability = mailto managesieve_sieve_capability = comparator-i;octet comparator-i;ascii-casemap fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date spamtest spamtestplus virustest namespace { inbox = yes location = prefix = separator = . } passdb { driver = pam } plugin { autocreate = Trash autocreate2 = Junk autocreate3 = Sent autocreate4 = Drafts autosubscribe = Trash autosubscribe2 = Junk autosubscribe3 = Sent autosubscribe4 = Drafts plugin = $mail_plugins autocreate managesieve sieve sieve = ~/.dovecot.sieve sieve_before = /var/sieve-scripts/roundcube.sieve sieve_dir = ~/sieve sieve_global_path = whatever } protocols = sieve imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0600 user = postfix } unix_listener auth-master { mode = 0666 } unix_listener auth-userdb { mode = 0666 } vsz_limit = 64 M } service imap-login { inet_listener imap { port = 0 } inet_listener imaps { address = * , [::] port = 993 } process_limit = 128 vsz_limit = 64 M } service imap { client_limit = 1 service_count = 0 } service managesieve-login { inet_listener managesieve-login { address = * , [::] port = 2000 } process_limit = 128 vsz_limit = 64 M } service pop3-login { inet_listener pop3 { port = 0 } inet_listener pop3s { address = * , [::] port = 995 } process_limit = 128 vsz_limit = 64 M } ssl_ca =
- Is it reproducible somehow?
this is rare but does occur from time to time. I do not know how to reproduce
- What is the Sieve script you see this behavior for? Or does ithappen for all users?
i use a simple script sieve of this style ~]$ cat .dovecot.sieve require ["fileinto", "mailbox" ,"reject", "regex", "variables","envelope", "subaddress"]; # rule:[perl] if anyof (header :contains "Return-Path" "perl.apache.org", header :contains "Return-Path" "perl",header :contains "Return-Path" "groups.yahoo.com", header :contains "Return-Path" "jaos", header :contains "Return-Path" "dkimproxy", header :contains "Return-Path" "mongueurs", header :contains "Return-Path" "pep", header :contains "Subject" "dkimproxy", header :contains "To" "perl@mongueurs.net", header :contains "To" "pep@perl.org", header :contains "To" "perlwebmail-devel@jaos.org", header :contains "Return-Path" "jlong@messiah.edu", header :contains "To" "dkimproxy-users@lists.sourceforge.net", header :contains "Cc" "dkimproxy-users@lists.sourceforge.net",header :contains "Return-Path" "templates-bounces@template-toolkit.org",header :contains "Return-Path" "pm.org") { fileinto :create "INBOX.perl"; stop; }
- Is there a specific kind of incoming message that gets discardedall the time?
no there is no particular type of message just some messages
- Is there any error or other message in the logs that may explain this behavior?
egrep lda /var/log/maillog
2011-06-22 14:34:45lda(fakessh): Info: sieve: msgid=<4E01E14E.4040401@sr******.info>: marked message to be discarded if not explicitly delivered (discard action) 2011-06-22 14:34:45lda(root): Info: sieve: msgid=<4E01E14E.4040401@sr******.info>: marked message to be discarded if not explicitly delivered (discard action)
Regards,
Stephan.
thanks Stephan
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x092164A7 gpg --keyserver pgp.mit.edu --recv-key 092164A7
Op 22-6-2011 16:05, ml@smtp.fakessh.eu schreef:
Op 22-6-2011 3:18, ml@smtp.fakessh.eu schreef:
I met a few times the problem or an email that passes through a sieve script is silently discard We cannot say much about this problem, unless we get some more information:
- What is your configuration? Provide the output of dovecot -n. my dovecot -n <snip/>
Le mercredi 22 juin 2011 10:21, Stephan Bosch a écrit : plugin = $mail_plugins autocreate managesieve sieve sieve = ~/.dovecot.sieve sieve_before = /var/sieve-scripts/roundcube.sieve sieve_dir = ~/sieve sieve_global_path = whatever <snip/>
Ok, so you are using multiscript with sieve_before.
- Is it reproducible somehow? this is rare but does occur from time to time. I do not know how to reproduce
:/
- What is the Sieve script you see this behavior for? Or does ithappen for all users?
i use a simple script sieve of this style ~]$ cat .dovecot.sieve <snip/>
- Is there any error or other message in the logs that may explain this behavior? egrep lda /var/log/maillog
2011-06-22 14:34:45lda(fakessh): Info: sieve: msgid=<4E01E14E.4040401@sr******.info>: marked message to be discarded if not explicitly delivered (discard action) 2011-06-22 14:34:45lda(root): Info: sieve: msgid=<4E01E14E.4040401@sr******.info>: marked message to be discarded if not explicitly delivered (discard action)
This is really strange. Even though your script does not contain a discard command, the message is discarded through an explicit discard action. I do notice that you are using the multiscript feature using sieve_before and I expect that our problem is there. Notice that the same message is discarded in an identical manner for two different users (root and fakessh). What does /var/sieve-scripts/roundcube.sieve contain?
Also, it can be helpful to enable mail_debug to get more info on what scripts are being executed and which script actually triggers the discard action.
Regards,
Stephan.
Le mercredi 22 juin 2011 16:41, Stephan Bosch a écrit :
Op 22-6-2011 16:05, ml@smtp.fakessh.eu schreef:
Le mercredi 22 juin 2011 10:21, Stephan Bosch a écrit :
Op 22-6-2011 3:18, ml@smtp.fakessh.eu schreef:
I met a few times the problem or an email that passes through a sieve script is silently discard
egrep lda /var/log/maillog
2011-06-22 14:34:45lda(fakessh): Info: sieve: msgid=<4E01E14E.4040401@sr******.info>: marked message to be discarded if not explicitly delivered (discard action) 2011-06-22 14:34:45lda(root): Info: sieve: msgid=<4E01E14E.4040401@sr******.info>: marked message to be discarded if not explicitly delivered (discard action)
This is really strange. Even though your script does not contain a discard command, the message is discarded through an explicit discard action. I do notice that you are using the multiscript feature using sieve_before and I expect that our problem is there. Notice that the same message is discarded in an identical manner for two different users (root and fakessh). What does /var/sieve-scripts/roundcube.sieve contain?
/var/sieve-scripts/roundcube.sieve contains a series of commands to handle spam
~]# cat /var/sieve-scripts/roundcube.sieve
require
["fileinto","regex","comparator-i;ascii-numeric","reject","relational"];
# rule:[spammanage]
#if anyof (header :contains "X-Spam-Flag" "YES")
#{
# fileinto "Junk";
#}
if header :value "ge" :comparator "i;ascii-numeric" ["X-Spam-score"] ["500"]
{
discard;
stop;
}
if header :value "ge" :comparator "i;ascii-numeric" ["X-Spam-score"] ["100"]
{
fileinto "Junk.spam";
stop;
}
if header :value "ge" :comparator "i;ascii-numeric" ["X-Spam-score"] ["10"] {
fileinto "Junk";
}
elsif anyof ( header :contains "Received" [ "[4.63.221.224", "[24.244.141.112", "[61.171.253.177", "[63.123.149.", "[63.209.206.", "(63.233.30.73", "[63.251.200.", "[64.41.183.","[64.49.250.", "[64.57.188.", "[64.57.221.", "[64.62.204.", "[64.70.17.", "[64.70.44.", "[64.70.53.", "[64.39.27.6", "[64.39.27.7","[64.191.25.","[64.191.36.", "[64.191.9.", "[64.125.181.", "[64.191.123.", "[64.191.23.", "[64.239.182.", "[65.211.3.", "[66.46.150.", "[66.62.162.", "[66.118.170.", "[66.129.124.", "[66.205.217.", "[66.216.111.", "[66.239.204.", "[67.86.69.", "[80.34.206.", "[80.80.98.", "[81.72.233.13", "[128.242.120.", "[157.238.18", "[168.234.195.18]", "[193.253.198.57", "[194.25.83.1", "[200.24.129.", "[200.161.203.", "[202.164.182.76]","[202.57.69.116", "[203.19.220.","[203.22.104.","[203.22.105.", "[204.188.52.", "[205.153.154.203", "[206.26.195.", "[206.154.33.","[206.169.178", "[207.142.3.", "[208.46.5.","[208.187.", "[209.164.27.","[209.236.", "[210.90.75.129]", "[211.101.138.199","[211.185.7.125]","[211.239.231.", "[212.240.95.", "[213.47.250.139", "[213.225.61.", "[216.22.79.","[216.39.115.","[216.99.240.", "[216.126.32.", "[216.187.123.","[217.36.124.53", "[218.145.25","[218.52.71.103","[218.158.136.115", "[218.160.42.74", "[218.242.112.4" , "[94.23.116.93" ] ) { fileinto "Junk"; } elsif anyof ( header :contains ["SPAM", "X-Spam-hits"] ["ADDRESSES_ON_CD","ACT_NOW","and other hits"
]) { fileinto "Junk"; }
Also, it can be helpful to enable mail_debug to get more info on what scripts are being executed and which script actually triggers the discard action.
Regards,
Stephan.
I just set up mail_debug = yes I expect the next reject in order to give you more information
-- http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x092164A7 gpg --keyserver pgp.mit.edu --recv-key 092164A7
participants (2)
-
ml＠smtp.fakessh.eu
-
Stephan Bosch