- dovecot - dovecot.org

[Dovecot] Dovecote Warnings
by anarchos78 14 Dec '12

14 Dec '12

Greetings, I have setup Postfix/Dovecote on Ubuntu 12.04 (apt-get install mail-stack-delivery). While everything is working fine in the mail server I have niticed the following errors: srv dovecot: config: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf: 2 Time(s) srv dovecot: config: Warning: Obsolete setting in /etc/dovecot/conf.d/01-mail-stack-delivery.conf:13: listen=..:port has been replaced by service { inet_listener { port } }: 2 Time(s) srv dovecot: config: Warning: Obsolete setting in /etc/dovecot/conf.d/01-mail-stack-delivery.conf:13: protocol { listen } has been replaced by service { inet_listener { address } }: 2 Time(s) srv dovecot: config: Warning: Obsolete setting in /etc/dovecot/conf.d/01-mail-stack-delivery.conf:14: protocol { ssl_listen } has been replaced by service { inet_listener { address } }: 2 Time(s) srv dovecot: config: Warning: Obsolete setting in /etc/dovecot/conf.d/01-mail-stack-delivery.conf:14: ssl_listen=..:port has been replaced by service { inet_listener { port } }: 2 Time(s) srv dovecot: config: Warning: Obsolete setting in /etc/dovecot/conf.d/01-mail-stack-delivery.conf:21: listen=..:port has been replaced by service { inet_listener { port } }: 2 Time(s) srv dovecot: config: Warning: Obsolete setting in /etc/dovecot/conf.d/01-mail-stack-delivery.conf:21: protocol { listen } has been replaced by service { inet_listener { address } }: 2 Time(s) srv dovecot: config: Warning: Obsolete setting in /etc/dovecot/conf.d/01-mail-stack-delivery.conf:22: protocol { ssl_listen } has been replaced by service { inet_listener { address } }: 2 Time(s) *The "01-mail-stack-delivery.conf" file looks like this:* # Some general options protocols = imap pop3 sieve disable_plaintext_auth = yes ssl = yes ssl_cert = </etc/ssl/certs/ssl-mail.pem ssl_key = </etc/ssl/private/ssl-mail.key ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM mail_location = maildir:~/Maildir auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # IMAP configuration protocol imap { listen = *:143 ssl_listen = *:993 mail_max_userip_connections = 10 imap_client_workarounds = delay-newmail } # POP3 configuration protocol pop3 { listen = *:110 ssl_listen = *:995 mail_max_userip_connections = 10 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } # LDA configuration protocol lda { postmaster_address = postmaster mail_plugins = sieve quota_full_tempfail = yes deliver_log_format = msgid=%m: %$ rejection_reason = Your message to <%t> was automatically rejected:%n%r } # Plugins configuration plugin { sieve=~/.dovecot.sieve sieve_dir=~/sieve } # Authentication configuration auth_mechanisms = plain login service auth { # Postfix smtp-auth unix_listener /var/spool/postfix/private/dovecot-auth { mode = 0660 user = postfix group = postfix } } What is going wrong with Dovecote. I am a newcomer and i need little help. Many thanks, Tom Greece -- View this message in context: http://dovecot.2317879.n4.nabble.com/Dovecote-Warnings-tp39221.html Sent from the Dovecot mailing list archive at Nabble.com.

2 3

[Dovecot] More detail re dovecot-uidlist and -uidvalidity files
by Dale Gallagher 13 Dec '12

13 Dec '12

