- dovecot - dovecot.org

[Dovecot] sync re-copies emails assigning new UIDs
by Anand Kumria 03 Sep '13

03 Sep '13

Hi, I have been (attempting) to transition a company from in-house dovecot 1.x to a hosted dovecot 2.2 setup. I am running the doveadm sync command, and for the four mailboxes have been blocked -- sync'ing seem to be copying the same mails, over and over (note, initially I was using doveadm backup but my reading has indicated that 'doveadm sync' is better) Example: # date && doveadm -v -o imapc_user=kaye(a)example.com -o imapc_password=*pass* -o imapc_host=imap.example.com -o imapc_port=993 -o imapc_ssl=imaps -o imap c_ssl_dir=/etc/ssl -o imapc_feature=rfc822.size -o imapc_ssl_verify=no sync -1 -R -u kaye(a)example.com imapc: Sat Aug 3 09:05:37 UTC 2013 [...] dsync(kaye(a)example.com): Info: copy from INBOX: box=INBOX, uid=5306, msgid=<FB3A2E1C62B148F8B057476BDCBB4A9B@THENORMANS>, size=13544 dsync(kaye(a)example.com): Info: copy from INBOX: box=INBOX, uid=5307, msgid=<006b01ce8dad$b8864930$2992db90$(a)com.au>, size=10163563 [...] dsync(kaye(a)example.com): Info: copy from INBOX: box=INBOX, uid=5311, msgid=< cm.083930.bijjdjk.jdkimlhij.r(a)createsend5.com>, size=46658 [...] # date && doveadm -v -o imapc_user=kaye(a)example.com -o imapc_password=*pass* -o imapc_host=imap.example.com -o imapc_port=993 -o imapc_ssl=imaps -o imapc_ssl_dir=/etc/ssl -o imapc_feature=rfc822.size -o imapc_ssl_verify=no sync -1 -R -u kaye(a)example.com imapc: Sat Aug 3 10:01:48 UTC 2013 [...] dsync(kaye(a)kamdha.com): Info: copy from INBOX: box=INBOX, uid=5324, msgid=<FB3A2E1C62B148F8B057476BDCBB4A9B@THENORMANS>, size=13544 dsync(kaye(a)kamdha.com): Info: copy from INBOX: box=INBOX, uid=5325, msgid=<006b01ce8dad$b8864930$2992db90$(a)com.au>, size=10163563 [...] dsync(kaye(a)kamdha.com): Info: copy from INBOX: box=INBOX, uid=5329, msgid=< cm.083930.bijjdjk.jdkimlhij.r(a)createsend5.com>, size=46658 [...] The exact same number of emails (some in the INBOX, some in the Sent folder) are transferred each time. In this case, I've firewalled the origin - so their entire mail system is stopped whilst I do the transfer just in case modifications of IMAP flags or additional delivieres might have been the problem. I am using Dovecot v2.2.4; is this normal expected behaviour? If so, what is the best way to ensure that a migration is done without data loss. If this isn't expected, has anyone else seen this kind of error before? Thanks, Anand

1 1

[Dovecot] setup of dovecot as proxy to dbmail
by Regan Yelcich 03 Sep '13

03 Sep '13

Can anyone point me in the direction of a detailed how-to for setting up a postfix and dovecot (proxy) node with dbmail? In particular I'm looking for a how-to which shows dovecot authenticating against the dbmail database directly. The only example I've found is this one which requires a duplication of the user database. http://content.fens.org/index.php?q=admin-howto/mail/dovecot2dbmail-proxy Thanks.

2 1

[Dovecot] Auth error in log
by Per-Henrik Lundblom 03 Sep '13

03 Sep '13

Hi, I have a setup with Dovecot handling a few virtual domains delivering mails to both local Unix account mailboxes and seperate mailboxes for virtual users defined in a MySQL database. A quick overview of the configuration shows two passdb definitions: auth default { mechanisms = plain login passdb pam { args = dovecot } passdb sql { args = /etc/dovecot/dovecot-sql.conf } userdb passwd { args = mail=maildir:~/Maildir blocking=yes } userdb static { args = uid=vmail gid=mail home=/var/spool/vmail/%d/%n allow_all_users=yes } user = root socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = vmail group = mail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } !include_try /etc/dovecot/auth.d/*.auth } When a virtual user defined in the MySQL database tries to log in using IMAP or SMTP I always get auth failures logged in the system logs. Entries are like this: Aug 21 06:25:36 roadrunner dovecot-auth: pam_unix(dovecot:auth): authentication failure; logname= uid=0 euid=0 tty=dovecot ruser=luser(a)mydomain.com rhost=85.224.xx.xx I assume these failures comes form the fact that PAM doesn't recognize the virtual users and Dovecot continues to the SQL passdb entry. As a result I get a _lot_ of auth failures in the logs. I have tried to come up with a way where the auth failures from PAM arent't logged if the the SQL authenication is successful. Is this possible or are there any other recommended ways to handle this? /PH -- Per-Henrik Lundblom email: ph(a)whatever.nu phone: +46 733 207126 webpage: www.whatever.nu

2 3

[Dovecot] local AND virtual mail locations ?
by Pierre-Philipp Braun 02 Sep '13

02 Sep '13

Hi, I would like to use Dovecot not only for virtual mboxes, but also for local users. In other words, I would like to use different "mail_location"s depending on "passdb" "passwd-file" versus "passwd". I need that as the smtp daemon I am using (david parsons' postoffice smtp server) serves both but is only able to process messages through procmail on local users. Here are the two mail_locations I would like to use: mail_location: mbox:~/mail/:INBOX=/var/mail/%u mail_location: mbox:/var/spool/virtual/%d/%n.imap:INBOX=/var/spool/virtual/%d/%n depending on those passdb stanzas, respectively: passdb passwd-file { args = username_format=%n /etc/virtual/%d/passwd } passdb passwd { } Any help would be appreciated. Here's my Dovecot version and current working configuration for virtual users only: # dovecot -n dovecot -n # 1.2.17: /usr/local/etc/dovecot.conf # OS: FreeBSD 8.3-RELEASE amd64 ufs protocols: imap ssl: no disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login first_valid_uid: 6 first_valid_gid: 6 mail_location: mbox:/var/spool/virtual/%d/%n.imap:INBOX=/var/spool/virtual/%d/%n imap_client_workarounds: tb-extra-mailbox-sep auth default: user: mail passdb: driver: passwd-file args: username_format=%n /etc/virtual/%d/passwd userdb: driver: static args: uid=6 gid=6 I find that first_valid_uid and first_valid_gid don't look pretty but it seems mandatory for the standard 'mail' user and group ownerships to work on the virtual mbox files and folders. I created the user while the group already existed. If you have any advices on that too, I would be pleased. Thanks Pierre-Philipp

3 7

[Dovecot] migration from IMAP/POP3 courier server to a remote dovecot server
by nik600 02 Sep '13

02 Sep '13

Dear all i'm planning a transparent migration from a courier server that provides both IMAP and POP3 access to users to a remote dovecot server with both IMAP and POP3 access. I have to migrate about 2500 users for 250 GB of space. I'm using dovecot 2.2.5.4 on debian6 squeeze. To make a transparent migration i have to maintain old IMAP UIDs and POP3 UIDs, so i've read http://wiki2.dovecot.org/Migration and http://wiki2.dovecot.org/Migration/Courier and http://wiki2.dovecot.org/Migration/Dsync And decided that probably the best tool to use is Dsync, as the courier-dovecot-migrate.pl<http://www.dovecot.org/tools/courier-dovecot-migrate.pl> script works only locally. I've tested the dsync following instructions reported above but after the migration of one test-account the client re-download messages. If i want to keep both IMAP UIDs and POP3 UIDs i have to sync both imapc and pop3c with two commands? doveadm -o imapc_user=foo -o pop3c_user=foo -o imapc_password=bar -o pop3c_password=bar backup -R -u user@domain imapc: doveadm -o imapc_user=foo -o pop3c_user=foo -o imapc_password=bar -o pop3c_password=bar backup -R -u user@domain pop3c: Or imapc is enough? Do you have any suggestion? Thanks -- /*************/ nik600 http://www.kumbe.it

