- dovecot - dovecot.org

doveadm acl set negative rights not supported?
by Peter Benko 21 Dec '16

21 Dec '16

Hi all, I'm trying to set an ACL with negative rights. I have no problems setting it with standard IMAP commands, but I'm unable to do it with the doveadm acl command. I tried: sudo -u vmail doveadm acl set -u "user@domain" Spam user="-user@domain" lookup (notice the "-" before the username) Unfortunately, this adds a (positive) ACL for the user named "-user@domain" instead of adding a negative one for the user "user@domain". Am I messing up something or is negative ACL support missing from doveadm? I have not seen anything in the docs about this... Regards, Peter

2 2

unexpected behaviour of search queries with mixed AND and OR
by Juergen Raschke 20 Dec '16

20 Dec '16

Hello, I found out an unexpected behaviour of search queries with mixed "AND" and "OR". With search query "$ condA OR condB condC $" I get an error: Fatal: Use parenthesis when mixing ANDs and ORs if I switch left and right OR-part and use the query "$ condB condC OR condA $" I get a result, but it is not the expected result of the query "$ \( condB condC $ OR condA \)" I get the result of the query "$ condB OR condC OR condA $" which is more then suprising. The query "$ condB condC OR condA $" should either throw an error like "$ condA OR condB condC $" or deliever the result of "$ \( condB condC $ OR condA \)" Example: doveadm -f flow fetch -u USER guid $ savedbefore 21d OR seen savedbefore 5d $ | wc -l Fatal: Use parenthesis when mixing ANDs and ORs 0 doveadm -f flow fetch -u USER guid $ seen savedbefore 5d OR savedbefore 21d $ | wc -l 63690 doveadm -f flow fetch -u USER guid $ seen OR savedbefore 5d OR savedbefore 21d $ | wc -l 63690 doveadm -f flow fetch -u USER guid $ \( seen savedbefore 5d $ OR savedbefore 21d \) |wc -l 63247 doveadm -f flow fetch -u USER guid $ savedbefore 21d OR \( seen savedbefore 5d $ \) |wc -l 63247 doveconf -n # 2.2.24 (a82c823): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.9 (357ac0a0e68b+) # OS: Linux 3.16.0-0.bpo.4-amd64 x86_64 Debian 7.9 Mit freundlichen Gruessen, Juergen Raschke -- Mittwald CM Service GmbH & Co. KG Koenigsberger Strasse 6 Tel: +49-5772-293-100 32339 Espelkamp Fax: +49-5772-293-333 Geschaeftsfuehrer: Robert Meyer, HRA 6640, AG Bad Oeynhausen Komplementaerin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen

2 2

Latest Dovecot v2.2.devel (9bc8d9b) crashes on login and lmtp
by Thomas Leuxner 20 Dec '16

20 Dec '16

