- dovecot - dovecot.org

Re: [Dovecot] dovecot.org moved
by Timo Sirainen 07 Feb '14

07 Feb '14

On 7.2.2014, at 10.02, Timo Sirainen <tss(a)iki.fi> wrote: > On 7.2.2014, at 9.58, Timo Sirainen <tss(a)iki.fi> wrote: > >> Looks like the old server doesn't stay up much at all anymore. And since it's kind of difficult currently to get access to the server I just restored everything from the previous night's backups. Latest mailing list subscribes/unsubscribes may need to be done again. Also I think there are some old configurations (and other things) still somewhere.. I'll change these as found and maybe I'll get access to the old server some day soon and can check again what differences there are. > > Archives weren't updating due to permission error .. Lets try again.. nope.

1 0

[Dovecot] dovecot -n FATAL
by Phil 06 Feb '14

06 Feb '14

Hi List, Im new to postfix-dovecot and im mystified by the following results in ubuntu 10.04lts :~$ dovecot -n # 1.2.9: /etc/dovecot/dovecot.conf Error: ssl_key_file: Can't use /etc/ssl/private/ssl-mail.key: Permission denied Fatal: Invalid configuration in /etc/dovecot/dovecot.conf ~$ sudo ls -dl /etc/ssl/private/ssl-mail.key lrwxrwxrwx 1 root root 38 2013-11-27 08:35 /etc/ssl/private/ssl-mail.key -> /etc/ssl/private/ssl-cert-snakeoil.key Why is dovecot happily delivering mail to local accounts ( thats all i use atm) without being able to access the ssl key, and how can i fix this problem so i can run dovecot -n successfully. i have tried 'chown dovecot' etc but there was no change in dovecot -n output. Any and all help is appreciated. Phil

4 8

[Dovecot] Plugin architecture
by Philipp Brüll 06 Feb '14

06 Feb '14

Hi, I'm currently developing a scrambler plugin which should be used to store the mails encrypted on the disk. It uses a special ostream for encryption and an istream for decryption. The idea is, that if a mail arrives via LMTP it goes through the ostream and is written encrypted to disk. If an mail is accessed via IMAP, the istream is used to decrypt the data from disk. That all works fine, but if I add the zlib plugin it all gets mixed up. For some reason, the lmtp process tries to read something from disk using the chain of istreams. That behaviour is a little bit bizzare to me, because my understanding is, that the zlib plugin at this point should only write (compressed) data to disk. Why is the istream used here? And what is read? If I remove zlib from the configuration again, it all works as expected. The dovecot version is 2.1.17. Best regards, Philipp

1 0

[Dovecot] Trying to get Dovecot Director Proxying working
by Murray Trainer 06 Feb '14

06 Feb '14

Hi All, Firstly, thanks for all the really helpful responses to my previous questions "Architecture for large Dovecot cluster" and "Sizing MTA servers". I am now trying to get a Dovecot director proxy working with a single backend mail server. When I try to connect to the dovecot proxy on the pop3 and imap ports I get connection refused. I want the authentication to be on the backend mail server initially. I am not sure if I am missing something? More info below... Thanks Murray # doveadm director status mail server ip vhosts users 27.54.95.41 100 0 # doveadm director map doveadm(root): Error: userdb list: Disconnected unexpectedly doveadm(root): Error: user listing failed user mail server ip expire time # doveadm fetch -A user ALL doveadm(root): Error: userdb list: Disconnected unexpectedly doveadm: Error: Failed to iterate through some users # doveconf -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.1 auth_cache_size = 32 M auth_cache_ttl = 2 hours auth_debug = yes auth_verbose = yes base_dir = /var/run/dovecot/ director_mail_servers = 27.54.95.41 director_servers = 27.54.95.37 disable_plaintext_auth = no mail_debug = yes passdb { args = nopassword=y proxy=y driver = static } service auth { unix_listener auth-userdb { mode = 0666 user = dovecot } } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 9090 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service imap-login { executable = imap-login director } service ipc { unix_listener ipc { user = dovecot } } service pop3-login { executable = pop3-login director } ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { args = uid=dovenull gid=dovenull home=/var/run/dovecot/empty driver = static }

1 0

[Dovecot] LMTP troubles
by Phillip Odam 06 Feb '14

06 Feb '14

