- dovecot - dovecot.org

Re: [Dovecot] Command died with signal 6
by गौरव जोशी 10 Jul '10

10 Jul '10

Hi Timo, Thank you for the response. I've sorted out my problem with the help of it. There was a big error i could find in error logs. =========================================================================== Jul 09 11:22:10 Error: Raw backtrace: /usr/local/libexec/dovecot/deliver [0x80c7c50] -> /usr/local/libexec/dovecot/deliver(default_fatal_handler+0x33) [0x80c7d33] -> /usr/local/libexec/dovecot/deliver [0x80c756c] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7f8524d] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7f900d7] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7f8fee2] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(sieve_eval_bc+0x205) [0xb7f91135] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(sieve_execute_bytecode+0xf3) [0xb7f96ba3] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(cmu_sieve_run+0x311) [0xb7f868d1] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7f844e4] -> /usr/local/libexec/dovecot/deliver(main+0x123d) [0x805bd5d] -> /lib/libc.so.6(__libc_start_main+0xe0) [0x327f70] -> /usr/local/libexec/dovecot/deliver [0x8059821] =========================================================================== It was sieve plugin which was not compatible with dovecot version. I upgraded the sieve plugin from 1.1.6 to 1.1.8 and the error stopped to come. Have a nice time, Gourav Joshi http://www.linuxquestions.in

1 0

Re: [Dovecot] I can receive but not send
by Dennis Clarke 10 Jul '10

10 Jul '10

>> Am I missing something obvious here ? > > Dovecot isn't a SMTP-Server/MTA. > See also: http://wiki.dovecot.org/MailServerOverview > That figures ... it had to be my sendmail config of all things. Geez .. I hate sendmail configuration. OKay .. thanks. -- Dennis

2 1

[Dovecot] I can receive but not send
by Dennis Clarke 09 Jul '10

09 Jul '10

I'm not too sure where to look here. I can access my mail via Dovecot and there is an initial requirement to accept an SSL key ( self signed ) however after I look in my inbox and read a piece of email ( via SeaMonkey eMail client ) I can not send. I simply get told that the server would not accept the smtp connection. I was hoping for a smtps connection but I'll take what I can get. Am I missing something obvious here ? -- Dennis

3 2

[Dovecot] Dovecot 2.0 with LMTP
by Thiago Henrique 09 Jul '10

09 Jul '10

Hello, I'm testing Dovecot 2.0. I plan to use Dovecot 2.0 with thousands of domains per server. My user base is under virtual MySQL. Is there a way to make the LMTP not make query to MySQL for each message delivered ? I'm afraid that the MySQL server does not support the load. Best Regards -- []'s Thiago Henrique Network Administration Digirati Networks K8 Networks

5 5

[Dovecot] Dovecat crash signal 11 core dump
by Ray Kirby 09 Jul '10

09 Jul '10

Vpopmail 5.5.0 Dovecot -n # 2.0.rc1: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.31.5-127.fc12.i686.PAE i686 Fedora release 12 (Constantine) auth_debug = yes auth_debug_passwords = yes auth_verbose = yes debug_log_path = /var/log/dovecot default_internal_user = vpopmail disable_plaintext_auth = no log_path = /var/log/dovecot mail_debug = yes mail_gid = 508 mail_location = maildir: /home/vpopmail/domains/%d/%n/Maildir mail_uid = 508 passdb { args = cache_key=%u%s:backend=%q driver = vpopmail } service auth { unix_listener auth-userdb { group = vpopmail user = vpopmail } } ssl = no userdb { driver = vpopmail } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 20 } Problem: Jul 08 12:35:08 auth: Debug: Loading modules from directory: /usr/local/lib/dovecot/auth Jul 08 12:35:08 auth: Debug: new auth connection: pid=5514 Jul 08 12:35:08 auth: Debug: client in: AUTH 1 PLAIN service=imap lip=30.30.14.22 rip=192.168.0.100 lport=143 rport=53112 Jul 08 12:35:08 auth: Debug: client out: CONT 1 Jul 08 12:35:08 auth: Debug: client in: CONT 1 AHJraXJieaBteUxprmV1cC5jb20AYWJzcmNr Jul 08 12:35:08 auth: Debug: vpopmail(user(a)mydomain.com,192.168.0.100): lookup user=user domain=mydomain.com Jul 08 12:35:08 auth: Debug: client out: OK 1 user=user(a)mydomain.com Jul 08 12:35:08 auth: Debug: master in: REQUEST 1 5514 1 4a87d9ed9185eb0794667c5f7adb724f Jul 08 12:35:08 auth: Debug: vpopmail(user(a)mydomain.com,192.168.0.100): lookup user=user domain=mydomain.com Jul 08 12:35:08 master: Error: service(auth): child 5516 killed with signal 11 (core dumped) Jul 08 12:35:08 master: Error: service(auth): command startup failed, throttling Jul 08 12:35:08 imap-login: Info: Internal login failure (auth failed, 1 attempts): user=<user(a)mydomain.com>, method=PLAIN, rip=192.168.0.100, lip=30.30.14.22, mpid=5517 Thanks

