- dovecot - dovecot.org

[Dovecot] Proxy and Master Config
by Regan Yelcich 10 Sep '13

10 Sep '13

I'm just sitting down to configure a Proxy & Master Dovecot setup with Postfix and virtual users. I have read plenty about how to configure Dovecot as a proxy, but I'm unclear what's required on the "master" end. Does the master need the -pop and -imap scripts? or does the proxy handle that and call -deliver on the master? Can anyone explain the basic setup so I get it right. Thanks.

1 0

Re: [Dovecot] Is dovecot locking properly?
by Joseph Tam 10 Sep '13

10 Sep '13

Scott Galambos writes: > Hello, I'm attempting to move form qpopper 4.1 to Dovecot 2.2.5 on > Linux. When a user checks POP mail qpopper seems to make a > .username.pop temporary file in the same /var/mail directory as the mbox > INBOX file. Watching what dovecot does I don't see this happening. Probably too quick (or perhaps you haven't configured dotlocking). Qpopper locks the INBOX when it creates a drop copy: this can be a time consuming operation, during which you can see the .$user.pop lock file. Dovecot is more intelligent: it doesn't create copies, and goes out of its way to avoid grautitous I/O. Most of the operations can be done by consulting the indices. However, I did contrive a situation to observe lock files being created. 1) Create large INBOX file test user (assuming mbox /inbox/testuser) 2a) In one window, run a shell loop monitor while : ; do ls -al /inbox/testuser.lock done 2b) In another window, create a POP3 session and do an operation that would require a lock: telnet pop-server 110 USER testuser PASS testpassword DELE 1 ... this still won't need locking -- not until ... QUIT If you use maildir format, it may still be too quick to catch. in this situation, you can process trace the pop3 worker process to verify a lock file is created. > Is this .pop file a lock file or just a temporary file? Temporary. If you have them lying around, qpopper crashed. Note: dovecot makes lockfiles of the form "$user.lock". > If its a temp file does dovecot do the same thing elsewhere? I'm > concerned dovecot is not locking properly and there will be mailbox > corruption, so I'm trying to get dovecot to mimic what qpopper does as > much as possible. By "mimic" you mean that locking works, but otherwise, you don't want dovecot to mimic qpopper: the former is much better. I have not had problems with users complaining about scrambled files. As I said, process trace your pop3 worker process if you need to verify the locking process. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] sieve vacation question
by Andreas Schulze 09 Sep '13

09 Sep '13

Hello Stephan, I love to use the vacation extension to build an echo service. I have not to worry about whether to answer or not if the sender is a list, postmaster, mailer-daemon or other crasy thing. But i like to echo the *complete headers* back. I did not found a solution with sieve yet. Is it really impossible? Thanks Andreas

2 2

[Dovecot] Is this odd?
by LuKreme 09 Sep '13

09 Sep '13

$ doveadm user kremels field value uid 1033 gid 1033 home /home/kremels mail maildir:~/Maildir system_groups_user kreme $ doveadm user user(a)virtual.example.com field value uid 89 gid 89 home /usr/local/virtual/user(a)virtual.example.com/ mail /usr/local/virtual/user(a)virtual.example.com mail_location /usr/local/virtual/user(a)virtual.example.com The local users doesn't have a mail_location set at all, and has a very different mail definition. This seem to be a side-effect of the fact that the home of the virtual user is the top level maildir, but should I set mail to maildir:~ ?? -- Where there is a party, everyone is there Everyone will leave at exactly the same time When this party is over it will start again But not been any different be exactly the same

2 2

[Dovecot] Is dovecot locking properly?
by Scott Galambos 09 Sep '13

09 Sep '13

Hello, I'm attempting to move form qpopper 4.1 to Dovecot 2.2.5 on Linux. When a user checks POP mail qpopper seems to make a .username.pop temporary file in the same /var/mail directory as the mbox INBOX file. Watching what dovecot does I don't see this happening. Is this .pop file a lock file or just a temporary file? If its a temp file does dovecot do the same thing elsewhere? I'm concerned dovecot is not locking properly and there will be mailbox corruption, so I'm trying to get dovecot to mimic what qpopper does as much as possible. I'm using procmail and its Locking strategies are: dotlocking, fcntl(), lockf(), flock(). I'm using sendmail too. I left dovecot's locking as the defaults. Thanks for any tips.

1 0

Re: [Dovecot] More fine-grained connection limitations?
by Joseph Tam 09 Sep '13

09 Sep '13

> There is the mail_max_userip_connections setting, which helps for > dealing with number of connections at any given time, but I'm looking > for something that will help deal with users who configure their mail > clients to connect too frequently. > > ... > > It would be really great if there were a way to tarpit those users to > slow them down, or send them an imap message saying they are connecting > to often and connections have been disabled for the next 5 minutes or > something. There might be an unintended consequence: I see connection spikes when users try to do a global string search across mailboxes. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] best practice to have sent mail folder on dovecot imap server
by Thomas Koch 08 Sep '13

08 Sep '13