1 2

[Dovecot] Getting back into Dovecot 2.2.5
by Kai Hendry 02 Sep '13

02 Sep '13

Hi there, I'm prompted to get into running my own mail server again with Gmail going bad. However I found /usr/share/doc/dovecot/example-config/conf.d/ a little scary, since I like to have my configs as minimalistic as possible, e.g. http://dabase.com/blog/Minimal_squid3_proxy_configuration/ So far I have: https://github.com/Webconverger/sg.webconverger.com/blob/master/dovecot/dov… I was kinda hoping for a Maildir, but this doesn't work: mail_location = maildir:~/Maildir:LAYOUT=fs:INBOX=/var/mail/%u I do realise /var/mail/%u is a mbox, but I was wondering if there could be some clever conversion. I was surprised something like INBOX=/var/mail/%u wasn't the default btw. Also surprised dovecot seems to choke on single line syntax like `passdb { driver = pam }` :-) Next thing I'm confused about is the `namespace inbox {` stuff. Is it really needed? I was expecting Dovecot to create the folders once I defined them, but mutt couldn't see them until I created them myself. The mail server is just for myself and a few colleagues. We will probably use mutt as our MUA and Apple Mail on IOS when we are out & about. I next plan to integrate dspam, and work out how to sort mails into folders like I previously effectively had with Gmail's labels. I was confused to which mechanism I should be using to sort mail into folders with rules. Sieve? Back to Procmail? Pigeonhole? I'm looking to avoid complexity here. On the topic of search, can I get away with not running a Solr server? Since I shudder at the thought of running Tomcat. http://wiki2.dovecot.org/Plugins/FTS Kiitos paljon for any pointers!

3 4

[Dovecot] Auto-blocking faulty login attempts
by Jos Chrispijn 01 Sep '13

01 Sep '13

Dear group, How can I block login attempts to dovecot after trying 5 times in error? -- Best regards, Jos Chrispijn --- Artificial intelligence is no match for natural stupidity

3 2

[Dovecot] Dovecot and Postfix Authentication
by Christopher Trom 31 Aug '13

31 Aug '13

I am a student and am trying to get a mail server setup for a project. I have all of the Postfix configuration taken care of, but I am confused by the way that authentication works with Dovecot in the mix. As a user of the system, am I supposed to authenticate myself to Postfix, Dovecot, both individually, or both together? My Postfix users are stored in a PostgreSQL database, should Dovecot also be connected to this db? Some basic pointers on how this setup ought to look is all that I'm hoping for. Thank you, Christopher

2 1

Re: [Dovecot] Bizarre permissions problem
by Joseph Tam 31 Aug '13

31 Aug '13

Bill Oliver writes: > There's *one* user I can't get it to work on without a > workaround. The user is "newuser" and the uid is 1111 (actual name and > number changed to protect the innocent). The error I get in my maillog > is: > > The error I get in may maillog is: > Aug 29 16:02:11 localbox dovecot: imap(newuser): Error: chown(/home/newuser/mail/.imap/INBOX, -1, 12(mail)) failed: Operation not permitted (egid=1111(newuser), group based on /var/mail/newuser) > Aug 29 16:02:11 localbox dovecot: imap(newuser): Error: mkdir(/home/newuser/mail/.imap/INBOX) failed: Operation not permitted > Aug 29 16:02:11 localbox dovecot: imap(newuser): Error: chown(/home/newuser/mail/.imap/INBOX, -1, 12(mail)) failed: Operation not permitted (egid=1111(newuser), group based on /var/mail/newuser) > Aug 29 16:02:11 localbox dovecot: imap(newuser): Error: mkdir(/home/newuser/mail/.imap/INBOX) failed: Operation not permitted > Aug 29 16:02:11 localbox dovecot: imap(newuser): Error: chown(/home/newuser/mail/.imap/INBOX, -1, 12(mail)) failed: Operation not permitted (egid=1111(newuser), group based on /var/mail/newuser) > Aug 29 16:02:11 localbox dovecot: imap(newuser): Error: mkdir(/home/newuser/mail/.imap/INBOX) failed: Operation not permitted > > Now, it looks to me like dovecot is saying that the user newuser can't > get to the /home/newuser/mail/.imap directory because it doesn't have > permission. However, the user newuser has all the permissions it needs: > > $ ls -la /home/newuser/mail > > total 20 > drwxrw---- 3 newuser newuser 4096 Aug 29 15:01 . > drwxrw---- 6 newuser newuser 4096 Aug 29 12:16 .. > drwxrwx--- 2 newuser newuser 4096 Aug 29 16:05 .imap > -rw-rw---- 1 newuser newuser 499 Aug 13 07:56 saved-messages > -rw-rw---- 1 newuser newuser 1756 Aug 16 11:15 sent-mail The output of doveconf -n would have been useful, especially as it relates to your mail_location value, but I can make a pretty good guess at what is happening. Dovecot is trying to create indices with analogous permissions to your mailbox files. Your user's INBOX (/var/mail/newuser) has permission user:group:mode = 1111:12:0660 *but* newuser is not in group "mail" (GID 12), hence it cannot do the required chown operations. (Notice the mode of .imap/: the group write is on so the chmod worked.) Your INBOX ended up this way because some LDA's auto-create new INBOX's with these permissions (to allow access to other part of the mail sysyem that are set-gid "mail"). Options: 1) chmod g-rwx /var/mail/newuser - assumes you have no other parts of your mailsystem that needs access to all user INBOX by assuming group "mail". - dovecot is smart enough to figure out group membersip is irrelevant is groups access is nil. 2) chgrp newuser /var/mail/newuser 3) To avoid future problems: make sure new mailboxes are created with workable permissions. There are also dovecot configs that loosen up some group access, but you'll have to investigate that yourself. Joseph Tam <tam(a)math.ubc.ca>

