- dovecot - dovecot.org

Converting maildir files from quoted-printable to 8bit
by Andrzej A. Filip 09 Aug '14

09 Aug '14

How to easily convert maildir files from (single part) quoted-printable to 8bit encoding? [I would like to ease access to sent/posted archives.]

1 0

Throttling pop3-login connections
by Alex 09 Aug '14

09 Aug '14

Hi, I have a fedora20 system with dovecot-2.2.13 running various services, including pop3. I'm noticing some users are frequently hamming pop3, and wondered if this was normal, or something I should be investigating? Aug 8 14:05:20 email dovecot: pop3-login: Login: user=<user1>, method=PLAIN, rip=97.77.115.121, lip=192.168.1.1, mpid=30509, session=<DnRtDCIAUQBhTXN5> Aug 8 14:05:21 email dovecot: pop3(user1): Disconnected: Logged out top=0/0, retr=0/0, del=0/15, size=5693601 So it is immediately followed by a logout, but when there are 50 of them successively in a five minute period, I wondered if it is creating unnecessary overhead on the system? I suppose this most likely is how they have their email client configured, but wondered if some throttling would be necessary? Any advice would be most appreciated. Thanks, Alex

4 5

Re: postfix-dovecot via lmtp
by Reindl Harald 08 Aug '14

08 Aug '14

STOP to post HTML and convert even plaintext messages Am 04.08.2014 um 12:50 schrieb Timothy Murphy: > On Monday, August 04, 2014 12:14:44 PM Reindl Harald wrote: > > > >> > I read in /var/log/maillog > >> > > >> > Aug 4 11:29:13 alfred postfix/lmtp[14871]: 9C04C220A99: > >> > to=<tim(a)localhost.gayleard.eu>, orig_to=<tim@localhost>, > >> > relay=alfred.gayleard.eu[private/dovecot-lmtp], delay=971, > >> > delays=971/0.03/0.02/0.1, dsn=4.3.0, status=deferred > >> > (host alfred.gayleard.eu[private/dovecot-lmtp] said: 451 4.3.0 > >> > <tim(a)localhost.gayleard.eu> Internal error occurred. > >> > Refer to server log for more information. (in reply to RCPT TO > >> > command)) > > > >> "Refer to server log for more information" comes from dovecot lmtpd > >> so look there and post the output of "doveconf -n" > > > > Thanks very much for your response. > > > > The only information in /var/log/dovecot > > (where I send dovecot debug and info logs) is > > Aug 04 11:29:13 lmtp(14872): > > Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= > > Aug 04 11:29:13 lmtp(14872): > > Info: Connect from local > > Aug 04 11:29:13 lmtp(14872): > > Debug: auth input: > > Aug 04 11:29:13 lmtp(14872): > > Info: Disconnect from local: Successful quit > > > > The output of "doveconf -n" is > > ------------------------- > > # 2.2.10: /etc/dovecot/dovecot.conf > > # OS: Linux 3.10.0-123.4.4.el7.x86_64 x86_64 CentOS Linux release 7.0.1406 (Core) > > debug_log_path = /var/log/dovecot > > info_log_path = /var/log/dovecot > > listen = * > > log_path = /var/log/dovecot > > login_trusted_networks = 192.168.2.0/24 > > mail_debug = yes > > mail_gid = 1000 > > mail_location = maildir:~/Maildir > > mail_uid = 1000 > > 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 > > mbox_write_locks = fcntl > > namespace inbox { > > inbox = yes > > location = > > mailbox Drafts { > > special_use = \Drafts > > } > > mailbox Junk { > > special_use = \Junk > > } > > mailbox Sent { > > special_use = \Sent > > } > > mailbox "Sent Messages" { > > special_use = \Sent > > } > > mailbox Trash { > > special_use = \Trash > > } > > prefix = > > } > > passdb { > > driver = pam > > } > > plugin { > > sieve = ~/.sieve/dovecot.sieve > > sieve_dir = ~/.sieve > > } > > protocols = imap pop3 lmtp sieve > > service imap-login { > > inet_listener imap { > > port = 143 > > } > > inet_listener imaps { > > port = 993 > > ssl = yes > > } > > } > > service lmtp { > > unix_listener /var/spool/postfix/private/dovecot-lmtp { > > group = postfix > > mode = 0777 > > user = postfix > > } > > } > > service managesieve-login { > > inet_listener sieve { > > port = 4190 > > } > > } > > ssl = required > > ssl_cert = </etc/pki/dovecot/certs/dovecot.pem > > ssl_key = </etc/pki/dovecot/private/dovecot.pem > > userdb { > > driver = passwd > > } > > protocol lmtp { > > mail_plugins = " sieve" > > } > > protocol lda { > > mail_plugins = " sieve" > > } > > protocol sieve { > > managesieve_notify_capability = fileinto reject envelope environment mailbox date > > } > > ------------------------- > > > > > > -- > > Timothy Murphy > > e-mail: gayleard /at/ eircom.net > > School of Mathematics, Trinity College, Dublin 2, Ireland