I've already asked this here: http://serverfault.com/questions/533940/best-practice-to-have-sent-mail- folder-on-dovecot-imap-server Hi, when I add a mail account to KMail (or most other MUA I suppose) the sent mail folder is on the local machine and I don't have my sent mails on other machines. I'd like to have a sent mail folder in IMAP and I thought that there would already exist a standard or best practice how to set this up so that the mail is only transfered once to the MTA and from the MTA to the IMAP server. I even thought to remember an RFC related to this problem? It isn't that simple, is it? I'm using Exim. Regards, Thomas Koch

3 2

[Dovecot] More fine-grained connection limitations?
by Micah Anderson 07 Sep '13

07 Sep '13

There is the mail_max_userip_connections setting, which helps for dealing with number of connections at any given time, but I'm looking for something that will help deal with users who configure their mail clients to connect too frequently. For example, I've seen users who configured their clients to check (IMAP) mail every 3 seconds. This is far too frequent and puts unnecessary load on the server. Even once per minute seems excessive to me. It would be really great if there were a way to tarpit those users to slow them down, or send them an imap message saying they are connecting to often and connections have been disabled for the next 5 minutes or something. Micah ps - what happens to a user when they hit mail_mx_userip_connections? Further connections are just denied, or dropped?

1 0

[Dovecot] Plus addressing
by LuKreme 07 Sep '13

07 Sep '13

It appease that I can enable +address filtering into separate mailboxes by simply setting $recipient_delimiter = '+'; However, is there anyway to get great control over that? For example, on one account I have a lot of +addresses I use. A few, I sort into mailboxes (like my bank, credit cards, etc). The rest are either on the “spammer => /dev/null” list or get sorted into a mailbox named “Misc” (like various newsletters and offers and sales from companies I do business with). -- Sigs are b0rk3d.

6 6

[Dovecot] Dovecot 2.1.7 not starting properly, mail not delivered
by Aldo & Caroline 07 Sep '13

07 Sep '13

On my debian box dovecot does not start properly any more, and mails don't get delivered or sent. I've googled around without finding any useful leads. Hopefully someone is willing to educate me. My guess is it must be a config problem after an upgrade, since I didn't change anything myself directly. Not sure when it started, since I this mail server is not our default machine (yet). Symptoms Upon /etc/init.d/dovecot restart my command line says [ ok ] Restarting IMAP/POP3 mail server: dovecot. But I find in /var/log/mail.log: Sep 6 11:17:36 debian2 dovecot: master: Warning: Killed with signal 15 (by pid=19112 uid=0 code=kill) Sep 6 11:17:36 debian2 dovecot: master: Dovecot v2.1.7 starting up (core dumps disabled) Sep 6 11:17:37 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:38 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:39 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:40 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:41 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:42 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:43 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:44 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:45 debian2 postfix/cleanup[18466]: warning: connect to TCP map 127.0.0.1:10001: Connection refused Sep 6 11:17:45 debian2 postfix/cleanup[18466]: warning: tcp:127.0.0.1:10001 lookup error for "aldo(a)alcatoka.nl" Sep 6 11:17:45 debian2 postfix/cleanup[18466]: warning: 57B7D3640073: sender_canonical_maps map lookup problem for aldo(a)alcatoka.nl Sep 6 11:17:45 debian2 postfix/pickup[17004]: warning: maildrop/4EA313640071: error writing 57B7D3640073: queue file write error I do NOT see a line like ... dovecot: auth-worker(default): pgsql: Connected to 127.0.0.1 (mailserver) as mentioned in this <https://workaround.org/ispmail/squeeze/setting-up-dovecot?page=1> tutorial, which I used to set up the previous Dovecot version (which worked OK). When starting Dovecot from the command line with dovecot -F -c /etc/dovecot/dovecot.conf nothing is printed (as if the process is waiting for more input), while it should at least produce some output, right? I'm running Debian 7.1 with an ext3 filesystem together with Postfix 2.9.6 on an x86 machine. CPU info: processor : 0 vendor_id : AuthenticAMD cpu family : 16 model : 6 model name : AMD Sempron(tm) 140 Processor cpu MHz : 800.000 cache size : 1024 KB As far as I can tell, Postfix is running OK. /etc/dovecot/dovecot.conf says: # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-686-pae i686 Debian 7.1 ext3 auth_mechanisms = plain login disable_plaintext_auth = no log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/var/vmail/%d/%n/Maildir mail_privileged_group = mail passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = imap pop3 service auth { unix_listener auth-master { group = vmail mode = 0600 user = vmail } user = root } ssl_cert = </etc/dovecot/dovecot.pem ssl_key = </etc/dovecot/private/dovecot.pem userdb { args = uid=3000 gid=3000 home=/var/vmail/%d/%n allow_all_users=yes driver = static } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } protocol lda { auth_socket_path = /var/run/dovecot/auth-master log_path = mail_plugins = sieve postmaster_address = aldo(a)alcatoka.nl As far as I understand, there must be a process (dovecot-auth?) that takes care of translating mail adresses, taking a string at port 10001 and returning the translated string on 10002. This process does not seem to kick off when dovecot restarts. Please tell me if I'm thinking in the right direction, and - more importantly - what I need to do to get dovecot running. I will be happy to provide more test results if that helps, just tell me what you need. Regards, Aldo Verlinde

1 1