- dovecot - dovecot.org

[Dovecot] Confusion when trying to set up a first postfix+dovecot mailserver
by Hans J. Albertsson 22 Jul '12

22 Jul '12

I'm trying to set up a first test for a dovecot + postfix (+ many other things) mail server for about 1000 accounts, and I keep stumbling on confusing inconsistencies in the HowTo documents I'm trying to follow. I tried to do a simple setup with virtual users using a howto saying it was for just that and that it's for Dovecot 2.x, and it shows a few text chunks to put in files, and then says it's better to do the changes in the example-config conf file.... And then the whole structure of config files and dirs is totally different from what is implied in the howto. And of course it won't run. Probably because of the structure of a conf.d dir is multiple files, and the instructions are explicitly written for the case of having a single conf file. Can anyone suggest an order in which to read docs that will take me thru w/o being totally confusing? I would very much like to be able to enable bit by bit, rather than have to understand all of dovecot before I can even begin to test it. P.S: I want to setup a server using postfix+dovecot+tls+virtualusers+maildir+dspam+mailman, at least that's the target I'm aiming for. Please suggest a good HowTo for this setup that will not be too confusing. Also, Sorry if I sound like a whining kid: I am new to dovecot and postfix, but I was a software support engineer for Sun for ages, and I should really be able to manage this if I just had some consistent and non-confusing HowTo or Tutorial to follow as a first try.

3 8

[Dovecot] Director for smtp-auth
by Patrick Westenberg 21 Jul '12

21 Jul '12

Hi all, isn't it possible to use the director functionality for smtp-auth too? I have a frontend system for imap and outgoing mails using sasl and I recognized that all sasl username/password combinations are accepted as these credentials aren't checked by the backend servers. Regards Patrick

2 2

[Dovecot] postfix/sendmail configuration
by Gary Partis 20 Jul '12

20 Jul '12

Hi all I have searched the net and cant find anything relating to this. In 15-lda.conf, the default sendmail is used to send messges from Dovecot, such as "out of hours" and "redirected" emails controlled by sieves. However, postfix/sendmail is looking in /etc/postfix/main.cf for the configuration file (as logged in /var/log/maillog), but I have the config file elsewhere, and I even have MAIL_CONFIG setup to point to the true config directory. Is there a method of setting 15-lda.conf sendmail config to ensure it uese the correct postfix config file? Thanks in advance Gary

2 1

Re: [Dovecot] Converting from Maildir format ?
by Nick＠5sg.eu 20 Jul '12

20 Jul '12

Hi Stan, >> I'm still trying to find out if anyone knows the correct >> way to either switch the existing Maildir multiple file >> format to the single file format I believe known as MBox. > Did you restart dovecot after the mailbox_location change? Yup... > Show 'dovecot -n' output It shows it - and 'plugin: convert_mail: mbox:%h/%u/mail' I also changed it in dovecot/conf.d/01-dovecot-postfix.conf Hi Charles, > format known as dbox Running v1.2.9 on Ubuntu v10.4 > The wiki/docs are pretty thorough for basic settings. That's where I got the mbox line above.. Thanks gentlemen, Nick. . . . . -- _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ . . . . . . . . ...---... (Stamp Out Spam and Save Our Servers) http://sosNow.ws -=[ do you know morse code ? ]=- . . . . . . . . _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/

3 2

[Dovecot] Append with literal+ and mailbox over quota
by Ewald Dieterich 19 Jul '12

19 Jul '12