I was unable to produce an IMAP core but have been successful with LMTP. Basically it crashes right upon login or delivery: Dec 20 08:55:23 nihlus dovecot: master: Dovecot v2.2.devel (9bc8d9b) starting up for imap, lmtp Dec 20 08:56:15 nihlus dovecot: imap(tlx(a)leuxner.net): Fatal: master: service(imap): child 5710 killed with signal 11 (core not dumped) Dec 20 08:57:23 nihlus dovecot: lmtp(5967): Connect from local Dec 20 08:57:23 nihlus dovecot: lmtp(5967): Fatal: master: service(lmtp): child 5967 killed with signal 11 (core dumped) $ gdb /usr/lib/dovecot/lmtp core_lmtp.5967.nihlus.leuxner.net GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from /usr/lib/dovecot/lmtp...Reading symbols from /usr/lib/debug/.build-id/ec/199069dd786feb54e5af43f983ce9c3bb4c29c.debug...done. done. [New LWP 5967] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Core was generated by `dovecot/lmtp'. Program terminated with signal SIGSEGV, Segmentation fault. #0 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33 33 ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S: No such file or directory. #0 __memcpy_sse2_unaligned () at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:33 No locals. #1 0x00007f9177db4779 in memcpy (__len=<optimized out>, __src=0x0, __dest=0x7f917a5c5bf8) at /usr/include/x86_64-linux-gnu/bits/string3.h:51 No locals. #2 p_strconcat (pool=<optimized out>, str1=<optimized out>) at strfuncs.c:218 args = {{gp_offset = 16, fp_offset = 48, overflow_arg_area = 0x7ffdcadea060, reg_save_area = 0x7ffdcade9f90}} temp = 0x0 ret = <optimized out> len = 49 #3 0x00007f91780744fd in mdbox_storage_create (_storage=0x7f917a5c5930, ns=0x7f917a5b79d0, error_r=0x7ffdcadea1a0) at mdbox-storage.c:57 storage = 0x7f917a5c5930 dir = <optimized out> #4 0x00007f917805952b in mail_storage_create_full (ns=ns@entry=0x7f917a5b79d0, driver=<optimized out>, driver@entry=0x0, data=<optimized out>, flags=flags@entry=(unknown: 0), storage_r=storage_r@entry=0x7ffdcadea170, error_r=error_r@entry=0x7ffdcadea1a0) at mail-storage.c:395 storage = 0x7f917a5c5930 list = 0x7f917a5c3ca0 list_set = {layout = 0x7f91781083c6 "fs", root_dir = 0x7f917a52e100 "/var/vmail/domains/leuxner.net/tlx/mdbox", index_dir = 0x0, index_pvt_dir = 0x0, control_dir = 0x0, alt_dir = 0x0, inbox_path = 0x0, subscription_fname = 0x7f917810f234 "subscriptions", list_index_fname = 0x7f917810925e "dovecot.list.index", maildir_name = 0x7f917810bc17 "dbox-Mails", mailbox_dir_name = 0x7f917810c301 "mailboxes", escape_char = 0 '\000', broken_char = 0 '\000', utf8 = false, alt_dir_nocheck = false, index_control_use_maildir_name = false} list_flags = <optimized out> p = <optimized out> __FUNCTION__ = "mail_storage_create_full" #5 0x00007f91780598cc in mail_storage_create (ns=ns@entry=0x7f917a5b79d0, driver=driver@entry=0x0, flags=flags@entry=(unknown: 0), error_r=error_r@entry=0x7ffdcadea1a0) at mail-storage.c:416 storage = 0x7f917a5bfc90 #6 0x00007f9178051b89 in mail_namespaces_init_add (user=user@entry=0x7f917a5bfc90, ns_set=<optimized out>, unexpanded_ns_set=0x7f917a5c0178, ns_p=ns_p@entry=0x7ffdcadea200, error_r=error_r@entry=0x7ffdcadea290) at mail-namespace.c:195 mail_set = <optimized out> ns = 0x7f917a5b79d0 driver = 0x0 error = 0x0 ret = <optimized out> #7 0x00007f9178052cd9 in mail_namespaces_init (user=0x7f917a5bfc90, error_r=error_r@entry=0x7ffdcadea290) at mail-namespace.c:414 mail_set = 0x7f917a5c0c58 ns_set = 0x7f917a5c0f70 unexpanded_ns_set = 0x7f917a5c0150 namespaces = 0x0 ns_p = 0x7ffdcadea200 i = <optimized out> count = <optimized out> count2 = <optimized out> __FUNCTION__ = "mail_namespaces_init" #8 0x00007f9178060b65 in mail_storage_service_init_post (ctx=<optimized out>, error_r=0x7ffdcadea290, mail_user_r=<optimized out>, priv=0x7ffdcadea2a0, user=0x7f917a573910) at mail-storage-service.c:728 mail_set = 0x7f917a5c0c58 home = 0x7f917a59e761 "/var/vmail/domains/leuxner.net/tlx" mail_user = 0x7f917a5bfc90 #9 mail_storage_service_next_real (mail_user_r=<optimized out>, user=0x7f917a573910, ctx=<optimized out>) at mail-storage-service.c:1427 len = <optimized out> temp_priv_drop = <optimized out> priv = {uid = 5000, gid = 5000, uid_source = 0x7f9178107684 "userdb lookup", gid_source = 0x7f9178107684 "userdb lookup", home = 0x7f917a59e761 "/var/vmail/domains/leuxner.net/tlx", chroot = 0x7f917a52d458 ""} error = 0x7f917a5b3830 "" disallow_root = <optimized out> use_chroot = <optimized out> #10 mail_storage_service_next (ctx=<optimized out>, user=0x7f917a573910, mail_user_r=mail_user_r@entry=0x7f917a560b48) at mail-storage-service.c:1445 old_log_prefix = 0x7f917a5ba530 "lmtp(5967, tlx(a)leuxner.net) " #11 0x00007f9178789f55 in client_deliver (session=0x7f917a5bf880, src_mail=0x7f917a5bb060, rcpt=0x7f917a5621d0, client=0x7f917a560a10) at commands.c:837 set_parser = <optimized out> line = <optimized out> str = <optimized out> mail_error = 2052462064 ret = <optimized out> input = <optimized out> ns = <optimized out> delivery_time_started = {tv_sec = 1482220643, tv_usec = 129544} sets = <optimized out> storage = 0x7f917a5b3870 mail_set = <optimized out> username = 0x7f917a52d070 "tlx(a)leuxner.net" dctx = {pool = 0x0, set = 0x7f917a560a10, session = 0x0, timeout_secs = 0, session_time_msecs = 0, delivery_time_started = {tv_sec = 140262799447056, tv_usec = 140262799447168}, dup_ctx = 0x2, session_id = 0x7f9177d980d8 <i_stream_file_read+136> "H\211\305H\211\350H\301\350?\204\300D\017\266\350\017\205\030\001", src_mail = 0xf72, src_envelope_sender = 0xf65305b35804d500 <error: Cannot access memory at address 0xf65305b35804d500>, dest_user = 0x0, dest_addr = 0x7f917a561410 "\001", final_dest_addr = 0x7f917a561480 "q ", dest_mailbox_name = 0x2 <error: Cannot access memory at address 0x2>, dest_mail = 0x0, var_expand_table = 0x7f9177d93c33 <i_stream_read+83>, tempfail_error = 0x7f917a560a10 "", tried_default_save = 64, saved_mail = 71, save_dest_mail = 83, mailbox_full = 122, dsn = 145} lda_set = <optimized out> error = <optimized out> #12 client_deliver_next (session=0x7f917a5bf880, src_mail=0x7f917a5bb060, client=0x7f917a560a10) at commands.c:930 count = <optimized out> #13 client_input_data_write_local (input=<optimized out>, client=0x7f917a560a10) at commands.c:1026 src_mail = 0x7f917a5bb060 first_uid = 4294967295 session = 0x7f917a5bf880 old_uid = 0 #14 client_input_data_write (client=0x7f917a560a10) at commands.c:1161 input = 0x7f917a57d1f0 #15 client_input_data_handle (client=0x7f917a560a10) at commands.c:1256 data = <optimized out> size = 110 ret = <optimized out> #16 0x00007f9177d9d962 in io_loop_call_io (io=0x7f917a5615f0) at ioloop.c:599 ioloop = 0x7f917a534740 t_id = 2 __FUNCTION__ = "io_loop_call_io" #17 0x00007f9177d9efba in io_loop_handler_run_internal (ioloop=ioloop@entry=0x7f917a534740) at ioloop-epoll.c:222 ctx = 0x7f917a53a370 io = <optimized out> tv = {tv_sec = 299, tv_usec = 984106} events_count = <optimized out> msecs = <optimized out> ret = 1 i = 0 j = <optimized out> call = <optimized out> __FUNCTION__ = "io_loop_handler_run_internal" #18 0x00007f9177d9d9fc in io_loop_handler_run (ioloop=ioloop@entry=0x7f917a534740) at ioloop.c:648 No locals. #19 0x00007f9177d9dba8 in io_loop_run (ioloop=0x7f917a534740) at ioloop.c:623 __FUNCTION__ = "io_loop_run" #20 0x00007f9177d25a83 in master_service_run (service=0x7f917a5345e0, callback=<optimized out>) at master-service.c:641 No locals. #21 0x00007f9178788262 in main (argc=1, argv=0x7f917a534390) at main.c:125 set_roots = {0x7f917855e400 <lda_setting_parser_info>, 0x7f917898f580 <lmtp_setting_parser_info>, 0x0} service_flags = <optimized out> storage_service_flags = <optimized out> c = <optimized out>

2 1

Checking sieve
by Gerben Wierda 19 Dec '16

19 Dec '16

A simple question: I’ve installed roundcube on macOS Sierra with Server 5.2 and created a set of sieve rules in my dovecot setup. How can I check their functioning (other than send test mails) e.g. is there some logging I can set / look at? G

2 1

Upgrade from version 1 to 2
by Peter Fraser 19 Dec '16

19 Dec '16

Hi All I am upgrading from dovecot-1.2.17 to dovecot2-2.2.27_4. I configured version 2 from scratch. I have email in the maildir format. Would it be ok in theory if I simply copy over the email files from the version 1 server to the version 2 server or are there any hidden dangers here? Any problems with indexing? Thanks for any advice

2 1

Problem with default_process_limit max 200
by Jean-François Sénéchal 19 Dec '16

19 Dec '16

Hello, The default_process_limit parameter is limited to 200 On my server there is a lot of connection imap and this figure is quickly reached And users can no longer connect If I try to increase it I get this error message Warning: service auth { client_limit=1000 } is lower than required under max. load (1100) [....] Restarting IMAP/POP3 mail server: dovecotdoveconf: Warning: service auth { client_limit=1000 } is lower than required under max. load (1100) Warning: service auth { client_limit=1000 } is lower than required under max. load (1100) How do I solve this problem? My full config # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.11 auth_master_user_separator = * auth_mechanisms = plain login auth_verbose = yes debug_log_path = /var/log/dovecot.debug default_process_limit = 200 dict { expire = mysql:/etc/dovecot/dovecot-dict-expire.conf.ext } disable_plaintext_auth = no first_valid_gid = 5000 first_valid_uid = 3000 imapc_features = rfc822.size fetch-headers imapc_host = mail.marche.be imapc_list_prefix = INBOX imapc_master_user = cyrus imapc_password = homer imapc_user = dherman info_log_path = /var/log/dovecot.log last_valid_gid = 5000 log_path = /var/log/dovecot.log mail_gid = 5000 mail_location = maildir:~/Maildir:LAYOUT=fs mail_plugins = " expire quota" mail_prefetch_count = 20 maildir_very_dirty_syncs = yes managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = type = private } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } passdb { args = /etc/dovecot/dovecot-master-users driver = passwd-file master = yes } passdb { driver = shadow } plugin { expire = Trash expire2 = Trash/* expire3 = Spam expire_cache = yes expire_dict = proxy::expire quota = maildir:User quota quota_grace = 10%% quota_rule = *:storage=150M quota_rule2 = Trash:storage=+100M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=90%% quota-warning 90 %u sieve = ~/.dovecot.sieve sieve_before = /etc/dovecot/sieve/before.sieve sieve_dir = ~/sieve sieve_global_dir = /etc/dovecot/sieve/ stats_refresh = 30 secs stats_track_cmds = yes } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh postmaster_address = jf(a)marche.be protocols = imap pop3 lmtp sieve quota_full_tempfail = yes service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } unix_listener auth-userdb { group = vmail mode = 0666 } } service dict { unix_listener dict { group = vmail mode = 0666 } } service imap-login { process_limit = 200 process_min_avail = 2 } service imap { process_limit = 1024 } service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } service pop3-login { inet_listener pop3 { port = 110 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh user = dovecot } ssl_ca = </etc/dovecot/ssl/server-ca.crt ssl_cert = </etc/dovecot/ssl/marche.crt ssl_dh_parameters_length = 2048 ssl_key = </etc/dovecot/private/marche.key ssl_protocols = !SSLv2 !SSLv3 userdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } userdb { driver = passwd } protocol lmtp { mail_plugins = " expire quota sieve" postmaster_address = jf(a)marche.be } protocol imap { mail_max_userip_connections = 5 mail_plugins = " expire quota imap_quota" } protocol sieve { mail_max_userip_connections = 5 } protocol pop3 { mail_max_userip_connections = 5 mail_plugins = " expire quota" }

1 0

Renumbering UID on messages
by Ricardo Branco 19 Dec '16

19 Dec '16

I am having a problem with Horde due to large variations in email UID for a few users. At one time they were receiving thousands of emails a day, they have deleted all these messages but because they still have early emails in the mailbox the UID range from start to now is massive. We use Horde webmail and it creates an internal array based on range of messages but due to large UID range it eats though the ram. If I use dsync on a mailbox will the UIDs be renumbered? -- The information contained in or attached to this email is intended only for the use of the individual or entity to which it is addressed. If you are not the intended recipient, you are not authorised to and must not disclose, copy, distribute, or retain any message or any part of it. If you have received an email in error, please contact the sender and delete the material from any computer. The contents of this email are not for publication unless specifically stated. Furthermore, the information contained in this message, and any attachment(s) thereto, is for information purposes only and may contain the personal views and opinions of the author, which are not necessarily the views and opinions of WENN or its subsidiaries and associated companies. We make every effort to keep our network free from viruses. However, you do need to check this e-mail and any attachments to it for viruses as we can take no responsibility for any computer virus which may be transferred by way of this e-mail. WENN Ltd: Registered Office: 4a Tileyard Studios, Tileyard Road, London, N7 9AH, England. Registered No: 4375163. Place of Registration: United Kingdom. USA Entertainment News Inc (d/b/a WENN): Registered Office: 352 7th Avenue, Suite 1105, New York, NY 10001-5657, USA The WENN name, design and related marks are trademarks of the WENN group of companies. (c) 2014 All Rights Reserved.

2 2

RFC 3501 violation in FETCH BODY responses
by Guilhem Moulin 18 Dec '16

18 Dec '16

Hi there, Quoting RFC 3501 sec. 7.4.2 “FETCH Response” (data item BODYSTRUCTURE): “A body type of type MESSAGE and subtype RFC822 contains, immediately after the basic fields, the envelope structure, body structure, and size in text lines of the encapsulated message.” According the ABNF (RFC 3501 sec. 9) the envelope structure is that of the ENVELOPE FETCH data item, and the env-{from,sender,reply-to,to,cc, bcc} fields are non-space-separated address lists: body-type-msg = media-message SP body-fields SP envelope SP body SP body-fld-lines envelope = "(" env-from SP … SP env-to SP … ")" env-from = "(" 1*address ")" / nil env-to = "(" 1*address ")" / nil While this is indeed the case for ‘FETCH … (ENVELOPE)’, for ‘FETCH … (BODY)’ dovecot 2.2.25 adds a space between addresses of an address list of the envelope structure of an encapsulated MESSAGE/RFC822 message. See the attached patch to ‘src/lib-imap/test-imap-bodystructure.c’, which currently (2.2.25) fails as follows test-imap-bodystructure.c:122: Assert failed: strcmp(str_c(str), testmsg_body) == 0 test-imap-bodystructure.c:129: Assert failed: strcmp(str_c(str), testmsg_bodystructure) == 0 imap bodystructure parser ............................................ : FAILED because the ‘env-to’ field of the envelope structure of the encapsulated MESSAGE/RFC822 message is printed as ((NIL NIL "sub-to1" "domain.org") (NIL NIL "sub-to2" "domain.org")) while it should be ((NIL NIL "sub-to1" "domain.org")(NIL NIL "sub-to2" "domain.org")) After a quick look at the source, this seems to be due to src/lib-imap/imap-bodystructure.c:imap_write_list, which always separates list items with spaces. In the case of an envelope, only the top-level list should be space-separated. Indeed, not adding a space between items of type IMAP_ARG_LIST in the recursive call makes the test pass again. Cheers, -- Guilhem.

2 1

Error while migrating mailbox with 'doveadm sync'
by Zhang Huangbin 18 Dec '16

18 Dec '16

Dear all, I successfully migrated hundreds of mailboxes with Dovecot 2.2.24 on OpenBSD 6.0 (amd64. Old server is OpenBSD 5.1, i386, Dovecot-2.0.17), but got error while migrating 3 mailboxes: # doveadm -o mail_fsync=never sync -1 -R -s '' -u user(a)domain.com imapc: dsync(user(a)domain.com): Panic: file mailbox-alias-plugin.c: line 77 (mailbox_symlink_exists): assertion failed: (ret > 0) Abort trap Same error while running ‘doveadm … backup …'. What does this error actually mean? How can i fix it? - Here’s full log running doveadm with ‘-D’ option: http://pastebin.com/Um5fbuNM - ‘dovecot -n’ on old server: http://pastebin.com/4E6xzFKU - ‘dovecot -n’ on new server: http://pastebin.com/4uHwQnMN I checked release notes of Dovecot 2.2.25/26/27, there’re 3 fixes related to 'doveadm sync’, but not sure whether it helps fix this issue. 2.2.26: + doveadm sync/backup: Added -I <max size> parameter to skip too large mails. + doveadm sync/backup: Fixed -t parameter and added -e for "end date”. 2.2.27: - doveadm sync -1: Fixed handling mailbox GUID conflicts.

1 1

Antispam plugin: insufficent error messages
by Volker Wysk 18 Dec '16

18 Dec '16

Hi! "Dovecot always logs a detailed error message if something goes wrong. If it doesn't, it's considered a bug and will be fixed." (http:// wiki2.dovecot.org/Logging) I'm trying to set up a spam filter with dovecot-antispam and dspam as backend. When I move a spam message from INBOX to Spam, I get this in syslog: Nov 28 21:15:58 desktop imap: antispam: mailbox_is_unsure(Spam): 0 Nov 28 21:15:58 desktop imap: antispam: mailbox_is_trash(INBOX): 0 Nov 28 21:15:58 desktop imap: antispam: mailbox_is_trash(Spam): 0 Nov 28 21:15:58 desktop imap: antispam: mail copy: from trash: 0, to trash: 0 Nov 28 21:15:58 desktop imap: antispam: mailbox_is_spam(INBOX): 0 Nov 28 21:15:58 desktop imap: antispam: mailbox_is_spam(Spam): 1 Nov 28 21:15:58 desktop imap: antispam: mailbox_is_unsure(INBOX): 0 Nov 28 21:15:58 desktop imap: antispam: mail copy: src spam: 0, dst spam: 1, src unsure: 0 There are no log entries about how dspam is called, or what goes on. Indeed, dspam doesn't get called at all. I know, because I've examined the antispam- plugin source code. There would be a log message if dspam was called. It's hard to study the source code, because there are hardly any comments. I have been able to trace the problem to function signature_extract_to_list() in signature.c. There, -1 is returned: int signature_extract_to_list(const struct signature_config *cfg, struct mailbox_transaction_context *t, struct mail *mail, struct siglist **list, enum classification wanted) { const char *const *signatures; struct siglist *item; signatures = get_mail_headers(mail, cfg->signature_hdr); if (!signatures || !signatures[0]) { if (!cfg->signature_nosig_ignore) { mail_storage_set_error(t->box->storage, ME(NOTPOSSIBLE) "antispam signature not found"); return -1; /* <-- HERE */ } else { return 0; } } while (signatures[1]) signatures++; item = i_new(struct siglist, 1); item->next = *list; item->wanted = wanted; item->sig = i_strdup(signatures[0]); *list = item; return 0; } So, what's happening is "antispam signature not found". My question: What does this mean? What's going on? My "dovecot -n" output is attached. Bye Volker

4 7