3 2

Re: [Dovecot] Sieve user info log (was: problems with sieve under 2.0)
by Stephan Bosch 08 Jul '10

08 Jul '10

Hi Perry, Perry E. Metzger wrote: > By the way, I've noticed that there doesn't seem to be a good way for > the user to get information on what email message gets filed where by > sieve -- syslog information seems to be the sole data source > available. > Right. There is a per-user <main-script>.log file (e.g. .dovecot.sieve.log), but that will only be written when there are any errors. Info logging is indeed only available in the syslogs. > procmail has a facility where you can ask it to log every action it > takes. I looked around for a similar facility for sieve and I didn't > seem to see it. Did I miss something, or is it absent? > I DO see the merit of this. However, configuring this behavior is an interesting issue. If the user log verbosity is configured in the Dovecot userdb, it may in many cases still only be configurable by the administrator. An alternative solution would be to provide the logging configuration directly in the Sieve script; analogous to the way Procmail handles this. This would give users direct control. However, the Sieve specification and its extensions currently define no such facility. In fact, both Sieve and ManageSieve don't provide any means for the user to control what is logged during script execution. This would require some new or custom (vnd.dovecot.) Sieve or ManageSieve extension. However, defining a new extension like that is rarely useful unless clients implement support for it. Another problem is that users need filesystem access or some other custom (HTTP) interface to read the logs. This can be problematic when virtual users are involved. This too could be mended with an extension to the ManageSieve protocol. Alternatively, the Pigeonhole TODO list mentions a solution that writes logs as messages in a special IMAP-accessible folder, but I'm still not sure how practical that is. The above considerations may warrant starting a draft RFC on controlling and accessing Sieve runtime logs. But, I'm deviating from the original issue... what is it that you truly need right now? And for the Dovecot list, any other ideas on the above? Regards, Stephan.

2 1

[Dovecot] trash folder (again)
by Holger Hegmanns 08 Jul '10

08 Jul '10