4 3

postfix-dovecot via lmtp
by Timothy Murphy 08 Aug '14

08 Aug '14

I've been trying for some days to get postfix + dovecot + pigeonhole/sieve working on a CentOS-7 home server. I think I may have detected the problem; I read in /var/log/maillog Aug 4 11:29:13 alfred postfix/lmtp[14871]: 9C04C220A99: to=<tim(a)localhost.gayleard.eu>, orig_to=<tim@localhost>, relay=alfred.gayleard.eu[private/dovecot-lmtp], delay=971, delays=971/0.03/0.02/0.1, dsn=4.3.0, status=deferred (host alfred.gayleard.eu[private/dovecot-lmtp] said: 451 4.3.0 <tim(a)localhost.gayleard.eu> Internal error occurred. Refer to server log for more information. (in reply to RCPT TO command)) (I've split one long line here.) 1) I see that the permissions on /var/spool/postfix/private/ are [tim@alfred ~]$ ls -ls /var/spool/postfix/ 4 drwx------. 2 postfix root 4096 Aug 4 11:30 private The socket dovecot-lmtp setup by postfix is in this directory; does dovecot need permission to access this? 2) I see that this mail (a test email from me) was deferred. What exactly does this mean? Where is the mail stored? I couldn't find it anywhere. (It has already been brought to the server by fetchmail.) 3) Am I right in thinking that there are 2 alternatives to dovecot/sieve a) amavisd-new with postfix + spamassassin b) postfix + procmail ? 4) I remember seeing a posting (probably not in this mailing list) describing how one can trace the progress of email through the server. Unfortunately I didn't note the URL, and now cannot find it. Does anyone have a pointer to such a document? As will probably be obvious, I am not at all clear how postfix and dovecot fit together if one introduces lmtp. I take it that without lmtp (or similar) postfix just delivers email to ~/Maildir/cur (in my case), and dovecot is not involved at all until a client (KMail in my case) looks at email? -- Timothy Murphy e-mail: gayleard /at/ eircom.net School of Mathematics, Trinity College, Dublin 2, Ireland

2 2

Dovecot, Thunderbird and messages in wrong folder
by Gerhard Wiesinger 08 Aug '14

08 Aug '14

