- dovecot - dovecot.org

[Dovecot] Director questions
by Mark Moseley 23 Jan '12

23 Jan '12

In playing with dovecot director, a couple of things came up, one related to the other: 1) Is there an effective maximum of directors that shouldn't be exceeded? That is, even if technically possible, that I shouldn't go over? Since we're 100% NFS, we've scaled servers horizontally quite a bit. At this point, we've got servers operating as MTAs, servers doing IMAP/POP directly, and servers separately doing IMAP/POP as webmail backends. Works just dandy for our existing setup. But to director-ize all of them, I'm looking at a director ring of maybe 75-85 servers, which is a bit unnerving, since I don't know if the ring will be able to keep up. Is there a scale where it'll bog down? 2) If it is too big, is there any way, that I might be missing, to use remote directors? It looks as if directors have to live locally on the same box as the proxy. For my MTAs, where they're not customer-facing, I'm much less worried about the latency it'd introduce. Likewise with my webmail servers, the extra latency would probably be trivial compared to the rest of the request--but then again, might not. But for direct IMAP, the latency likely be more noticeable. So ideally I'd be able to make my IMAP servers (well, the frontside of the proxy, that is) be the director pool, while leaving my MTAs to talk to the director remotely, and possibly my webmail servers remote too. Is that a remote possibility?

2 2

[Dovecot] LMTP ignoring tcpwrappers
by Harm Weites 23 Jan '12

23 Jan '12

Hello, we want to use dovecot LMTP for efficient mail delivery from our MX servers (running postfix 2.8) to our storage servers (dovecot 2.0.17). However, the one problem we see is the lack of access control when using LMTP. It apears that every client in our network who has access to the storage machines can drop a message in a Maildir of any user on that storage server. To prevent this behaviour it would be nice to use libwrap, just as it can be used for POP3/IMAP protocols. This, however, seems to be impossible using the configuration as mentioned on the dovecot wiki: login_access_sockets = tcpwrap service tcpwrap { unix_listener login/tcpwrap { group = $default_login_user mode = 0600 user = $default_login_user } } This seems to imply it only works for a login, and LMTP does not use that. The above works perfectly when trying to block access to IMAP or POP3 in /etc/hosts.deny, though a setting for LMTP is simply ignored. Is there a configuration setting needed for this to work for LMTP, or is it simply not possible (yet) and does libwrap support for LMTP requires a patch? Any help is appreciated. Regards, Harm

2 2

[Dovecot] Quota is not working (Debian Squeeze - Dovecot 1.2)
by RaSca 23 Jan '12

23 Jan '12

Hi all, I'm trying to make quota work in Squeeze (Dovecot 1.2.15-7). The quota module is correctly loaded and, when receiving a message, from the log I see these messages: Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): Loading modules from directory: /usr/lib/dovecot/modules/lda Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): Module loaded: /usr/lib/dovecot/modules/lda/lib10_quota_plugin.so Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): Module loaded: /usr/lib/dovecot/modules/lda/lib90_sieve_plugin.so Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): auth input: uid=5000 Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): auth input: gid=5000 Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): auth input: home=/mail/mailboxes/<mydomain>/testquota Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): Quota root: name=/mail/mailboxes/<mydomain>/testquota backend=maildir args= Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): maildir: data=/mail/mailboxes/<mydomain>/testquota@<mydomain> Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): maildir++: root=/mail/mailboxes/<mydomain>/testquota@<mydomain>, index=, control=, inbox=/mail/mailboxes/<mydomain>/testquota@<mydomain> Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): sieve: user's script path /mail/mailboxes/<mydomain>/testquota/.dovecot.sieve doesn't exist (using global script path in stead) Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): sieve: using sieve path for user's script: /mail/sieve/globalsieverc Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): sieve: opening script /mail/sieve/globalsieverc Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): sieve: executing compiled script /mail/sieve/globalsieverc Jan 16 11:20:04 mail-1 dovecot: deliver(testquota@<mydomain>): Namespace : Using permissions from /mail/mailboxes/<mydomain>/testquota@<mydomain>: mode=0700 gid=-1 Jan 16 11:20:05 mail-1 dovecot: deliver(testquota@<mydomain>): sieve: msgid=<4F13F996.4000501(a)seat.it>: stored mail into mailbox 'INBOX' Now, since I've got a message like this: Quota root: name=/mail/mailboxes/<mydomain>/testquota@<mydomain> backend=maildir args= it seems that something is checked, but even if this directory is over quota, nothing happens. This is my dovecot conf: protocols = imap pop3 disable_plaintext_auth = no log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/mail/mailboxes/%d/%n@%d mail_privileged_group = mail mail_debug = yes mail_nfs_storage = yes mmap_disable=yes fsync_disable=no mail_nfs_index = yes protocol imap { mail_plugins = quota imap_quota } protocol pop3 { pop3_uidl_format = %08Xu%08Xv mail_plugins = quota } protocol managesieve { } protocol lda { auth_socket_path = /var/run/dovecot/auth-master postmaster_address = postmaster@<mydomain> mail_plugins = sieve quota quota_full_tempfail = no log_path = } auth default { mechanisms = plain passdb sql { args = /etc/dovecot/dovecot-sql.conf } userdb passwd { } userdb static { args = uid=5000 gid=5000 home=/mail/mailboxes/%d/%n@%d allow_all_users=yes } user = root socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = vmail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } plugin { quota = maildir:/mail/mailboxes/%d/%n@%d sieve_global_path = /mail/sieve/globalsieverc } The db connection works, this is /etc/dovecot/dovecot-sql.conf: driver = mysql connect = host=<myserver> dbname=mail user=<myuser> password=<mypassword> default_pass_scheme = CRYPT password_query = SELECT username, password FROM mailbox WHERE username='%u' user_query = SELECT username AS user, maildir AS home, CONCAT('*:storage=', quota , 'B') AS quota_rule FROM mailbox WHERE username = '%u' AND active = '1' and for the user testquota the user_query results in this: +-------------------+----------------------------+--------------------+ | user | home | quota_rule | +-------------------+----------------------------+--------------------+ | testquota@<mydom> | <mydom>/testquota@<mydom>/ | *:storage=1024000B | +-------------------+----------------------------+--------------------+ everything else is ok, for example I'm using sieve for the spam filter, and the SPAM is correctly put in the .SPAM dir. I turned on debug on dovecot, but I can't see if the query in some way fails. Can you please help me to understand what am I doing wrong? -- RaSca Mia Mamma Usa Linux: Niente è impossibile da capire, se lo spieghi bene! rasca(a)miamammausalinux.org http://www.miamammausalinux.org

