- dovecot - dovecot.org

[Dovecot] (2.1 recent:) fts_decoder
by Lutz Preßler 23 Sep '11

23 Sep '11

Hello again, test setup as in previous messages. With fts = lucene, I enabled the adapted decode2text.sh (at least I tried...) as suggested in the comment section. On dovecot-start /var/run/dovecot/decode2text socket is created with sufficiant permissions (rw for anybody), but decode2text.sh is not started (it's rx for anybody). When creating lucene indexes, I cannot see it executed either (and no attachment-only content is findable afterwards). No errors with mail_debug - if I change fts_decoder to a nonexistant value, that's logged. Lutz

2 1

[Dovecot] 64.31.19.48 attempt to break into my computer
by Rick Baartman 23 Sep '11

23 Sep '11

>From my secure log: Sep 19 01:16:44 lin12 dovecot-auth: pam_unix(dovecot:auth): check pass; user unknown Sep 19 01:16:44 lin12 dovecot-auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser= rhost=::ffff:64.31.19.48 Sep 19 01:16:44 lin12 dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user aaron Sep 19 01:16:45 lin12 dovecot-auth: pam_unix(dovecot:auth): check pass; user unknown Sep 19 01:16:45 lin12 dovecot-auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser= rhost=::ffff:64.31.19.48 Sep 19 01:16:45 lin12 dovecot-auth: pam_succeed_if(dovecot:auth): error retrieving information about user abby etc. Literally, 30,000 user names attempted. -- rick baartman TRIUMF 4004 Wesbrook Mall Vancouver, BC V6T2A3

10 17

Re: [Dovecot] 64.31.19.48 attempt to break into my computer
by Alex 23 Sep '11

23 Sep '11

It is a great tool. Unfortunately dovecot allows infinate incorrect logins during a single session. When fail2ban has firewalled the ip its pointless as the rule only affects new sessions, not established ones. I am disappointed that the author of dovecot has no interest in adding a feature that closes the session after x auth failures. It would certainly make tools like fail2ban more effective. ----- Reply message ----- From: "John Alexander" <john.alexander(a)preachain.org> Date: Fri, Sep 23, 2011 00:13 Subject: [Dovecot] 64.31.19.48 attempt to break into my computer To: <dovecot(a)dovecot.org> Fail2Ban is an excellent tool to deal with this sort of thing. On Mon, 19 Sep 2011 10:05:47 -0700, Rick Baartman wrote > >From my secure log: > > Sep 19 01:16:44 lin12 dovecot-auth: pam_unix(dovecot:auth): check > pass; user unknown > Sep 19 01:16:44 lin12 dovecot-auth: pam_unix(dovecot:auth): > authentication failure; logname= uid=0 euid=0 tty=dovecot ruser= > rhost=::ffff:64.31.19.48 > Sep 19 01:16:44 lin12 dovecot-auth: pam_succeed_if(dovecot:auth): > error retrieving information about user aaron

3 2

[Dovecot] Dovecot 1.x vs 2.x
by Lee Standen 22 Sep '11

22 Sep '11

Hi All, I'm currently in the planning stages for a technology refresh for a very large mail installation, and looking at using Dovecot with LDA/Sieve/FTS_Solr and a number of other plugins to give our users some great features. Currently, our standard distribution is Ubuntu Lucid, which has Dovecot 1.x included with it in pre-built packages, and Dovecot 2.x is in the upcoming Oneiric beta coming out next month. My question is, are there any compelling reasons why we should gravitate towards running Dovecot 2.x beyond the fact it's the "latest and greatest" version? What features would we miss that we're likely to want or need on a very large installation (i'm talking dozens of VM's, over 1 million mailboxes). Thanks

1 0

[Dovecot] Dovecot 1.2, problem with SQL quota and mail aliases
by Jacek Osiecki 22 Sep '11

22 Sep '11

Hello, I have a small server running dovecot 1.2 (still not balsy enough to switch to 2.0 - virtual sql accounts, managesieve etc.). There are no local users - only ones defined in the SQL database, and everything else (including quota) is defined in SQL db too. Dovecot is used as IMAP daemon, and dovecot-lda is responsible for delivery (in order to make use of sieve and managesieve). I know that my configuration might be a bit ancient, but this is not referring to any bug (at least I think so) and rather to errors I've made in configuration. Several users have reported, that they are running out of quota even though their mailboxes are empty. I thought these were some single cases, but recently I discovered that this situation occurs when: - user john(a)domain.com has a mail alias, eg. john.smith(a)domain.com - he logs in to the imap account (using MUA or webmail) using his alias (john.smith(a)domain.com) In effect, all incoming emails for john(a)domain.com are increasing the counters (both "bytes" and "messages"), but since user logs in using john.smith(a)domain.com - anything he deletes from the mailbox decreases the records for john.smith(a)domain.com. Finally, John has two records: +---------------------------+-----------+----------+ | username | bytes | messages | +---------------------------+-----------+----------+ | john.smith(a)domain.com | -5488133 | -13 | | john(a)domain.com | 341411029 | 1111 | +---------------------------+-----------+----------+ The record for john(a)domain.com finaly reaches the quota limit - and even removing all emails does not help. My /etc/dovecot/dovecot-dict-quota.conf looks like this: map { pattern = priv/quota/storage table = quota username_field = username value_field = bytes } map { pattern = priv/quota/messages table = quota username_field = username value_field = messages } And my question is: what is used as "username"? Always the username given wher user logs in? Is there a way to provide some dictionary to translate all aliases to the real username? Best regards, -- Jacek Osiecki joshua(a)ceti.pl GG:3828944 I don't want something I need. I want something I want.

3 4

[Dovecot] Shared Namespace
by Tom Clark 22 Sep '11

22 Sep '11

Is there anyway of limiting a shared namespace to a domain? E.g. mailbox.com and mailbox2.com are setup with vpopmail. We've got a shared namespace but only want the ability on mailbox.com. Thanks, Tom

2 4

[Dovecot] Trouble getting lda to gzip incomming mails (zlib plugin)
by Helge Milde 22 Sep '11

22 Sep '11

Hi! I've followed the guide at http://wiki2.dovecot.org/Plugins/Zlib to try to make Dovecot gzip incomming mails, but it doesn't seem to work. I've made pop/imap read gzipped files, and this seems to work perfectly, but LDA is still saving incomming mails in plain text. There's not too much information out there regarding the zlib module, so I'm not sure where to start debugging the problem, and was hoping someone could point me in the right direction. The only mention of zlib when LDA is delivering a file: Sep 20 15:51:19 mail dovecot: deliver(helgemil): Module loaded: /usr/lib/dovecot/modules/lda/lib20_zlib_plugin.so The most relevant lines from dovecot.conf: mail_debug = yes protocols = imap pop3 imaps pop3s mail_location = maildir:~/Maildir mail_privileged_group = mail max_mail_processes = 1024 mail_process_size = 512 protocol imap { mail_max_userip_connections = 50 mail_plugins = fts fts_squat zlib } protocol pop3 { pop3_uidl_format = %08Xu%08Xv mail_max_userip_connections = 50 mail_plugins = zlib } protocol lda { postmaster_address = postmaster(a)monsternett.no mail_plugins = sieve zlib mail_plugin_dir = /usr/lib/dovecot/modules/lda sieve_global_dir = /etc/dovecot/sieve/ sieve_global_path = /etc/dovecot/sieve/default.sieve } plugin { zlib_save_level = 6 zlib_save = gz fts = squat sieve = ~/dovecot.sieve sieve_dir = ~/ } -- Helge Milde, 69701808 www.monsternett.no

3 5

[Dovecot] Create userdir on dovecot login
by Andreas Cieslak 22 Sep '11

22 Sep '11

Hi List, I am trying to set up automated userdir-creation on login via squirrelmail or email-client with a dovecot backend. The users are first imported on an openldap directory on the same server as the dovecot runs on. Authentication on the dovecot mail system via pam_ldap works properly. Tried already to integrate some advices from the dovecot wiki like Passdb { Driver = pam args = session=yes dovecot } But the homedir creation works only when the user logs onto the machine. When I try to log in via Squirrel on the dovecot no homedir is created and there is following message in the logs: auth: Error: pam(cieslak,193.175.157.121): pam_open_session() failed: Permission denied I think its something about the user rights, but dont really know where to search for the needle Here is the config of my environment root@server:/home# dovecot -n # 2.0.13: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686 i686 Debian 6.0.2 auth_debug = yes auth_mechanisms = login plain auth_verbose = yes first_valid_uid = 1000 hostname = server info_log_path = /var/log/dovecot-info last_valid_uid = 10000 listen = * log_path = /var/log/dovecot mail_access_groups = mail mail_debug = yes mail_full_filesystem_access = yes mail_location = maildir:~/Maildir mbox_write_locks = fcntl passdb { args = session=yes dovecot driver = pam } postmaster_address = mailaddress service auth-worker { group = shadow user = $default_internal_user } service auth { user = $default_internal_user } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 0 service_count = 0 vsz_limit = 256 M } service lmtp { unix_listener lmtp { mode = 0666 } } service pop3-login { inet_listener pop3s { port = 995 ssl = yes } } ssl_ca = </usr/local/etc/dovecot/ca ssl_cert = </usr/local/etc/dovecot/crt ssl_key = </usr/local/etc/dovecot/key userdb { driver = passwd } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } dovecot --version 2.0.13 The configuration of the pam module /etc/pam.d/dovecot looks like @include common-auth @include common-account @include common-session The common-session has the line session required pam_mkhomedir.so skel=/etc/skel umask=0077 I would appreciate any hints. Andreas

1 0

Re: [Dovecot] IMAP delete logs
by James isolder 22 Sep '11

22 Sep '11

Since enabling the mail_plugins = mail_log. I now get an error. Is there anything else I need to check adn how I can put the dovecot into debug mode so I can get more info about where it is failing. dovecot not running? (check /var/run/dovecot//master.pid). Starting dovecot. Error: imap dump-capability process returned 1 Fkevent(EV_ADD, 0) failed: Operation not supported by device Fatal: Invalid configuration in /usr/local/etc/dovecot.conf # 1.2.17: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.0-RELEASE i386 base_dir: /var/run/dovecot/ protocols: imap pop3 listen(default): *:1143 listen(imap): *:1143 listen(pop3): *:1110 ssl: no disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_log_format_elements: pid=%p rsock=%r:%b lsock=%l:%a proto=%s user=%u auth_method=%m secure=%c login_log_format: role=proxy realm=test %$: %s login_process_per_connection: no login_processes_count: 50 login_max_processes_count: 5120 login_max_connections: 512 max_mail_processes: 6144 mail_max_userip_connections(imap): 8 mail_max_userip_connections(pop3): 10 verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_privileged_group: mail mail_location: mbox:~/mail/:INBOX=/var/mail/%u mail_debug: yes maildir_copy_preserve_filename: yes mail_executable(default): /usr/local/libexec/dovecot/rawlog /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/rawlog /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/rawlog /usr/local/libexec/dovecot/pop3 mail_plugins(default): mail_log mail_plugins(imap): mail_log mail_plugins(pop3): mail_plugin_dir: /usr/local/lib/dovecot/pop3 mail_log_max_lines_per_sec: 0 pop3_enable_last(default): yes pop3_enable_last(imap): yes pop3_enable_last(pop3): no pop3_client_workarounds(default): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(imap): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(pop3): auth default: mechanisms: plain login cache_ttl: 0 cache_negative_ttl: 0 worker_max_count: 60 process_size: 512 passdb: driver: sql args: /usr/local/etc/dovecot-proxy.sql socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 plugin: mail_log_events: delete undelete expunge copy mailbox_delete mailbox_rename On Wed, 14 Sep 2011 14:40:21 +0200 "mailing(a)securitylabs.it" <mailing(a)securitylabs.it> wrote > Il 14/09/2011 07:48, James isolder ha scritto: > > Version - 1.2.17 > > > > Is there a way to include message or folder deletion logs in the dovecot > > log > > files. > > > > > > Yes, you can use the mail logger plugin: > > http://wiki.dovecot.org/Plugins/MailLog ____________________________________________________________ South Africas premier free email service - www.webmail.co.za For super low premiums, click here. http://www.dialdirect.co.za/?vdn=15828

2 1

[Dovecot] Create userdir on dovecot login
by Andreas Cieslak 22 Sep '11

22 Sep '11

Hi List, I am trying to set up automated userdir-creation on login via squirrelmail or email-client with a dovecot backend. The users are first imported on an openldap directory on the same server as the dovecot runs on. Authentication on the dovecot mail system via pam_ldap works properly. Tried already to integrate some advices from the dovecot wiki like Passdb { Driver = pam args = session=yes dovecot } But the homedir creation works only when the user logs onto the machine. When I try to log in via Squirrel on the dovecot no homedir is created and there is following message in the logs: auth: Error: pam(cieslak,193.175.157.121): pam_open_session() failed: Permission denied I think its something about the user rights, but dont really know where to search for the needle Here is the config of my environment root@server:/home# dovecot -n # 2.0.13: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-686 i686 Debian 6.0.2 auth_debug = yes auth_mechanisms = login plain auth_verbose = yes first_valid_uid = 1000 hostname = server info_log_path = /var/log/dovecot-info last_valid_uid = 10000 listen = * log_path = /var/log/dovecot mail_access_groups = mail mail_debug = yes mail_full_filesystem_access = yes mail_location = maildir:~/Maildir mbox_write_locks = fcntl passdb { args = session=yes dovecot driver = pam } postmaster_address = mailaddress service auth-worker { group = shadow user = $default_internal_user } service auth { user = $default_internal_user } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } process_min_avail = 0 service_count = 0 vsz_limit = 256 M } service lmtp { unix_listener lmtp { mode = 0666 } } service pop3-login { inet_listener pop3s { port = 995 ssl = yes } } ssl_ca = </usr/local/etc/dovecot/ca ssl_cert = </usr/local/etc/dovecot/crt ssl_key = </usr/local/etc/dovecot/key userdb { driver = passwd } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } dovecot --version 2.0.13 The configuration of the pam module /etc/pam.d/dovecot looks like @include common-auth @include common-account @include common-session The common session has the line session required pam_mkhomedir.so skel=/etc/skel umask=0077 I would appreciate any hints. Andreas

1 0