- dovecot - dovecot.org

[Dovecot] deliver: Panic: file sieve-cmu.c: line 90 (unfold_header): assertion failed: (str[i] == ' ' || str[i] == '\t')
by Anton Yuzhaninov 19 Feb '09

19 Feb '09

I use dovecot-1.1.10 and dovecot-sieve-1.1.6 /usr/local/libexec/dovecot/deliver coredups several times per day with bt like this: (gdb) bt #0 0x0000000800a3a91c in kill () at kill.S:2 #1 0x0000000800a3a88a in __raise (s=6) at /usr/src/lib/libc/gen/raise.c:46 #2 0x0000000800a38f83 in abort () at /usr/src/lib/libc/stdlib/abort.c:65 #3 0x00000000004a7de5 in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at failures.c:151 #4 0x00000000004a8777 in i_syslog_fatal_handler (type=Could not find the frame base for "i_syslog_fatal_handler". ) at failures.c:309 #5 0x00000000004a80ca in i_panic (format=Could not find the frame base for "i_panic". ) at failures.c:198 #6 0x0000000800e0b265 in unfold_header ( str=0x800c55a40 "\"firm ru\nÐ\217Ð\201Ð±ÐŒÂ¬Â® Ñ\236Ò\220Ð\216Â¬Â Ð±Ð²Ò\220Ð°Ð³\" <our_email@ example.ru>") at sieve-cmu.c:90 #7 0x0000000800e0b381 in unfold_multiline_headers (headers=0x800c55a30) at sieve-cmu.c:119 #8 0x0000000800e0b406 in getheader (v=0x7fffffffeab0, phead=0x800c5a160 "to", body=0x7fffffffc048) at sieve-cmu.c:132 #9 0x0000000800e1affc in eval_bc_test (interp=0x800c2d380, body_cache=0x0, m=0x7fffffffeab0, bc=0x800c5a000, ip=0x7fffffffc300) at bc_eval.c:541 #10 0x0000000800e1ac96 in eval_bc_test (interp=0x800c2d380, body_cache=0x0, m=0x7fffffffeab0, bc=0x800c5a000, ip=0x7fffffffd8e4) at bc_eval.c:445 #11 0x0000000800e1c131 in sieve_eval_bc (exe=0x800c240b0, is_incl=0, i=0x800c2d380, body_cache=0x0, sc=0x7fffffffeb60, m=0x7fffffffeab0, imapflags=0x7fffffffda20, actions=0x800c660f0, notify_list=0x800c13a40, errmsg=0x7fffffffda38) at bc_eval.c:1009 #12 0x0000000800e23ece in sieve_execute_bytecode (exe=0x800c240b0, interp=0x800c2d380, script_context=0x7fffffffeb60, message_context=0x7fffffffeab0) at script.c:868 #13 0x0000000800e0dee4 in cmu_sieve_run (namespaces=0x800c0b848, storage_r=0x7fffffffec98, mail=0x800c1d848, script_path=0x800c02d28 "/home/public/.dovecot.sieve", destaddr=0x7fffffffef3e "user_xxxxx", username=0x800c1ce35 "user_xxxxx", mailbox=0x4c581c "INBOX") at sieve-cmu.c:1038 #14 0x0000000800e0ae6d in cmusieve_deliver_mail (namespaces=0x800c0b848, storage_r=0x7fffffffec98, mail=0x800c1d848, destaddr=0x7fffffffef3e "user_xxxxx", mailbox=0x4c581c "INBOX") at cmusieve-plugin.c:81 #15 0x0000000000417d7f in main (argc=3, argv=0x7fffffffedc8) at deliver.c:1084 I log messages: deliver(user_xxxxx): Panic: file sieve-cmu.c: line 90 (unfold_header): assertion failed: (str[i] == ' ' || str[i] == '\t') -- Anton Yuzhaninov

2 2

[Dovecot] Effects of going read-only on dovecot & pop/imap clients
by Mark Zealey 19 Feb '09

19 Feb '09