1 0

[Dovecot] kqueue bug?
by Timo Sirainen 31 Aug '13

31 Aug '13

Apparently Dovecot with kqueue ioloop enabled causes random crashes in FreeBSD 9.1. Anyone else noticed something like that? I'm wondering if Dovecot's kqueue code has a bug somewhere (I can't find it) or could it be that FreeBSD itself has a bug? Anyway it seems to be returning events for filters that have already been removed.

4 3

[Dovecot] Log successful login plain text password
by Marco Fretz 30 Aug '13

30 Aug '13

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, I want to use dovecot as a IMAP and POP3 proxy in front of our current E-Mail hosting server to log the plain text passwords of all successful logins for migration reasons. Actually I don't need the password to see in plain text, storing them as SHA256-CRYPT (or something dovecot can use later for auth) hash in a file or DB would be fine, too. I need this for the migration from the current mail server (using proprietary hashing to store passwords) to a new postfix / dovecot base mail system. I played around with "auth_debug_passwords" and all debug / logging options I found in the manual. Nothing logs successful login plaintext passwords. Any hint welcome. Thanks a lot, Marco -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.13 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSHZ9tAAoJEKxm7Ju3UATui2cP/A3cf2TrNvOjjtP1TCgZZ5EC igsgngPlKiXU/RwHO9shBLXUyhKDHPGihNf9KL/RjoFnrgX1asPd/RF/2b080IU3 bNO49BLs8QqoroKz5E+TL8UNixlO5YQjnerKfJ5GIJbSUTC3MaxmN62Cl9jEaTWu 4dX3MXoB3ghoxt6FETSLXz6cEXsGd6KvqxolQC13NYtvpZED+qk7z3RywK8Xp/Au Ipx3xEnDRc/YvG3PeJlsjF9Ge80GxVVH0nudNOV/zmyuNfh4PkPRerk1R4Px01zI sxnXvcNjjenCJ6DMKBmOCyBii9Wl9i4opw9k4X4Z6MFEZGiodRz1usKWJMT0VqUG NBEJDOWsoWpasWMCtduBRrNQS3JI+o1tebDAI5n3K4lJ2d27+nosDvdQ8vNlVszM 8nhSn228RQNy9SJZNAvspOYQBM2gt5IQyWGA4jhrMUkwKeTfHZik8vh8lEcwbK9q H6Myue+i+G8wVa57F1V7/7x2LNGn56BWxTDlBrtKdK3KphCgEoCny/f5VYerO8It MnCMLPXI2oCC8qqkK7x45SYSe/eQhgV93LHpI5z25TqyeJ6R+7dglderRDQcNN0n OtbYMYkqlF8xJ4k+rVFwOC5VD7Bq+S2Q4LyLEf7wFH32Dc12pI/SnAL8DPvkNgbL FshgaVOXUEkb0WhnvROl =oEzx -----END PGP SIGNATURE-----

2 5

[Dovecot] Pigeonhole Sieve - sent message to xmpp account
by Ingo Thierack 30 Aug '13

30 Aug '13

Hello, does someone know, how far the implementation of enotify - xmpp is. Would be nice to push notifications to an jabber account for specific filtered mails. Regards, Ingo

2 1

[Dovecot] Bizarre permissions problem
by Bill Oliver 30 Aug '13

30 Aug '13

Help! I have been using dovecot for some years with great success. A little while ago, I changed my mail server from Fedora to CentOS linux. I reinstalled dovecot, and *almost* everything seems to be working, but one thing. There's *one* user I can't get it to work on without a workaround. The user is "newuser" and the uid is 1111 (actual name and number changed to protect the innocent). The error I get in my maillog is: The error I get in may maillog is: Aug 29 16:02:11 localbox dovecot: imap(newuser): Error: chown(/home/newuser/mail/.imap/INBOX, -1, 12(mail)) failed: Operation not permitted (egid=1111(newuser), group based on /var/mail/newuser) Aug 29 16:02:11 localbox dovecot: imap(newuser): Error: mkdir(/home/newuser/mail/.imap/INBOX) failed: Operation not permitted Aug 29 16:02:11 localbox dovecot: imap(newuser): Error: chown(/home/newuser/mail/.imap/INBOX, -1, 12(mail)) failed: Operation not permitted (egid=1111(newuser), group based on /var/mail/newuser) Aug 29 16:02:11 localbox dovecot: imap(newuser): Error: mkdir(/home/newuser/mail/.imap/INBOX) failed: Operation not permitted Aug 29 16:02:11 localbox dovecot: imap(newuser): Error: chown(/home/newuser/mail/.imap/INBOX, -1, 12(mail)) failed: Operation not permitted (egid=1111(newuser), group based on /var/mail/newuser) Aug 29 16:02:11 localbox dovecot: imap(newuser): Error: mkdir(/home/newuser/mail/.imap/INBOX) failed: Operation not permitted Aug 29 16:02:11 localbox dovecot: imap(newuser): Disconnected: Logged out bytes=108/669 Now, it looks to me like dovecot is saying that the user newuser can't get to the /home/newuser/mail/.imap directory because it doesn't have permission. However, the user newuser has all the permissions it needs: $ ls -la /home/newuser/mail total 20 drwxrw---- 3 newuser newuser 4096 Aug 29 15:01 . drwxrw---- 6 newuser newuser 4096 Aug 29 12:16 .. drwxrwx--- 2 newuser newuser 4096 Aug 29 16:05 .imap -rw-rw---- 1 newuser newuser 499 Aug 13 07:56 saved-messages -rw-rw---- 1 newuser newuser 1756 Aug 16 11:15 sent-mail newuser has the correct uid (1111) in /etc/dovecot/users newuser *is* the correct uid for that user, i.e.: $ id -u newuser 1111 the password is correct Both my web mail package (roundcube) and my android fail. Both work fine with all other accounts that are set up for imap services. The workaround, it turns out, is that if I make the directory /home/newuser/.imap/INBOX by hand as the user newuser, then things work. So, things seem to be working. However, I just don't understand why *this* user is having problems when none of the others are... The only thing that sets this user apart from any of the others is that it has administration privileges for the roundcube mailer MySQL database. Any explanations? Thanks! billo

2 1

[Dovecot] Sieve vacation reply problem (Dovecot+Sieve/Sendmail/Horde)
by megodin＠inboxalias.com 29 Aug '13

29 Aug '13

Hello Dovecot community, I have an annoying problem with successfully activating Sieve vacation replies - on which I have been working hard the last days without success :( I'm using Dovecot 2.2 + Sendmail + Sieve connected with Horde web-mailer IMP H3 which is generally working fine. BUT: Whenever I activate vacation script in Horde (via Ingo) and send a test-mail to this account, the mail itself arrives but the auto-vacation-reply failes: [mail.err] dovecot: lda(exampleuser): Error: sieve: original envelope recipient address 'exampleuser@dovecot_localhost' is unparsable [mail.warning] dovecot: lda(exampleuser): Warning: sieve: msgid=: vacation action aborted: envelope recipient is <> The Sieve Script which is generated and executed: # Sieve Filter produced by Ingo (http://www.horde.org/ingo/) (20.08.2013, 16:10) require ["vacation", "regex"]; # Abwesenheit if allof ( not exists ["list-help", "list-unsubscribe", "list-subscribe", "list-owner", "list-post", "list-archive", "list-id", "Mailing-List"], not header :comparator "i;ascii-casemap" :is "Precedence" ["list", "bulk", "junk"], not header :comparator "i;ascii-casemap" :matches "To" "Multiple recipients of*" ) { vacation :days 7 :addresses "example.user(a)example.com" :subject "vacation" "I am on vacation until xxxx. Please refer all urgent business to devnull(a)example.com ."; } I understand that Sieve is trying to send vacation replies to the envelope sender - apparently it gets it on the wrong line somewhere from the sendmail config. To get sendmail working along with Dovecot, I had to do some modifications: in /etc/mail/virtusertable (Alias with domain-path) @vlmail.example.com %1@dovecot_localhost in /etc/mail/access (allows relaying) to:dovecot_localhost RELAY in /etc/mail/mailertable (where to be relayed) dovecot_localhost dovecot:vlmail.example.com in /etc/mail/sendmail.cf (relevant part for the Dovecot Mailer specification): Mdovecot, P=/usr/libexec/dovecot/dovecot-lda, F=lDFMPhnu59, S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP/HdrFromSMTP, U=vmail:vmail, T=DNS/RFC822/X-Unix, A=/usr/libexec/dovecot/dovecot-lda -d $u After several hours playing with sendmail's config I came to the end that sendmail's part must be already over when sieve is getting the original envelope recipient - it seems like it gets it from dovecot-lda. Though, when playing with the Dovecot Mailer specifications in sendmail.cf I can get different error message if I add A=/usr/libexec/dovecot/dovecot-lda -d $u -a $n (adding username part in destination address): [mail.info] dovecot: lda(exampleuser): sieve: msgid=: discarding vacation response for implicitly delivered message; no known (envelope) recipient address found in message headers (recipient=, and additional `:addresses' are specified) BTW, the original mails arriving have a valid Return-Path in header... I am thinking of writing global Sieve scripts (executing before the user's private sieve script), telling Sieve to use the TO: field instead of the Envelope sender but I'm not sure if this is possible, and if, which commands are needed specifically. I really start getting desperate... Can somebody get me some clue what is wrong in my config / where I should put modifications to get sieve vacation replys working properly?! Thanks in advance!! Megodin My Setup: - Dovecot EE 2.2.5.3 + pigeonhole Sieve 0.4.1 - Sendmail Version 8.14.4 (compiled with: DNSMAP HESIOD HES_GETMAILHOST LDAPMAP LOG MAP_REGEX MATCHGECOS MILTER MIME7TO8 MIME8TO7 NAMED_BIND NETINET NETINET6 NETUNIX NEWDB NIS PIPELINING SASLv2 SCANF SOCKETMAP STARTTLS TCPWRAPPERS USERDB USE_LDAP_INIT) - Horde 3.3.13 (Ingo H3 1.2.6) doveconf -n # 2.2.5.3 (f54f8c8f5502): /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-279.22.1.el6.x86_64 x86_64 CentOS release 6.4 (Final) nfs auth_cache_size = 10 M auth_cache_ttl = 10 mins auth_debug = yes auth_master_user_separator = * auth_username_format = %n auth_verbose = yes disable_plaintext_auth = no listen = * lock_method = dotlock mail_debug = yes mail_fsync = always mail_gid = vmail mail_home = /mnt/vmails/%u mail_location = sdbox:/mnt/vmails/%u/mailstore mail_plugins = " quota fts fts_lucene" mail_privileged_group = mail mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave mmap_disable = yes passdb { args = /etc/dovecot/users.blocked deny = yes driver = passwd-file } passdb { args = /etc/dovecot/passwd.masterusers driver = passwd-file master = yes } passdb { args = /etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { fts = lucene fts_lucene = whitespace_chars=@. quota = dict:User quota::file:%h/dovecot-quota quota_rule = *:storage=100M quota_rule2 = Trash:storage=+50M quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=98%% quota-warning 98 %u sieve = /mnt/vmails/%u/.dovecot.sieve sieve_dir = /mnt/vmails/%u/sieve sieve_global_dir = /var/lib/dovecot/sieve/global/ sieve_global_path = /var/lib/dovecot/sieve/default.sieve } postmaster_address = postmaster(a)example.com protocols = imap pop3 sieve service auth { unix_listener auth-userdb { group = vmail user = vmail } } service managesieve-login { inet_listener sieve { port = 4190 } } service quota-warning { executable = script /usr/local/bin/quota-warning.sh unix_listener quota-warning { user = vmail } user = vmail } ssl_cert = --- Alle PostfÃ¤cher an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen _________________________________________________________________ Send and receive anonymous emails to your inbox with InboxAlias. http://www.inboxalias.com

2 1

[Dovecot] 2.2.4 + metadata plugin: autoconf failed
by Andreas Schulze 29 Aug '13

29 Aug '13

Hello, I can compile metadata plugin using debian squeeze + wheezy. But build on suse enterprise server 9,10 and 11 failed. The metadata plugin require autoconf-2.65 which i too new. On the other side I can build the dovecot-2.2.4 and pigeonhole-0.4.0 plugin without problems: dovecot require autoconf-2.59 and pigeonhole does not require any specific autoconf version. I asked the authors of the plugin for support but got no response. Maybe somebody could review the plugin. Thanks Andreas -- Andreas Schulze Internetdienste | P252 DATEV eG 90329 Nürnberg | Telefon +49 911 319-0 | Telefax +49 911 319-3196 E-Mail info @datev.de | Internet www.datev.de Sitz: 90429 Nürnberg, Paumgartnerstr. 6-14 | Registergericht Nürnberg, GenReg Nr.70 Vorstand Prof. Dieter Kempf (Vorsitzender) Dipl.-Kfm. Wolfgang Stegmann (stellvertretender Vorsitzender) Dipl.-Kfm. Michael Leistenschneider Dipl.-Kfm. Dr. Robert Mayr Jörg Rabe v. Pappenheim Dipl.-Vw. Eckhard Schwarzer Vorsitzender des Aufsichtsrates: Reinhard Verholen

2 3

Re: [Dovecot] Dovecot Dsync
by Ed W 29 Aug '13

29 Aug '13

On 27/08/2013 09:54, Ben wrote: > On 23/08/2013 13:08, Ed W wrote: >> Hi >> >>> I'm on an Ubuntu LTS release so the dovecot came from their release. >>> I'd prefer to stay that way unless I really have to... >> >> Everyone is entitled to their own opinions, but "IMHO" this kind of >> attitude is a huge detriment to most software projects. I see very >> little reason to take such policies personally... >> >> 1) I use virtualisation (especially lightweight virtualisation such as >> vservers) so that each service is in its own container. Now if I have no >> interest in some container and want to let it rot (ie as per LTS), then >> I can just do so. >> 2) I use a fast moving rolling distro (gentoo in my case, Arch is >> probably a good choice also) so that I have the option to stay up to >> date when I want to >> >> The end result is you can be as up to date as you want, or let things >> rot, as you please. >> >> Unfortunately if you want to use a very old bit of software, then you >> also get to keep all it's bugs... Sorry. >> >> Good luck! Hope this inspires you to try a different route! >> >> Ed W > > Whilst to some degree I appreciate where you're coming from and agree > with you to a certain extent, I would caution that following the > bleeding edge, always running the latest versions is not without risk > or bugs either ! OK, but virtualisation also helps you mitigate this: - I setup my "containers" so that I have at least two mount points, one for the operating system and any data broken out into it's own mount. - This makes it quite simple to duplicate the container and spin up a test version pointing if required at the live data - Now you can run a test upgrade on the test container. If it works either swap them around or upgrade the original Additionally: - My choice of distro (gentoo) makes it fairly simple to build binary packages of the software I'm using. - I then use these binary packages on all my containers, additionally with guided profiles which control which packages and which options we deploy. - It's fairly simple to roll back most packages to the previous binary version if a problem is detected (logging of package changes is built-in) So it's quite low risk to use such a rolling distro in general. Note, I can't speak for other distros, but gentoo "stable" is fairly conservative and shouldn't be a problem for an experienced admin to keep up to date. It has the option to unmask "bleeding edge" packages where necessary and this can be useful to hit specific version numbers of software. It's also pretty trivial to keep a private repo of customised packages (ebuilds) with either personal patches or to pin certain versions of software. (So for example if you run, say, Dovecot with a few custom patches, then it's fairly trivial to drop these patches in a directory and now you can use the package manager to follow stable builds, but your custom patches will be rolled in for you with each update - can be very handy for some requirements) I don't have the same experience with RPM/DEB so I can't say that all the same is easy to do, but the key thing is the use of containers/virtualisation to assist with testing and upgrades. Even worst case you have to do a whole OS upgrade, at least if you can do that in a test container while the live remains running, is a big advantage Good luck Ed W