Hi, I read very intently all the issues related to imap trash folders, but either I didn't unerstand them or my problem is slightly different. I plan to migrate from cyrus to dovecot. I've executed the perl script cyrus2dovecot successfully with the substitution flag "-E 's/^\./.INBOX./'" cause I want to have all folders as subfolders of the INBOX. The vmail dir looks like this afterwards: drwxr-xr-x 11 vmail vmail 4096 Jul 8 14:19 . drwxr-xr-x 3 vmail vmail 4096 Jul 8 14:19 .. drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.Drafts drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.Sent drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.Templates drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.Trash drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.blah drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.blub drwxr-xr-x 2 vmail vmail 4096 Jul 8 14:19 cur -rw-r--r-- 1 vmail vmail 119 Jul 8 14:19 dovecot-uidlist drwxr-xr-x 2 vmail vmail 4096 Jul 8 14:19 new -rw-r--r-- 1 vmail vmail 80 Jul 8 14:19 subscriptions drwxr-xr-x 2 vmail vmail 4096 Jul 8 14:19 tmp After the first access with Thunderbird, regardless of the version (TB2x or TB3x) and regardless of using TB with an empty profile or a well filled up, the directory looks different: drwxr-xr-x 12 vmail vmail 4096 Jul 8 14:21 . drwxr-xr-x 3 vmail vmail 4096 Jul 8 14:19 .. drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.Drafts drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.Sent drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.Templates drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.Trash drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.blah drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:19 .INBOX.blub drwxr-xr-x 5 vmail vmail 4096 Jul 8 14:21 .Trash drwxr-xr-x 2 vmail vmail 4096 Jul 8 14:19 cur -rw-r--r-- 1 vmail vmail 119 Jul 8 14:21 dovecot-uidlist -rw-r--r-- 1 vmail vmail 17408 Jul 8 14:21 dovecot.index.cache -rw-r--r-- 1 vmail vmail 448 Jul 8 14:21 dovecot.index.log drwxr-xr-x 2 vmail vmail 4096 Jul 8 14:19 new -rw-r--r-- 1 vmail vmail 86 Jul 8 14:21 subscriptions drwxr-xr-x 2 vmail vmail 4096 Jul 8 14:19 tmp A Trash folder was added by TB, I guess. The related lines of the local TB imap logfile (beginning chars are cutted): mydovedomain.lan:A:CreateNewLineFromSocket: * LIST (\HasChildren) "." "INBOX" ReadNextLine [stream=4ecf8a10 nb=22 needmore=0] mydovedomain.lan:A:CreateNewLineFromSocket: 5 OK List completed. mydovedomain.lan:A:SendData: 6 list "" "Trash" ReadNextLine [stream=4ecf8a10 nb=22 needmore=0] mydovedomain.lan:A:CreateNewLineFromSocket: 6 OK List completed. mydovedomain.lan:A:SendData: 7 create "Trash" ReadNextLine [stream=4ecf8a10 nb=24 needmore=0] mydovedomain.lan:A:CreateNewLineFromSocket: 7 OK Create completed. mydovedomain.lan:A:SendData: 8 subscribe "Trash" ReadNextLine [stream=4ecf8a10 nb=27 needmore=0] mydovedomain.lan:A:CreateNewLineFromSocket: 8 OK Subscribe completed. mydovedomain.lan:A:SendData: 9 list "" "Trash" ReadNextLine [stream=4ecf8a10 nb=37 needmore=0] mydovedomain.lan:A:CreateNewLineFromSocket: * LIST (\HasNoChildren) "." "Trash" Maybe it's a namespace related problem, cause the advanced TB preference panel looks like that: private namespace "" and the other both input fields are empty. In opposite to cyrus. The preexisting Trash folder (I created all the standard folders with cyradm by hand) below the INBOX seems sufficient to TB, no further Trash can was created and here all input fields are filled up as followed: private namespace "INBOX." shared "" other users "user." (only translated by me, it's a localized german version of TB) I tried hard to understand the namespace wiki page of dovecot, but without success. Finally my dovecot.conf, dovecot version is 1.2.11: protocols = imap managesieve protocol imap { listen = mydovedomain.lan:10143 } protocol managesieve { listen = mydovedomain.lan:12000 } disable_plaintext_auth = no log_path = /var/log/imap/dovecot.log ssl = no ssl_cert_file = /etc/ssl/dovecot/server.pem ssl_key_file = /etc/ssl/dovecot/server.key mail_location = maildir:~/Maildir mail_privileged_group = mail mail_debug = yes protocol imap { } protocol pop3 { } protocol managesieve { } protocol lda { postmaster_address = postmaster at mydovedomain.lan mail_plugins = cmusieve acl } auth_verbose = yes auth default { mechanisms = plain cram-md5 passdb passwd-file { args = /etc/dovecot/passwd } passdb pam { } userdb static { args = uid=vmail gid=vmail home=/var/spool/dovecot/vmail/%u } user = root } dict { } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename flag_change append } Please don't punish me, if my problem is already solved. And sorry for my poor English Holgerr

2 4

[Dovecot] Thunderbird and shared mailboxes
by Keith Edmunds 08 Jul '10

08 Jul '10

I'm setting up shared mailboxes as in http://wiki.dovecot.org/SharedMailboxes/Shared, and have set ACLs as described on that page to share one folder of user A's mailbox with User B. However, I'm struggling to get Thunderbird for userb(a)example.com to read the shared folder of usera(a)example.com. Has anyone done this? Thunderbird 3.0, Dovecot 1.2.11 Thanks, Keith

2 10

[Dovecot] Eronious comment in sample Director configuration
by Brad Davidson 08 Jul '10

08 Jul '10

The sample Director configuration (10-director.conf) says that director_servers and director_mail_servers can be lists of either IPs or hostnames: # List of IPs or hostnames to all director servers, including ourself. # Ports can be specified as ip:port. The default port is the same as # what director service's inet_listener is using. #director_servers = # List of IPs or hostnames to all backend mail servers. Ranges are allowed # too, like 10.0.0.10-10.0.0.30. #director_mail_servers = However, if I use hostnames, it bails out with an "Invalid IP address" error. It also seems to be confusing the dashes in my hostnames for address range specifications. Obviously hostnames are not currently supported, but I thought I'd mention it so the documentation could be updated. -Brad

2 1

[Dovecot] Director error during sync
by Brad Davidson 08 Jul '10

08 Jul '10

Just an FYI - if I have a two-node director ring, I get this when I start up the second node: Jul 7 16:59:38 oh-popmap7 dovecot: director: Error: Received SYNC from 10.142.0.162:1234/left (seq=6) while already synced Totally expected since it's already received the same SYNC from the right side, but since I thought I heard you say that "any errors that Dovecot logs are bugs" I thought I'd report it ;) For that matter, it also logs errors when I shut down / restart the second node: Jul 7 16:59:37 oh-popmap7 dovecot: director: Error: Director 10.142.0.162:1234/left disconnected Jul 7 16:59:37 oh-popmap7 dovecot: director: Error: Director 10.142.0.162:1234/right disconnected Jul 7 16:59:37 oh-popmap7 dovecot: director: Error: director(10.142.0.162:1234/out): connect() failed: Connection refused -Brad

2 2