Hello, Sometimes it happens that messages (e.g. one or two) appear in wrong folders in Thunderbird (latest version, also past versions, different computers, also Earlybird). When I repair the folder (folder/Settings/Repair Folder) in Thunderbird, the folder is correct then. It happens on my new server with Fedora 20, Dovecot 2.2.13 and Maildir but it also happened on my old server with Fedora 1, Dovecot 2.2.13 and mbox. Has anyone the same issue? Any guess whether it might be a thunderbird or dovecot issue? Anyone has the same issues with thunderbird and a different IMAP server (e.g. cyrus)? Thank you. Ciao, Gerhard Config (only relevant parts here): # 2.2.13: /etc/dovecot/dovecot.conf # OS: Linux 3.15.8-200.fc20.x86_64 x86_64 Fedora release 20 (Heisenbug) auth_mechanisms = plain login lda_mailbox_autocreate = yes listen = * mail_gid = vmail mail_home = /home/vmail/%n mail_location = maildir:~/Maildir mail_max_userip_connections = 20 mail_plugins = " stats mailbox_alias zlib" mail_uid = vmail protocols = imap lmtp sieve service imap-login { inet_listener imap { port = 0 } process_min_avail = 2 service_count = 0 } service imap { client_limit = 20 executable = imap postlogin process_limit = 20 } service lmtp { inet_listener lmtp { port = 24 } process_min_avail = 2 } service managesieve-login { process_min_avail = 1 } service postlogin { executable = script-login -d rawlog } service stats { fifo_listener stats-mail { mode = 0600 user = vmail } } ssl_cert = </etc/pki/dovecot/imap.crt ssl_key = </etc/pki/dovecot/imap.key submission_host = 127.0.0.1 userdb { args = username_format=%n /etc/dovecot/users driver = passwd-file } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_plugins = " stats mailbox_alias zlib imap_stats imap_zlib" } protocol lmtp { mail_plugins = " stats mailbox_alias zlib sieve" }

2 1

Dovecot and remote SASL Client via TLS
by Gerhard Wiesinger 08 Aug '14

08 Aug '14

Hello, Is it possible to configure Dovecot as SASL client for central authentication (also remotely via TCP/TLS)? Following use case: IMAP server (host 1) <=> Windows Domain Controller and /etc/shadow authenticator via pam (host2) Should work as: IMAP server (host 1) <=> SASL Client via TLS <=> Network <=> SASL Server via TLS <=> Local SASL via pam <=> Windows Domain Controller and /etc/shadow authenticator via pam (host2) Thank you. Ciao, Gerhard -- http://www.wiesinger.com/

1 2

invalid/unknown path to storage
by Benjamin Connelly 08 Aug '14

08 Aug '14

Am I correct: pigeonhole now wants the symlink to the filter file to use an absolute path instead of the relative paths we had? i.e.) sieve-filterfile@ -> /home/mail/domain/user(a)domain/roundcube.sieve instead of sieve-filterfile@ -> roundcube.sieve Dovecot logs these: dovecot: managesieve(user(a)domain.org): Warning: sieve-storage: Active sieve script symlink /home/mail/domain.org/user(a)domain.org/sieve-filterfile is broken: invalid/unknown path to storage (points to roundcube.sieve). and the debug log: Jul 29 15:37:59 managesieve(user(a)domain.org): Debug: sieve: Pigeonhole version 0.4.3 initializing Jul 29 15:37:59 managesieve(user(a)domain.org): Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global' scripts. Jul 29 15:37:59 managesieve(user(a)domain.org): Debug: sieve-storage: using active sieve script path: /home/mail/domain.org/user(a)domain.org/sieve-filterfile Jul 29 15:37:59 managesieve(user(a)domain.org): Debug: sieve-storage: using sieve script storage directory: /home/mail/domain.org/user(a)domain.org/ Jul 29 15:37:59 managesieve(user(a)domain.org): Debug: sieve-storage: using permissions from /home/mail/domain.org/user(a)domain.org/: mode=0700 gid=-1 Jul 29 15:37:59 managesieve(user(a)domain.org): Debug: sieve-storage: relative path to sieve storage in active link: I found if I manually delete a symlink and replace it using the full path: sieve-filterfile -> /home/mail/domain.org/user(a)domain.org/roundcube.sieve then everybody is happy. So I'm looking to make a configuration change (and then change all existing symlinks.) I just wanted to check with the list about the two settings we return as part of the user_query: concat(homedir, maildir, 'sieve-filterfile') as sieve, concat(homedir,maildir) as sieve_dir In testing it seems like changing 'sieve' to return not the whole path but just the link name, actuall causes pigeonhole to properly make the symlink with full path! Does this seem right? FreeBSD (8.4) dovecot-pigeonhole (0.4.3_1) dovecot2 (2.2.13_3) Benjamin