1 0

Re: [Dovecot] mailbox_list_index, stops showing new mails in mailboxes
by Joseph Tam 29 Aug '13

29 Aug '13

Anton Lundin writes: > I'm using 2.2.4 over imap and ssh/imap, and after a while dovecot > stops noticing new mail in some folders. Its always the same 2-3 > folders of about 30. > ... > This is dovecot 2.2.4, running on Solaris 10 x86_64 to homedirs on zfs, > where procmail is used to deliver mail to mailboxes in mbox-format. What's your procmail recipe for delivering messages? If you're storing it directly to a mbox file, dovecot will never get a chance to see it and update the indices. An example of invoking LDA to store messages :0 Hw * /^From:.*dummy@/ | dovecot-lda -d yourusername -m dummybox # Dump mail into my INBOX using dovecot's LDA :0 w | dovecot-lda -d yourusername Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] Issues with dovecot-antipsam plugin
by Vijay Rajah 29 Aug '13

29 Aug '13

Hello list, I have a postfix 2.11 with dovecot 2.2.5 instance. I have configured and installed anavisd-new to use Spamassassin. I want to train the filter. For that i choose dovecot's antispam plugin using mailtrain backend. I compiled and installed the latest version of the antispam plugin from http://hg.dovecot.org/dovecot-antispam-plugin/rev/5ebc6aae4d7c The configuration is below. Whenever I receive an email, the LMTP process segfaults. If I comment out the antispam plugin part in the config files, all works good. THis leads me to believe the issue is with antispam plugin, or its configuration. Here is what i see in /var/log/mailllog Aug 28 23:06:31 hostname.tld postfix/qmgr[1437]: 055F6345E: from=< sender(a)example.com>, size=10370, nrcpt=1 (queue active) Aug 28 23:06:31 hostname.tld postfix/smtpd[5512]: disconnect from localhost[127.0.0.1] Aug 28 23:06:31 hostname.tld amavis[5369]: (05369-05) Passed SPAM {RelayedTaggedInbound,Quarantined}, [74.125.82.176]:51219 [74.125.82.176] < sender(a)example.com> -> <email(a)mydomain.tld>, quarantine: spam-J09TFNU33sxa.gz, Queue-ID: 3A8093119, Message-ID: < CAMGVk5vH9YzkNFJ3xnWJ0060vpuf1PPzaCHWx71AmGF_qgJTmg(a)mail.gmail.com>, mail_id: J09TFNU33sxa, Hits: 12.123, size: 9323, queued_as: 055F6345E, dkim_sd=20120113:gmail.com, 606 ms Aug 28 23:06:31 hostname.tld postfix/lmtp[5510]: 3A8093119: to=<email(a)mydomain.tld>, relay=127.0.0.1[127.0.0.1]:10024, delay=1.6, delays=0.94/0/0/0.61, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 055F6345E) Aug 28 23:06:31 hostname.tld postfix/qmgr[1437]: 3A8093119: removed Aug 28 23:06:31 hostname.tld dovecot: lmtp(5514): Connect from local Aug 28 23:06:31 hostname.tld dovecot: lmtp(5514): Fatal: master: service(lmtp): child 5514 killed with signal 11 (core dumps disabled) Aug 28 23:06:31 hostname.tld postfix/lmtp[5513]: 055F6345E: to=<email(a)mydomain.tld>, relay=hostname.tld[/opt/var/postfix/dovecot-lmtp], delay=0.09, delays=0.04/0/0.04/0, dsn=4.4.2, status=deferred (lost connection with hostname.tld[/opt/var/postfix/dovecot-lmtp] while sending end of data -- message may be sent more than once) Can someone help in fixing the issue… -Thanks in advance Vijay ######doveconf -n # 2.2.5: /opt/dovecot/2.2.5/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-358.14.1.el6.x86_64 x86_64 CentOS release 6.4 (Final) ext4 auth_mechanisms = plain login digest-md5 cram-md5 auth_socket_path = /opt/var/dovecot/run/auth-userdb base_dir = /opt/var/dovecot/run/ debug_log_path = /var/log/dovecot-debug.log hostname = mail1(a)rvijay.me mail_debug = yes mail_location = maildir:/opt/mailbox/%d/%n/Maildir mail_plugin_dir = /opt/dovecot/2.2.5/lib/dovecot/ mail_plugins = " virtual quota antispam zlib" managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Spam { auto = subscribe } mailbox Trash { auto = subscribe special_use = \Trash } prefix = separator = / type = private } passdb { args = /opt/dovecot/2.2.5/etc/dovecot/conf.d/dovecot-sql.conf.ext driver = sql } plugin { antispam_allow_append_to_spam = no antispam_backend = mailtrain antispam_mail_notspam = --ham antispam_mail_sendmail = /opt/dovecot/2.2.5/bin/sa-learn-pipe.sh antispam_mail_sendmail_args = -u vmail antispam_mail_spam = --spam antispam_mail_tmpdir = /tmp antispam_spam = Spam antispam_trash = Trash mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size quota = maildir:User quota quota_grace = 10%% quota_rule = *:storage=1GB quota_rule2 = Trash:storage=+10%% quota_rule3 = Spam:storage=+20%% quota_status_nouser = DUNNO quota_status_overquota = 450 4.2.2 Mailbox is full. Try again later quota_status_success = DUNNO quota_warning = storage=95%% quota-warning 95 %u quota_warning2 = storage=80%% quota-warning 80 %u quota_warning3 = -storage=100%% quota-warning below %u sieve = ~/.dovecot.sieve sieve_before = /opt/var/dovecot/sieve/ sieve_dir = ~/sieve sieve_global_dir = /opt/var/dovecot/sieve zlib_save = bz2 zlib_save_level = 9 } protocols = imap lmtp sieve service auth { unix_listener /opt/var/postfix/dovecot-auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imap { port = 143 } } service lmtp { unix_listener /opt/var/postfix/dovecot-lmtp { group = postfix mode = 0660 user = postfix } } service managesieve-login { inet_listener sieve { port = 4190 } service_count = 10 vsz_limit = 64 M } service managesieve { process_limit = 1024 } service quota-status { client_limit = 1 executable = quota-status -p postfix inet_listener { port = 12340 } } service quota-warning { executable = script /opt/dovecot/2.2.5/etc/dovecot/conf.d/quota-warning.sh user = vmail } shutdown_clients = no ssl_ca = </opt/dovecot/2.2.5/etc/dovecot/ssl/mayca.crt.pem ssl_cert = </opt/dovecot/2.2.5/etc/dovecot/ssl/cert.pem ssl_key = </opt/dovecot/2.2.5/etc/dovecot/ssl/key.key ssl_parameters_regenerate = 30 hours submission_host = 127.0.0.1:587 userdb { driver = prefetch } userdb { args = /opt/dovecot/2.2.5/etc/dovecot/conf.d/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = " virtual quota antispam zlib sieve zlib" } protocol imap { mail_plugins = " virtual quota antispam zlib imap_quota imap_zlib" } protocol lmtp { debug_log_path = /var/log/dovecot-lmtp-debg.log mail_plugins = " virtual quota antispam zlib sieve zlib" }