I'm appending a mail with literal+ to a mailbox that is over quota: 1 APPEND INBOX {127+} From: <ewald.dieterich(a)fun.de> To: <ewald.dieterich(a)fun.de> Subject: Quota-Test Message-ID: <abcdefg(a)fun.de> Quota-Test 1 NO [OVERQUOTA] Quota exceeded (mailbox for user is full) 2 NOOP 1 BAD Error in IMAP command APPEND: Invalid arguments. 3 NOOP 3 OK NOOP completed. Somehow the first NOOP is considered to be part of the already failed APPEND. I have to add an empty line after to NO response for the NOOP to work: 1 APPEND INBOX {127+} From: <ewald.dieterich(a)fun.de> To: <ewald.dieterich(a)fun.de> Subject: Quota-Test Message-ID: <abcdefg(a)fun.de> Quota-Test 1 NO [OVERQUOTA] Quota exceeded (mailbox for user is full) 2 NOOP 2 OK NOOP completed. Can somebody confirm this to be bug? Here is the output of doveconf -n # 2.1.8: /usr/local/dovecot-orig/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.3 ext3 auth_debug = yes auth_verbose = yes debug_log_path = /var/log/dovecot/debug.log disable_plaintext_auth = no info_log_path = /var/log/dovecot/info.log log_path = /var/log/dovecot/error.log mail_debug = yes mail_location = mdbox:/var/spool/dovecot/%2.256Hu/%3.4096Hu/%u mail_plugins = notify mail_log quota acl namespace { inbox = yes location = prefix = INBOX. separator = . type = private } passdb { driver = pam } plugin { acl = vfile autocreate = INBOX.Drafts autocreate2 = INBOX.Sent autocreate3 = INBOX.Trash quota = dict:User quota::file:/var/spool/dovecot/%2.256Hu/%3.4096/%u/dovecot.dict quota_rule = *:bytes=2000 } ssl = no userdb { driver = passwd } protocol imap { mail_plugins = notify mail_log quota acl autocreate imap_quota imap_acl

1 1

[Dovecot] Disable W=<vsize> in filenames
by Daniel Pieper 19 Jul '12

19 Jul '12

Hi, I'm using Dovecot 2.1.8. Is it possible to deactivate the "W=" Maildir filename extension, so that dovecot not add it to maildir filenames?

2 1

[Dovecot] Converting from Maildir format ?
by Nick＠5sg.eu 19 Jul '12

19 Jul '12

Hi again, I'm still trying to find out if anyone knows the correct way to either switch the existing Maildir multiple file format to the single file format I believe known as MBox. Failing that, though it'll mean a LOT of work for me to manually convert all of the existing Maildirs, how do I get dovecot to work in future in MBox single file format. I tried entering 'mail_location = mbox:~/mail:INBOX=/%h/%u' in the 'dovecot.conf', but it still saves each message in a file of its own in the /new /cur /tmp directories ?? Thanks, Nick. . . . . -- _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ . . . . . . . . ...---... (Stamp Out Spam and Save Our Servers) http://sosNow.ws -=[ do you know morse code ? ]=- . . . . . . . . _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/ _/

3 2

[Dovecot] Make a whole mailbox read-only
by Sandro Tosi 19 Jul '12

19 Jul '12

Hello, i've found an old thread [1] where it was stated that a whole mailbox can be made read-only only setting the according permissions on the filesystem side. [1] http://www.mailinglistarchive.com/html/dovecot@dovecot.org/2011-12/msg00300… i'd like to check if it's still the only option we have with dovecot v2.0.18 . Regards, -- Sandro Tosi Product Engineer Shared Hosting Products R&D | Dada.pro eml sandro.tosi(a)register.it

3 5

Re: [Dovecot] Issues with Plus addressing and detail part of subaddress.
by Sean Kamath 19 Jul '12

19 Jul '12