Hi all, We need to set our filestore to read-only for quite a while, and I want to mitigate the effects for our clients. First issue; dovecot. If we just change the nfs mounts to read-only, dovecot complains: 2009-02-19T14:03:19+00:00 mail2 dovecot: pop3-login: Login: user=<test2(a)markandruth.co.uk>, method=PLAIN, rip=10.15.10.95, lip=10.15.10.102:11002 2009-02-19T14:03:19+00:00 mail2 dovecot: POP3(test2(a)markandruth.co.uk): open() failed with file /var/spool/mail/supplier_2/ma/rk/an/markandruth.co.uk/te/st/2_/test2/Mai ldir/dovecot.index.log: Read-only file system 2009-02-19T14:03:19+00:00 mail2 dovecot: POP3(test2(a)markandruth.co.uk): open(/var/spool/mail/supplier_2/ma/rk/an/markandruth.co.uk/te/st/2_/test 2/Maildir/dovecot-uidlist.lock) failed: Read-only file system 2009-02-19T14:03:19+00:00 mail2 dovecot: POP3(test2(a)markandruth.co.uk): file_dotlock_create(/var/spool/mail/supplier_2/ma/rk/an/markandruth.co.u k/te/st/2_/test2/Maildir/dovecot-uidlist) failed: Read-only file system 2009-02-19T14:03:19+00:00 mail2 dovecot: POP3(test2(a)markandruth.co.uk): Couldn't init INBOX: Internal error occurred. Refer to server log for more information. [2009-02-19 14:03:19] 2009-02-19T14:03:19+00:00 mail2 dovecot: POP3(test2(a)markandruth.co.uk): Mailbox init failed bytes=0/95, top=0/0, retr=0/0, del=0/0, size=0 Even when I use :INDEX=MEMORY, it's still complaining about creating .lock's or uidlist files and just issuing internal errors. Is there any way to make dovecot just do as much as it can under the circumstances ie allow read access to mails? Also, has anyone got experience of how clients handle mailboxes being read-only? My guess is that pop clients would probably break and download the same messages over and over? Thanks, Mark -- Mark Zealey -- Shared Hosting Team Leader Product Development * Webfusion 123-reg.co.uk, webfusion.co.uk, donhost.co.uk, supanames.co.uk This mail is subject to http://www.gxn.net/disclaimer

2 3

[Dovecot] UNSUBSCRIBE
by Eric B. Schorvitz, Ph.D. 19 Feb '09

19 Feb '09

2 1

[Dovecot] limiting authentication failures
by Eric B. Schorvitz, Ph.D. 19 Feb '09

19 Feb '09

In my log files I occasionally get a huge number of Dovecot authentication failures (see clip below). I wanted to know if there's a way to limit the number of times an IP address can attempt to authenticate, if there's a way to have a timeout between attempted authentications, or if there is a way to limit authentication attempts by a specific username within a certain period of time. My current solution is to permanently block the specific IP, an IP range, or an entire country from accessing my server AFTER I notice the huge number of authentication failures. This is too ad-hoc a process and was hoping dovecot has something more proactive built in. Thank you in advance for spending time considering this inquiry, Eric --------------------- pam_unix Begin ------------------------ dovecot: Authentication Failures: rhost=::ffff:200.111.39.219 : 764 Time(s) root: 25 Time(s) mysql: 6 Time(s) smmsp: 6 Time(s) --SNIP-- Unknown Entries: check pass; user unknown: 764 Time(s) ---------------------- pam_unix End ------------------------- --------------------- Connections (secure-log) Begin ------------------------ **Unmatched Entries** dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user info dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user info dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user info dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user info --SNIP--

2 1

[Dovecot] sieve filters
by Ian P. Christian 19 Feb '09

19 Feb '09

Hi all, I'm trying to figure out a way of filtering mail from a commercial anti-spam platform. Unfortunately you need to compare part of one header against part of another header. I figured I could solve this using sieve variables and pattern matching, however I'm having little luck and don't know how to debug sieve issues. # example headers: must compare 0.00799 against 1:0000 (the 2nd number in the 2nd header) # X-pstn-levels: (S: 0.00799/98.42547 CV:99.9000 FC:95.5390 LC:95.5390 R:95.9108 P:95.9108 M:97.0282 C:98.6951 ) # X-pstn-settings: 3 (1.0000:1.0000) s cv gt3 gt2 gt1 r p m c if header :matches "X-pstn-levels" "(S: */*" { set "score" "${1}"; if header :matches "X-pstn-settings" " ? (*:*) *" { fileinto "somewhere"; } } The first if appears to match, as if I move the fileinto up there it works - however it doesn't work as it shown here. Can anyone suggest why? Can I achieve what I'm trying to do with sieve? How can I go about debugging scripts? Thanks, Ian

2 2

[Dovecot] kerberos trying to obtain credentials for wrong machine
by Nikolay Shopik 19 Feb '09

19 Feb '09

Hi, I'm currently trying to configure Dovecot to use kerberos. My KDC is Windows 2003 and I successful generated keytab file for Dovecot machine. Problem is when I'm trying to use GSSAPI it told me Obtaining credentials for imap@debian5 - and of course this fails because debian5 isn't KDC, it should look for imap/debian5.inblock.local(a)INBLOCK.LOCAL. What I'm missing?

2 1

[Dovecot] Time moved backwards ....
by Harry Lachanas 18 Feb '09

18 Feb '09

OK.. So I synced the clock.... and got .... dovecot: Time just moved backwards by 1 seconds. I'll sleep now until we're back in present. http://wiki.dovecot.org/TimeMovedBackwards ( The first time I did this the clock moved backwards 2 hours after a timezone change and dovecot suicided ) I think I understand the concept ... However a mail server should probably be synchronized to the local time ..... Suggestions ...??? Harry.