1 0

[Dovecot] Enforcing server cipher list order
by Phillip Odam 29 Aug '13

29 Aug '13

I noticed a similar/same discussion back on Aug 14th titled force ciphers order for clients. However from that thread I can't find quite what I'm after. From my testing of dovecot 2.1.6, by default it appears to honor the clients cipher list order for SSL/TLS connections. I can't find any documentation on dovecot providing a setting like Apache HTTPDs to either honor the client or server cipher list i.e. SSLHonorCipherOrder. Do newer versions (> 2.1.6) of dovecot either make this configurable or force honoring of the servers cipher list order? Or is the cipher selection a function that openssl performs? The version of openssl in use is 1.0.1e-fips. Thanks Phillip

1 0

Re: [Dovecot] Log successful login plain text password
by Joseph Tam 29 Aug '13

29 Aug '13

Marco Fretz writes: > Maybe you can find a way in this direction > > http://wiki2.dovecot.org/HowTo/ConvertPasswordSchemes I've sync'd a separate password system by process tracing dovecot's auth process and dumping out the arguments of read() calls for some fixed set of descriptors and piping it into password synching script. A bit of a hack, but it works without having to touch dovecot. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] Bug in dovecot 2.2.5: segfault due to bad alignment
by Andreas F. Borchert 29 Aug '13