3 4

Re: [Dovecot] change smtp port
by Giles Coochey 23 Jan '12

23 Jan '12

On 2012-01-23 14:38, Amira Othman wrote: > And there is no way to receive incoming emails not on port 25 ? > > No. http://en.wikipedia.org/wiki/Simple_Mail_Transfer_Protocol

2 2

Re: [Dovecot] change smtp port
by Ralf Hildebrandt 23 Jan '12

23 Jan '12

* Amira Othman <a.othman(a)cairosource.com>: > Hi all > > I am using postfix 2.8 with dovecot-1.2.17-0_116.el5 on cento 5.7 server . > when I changed smtp port from 25 to 587 from postfix configuration my mail > server stops to receive emails. That's normal. > I think it sounds strange and I don't understand why this happen any > one can help me Mail from other systems comes in via port 25. Once you change the port, nobody can send mail to your server. Easy, no? -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

2 1

Re: [Dovecot] change smtp port
by Giles Coochey 23 Jan '12

23 Jan '12

On 2012-01-23 14:30, Amira Othman wrote: > Hi all > > I am using postfix 2.8 with dovecot-1.2.17-0_116.el5 on cento 5.7 > server . > when I changed smtp port from 25 to 587 from postfix configuration my > mail > server stops to receive emails. I think it sounds strange and I don't > understand why this happen any one can help me > > > > Regards If this SMTP server is your MX record, then you need to use port 25. Only use the 587 port for authenticated submissions from your own users for outgoing email. -- Message sent via my webmail account.

1 0

[Dovecot] change smtp port
by Amira Othman 23 Jan '12

23 Jan '12

Hi all I am using postfix 2.8 with dovecot-1.2.17-0_116.el5 on cento 5.7 server . when I changed smtp port from 25 to 587 from postfix configuration my mail server stops to receive emails. I think it sounds strange and I don't understand why this happen any one can help me Regards

1 0

[Dovecot] Sieve tempoary script folder
by Markus Fritz 21 Jan '12

21 Jan '12

Hello, I got the issue that sieve wants to write his tmp files to /etc/dovecot/. But I want sieve to write in a folder which it has write rights. I created a script to to put spam in the 'Spam' folder, put it in /etc/dovecot/.dovecot.sieve. When recieving a mail sieve want's to create a tmp file like /etc/dovecot/.dovecot.sieve.12033 How to change the desired tmp folder by sieve?

1 0

[Dovecot] 2.1.rc3 (1a722c7676bb): doveadm mailbox list withholds child mailboxes
by Pascal Volk 21 Jan '12

21 Jan '12

Probably I've overlooked something. But a quick search in `hg log -k doveadm` didn't show appropriate information. doveadm mailbox list -u user(a)example.com doesn't show child mailboxes. mailbox = N/A || \*: Sent Trash INBOX Drafts Junk-E-Mail Supplier mailbox = Supplier*: Supplier mailbox = Supplier/*: Supplier/Dell Supplier/VMware Supplier/… The same problem exists in `doveadm mailbox status` Regards, Pascal -- The trapper recommends today: defaced.1201301(a)localdomain.org

1 1

Re: [Dovecot] mail_max_userip_connections exceeded.
by Joseph Tam 21 Jan '12

21 Jan '12

Simon Brereton <simon.brereton(a)buongiorno.com> writes: > /var/log/mail.log.1:2490:Jan 19 12:02:55 mail dovecot: imap-login: > Maximum number of connections from user+IP exceeded > (mail_max_userip_connections): user=<user(a)example.com>, method=PLAIN, > rip=127.0.0.1, secured > > I never changed this from the default 10. When I googled this error > there was a thread on this list from May 2011 that indicated one would > need one connection per user per subscribed folder. However, I know > that user doesn't have 10 folders, let alone 10 subscribed folders! I > can increase, it but it's not going to scale well. And there are > people on this list with many 1000x users than I have - so how do they > deal with that? > > 127.0.0.1 is obviously webmail (IMP5). IMAP proxy or lack of proxy? IMAP proxy could be a problem if the user had opened more than 10 (unique) mailboxes. The proxy would keep this connection open until a timeout, and after some time, could accumulate more connections than your limit. The lack of proxy could solve your problem if for some reason your webmail software is not closing the IMAP connection properly (I assume IMP does a connect/authenticate/IMAP command/logout for every webmail operation). Every connection (even to the same mailbox) would open up a new connection. The proxy software will recognize the reconnnection and funnel it through its cached connection. You can lsof the user's IMAP processes (or troll through /proc/{imap-process} or what you have) to figure out which mailboxes it has opened. On my system, file descriptor 9 and 11 gives you the names of the index files that indicate which mailboxes are being accessed. Joseph Tam <jtam.home(a)gmail.com>

2 1