Background: Dovecot: v 2.0.9 OS: AWS Linux (derived from CentOS) At this stage I've avoided upgrading to a newer version of Dovecot as version 2.0.9 is what AWS Linux provides and I'd like to be able to run a regular AWS Linux installation if I can. As opposed to pulling newer versions of dovecot from other repositories or building from source, since the odds are this issue is not a bug in dovecot. I've just tried setting up the LMTP service and eventually uncovered that that the greeting the server responds with straight after connecting isn't being returned. This must be a configuration mistake on my behalf but I just haven't been able to figure it out yet. I haven't had LMTP configured for awhile but I'm sure I've had it all in place and don't recall any issue like this. I've followed the detail here http://wiki2.dovecot.org/LMTP, in particular # add lmtp to protocols, otherwise its listeners are ignored protocols = imap pop3 lmtp service lmtp { inet_listener lmtp { address = 192.168.0.24 127.0.0.1 ::1 port = 24 } unix_listener lmtp { #mode = 0666 } } What's also interesting, using telnet my first attempt to connect results in the server closing the connection immediately and then a second attempt to connect results in an established connection but no response from the server so that then the LMTP client knows it's all good to begin issuing commands. I have no idea about the architecture of dovecot and the LMTP service but it's as if dovecot has successfully bound to the port allocated for LMTP* but the the LMTP service has either not started or dovecot doesn't know which service to pass the connection on to. * - dovecot has definitely bound to the port (localhost:24) as netstat clearly shows this. I've tried enabling debug logging per the details here http://wiki2.dovecot.org/Logging and checked that I'm looking at all the logs I need to be using doveadm log find but not seeing any information that helps. At the moment I know I'm light on necessary detail for anyone to help but I thought I'd try in case anyone has seen this before and is able to tell me I've missed X and Y. I'm planning on setting up a clean environment to sort this issue out and if needed will follow up here with more detail and the final solution/s. Thanks Phillip

1 0

[Dovecot] qmail dovecot lda
by Florin Portase 06 Feb '14

06 Feb '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 SETUP: qmail + dovecot 2.2.10 + pigeonhole 0.4.2 I have a user who's quota is at 98% so theoretically when this user is receiving any mails qmail shout send a rejection message like user is overquota /vpopmail/domains/medianetork.ro/.qmail-default #| /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox | DTLINE=${DTLINE/$USER-} /var/qmail/bin/preline -f /usr/libexec/dovecot/dovecot-lda -d $EXT@$USER -a $EXT@$USER If I let enabled only this line | /home/vpopmail/bin/vdelivermail '' bounce-no-mailbox everything is working OK 1st test: from yahoo mail - - send an _attachment of 2mb ( way over quota ) and the response: @4000000052f370fd3381b504 info msg 3793: bytes 4268 from <<>@medianetork.ro> qp 19703 uid 420 @4000000052f370fd3381b8ec starting delivery 6: msg 3793 to remote pflorin1(a)yahoo.com @4000000052f370fd3381b8ec status: local 0/10 remote 1/120 @4000000052f371011135ec04 delivery 6: success: 66.196.118.33_accepted_message./Remote_host_said:_250_ok_dirdel/ @4000000052f371011135f3d4 status: local 0/10 remote 0/120 2nd test: from lotus domino - - send an _attachment of 2mb ( way over quota ) @4000000052f34f832bc8fa0c info msg 3774: bytes 3444 from <<>@medianetork.ro> qp 13708 uid 420 @4000000052f34f832bc8fa0c starting delivery 2: msg 3774 to remote pflorin1(a)fr.ibm.com @4000000052f34f832bc8fdf4 status: local 0/10 remote 1/120 @4000000052f34f84346185e4 delivery 2: failure: Connected_to_195.75.94.105_but_sender_was_rejected./Remote_host_said:_501_Syntax_error_in_parameters_or_arguments:_(-132)/ Also gmail complains about Syntax error -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJS839EAAoJECEzxtLP+204PG8H/3+melSRQ9zWlqaY77rnxIIV 7fV3c6DFvwWeBr7MJx7MAtWRljzyS8dMLkNrfqvZlhWBRljinV3P8iX8m+ZT6wKG 42H5BLCRPhXccppFvYwTL22CNFO0+ZKdhogFFrr3bBxdoir3xW+rG9dUDw+uvQZw y2R6zUp4o33nBKq44mfvIOV8/kwDiVdxN+p/pbs/QFsvtFJh+NI39F9mxWFMkTAk leQjjSrKSw/yKBXjWRT4Gu35XrqylbUHo8n9EzS6jP47OE2DAHMhfKI8/0qCHcNK R3NiWu7xvW8GX66zhF3LUZN5ojAxniZ+AvJ+q016BQi7EWMeNcR7a/o8bavSaMg= =kcDs -----END PGP SIGNATURE-----