29 Aug '13

Take a look at the sources, hmac.h declares struct hmac_context: struct hmac_context { char ctx[HMAC_MAX_CONTEXT_SIZE]; char ctxo[HMAC_MAX_CONTEXT_SIZE]; const struct hash_method *hash; }; If compiled for a 32 bit virtual address space, this has an alignment requirement of 4 due to the hash pointer. In line 171 of auth-token.c, we have following declaration of ctx as a local variable in auth_token_get(): struct hmac_context ctx; This is put on an address with an alignment requirement of 4. In lines 174 and 175 hmac_init is invoked with hash_method_sha1: hmac_init(&ctx, (const unsigned char*)username, strlen(username), &hash_method_sha1); In hmac.c, lines 43 and following, ctx->ctx with an alignment of 4 is passed to meth->init and meth->loop where meth refers to hash_method_sha1: meth->init(ctx->ctx); meth->loop(ctx->ctx, k_ipad, 64); These functions refer now to sha1_init and sha1_loop where the first parameter is expected to be a pointer to struct sha1_ctxt, a data structure which is declared in sha1.h: struct sha1_ctxt { union { uint8_t b8[20]; uint32_t b32[5]; } h; union { uint8_t b8[8]; uint64_t b64[1]; } c; union { uint8_t b8[64]; uint32_t b32[16]; } m; uint8_t count; }; Here we have with b64 one uint64_t which has on a SPARC platform an alignment requirement of 8. In consequence, struct sha1_ctxt has an alignment requirement of 8. With the invocations of meth->init and meth->loop above we pass a pointer to a data structure of alignment 4 to a function expecting a pointer to a data structure of alignment 8. Chances are that the alignment requirement is not met, causing a segmentation violation. This must be solved by declaring struct hmac_context such that is not just big enough but respects also the highest alignment required for one of the hashing data structures. There are several options to do this: * Beginning with C11, you are free to use an alignment specifier, i.e. add _Alignas ( uint64_t ) (see section 6.7.5 in ISO 9899-2011) * GCC supports alignment attributes, i.e. add __attribute__ ((aligned (8))) or whatever is required instead of 8, see http://gcc.gnu.org/onlinedocs/gcc/Variable-Attributes.html * Do not use a local variable for it, allocate the data structure using malloc instead. If you want to see a live crash, here is the relevant output of gdb that debugs ${prefix}/libexec/dovecot/auth. Program received signal SIGSEGV, Segmentation fault. sha1_loop (ctxt=0xffbff63c, input=0xffbff548, len=64) at sha1.c:224 224 sha1.c: No such file or directory. (gdb) where #0 sha1_loop (ctxt=0xffbff63c, input=0xffbff548, len=64) at sha1.c:224 #1 0xff2e218c in hmac_init (ctx=ctx@entry=0xffbff63c, key=key@entry=0x6a698 "borchert", key_len=8, meth=0x555d0 <hash_method_sha1>) at hmac.c:44 #2 0x00023310 in auth_token_get (service=service@entry=0x6a648 "imap", session_pid=0x56071 "26272", username=0x6a698 "borchert", session_id=0x6a650 "AErv6nbk6gB/AAAB") at auth-token.c:174 #3 0x00021708 in userdb_callback (result=USERDB_RESULT_OK, request=0x6a530) at auth-request-handler.c:668 #4 0x0001f144 in auth_request_userdb_callback (result=<optimized out>, result@entry=USERDB_RESULT_OK, request=request@entry=0x6a530) at auth-request.c:1039 #5 0x000312c8 in prefetch_lookup (auth_request=0x6a530, callback=0x1f058 <auth_request_userdb_callback>) at userdb-prefetch.c:40 #6 0x0001f37c in auth_request_lookup_user (request=0x6a530, callback=callback@entry=0x2150c <userdb_callback>) at auth-request.c:1072 #7 0x00022034 in auth_request_handler_master_request ( handler=<optimized out>, master=master@entry=0x6b120, id=1292369921, client_id=1, params=0x55bfc) at auth-request-handler.c:758 #8 0x0001be98 in master_input_request (args=<optimized out>, conn=0x6b120) at auth-master-connection.c:127 #9 auth_master_input_line (line=<optimized out>, conn=0x6b120) at auth-master-connection.c:598 #10 master_input (conn=0x6b120) at auth-master-connection.c:653 #11 0xff2ecca4 in io_loop_call_io (io=io@entry=0x6b398) at ioloop.c:387 #12 0xff2ed604 in io_loop_handler_run (ioloop=ioloop@entry=0x5e5e8) at ioloop-poll.c:211 #13 0xff2ec7a8 in io_loop_run (ioloop=0x5e5e8) at ioloop.c:406 #14 0xff29ad7c in master_service_run (service=0x5e128, callback=0x27b40 <client_connected>) at master-service.c:566 #15 0x0001852c in main (argc=1, argv=0xffbffd54) at main.c:393 (gdb) print ctxt $1 = (struct sha1_ctxt *) 0xffbff63c As you can see, ctxt is on a 4-byte boundary, not on an 8-byte boundary. The crash happens at sha1.c:224 where the 8-byte-alignment is indeed mandatory on a SPARC architecture: ctxt->c.b64[0] += copysiz * 8; The environment is Solaris 10 on SPARCv9. The sources have been compiled using gcc 4.8.0 for 32 bit. Andreas.