On Jul 17, 2012, at 3:18 AM, Charles Marcus wrote: >> I really thought it would be a simple "here's what you missed", since >> the logs are relatively uninformative... > > The point is, what may appear to be uninformative to you may tell Timo (or someone else who knows what to look for) all they need to know to pinpoint the problem. Whilst I would normally agree, at the same time I've had a fair amount of experience with dovecot and sendmail (been running them for over 10 years). Pigeonhole is new to me, however. . . > One thing I did notice is that you are sending this mail from an internal IP... since most people use very different checks for such mail (bypassing many/most checks), maybe you should be testing from an external address (one that comes in from outside your network)? So I have a DMZ that houses the mail server for my domain, which is where the private addresses are. Connections are passed through the OpenBSD router to the mail server. So testing from an external address would be essentially the same (since the connection to the SMTP server talks to the sendmail process as the /usr/lib/sendmail process). Regardless, my original tests were sending mail from the Mac off-network. > Also, it is always recommended when setting up a new server to start with the latest version... for 2.0.x that would be 2.0.19, but the latest is 2.1.8... When I set it up, 2.0.13 _was_ the latest. :-) I was hoping to avoid the pain of recompiling dovecot and pigeonhole. Not that big a deal, I guess. . . >> lda_original_recipient_header = X-Original-To >> lmtp_save_to_detail_mailbox = yes > > Ok, I think this is the problem... > > Dovecot's LMTP currently does NOT preserve the x-original-to header... in fact, brought this up recently (I was one of the ones interested in Timo adding support for it) on this (and the postfix, which is what I use) on this very list: > > http://www.dovecot.org/list/dovecot/2012-April/065075.html > > Apparently, after Timo discussed this on the postfix list, he determined that it would not be a very significant change for him to make to add support for this header in LMTP and that he would get to it sooner than later, but as of now, it has not been added. Actually, I'm not using lmtp. I whacked the lmtp_save_to_detail_mailbox in an effort to see if that was the issue before I realized I don't have it turned on. dovecot.conf has: protocols = imap though in 20-managesieve.conf I have: protocols = $protocols sieve I just turned it off and restarted dovecot (though lmtp was not running) and re-ran the test with the same result. So, I think what's going on is pretty straightforward. The local mailer definition in the sendmail.cf file is: Mlocal, P=/usr/local/libexec/dovecot/dovecot-lda, F=lsDFMAw5:/|@qSPhn9, S=EnvFromL/HdrFromL, R=EnvToL/HdrToL, T=DNS/RFC822/X-Unix, A=/usr/local/libexec/dovecot/dovecot-lda -d $u This is more or less right out of the wiki. Since dovecot-lda is passed the -d option, it's using that (and only that) for delivery. Since there's no X-Original-To: header, it doesn't really have any option (since the non-envelope-to address might not exist, or point to something other than the end user's mailbox, etc). It would appear that I have two options: 1) Figure out what macro(s) is(are) valid to pass to dovecot-lda with the -a option in the sendmail config file (sendmail.cf). 2) Get sendmail to put "X-Original-To: <address>" in the header. Both would appear to be a sendmail issue, not a dovecot/pigeonhole issue. Everything I find on the web seems to center around how to use plus addressing to accept mail from multiple email address and filter it into a single address for delivery, only to have the local delivery agent break it back out again. That's not my issue. :-( Sean Sean

1 1

[Dovecot] doesn't work at all
by David Drexler 19 Jul '12

19 Jul '12

Hi, I can't seem to get dovecot to work. When I connect with thunderbird, tbird complains that it can't find the settings for my email. When I connect with evolution, it seems to go through all the motions but it doesn't pick up the waiting messages. Those messages are marked Status: O s if it had read them. The log file for tbird looks like this: Jul 18 17:03:21 why dovecot: imap-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: imap-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: imap-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: pop3-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: pop3-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: pop3-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: imap-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: pop3-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: imap-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: pop3-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 Jul 18 17:03:22 why dovecot: pop3-login: Aborted login (no auth attempts): rip=68.12.110.134, lip=184.176.6.227 The log file with evolution is: Jul 17 19:36:43 why dovecot: imap-login: Login: user=<ddrex>, method=PLAIN, rip=68. 12.110.134, lip=184.176.6.227, mpid=22717, TLS Jul 17 19:36:43 why dovecot: imap(ddrex): Debug: Effective uid=500, gid=500, home=/ home/ddrex Jul 17 19:36:43 why dovecot: imap(ddrex): Debug: fs: root=/home/ddrex/mail, index=, control=, inbox=/var/mail/ddrex Jul 17 19:46:17 why dovecot: imap(ddrex): Error: Next message unexpectedly corrupte d in mbox file /var/mail/ddrex at 1504 My conf file: # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-220.23.1.el6.x86_64 x86_64 CentOS release 6.2 (Final) base_dir = /var/run/dovecot/ imap_client_workarounds = "delay-newmail " listen = * mail_debug = yes mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail mbox_very_dirty_syncs = yes mbox_write_locks = fcntl passdb { driver = pam } pop3_client_workarounds = outlook-no-nuls oe-ns-eoh protocols = imap pop3 service imap-login { vsz_limit = 64 M } service pop3-login { vsz_limit = 64 M } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } -------------------------------------------------------------------- Thanks for any clues. dd

2 2