Regarding the dovecot-uidlist header (first line) - I've tried to search for and figure out what exactly is meant by the "mailbox global uid" and once I do, how to manually generate the 128 bit hex variation of it? Could someone elaborate on this, please. How would omitting the global uid field, beginning with G, affect remote clients' syncing of mail? Is this field mandatory? Would "3 V$uid_validity N$next_uid" be sufficient to ensure that clients don't re-download everything? I also see that Dovecot's dovecot-uidvalidity is of the form 4df8a4e2, whereas the IMAP syncing utility which I'm using (isync) uses an integer. I'd appreciate it if someone could elaborate on what Dovecot uses and whether I need to convert one to the other (ie. after syncing with isync, do I need to convert it to work with Dovecot? Thanks.

2 1

Re: [Dovecot] number of imap connection
by Joseph Tam 13 Dec '12

13 Dec '12

<klimenko.n(a)theitidea.ru> writes: > how to calculate the expected number of imap processes? Set your mail_max_userip_connections to a large value (~20) and run "doveadm who" periodically to look at your user's actual connection counts. > how many imap processes must be used for each user? > i have 6-7 connection for each one user > is it normal behavior? It's typical. Some popular mail readers open about 5, some more, some less. I set my mail_max_userip_connections at 12 even though there are some users who regularly bump up against this. They don't seem to notice -- dovecot probably bumps off the least recently used connection and their mail reader reconnects if it needs to open that mailbox again. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] number of imap connection
by Николай Клименко 13 Dec '12

13 Dec '12

Hi to all. how to calculate the expected number of imap processes? how many imap processes must be used for each user? i have 6-7 connection for each one user is it normal behavior? thx.

3 2

[Dovecot] rare ssl issue
by Eduardo Casarero 12 Dec '12

12 Dec '12

I'am having a rare situation with ssl connections. I can connect to 993/995 but the connection never starts. >From the client side i test with: $ openssl s_client -connect example.com:993 CONNECTED(00000003) and stays like that... waiting. In the other side i see in dovecot logs: Disconnected: Inactivity (no auth attempts): rip=x.x.x.x, lip=x.x.x.x, TLS handshaking this happens from some networks only, so i think that mi isp (where the server is hosted) is doing some kind of shaping. But if i try to connect to port 465 for example, or 443 it works like a charm. i am talking to my isp, but i thougth that someone may have a hint or any comment that could help. regards, eduardo.

1 0

[Dovecot] [vnd.dovecot.pipe] - timeout settings
by kjonca＠o2.pl 12 Dec '12

12 Dec '12

In install file we can read that: sieve_<extension>_exec_timeout = 10s set timeout for executing program. But regardless of setting this value (say sieve_pipe_exec_timeout=86000) I got: --8<---------------cut here---------------start------------->8--- 2012-12-10 20:55:33 LDA(kjonca): Debug: sieve: action pipe: running program: maildrop.sh 2012-12-10 20:55:43 LDA(kjonca): Debug: program `/home/kjonca/sieve/bin/maildrop.sh' execution timed out: sending TERM signal --8<---------------cut here---------------end--------------->8--- What am I doing wrong? KJ -- http://modnebzdury.wordpress.com/2009/10/01/niewiarygodny-list-prof-majewsk… When does summertime come to Minnesota, you ask? Well, last year, I think it was a Tuesday.

2 1

[Dovecot] dovcot+offlineimap+gmail: INBOX empty, mail doubled
by Uwe Brauer 11 Dec '12

11 Dec '12

Hello I have used for years offlineimap-6.2.0 dovecot-imapd 1:1.2.9 in Kubuntu 10.04 Together with a imap server of my university. Yesterday we switched to google, which I know, is not a real imap server. I have 2 problems and the first I think has to do with either an old version of offlineimap or a bad configuration file: - All folders are downloaded+ Gmail[All Mail] so doubling my mail. - My INBOX folder is empty, however this is the only folder for which offlinemap gives the following warning: Syncing INBOX: Gmail -> MappedIMAP WARNING: UID validity problem for folder INBOX (repo UniLocal) (saved 1309334376; got 1355232397); skipping it So maybe this is also a offlineimap fault. In any case I have googled around and found out that I am not the only person suffering this problem. I have attached my configuration file in the hope that may be somebody could give me a hint. Thanks in advance Uwe Brauer --8<------------------------schnipp------------------------->8--- [general] accounts = Uni ui = Noninteractive.Basic maxsyncaccounts = 1 [Account Uni] localrepository = UniLocal remoterepository = UniRemote [Repository UniLocal] type = IMAP ssl = no remotehost = localhost remoteuser = myuser remotepass = mypasswd maxconnections = 2 [Repository UniRemote] type = Gmail # ssl =no ssl =yes #remotehost = ucimap.ucm.es remotehost = imap.gmail.com remoteuser = myuser remotepass = mypasswd # nametrans = lambda foldername: re.sub ('^\[gmail\]', 'bak', # re.sub ('sent_mail', 'sent', # re.sub ('starred', 'flagged', # re.sub (' ', '_', foldername.lower())))) folderfilter = lambda foldername: foldername in ['INBOX'] idlefolders = ['INBOX'] folderfilter = lambda foldername: foldername not in '[Gmail]/All Mail' sslcacertfile = /etc/ssl/certs/ca-certificates.crt maxconnections = 1 realdelete = yes # Don't sync shared folders # folderfilter = lambda foldername: not re.search('Shared Folders', foldername) # automatic stuff maxsyncaccounts = 1 quick = 10 autorefresh = 5 keepalive = 60 holdconnectionopen = yes # This will suppress anything but errors ui = quiet --8<------------------------schnapp------------------------->8--- --8<------------------------schnipp------------------------->8--- version_ignore=yes first_valid_uid = 1 log_path = /var/log/dovecot.log ssl_cert_file = /etc/ssl/certs/dovecot.pem ssl_key_file = /etc/ssl/private/dovecot.pem # mail_location = maildir:/var/spool/mail/%u # not sure about the following mail_location = maildir:/var/spool/mail/%u:INBOX=/var/spool/mail/%u maildir_copy_with_hardlinks = yes protocol imap { listen = 127.0.0.1:143 ssl_listen = 127.0.0.1:943 } auth default { mechanisms = plain # defines users/passwords passdb passwd-file { args = /etc/dovecot/passwd } userdb static { args = uid=mail gid=mail home=/var/spool/mail/%u } } --8<------------------------schnapp------------------------->8---

1 0

Re: [Dovecot] Automatically Cleaning Kerberos Credential Cache Files
by Maura Dailey 11 Dec '12

11 Dec '12

On 12/10/2012 05:31 PM, Ben Morrow wrote: > At 3PM -0500 on 10/12/12 you (Maura Dailey) wrote: >> I'm in a situation here at work where I'm trying to support a mixed >> network of OS X and RHEL desktop machines with a Postfix/Dovecot >> combination. >> - user account information is stored in LDAP >> - user credentials are in MIT Kerberos >> - server is running RHEL 6/Dovecot 2.0.9/Postfix 2.6.6 >> >> I am currently using the PAM passdb module to authenticate my users (I >> began to have trouble with using GSSAPI directly). After I implemented >> it, a few weeks later, I noticed that some users were no longer getting >> their mail if they hadn't logged in during the past day. Postfix's mailq >> showed that hundreds of messages were backing up in the queue. I >> eventually tracked it down to leftover Kerberos credential cache files >> (/tmp/krb5cc_????) sitting in /tmp on the mail server. The presence of >> expired credential files was preventing Postfix from delivering mail to >> those users' mail spools. If I delete the credential files manually, >> Postfix immediately delivers the queued emails. > This is rather odd. Is krb5-authenticated NFS involved here, or does > Postfix's delivery make any other use of Kerberos? The only other thing > I can think of is that so many expired ccaches are accumulating that the > user goes over their inode quota. Each user has one credential cache file in /tmp on the mail server after logging into Dovecot. We aren't using randomized names, so everything is in the standard format /tmp/krb5cc_uid. We do use KRB5 authenticated (and encrypted) NFS, but we don't deliver mail to home directories. Since all users are "real" users, and our office size is small, everyone has a mail spool directory on the mail server. Postfix is configured to use Dovecot for Kerberos. The relevant lines in its /etc/postfix/main.cf are as follows: smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_auth_enable = yes smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_client_restrictions = permit_mynetworks, permit_sasl_authenticated, reject smtpd_sasl_security_options = noanonymous >> Currently, I have a cron job deleting the files manually every night. >> Obviously, this is a cruddy solution. > Well, I don't know about that: obviously, it would be a good idea to > work out what's going on here, in case it causes anything else to go > wrong, but a cronjob clearing out /tmp is a good idea in any case. Fair enough. And of course, I get a cache file every time I use sudo or log in through a GUI. Those aren't cleaned up either! Maybe I should be deleting credential cache files on all the machines every night. Those cache files have never given me a problem, though. >> I have Dovecot configured on a >> RHEL 6 box. The Pam stack on a RHEL 6 machine uses sssd (pam_sss.so) for >> authentication with Kerberos, not pam_krb5.so. I'm trying to track down >> which piece of the puzzle is responsible for cleaning up leftover >> credential caches. Is there a configuration option I can pass to >> Dovecot's passdb directly to clean up these cache files? > There are two relevant Dovecot settings: passing setcred=yes to the pam > passdb will make Dovecot call pam_setcred, and passing session=yes will > make it open and immediately close a PAM session. (Probably it ought to > wait until the IMAP user logs out to close the session, but currently it > can't do that because of the way the passdb lookups are done.) Changing > either of these may have an effect, depending on when exactly your PAM > module creates and destroys ccaches. I've tried session=yes by itself, but I don't think I've tried it with setcred=yes. I'll throw it in there and give it a try after I send this email. >> Do others >> generally have more success using a custom PAM stack with pam_krb5.so >> instead of pam_sss.so? > Well, I don't use RH (I use FreeBSD), but I use and would recommend Russ > Allbery's pam_krb5.so, which may or may not be the same as the normal > pam_krb5.so provided by your system. It has options to control whether > and where ccaches are created; assuming Dovecot doesn't need krb5 creds > (say, for NFS), you would probably be better off telling it not to > create a permanent ccache at all. > > http://www.eyrie.org/~eagle/software/pam-krb5/ I haven't had to configure pam_krb5.so directly before (we use the Red Hat/Fedora configured default, pam_sss.so, which claims to be a one stop shop for LDAP/Kerberos/NIS,etc.), but it does seem to have more options. We certainly don't need credential caches to stick around for email users. All the mail spools are stored on locally mounted storage on the mail server. >> Poring over sssd's configuration options didn't >> reveal anything useful. I'm still not sure why Postfix even cares if >> there are expired credential cache files in /tmp at all. >> >> I'm back to trying GSSAPI directly again as well in the meantime on a >> few test clients. When I used that in the past, users were getting >> issued duplicate Kerberos tickets and users were forced to log into the >> mail server directly using SSH after a day in order to get their mail to >> work (seemingly a related issue). If I get those same errors again, I'll >> start another thread. > This certainly does all sound related. What are the ccache files called: > are they just /tmp/krb5cc_UID or is there a random portion as well? Are > they being created with the correct permissions, and are there any > security policies (SELinux or ACLs of some kind) set up which might > interfere with their creation or destruction? No random portion (the only application we have configured with random ccache names is SSH), just the usual /tmp/krb5cc_uid. Permissions appear correct, they belong to the appropriate user and group accounts. The SELinux permissions are set to: system_u:object_r:user_tmp_t:s0. This is different from the machine's credential cache (system_u:object_r:gssd_tmp_t:s0), but I've disabled and re-enabled SELinux during different parts of my testing and didn't notice any errors. Using GSSAPI directly doesn't create any cached credential files on the server. However, I just verified that I'm still sporadically getting the duplicate tickets (two lines for imap/hostname.server.com(a)SERVER.COM, with identical expiration dates). It comes and goes. I have a few users testing it for me, and they'll let me know if their logins break tomorrow like they have in the past once the normal log in period elapses. Since the "fix" for that problem is to log into the mail server, I have a hard time testing for the problem myself (being logged into the mail server nearly continuously just now). > What happens if you log in as an ordinary user (preferably using the > same PAM stack as Dovecot uses), use klist to find the ccache name and > 'ls -i' to find its inode number, then manually kinit again? Does the > kinit succeed, and does the new ccache have a different inode number > from before? Does the ccache file get removed when you log out? I've noticed that the ccache files for regular users do not get deleted when they log out. On another user's workstation, I found a ccache file for my account from a week ago (my current session was using a randomly generated SSH ccache file). I ran a command with sudo to force it to reauthenticate with pam_sss, and the timestamp on the ccache file was updated and the inode changed. My best guess is that pam_sss.so just doesn't do ccache cleanup. > Ben > Thanks for taking a look, I appreciate all the suggestions. This problem's been driving me up a wall for weeks now. I only just managed to narrow down the cause in the last few days. If I can't get a fix working in Dovecot, I'll try tackling it from a different perspective. I understand why Dovecot might not be cleaning up credential files (especially if it's just calling PAM normally), but I definitely do not understand why Postfix is behaving the way it does. If I can just get GSSAPI to work, I could probably bypass the problem as well. - Maura Dailey maura(a)eclipse.ncsc.mil

2 2

[Dovecot] Switch from MySQL/CourierMail to MySQL/Dovecot
by Robert Moskowitz 11 Dec '12

11 Dec '12

Hello, new here. I am a Centos/Fedora user, and for the past 3 years have been running my mail server using Postfix/MySQL/CourierMail/Squirrelmail on Fedora. The current incantation of the tutorial is at: http://www.howtoforge.com/virtual-users-and-domains-with-postfix-courier-my… Well it is time to rebuild my mailserver; this time on Centos 6.3. My goal is to use supplied rpms, not to build my own (and rebuild everytime there is an important update). So I am pulling quotas which has been a pain anyway, and I am investigating using Dovecot in place of CourierMail. In Centos 6.3, the version of Dovecot is: 2.0.9-2 I am looking for a tutorial to assist in the setup, as I am nowhere an expert on any of this (I am a communications security expert in the IETF and IEEE 802). There are a couple items that I have come to depend on in my current setup that are musts in anything new: Virtual user/domain That is, not only virtual domains, but also users defined by domain. So in the MySQL user table, the email value is set to user@domain. Thus a user can receive/send mail from multiple domains with the same addr and only those domains defined for the user in the user table. Obviously there is no coupling of Linux user accounts and email accounts. CourierMail is storing mail under /home/vmail/domain/user/... Encrypted passwords The passwords in the user table in MySQL are encrypted. This will be used to auth the user for POPing or IMAPing and sending their mail. I have encountered a few tutorials where it seems like passwords are stored in the clear? Anyway, not much else! Well as far as the user interface is concerned. Postfix with clamav and spamassassin and maybe one or two extras. And SquirrelMail for Webmail. A better gui than phpMyAdmin for maintaining the tables would be nice, but I don't have a lot of users, so it works well enough. Can someone point me to a tutorial best suited to my needs? Also any firewall rules, as I don't want to turn off iptables (and ip6tables) and any SELinux policy rules to add. Oh, and IPv6 will be a must in the near future, so anything needed to ensure IPv6 working right as well. Thanks

2 3

[Dovecot] Automatically Cleaning Kerberos Credential Cache Files
by Maura Dailey 11 Dec '12

11 Dec '12

I'm in a situation here at work where I'm trying to support a mixed network of OS X and RHEL desktop machines with a Postfix/Dovecot combination. - user account information is stored in LDAP - user credentials are in MIT Kerberos - server is running RHEL 6/Dovecot 2.0.9/Postfix 2.6.6 I am currently using the PAM passdb module to authenticate my users (I began to have trouble with using GSSAPI directly). After I implemented it, a few weeks later, I noticed that some users were no longer getting their mail if they hadn't logged in during the past day. Postfix's mailq showed that hundreds of messages were backing up in the queue. I eventually tracked it down to leftover Kerberos credential cache files (/tmp/krb5cc_????) sitting in /tmp on the mail server. The presence of expired credential files was preventing Postfix from delivering mail to those users' mail spools. If I delete the credential files manually, Postfix immediately delivers the queued emails. Currently, I have a cron job deleting the files manually every night. Obviously, this is a cruddy solution. I have Dovecot configured on a RHEL 6 box. The Pam stack on a RHEL 6 machine uses sssd (pam_sss.so) for authentication with Kerberos, not pam_krb5.so. I'm trying to track down which piece of the puzzle is responsible for cleaning up leftover credential caches. Is there a configuration option I can pass to Dovecot's passdb directly to clean up these cache files? Do others generally have more success using a custom PAM stack with pam_krb5.so instead of pam_sss.so? Poring over sssd's configuration options didn't reveal anything useful. I'm still not sure why Postfix even cares if there are expired credential cache files in /tmp at all. I'm back to trying GSSAPI directly again as well in the meantime on a few test clients. When I used that in the past, users were getting issued duplicate Kerberos tickets and users were forced to log into the mail server directly using SSH after a day in order to get their mail to work (seemingly a related issue). If I get those same errors again, I'll start another thread. The output of doveconf -N: # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-279.14.1.el6.x86_64 x86_64 Red Hat Enterprise Linux Server release 6.3 (Santiago) ext4 auth_cache_size = 10 k auth_cache_ttl = 5 hours auth_default_realm = server.com auth_gssapi_hostname = hostname.server.com auth_krb5_keytab = /etc/dovecot/dovecot.keytab auth_mechanisms = gssapi plain auth_realms = server.com auth_username_format = %n auth_verbose = no disable_plaintext_auth = yes listen = * mail_location = maildir:/var/spool/mail/%u mail_privileged_group = mail mbox_read_locks = fcntl mbox_write_locks = fcntl namespace { inbox = yes location = prefix = separator = / type = private } passdb { driver = pam } protocols = pop3 imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } ssl = yes ssl_cert = </usr/share/ssl/private/mail.server.com.pem ssl_key = </usr/share/ssl/private/mail.server.com.pem userdb { driver = passwd } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_plugins = " listescape" } Thanks for any pointers, Maura Dailey maura(a)eclipse.ncsc.mil

2 1