2 1

Pigeonhole version 0.4.3 on FreeBSD-10
by Jerry 07 Aug '14

07 Aug '14

Thu, 7 Aug 2014 06:22:01 -0400 I am running Pigeonhole version 0.4.3 on a FreeBSD 10 machine. How do I actually trace which rule in my sieve file is causing a specific action on a specific email. Other then eliminating each rule one by one and rerunning the script to isolate it, how can I discover what rule is causing the problem? Thanks! -- Jerry

2 3

Is atomic MOVING of messages between IMAP folders possible?
by Greg Sullivan 07 Aug '14

07 Aug '14

I would like to use a shared IMAP account, with multiple users accessing it simultaneously. The users would take ownership of messages by first attempting to MOVE the messages from the Inbox, into their private IMAP folder, still within the same account. Now, since there will be multiple users competing for the same messages, I naturally want only ONE of the simultaneous moves to be successful at a time. So far, this isn't working. If I do the move from two clients, simultaneously, the messages can go to *both *destination folders - duplicates can result. Is it possible to configure Dovecot and/or an IMAP client to behave the way I want it to? If the answer to this is YES, then I'll offer my config details. If the answer is NO, the next question is - do any email systems at all behave the way I want? (I tried a hosted Exchange/OWA service - it has the same problem) Thanks & regards, Greg.

7 13

Panic on alway_bcc mail with attachment while using sdbox
by Fischer, Bernhard 07 Aug '14

07 Aug '14

I do always get a panic on service lmtp, while receiving a mail by postfix through always_bcc, containing an attachment. If the bcc recipient would be supplied by a small delay, I would say that the panic wouldn't occur, but I don't know how to verify this. dovecot is configured with 'mail_attachment_dir' and the public namespace location is sdbox dovecot log: Aug 6 14:18:02 dovecot dovecot: lmtp(20367, vscanner(a)fischer-ing.de) Panic: file fs-api.c: line 615 (fs_copy): assertion failed: (src->fs == dest->fs) Aug 6 14:18:02 dovecot dovecot: lmtp(20367, vscanner(a)fischer-ing.de) Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x66676) [0x443676] -> /usr/lib/dovecot/libdovecot.so.0(+0x66700) [0x443700] -> /usr/lib/dovecot/libdovecot.so.0(+0x18c23) [0x3f5c23] -> /usr/lib/dovecot/libdovecot.so.0(+0x2278b) [0x3ff78b] -> /usr/lib/dovecot/libdovecot-storage.so.0(sdbox_copy+0x4ad) [0x23c6ad] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_copy+0x62) [0x27da72] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_save_using_mail+0x2b) [0x27db4b] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver_save+0x1a1) [0x5dd3c1] -> /usr/lib/dovecot/libdovecot-lda.so.0(mail_deliver+0x143) [0x5dd7c3] -> dovecot/lmtp() [0x804d090] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x43) [0x455973] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xdb) [0x456c4b] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x48) [0x4558b8] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x2e) [0x3fb0ee] -> dovecot/lmtp(main+0x1b3) [0x804b463] -> /lib/libc.so.6(__libc_start_main+0xe6) [0x5f9d26] -> dovecot/lmtp() [0x804b1e1] Aug 6 14:18:02 dovecot dovecot: lmtp(20367, vscanner(a)fischer-ing.de) Fatal: master: service(lmtp): child 20367 killed with signal 6 (core dumps disabled)

1 1