最近得到amavis 正确标记消息,它们会通过适当的X-Spam-Flag: YES
标头传递。我已经使用 sieve 协议设置了 dovecot:
protocol managesieve {
# Login executable location.
login_executable = /usr/lib/dovecot/managesieve-login
# MANAGESIEVE executable location. See IMAP's mail_executable above for
# examples how this could be changed.
mail_executable = /usr/lib/dovecot/managesieve
# Maximum MANAGESIEVE command line length in bytes. This setting is
# directly borrowed from IMAP. But, since long command lines are very
# unlikely with MANAGESIEVE, changing this will not be very useful.
#managesieve_max_line_length = 65536
# Specifies the location of the symlink pointing to the active script in
# the sieve storage directory. This must match the SIEVE setting used by
# deliver (refer to http://wiki.dovecot.org/LDA/Sieve#location for more
# info). Variable substitution with % is recognized.
sieve=/var/mail/%d/%n/.dovecot.sieve
# This specifies the path to the directory where the uploaded scripts must
# be stored. In terms of '%' variable substitution it is identical to
# dovecot's mail_location setting used by the mail protocol daemons.
sieve_storage=/var/mail/%d/%n/sieve
# If, for some inobvious reason, the sieve_storage remains unset, the
# managesieve daemon uses the specification of the mail_location to find out
# where to store the sieve files (see explaination in README.managesieve).
# The example below, when uncommented, overrides any global mail_location
# specification and stores all the scripts in '~/mail/sieve' if sieve_storage
# is unset. However, you should always use the sieve_storage setting.
# mail_location = mbox:~/mail
# To fool managesieve clients that are focused on timesieved you can
# specify the IMPLEMENTATION capability that the dovecot reports to clients
# (default: dovecot).
#managesieve_implementation_string = Cyrus timsieved v2.2.13
}
我可以看到 managesieve-login 正在运行。managesieve 没有运行。该文件确实存在。有什么想法可以从哪里开始吗?启用mail_debug = yes
似乎没有告诉我任何有用的信息。
答案1
要使用 dovecot sieve,您必须使用名为 deliver 的 dovecot LDA。Sieve 由其插件处理。
答案2
managesieve 是为用户管理筛选配置的前端。
dovecot 包只是一个 IMAP/POP3 邮件服务器 - 它不会(也不应该)实际上进行筛选处理。
处理应该由您的 MDA 程序(例如 Cyrus)负责。您需要配置系统中实际投递邮件的程序,并告诉它解析筛选脚本。