8 10

[Dovecot] mbox snarf plugin + idle
by Jonathan Siegle 18 Feb '09

18 Feb '09

I'm having a problem with mbox snarf not looking at /var/spool/mail/ when in idle mode thus never giving me a RECENT line even though there are new messages in /var/spool/mail/ . Here are the imap commands to reproduce the problem: 1 login userid password 2 select inbox 3 idle When I run "select inbox" it does see my messages in /var/spool/mail/ and moves them over fine. When I truss the process, I see it only running stat calls on my "mbox- snarf" file. To get new messages I issue DONE, CLOSE, and SELECT INBOX. I'm not sure why it is reporting alpha5 two lines below. I did an hg pull just the other day and see 1.2.beta1 in the output of hg tags. # /usr/ladmin2/sbin/dovecot -n # 1.2.alpha5: /usr/ladmin2/etc/dovecot.conf Warning: fd limit 2000 is lower than what Dovecot can use under full load (more than 4224). Either grow the limit or change login_max_processes_count and max_mail_processes settings # OS: AIX 3 0001112AD300 syslog_facility: local0 protocols: imap listen: *:2222 ssl: no disable_plaintext_auth: no login_dir: /usr/ladmin2/var/run/dovecot/login login_executable: /usr/ladmin2/libexec/dovecot/imap-login login_greeting: Dovecot ready. login_processes_count: 30 max_mail_processes: 4096 mail_location: mbox:%h/new:INBOX=/var/spool/mail/14/%u mmap_disable: yes dotlock_use_excl: no mbox_write_locks: fcntl mbox_lazy_writes: no mail_plugins: mbox_snarf imap_client_workarounds: delay-newmail auth default: mechanisms: plain gssapi krb5_keytab: /etc/krb5/dovecot.keytab gssapi_hostname: $ALL verbose: yes debug: yes passdb: driver: pam userdb: driver: passwd plugin: mbox_snarf: /gpfs/inbox/14/%u Thanks, Jonathan

2 2

Re: [Dovecot] from postfix deliver to dovecot deliver
by dovecot＠corwyn.net 18 Feb '09

18 Feb '09

you're using maildir? (I only ask because I am). In that case, no making the change doesn't require changes in the mailboxes. I made the appropriate changes (just a few days ago) to main.cf and I was good to go. Rick At 08:01 AM 2/18/2009, Johan Hendriks wrote: >Hello all. >I use dovecot in combination with postfix, postfixadmin for virtual users. >Deliver to the mailbox now is done by postfix >Now i want to enable quota's and therefor i need dovecot deliver. >Can i just switch to dovecot deliver? >Or must i first do some prrperations in the mailboxes. > >regards >-- >_______________________ >*Johan Hendriks* >*Schavemaker Transport* > >Tel: +31 (0)251 229098 >Fax: +31 (0)251 212016 >email: j.hendriks(a)schavemaker.com <mailto:j.hendriks@schavemaker.com> >web: http://www.schavemaker.com >_______________________ >/Confidentiality Notice: The information in this document may be >confidential. It is intended only for the use of the named recipient. >If you are not the intended recipient, please notify me immediately >and then delete this document. Do not disclose the contents of this document >to any other person, nor take any copies. Violation of this notice >may be unlawful. / >_______________________

1 0

[Dovecot] assertion failed
by Ian P. Christian 18 Feb '09

18 Feb '09

Does anyone know what might cause this? # dovecot --version 1.1.7 Feb 17 18:21:51 imap-proxy-temp dovecot: Panic: auth(default): file passdb-cache.c: line 121 (passdb_cache_lookup_credentials): assertion failed: (*scheme_r != NULL || *password_r == NULL) Feb 17 18:21:51 imap-proxy-temp dovecot: auth(default): Raw backtrace: dovecot-auth [0x42c0ea] -> dovecot-auth [0x42c143] -> dovecot-auth [0x42b7f6] -> dovecot-auth [0x41acb6] -> dovecot-auth(auth_request_lookup_credentials+0x6f) [0x411cdf] -> dovecot-auth [0x416caf] -> dovecot-auth(auth_request_handler_auth_continue+0xc9) [0x4128e9] -> dovecot-auth [0x40e40a] -> dovecot-auth(io_loop_handler_run+0xf8) [0x42fb48] -> dovecot-auth(io_loop_run+0x1d) [0x42ea4d] -> dovecot-auth(main+0x2f7) [0x416367] -> /lib/libc.so.6(__libc_start_main+0xda) [0x7f83990e54ca] -> dovecot-auth [0x40cdba] Feb 17 18:21:51 imap-proxy-temp dovecot: child 20579 (auth) killed with signal 6

2 4