2 1

[Dovecot] mime support for pigeonhole
by Tim Dickson 06 Feb '14

06 Feb '14

is there any chance of rfc5703 (mime support/extension) being added to pigeonhole? I am trying to filter mail with .exe and .zip attachments, to no success. I have tried *header :contains "x-attached" [".zip", ".exe"] *but emails i'm getting don't have x-attached. a sample snippet is below. Subject: testa1 Content-Type: multipart/mixed; boundary="------------020304040002050407030900" This is a multi-part message in MIME format. --------------020304040002050407030900 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit this has a compressed file added a1 --------------020304040002050407030900 Content-Type: application/x-zip-compressed; name="pinglog.zip" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="pinglog.zip" I have tried *header :contains ["Content-Type","name","filename"] ["application/x-zip-compressed",".zip",".exe"]* but that doesn't work either. I can't use body because that doesn't include the mime headers, so the only way I can see is to use mime (aka rfc5703) I am using dovecot 2.1.8 with pigeonhole 0.3.3 (and am about to use dovecot 2.2.9 with pigeonhole 0.4.2 on another server) If I'm just missing the point, or there is already support, please point me in the right direction.

6 7

[Dovecot] Mail location security
by Roman Gelfand 06 Feb '14

06 Feb '14

I am not sure I understood this issue correctly... When using maildir with ie ldap. Suppose ldap attribute settings say gid 8 and uid 999, Those are the permissions for every email address. If so, someone who has access to one email user on the server, has access to all. If this is so, is using mailbox instead of maildir resolve this problem? Thanks in advance

2 1

[Dovecot] userdb section not recognized in dovecot.conf. Help?
by CypherPunk 06 Feb '14

06 Feb '14

I'm following a tutorial[1] on how to configure dovecot and the tutorial says to insert the following configuration options into the dovecot.conf file: disable_plaintext_auth = no mail_privileged_group = mail mail_location = mbox:~/mail:INBOX=/var/mail/%u userdb { driver = passwd } This seems to have worked for a lot of others using this tutorial but not for me. When I try to start dovecot, I am told that the section at userdb is an unknown section type. I've spent the last few hours on Google searching this out and I've gotten conflicting answers that don't make sense. Is this the proper way to use the userdb directive? For information, I've also tried userdb{ driver = passwd-file } and that didn't work either. So I'm assuming that perhaps userdb is deprecated somehow but I don't know what to replace it with. Can someone point me in the right direction? Many Thanks! CypherPunk [1] https://www.digitalocean.com/community/articles/how-to-set-up-a-postfix-e-m…

2 1

[Dovecot] Debian Wheezy-Backports - Dovecot (1:2.2.9-1~bpo70+1) missing xz compression support?
by T.B. 05 Feb '14

05 Feb '14

Hallo Everyone, since some days a new dovecot version is available in Debian "wheezy-backports": (1:2.2.9-1~bpo70+1) wheezy-backports As described in http://wiki2.dovecot.org/Plugins/Zlib and http://www.dovecot.org/doc/NEWS-2.2 "xz"-compression is available since Dovecot version 2.2.9. Today I tried to convert my mailboxes with the new xz compression. Therfore I changed my config as follows: /etc/dovecot/conf.d/10-mail.conf: # Space separated list of plugins to load for all services. Plugins specific to IMAP, LDA, etc. are added to this list in their own .conf files. mail_plugins = zlib acl fts fts_solr /etc/dovecot/conf.d/90-plugin.conf: # Enable these only if you want compression while saving: zlib_save_level = 9 # 1..9 zlib_save = xz # gz or bz2 or xy Now I tried to convert my mailboxes - but somehow, something goes wrong: root@SERVER:/# dovecot --version 2.2.9 root@SERVER:/# dsync mirror mdbox:/srv/converted_vmail/ doveadm(root): Error: zlib_save: Support not compiled in for handler: xz dsync(root): Error: zlib_save: Support not compiled in for handler: xz Where is the failure? Did the packet maintainer forget to activate xz? I can't find anything xz related in the debian package changelog: http://metadata.ftp-master.debian.org/changelogs//main/d/dovecot/dovecot_2.… Should I contact the Debian packet maintainer? http://packages.qa.debian.org/d/dovecot.html Best regards T.B.

2 2