2 1

[Dovecot] Dovecot proxy to Microsoft Exchange 2013
by Ricardo Machini Barbosa 29 Aug '13

29 Aug '13

Hello, I am trying to do a proxy with dovecot to IMAP backend server that are using Microsoft Exchange 2013. I already did this with Microsoft Exchange 2007 and Microsoft Exchange 2010 and it works perfectly! But with Microsoft Exchange 2013 I can not perform LOGIN. The error log message is: /imap-login: Error: proxy(user(a)domain.com.br): Login for exchange2013.domain.com.br:143 timed out in state=4 (after 30 secs, local=x.x.x.x:59640)/ My troubleshoot was: - tcpdump on dovecot server side: I can see the commands sent/received by Microsoft Exchange. But no the "OK LOGIN" response. /* OK The Microsoft Exchange IMAP4 service in xxxx is ready.// //C CAPABILITY// //L LOGIN "user(a)domain.com.br" "123456"// //* CAPABILITY IMAP4 IMAP4rev1 AUTH=PLAIN STARTTLS UIDPLUS CHILDREN IDLE NAMESPACE LITERAL+// //C OK CAPABILITY completed./ - tcpdump with telnet login on dovecot server side: Works fine. /* OK The Microsoft Exchange IMAP4 service in xxxx is ready.// //a login "user(a)domain.com.br" "123456"// //a OK LOGIN completed.// //a logout// //* BYE Microsoft Exchange Server 2013 IMAP4 server signing off.// //a OK LOGOUT completed./ - Log verbose on Microsoft Exchange 2013. Look like that Microsoft Exchange did not receive the login command. Someone already tried do this with Microsoft Exchange 2013 ? See bellow some information about my dovecot configuration: /# 2.2.2: dovecot.conf// //# OS: Linux 2.6.32-358.2.1.el6.centos.plus.x86_64 x86_64 CentOS release 6.4 (Final)// // //base_dir = /var/run/dovecot/// //disable_plaintext_auth = no// //listen = x.x.x.x// //mbox_write_locks = fcntl// //passdb {// // args = /etc/dovecot/dovecot-ldap.conf.ext// // driver = ldap// //}// // //protocols = imap pop3// //service imap-login {// // inet_listener imap {// // port = 143// // }// // inet_listener imaps {// // port = 993// // ssl = yes// // }// // process_min_avail = 4// // service_count = 0// // vsz_limit = 512 M// //}// //service pop3-login {// // inet_listener pop3 {// // port = 110// // }// // inet_listener pop3s {// // port = 995// // ssl = yes// // }// // process_min_avail = 4// // service_count = 0// // vsz_limit = 512 M// //}// //ssl_cert = </etc/dovecot/certificate/chained.crt// //ssl_key = </etc/dovecot/certificate/cert.key// //userdb {// // driver = prefetch// //}// // ///etc/dovecot/dovecot-ldap.conf.ext// //hosts = x.x.x.x// //dn = cn=admin,o=email// //dnpass = xxxxxxx// //ldap_version = 3// //base = o=email// //scope=subtree// //pass_filter = mail=%u// //pass_attrs = uid=user,=password=,=proxy=y,mailHost=host,=nopassword=y/ Thanks, Ricardo Machini

4 7

[Dovecot] Disable PAM username change?
by George 28 Aug '13

28 Aug '13

Hi! I have a problem involving Samba4, exim4, fetchmail, Dovecot and PAM... I am using Dovecot 2.1.7 on Debian Wheezy. I have setup a "maildrop" machine, which fetches mail from an external POP3 server for multiple accounts using fetchmail, delivers to local users mailboxes through exim4 and then serves them on the intranet via IMAP with Dovecot. This works great with local unix users, but I am having some trouble to configure it to work with Samba4 AD users (Samba 4.0.9 running as a DC on the same machine). Basically, I have configured PAM with winbind and it works fine (AD users can SSH the machine for example). Dovecot also authenticates properly via PAM, but the problem is that the username gets changed in the process (PAM returrns the "username" as "DOMAIN\username"): Aug 21 22:50:22 dc2 dovecot: auth-worker(5179): Debug: auth(foo,127.0.0.1): username changed foo -> DOMAIN\foo Aug 21 22:50:22 dc2 dovecot: auth: Debug: auth(foo,127.0.0.1,<0bBfg3/kpQB/AAAB>): username changed foo -> DOMAIN\foo Aug 21 22:50:22 dc2 dovecot: auth: Debug: client out: OK#0111#011user=DOMAIN\foo So the actual problem is that exim4 is delivering the mail to, for example, "/var/mail/foo" but Dovecot is looking for the mailbox on "/var/mail/DOMAIN\foo", even if the username given in the IMAP session is just "foo". The wiki mentions<http://wiki2.dovecot.org/PasswordDatabase/PAM>that "a PAM module can change the username". Can this be avoided? I need either: * Exim to deliver the mail to the user mailbox, *including* the domain part (out of scope of this list, but information is welcome), or * Dovecot to fetch the mail *not* using the domain part as part of the username variable. As a quick and dirty workaround, I hardcoded the domain part in the exim delivery path (something like "/var/mail/DOMAIN\\$local_part"), but this is far from optimal since I cannot use both unix users and AD users, I cannot use dovecot_delivery LDA transport, etc. As a bottom line, I also posted this to the Samba list because I believe this could also be solved if winbind just always returned the username without the domain when queried (conf option not working, probable bug) Ideas are welcome!! Best regards, Jorge

1 1

[Dovecot] Install of Dovecot 2.2.5 on Solaris 10/Openssl version 0.9.7d 17 Mar 2004
by Haney, Donald 28 Aug '13

28 Aug '13

Greetings! I am attempting to install Dovecot 2.2.5 on Solaris 10 Sparc hardware with openssl version 0.9.7d 17 Mar 2004. I have created a dovecot user and a dove null user, assigned them their own login directories specifying the ksh shell and assigned them to their own groups. I have run the configure command successfully and am having trouble with the make. At first, I received the problem listed below: /bin/bash ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-test -DMODULE_DIR=\""/usr/local/lib/dovecot"\" -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -I/usr/sfw/include -MT iostream-openssl-context.lo -MD -MP -MF .deps/iostream-openssl-context.Tpo -c -o iostream-openssl-context.lo iostream-openssl-context.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-test -DMODULE_DIR=\"/usr/local/lib/dovecot\" -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -fno-builtin-strftime -I/usr/sfw/include -MT iostream-openssl-context.lo -MD -MP -MF .deps/iostream-openssl-context.Tpo -c iostream-openssl-context.c -fPIC -DPIC -o .libs/iostream-openssl-context.o iostream-openssl-context.c: In function `ssl_proxy_ctx_set_crypto_params': iostream-openssl-context.c:451: error: `SSL_OP_SINGLE_ECDH_USE' undeclared (first use in this function) iostream-openssl-context.c:451: error: (Each undeclared identifier is reported only once iostream-openssl-context.c:451: error: for each function it appears in.) I followed directions found in http://hg.dovecot.org/dovecot-2.2/rev/27ebd9552471 to resolve this problem (I believe). I am now seeing the following error: test-http-server.c: In function `main': test-http-server.c:122: error: size of array `type name' is negative *** Error code 1 make: Fatal error: Command failed for target `test-http-server.o' Current working directory /export/home/hanedo00/dovecot-2.2.5/src/lib-http *** Error code 1 The following command caused the error: fail= failcom='exit 1'; \ for f in x $MAKEFLAGS; do \ case $f in \ *=* | --[!k]*);; \ *k*) failcom='fail=yes';; \ esac; \ done; \ dot_seen=no; \ I have not had any luck thus far finding the solution for this error against test-http-server.o. Any assistance would be appreciated. Thanks, Don Haney This message and any attachments are solely for the use of intended recipients. The information contained herein may include trade secrets, protected health or personal information, privileged or otherwise confidential information. Unauthorized review, forwarding, printing, copying, distributing, or using such information is strictly prohibited and may be unlawful. If you are not an intended recipient, you are hereby notified that you received this email in error, and that any review, dissemination, distribution or copying of this email and any attachment is strictly prohibited. If you have received this email in error, please contact the sender and delete the message and any attachment from your system. Thank you for your cooperation

2 1

[Dovecot] Trouble with case-sensitive LDAP user logins
by Jason Discount 28 Aug '13

28 Aug '13

Hi All, I have a client running Dovecot-Postfix on Debian Squeeze. I'm using Dovecot from the Squeeze repository. # dovecot --version 1.2.15 I've implemented a central mail_location and am using one vmail user, as I thought this would be be the best approach for when it came time to implement Shared and Public Mailboxes. # dovecot -n # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-xen-686 i686 Debian 6.0.7 ext3 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3s managesieve listen(default): 127.0.0.1:143 listen(imap): 127.0.0.1:143 listen(pop3): 127.0.0.1:110 listen(managesieve): * ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_listen(managesieve): ssl_ca_file: /etc/ssl/certs/RapidSSL_CA_bundle.pem ssl_cert_file: /etc/ssl/certs/mail.example.com.2013.chain.pem ssl_key_file: /etc/ssl/private/example.2013.key login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_max_userip_connections(default): 40 mail_max_userip_connections(imap): 40 mail_max_userip_connections(pop3): 10 mail_max_userip_connections(managesieve): 10 mail_privileged_group: mail mail_uid: vmail mail_gid: vmail mail_location: maildir:/var/spool/dovecot/%d/%u mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve namespace: type: private separator: / inbox: yes list: yes subscriptions: yes lda: postmaster_address: postmaster(a)example.com mail_plugins: sieve quota log_path: /var/log/dovecot-deliver.log info_log_path: /var/log/dovecot-deliver.log auth default: mechanisms: plain login passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap-userdb.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail plugin: quota: maildir:User quota_rule: *:storage=1200M quota_rule2: Deleted Messages:storage=10%% quota_rule3: Deleted Items:storage=10%% quota_rule4: Trash:storage=10%% sieve: /var/spool/sieve/%d/%u/.dovecot.sieve sieve_dir: /var/spool/sieve/%d/%u All of the mail users are LDAP users only (not local UNIX users - not using nsswitch). dovecot-ldap-userdb.conf is a symbolic link to dovecot-ldap.conf # grep -v '^ *$#.*$\?$' /etc/dovecot/dovecot-ldap.conf uris = ldaps://mail.example.com/ dn = uid=mail,ou=Services,dc=example,dc=com dnpass = ****************** tls_require_cert = hard auth_bind = yes base = ou=People,dc=example,dc=com user_attrs = quota=quota_rule=*:storage=%$M user_filter = (&(objectClass=posixAccount)(mail=%u)) pass_attrs = uid=mail,userPassword=password pass_filter = (&(objectClass=posixAccount)(mail=%u)) Now, mail addressed to user(a)example.com and user(a)EXAMPLE.com correctly gets delivered to the correct mail location of /var/spool/dovecot/example.com/user, but the problem occurs when the user creates their account with uppercase characters in their username, e.g. user(a)exaMPLE.com. This creates a new directory at /var/spool/dovecot/exaMPLE.com/user, which ever receives any mail. Is it possible to ignore the case the user enters in their mail client and always land them at the lowercase mail directory? Where would this be done? Thank you, Jay

1 0