- dovecot - dovecot.org

Re: [Dovecot] How to upgrade a running Dovecot?
by Jerry Yeager 05 Oct '07

05 Oct '07

On Oct 5, 2007, at 12:41 PM, dovecot-request(a)dovecot.org wrote: > > ---------------------------------------------------------------------- > > Message: 1 > Date: Fri, 5 Oct 2007 10:25:49 +0100 > From: Mike Brudenell <pmb1(a)york.ac.uk> > Subject: Re: [Dovecot] How to upgrade a running Dovecot? > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Message-ID: <B9A4EC9A-82C0-4250-BC98-606695775041(a)york.ac.uk> > Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed > > Hi, Jerry/et al - > Hello Mike, (stuff chomped out) > >>> Scenario 2: Altered SSL Certificates >>> ===================================== >>> I need to replace our current certificates and have prepared new >>> files containing the replacement certificate and private key. Am I >>> right in thinking that I can simply modify dovecot.conf to point at >>> the new files and send a HUP signal to dovecot? Specifically, will >>> new connections use the revised certificates, and existing >>> connections continue to work OK without interruption? >> >> Ehh not really, the auth child processes can be killed and new ones >> started. See your next scenario question. > > ...So here you're saying that although the "dovecot" master process > re-reads the configuration file, it doing so has no effect on the > existing authenticator child processes? And is it these processes > that are dealing with the SSL connection? ... I'd have thought it was > either the "imap-login" or "imap" processes? > Just to be clear about this for myself, (instead of relying on the 'ol saying 'that is how it used to work' -- because I am switching over to 1.1 from 1.0.n your question takes on new relevance for me as well) I tested this and yes it works as before, the new files seem to be used for the new connections (all of the dovecot auth processes are killed on the HUP signal -- dovecot itself just rereads the conf file and new auth listeners are started -- assuming that you use Dovecot for the auth mechanism to Postfix) and existing connections seem to handle things okay. I did find something new (or I have not noticed it before) If you kill (not just restart) the Dovecot process itself and restart it with existing connections (someone was connected to IMAPS when you killed Dovecot) Dovecot will not restart, complaining that port 993 is taken already. This happens regardless of the shutdown_clients = yes/no setting. This may be particular to the new version 1.1, I do not know. > Jerry

1 0

[Dovecot] Thunderbird and imap alerts
by Marco De Benedetto 05 Oct '07

05 Oct '07

Is Thunderbird supposed to show alerts sent via post-login scripts as in the wiki example? dovecot-imapd 1.0.5-1 (Debian) Thunderbird (Icedove) 2.0.0.4 (Debian) # dovecot -n|grep 'mail_executable(imap)' mail_executable(imap): /usr/local/sbin/dovecot-alert.sh # cat /usr/local/sbin/dovecot-alert.sh #!/bin/sh echo "* OK [ALERT] Hello World." exec /usr/lib/dovecot/imap Logging in with Thunderbird I get this alert: "Mail server imap.example.org is not an IMAP4 server". -- Thank you, Marco De Benedetto

1 0

Re: [Dovecot] How to upgrade a running Dovecot?
by Jerry Yeager 05 Oct '07

05 Oct '07

> Have you considered sending out a message to each user to the effect that on some day, darned-early a.m. the system will be offline for 30 minutes for maintenance (no incoming email will be lost, etc., etc.). > Message: 3 > Date: Thu, 4 Oct 2007 13:57:03 +0100 > From: Mike Brudenell <pmb1(a)york.ac.uk> > Subject: [Dovecot] How to upgrade a running Dovecot? > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Message-ID: <06B4C604-41E3-4061-96B2-C7C719E21D49(a)york.ac.uk> > Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed > > Greetings - > > Could someone confirm how to perform various upgrades on a live > system running Dovecot please? > > > Scenario 1: Change to dovecot.conf > =================================== > If I make a change to dovecot.conf am I right in thinking I can > simply send a HUP signal to the main dovecot process to get it to re- > read the configuration file and act on its revised content? > Yes, this is correct. > > Scenario 2: Altered SSL Certificates > ===================================== > I need to replace our current certificates and have prepared new > files containing the replacement certificate and private key. Am I > right in thinking that I can simply modify dovecot.conf to point at > the new files and send a HUP signal to dovecot? Specifically, will > new connections use the revised certificates, and existing > connections continue to work OK without interruption? > > Ehh not really, the auth child processes can be killed and new ones started. See your next scenario question. > Scenario 3: Software Upgrade > ============================= > I build a particular version of Dovecot into the tree /usr/local/ > dovecot-A.B.C and then have a symlink called "dovecot" pointing at > the this directory. To upgrade I can then build the new version > into /usr/local/dovecot-X.Y.Z and test. > > To actually switch over the live service to the new X.Y.Z version do > I need to: > > a) Totally shut down the old A.B.C version of Dovecot, thereby > breaking all > open connections for users? or > > b) Assuming I am using "shutdown_clients = no" can I just kill the > master > "dovecot" process and then start up the new version? > See the preface, do the update when you typically have few folks using the system -- which gives you fewer complaints from users should things break on their end. > Ideally I want existing connections to remain running, but new > connections to start up using the new X.Y.Z version of Dovecot. > > The comment for "shutdown_clients" implies this, but also says: > > "This however means that after master process has died, the > client > processes can't write to log files anymore." > > So if I understand this correctly then with "shutdown_clients = no" > in force then the sequence and behaviour is this? ... > > 1. Old version A.B.C of Dovecot running, clients can log > through the > master "dovecot" process to the logfiles. > > 2. Kill the old master "dovecot" process, start new X.Y.Z > version up. > > 3. New connections get served by version X.Y.Z. > Old connections DON'T get killed and can continue, BUT can > no longer > write anything to the logfiles? > > > With many thanks, > Mike B-) > > -- > The Computing Service, University of York, Heslington, York Yo10 > 5DD, UK > Tel:+44-1904-433811 FAX:+44-1904-433740 > > * Unsolicited commercial e-mail is NOT welcome at this e-mail > address. * > > > > >

4 3

[Dovecot] Compiling drac.c on a 64 bit system
by Robin Atwood 05 Oct '07

05 Oct '07

I have just installed dovecot and want to set up the drac interface. However, when I compile drac.c I get the following link errors; anybody know what the right compile options are for a 64 bit system? I have a Gentoo Linux system using the amd64 architecture. gcc -Wall -W -shared -fPIC -DHAVE_CONFIG_H -I$dovecot -I$dovecot/src/lib drac.c -o drac.so -ldrac /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../x86_64-pc-linux-gnu/bin/ld: /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../lib64/libdrac.a(dracauth.o): relocation R_X86_64_32S against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/lib/gcc/x86_64-pc-linux-gnu/4.1.2/../../../../lib64/libdrac.a: could not read symbols: Bad value collect2: ld returned 1 exit status TIA -Robin. -- ---------------------------------------------------------------------- Robin Atwood. "Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst" from "Mandalay" by Rudyard Kipling ----------------------------------------------------------------------

2 2

[Dovecot] Deliver prints passwort to the syslog
by Dominik Schulz 05 Oct '07

05 Oct '07

Hi, I've got the problem that dovecot's deliver prints the authentification information to the syslog. Like this: Sep 18 12:11:22 mail deliver(user(a)domain.tld): auth input: user=user(a)domain.tld Sep 18 12:11:22 mail deliver(user(a)domain.tld): auth input: password=XXXX Sep 18 12:11:22 mail deliver(user(a)domain.tld): auth input: home=/home/mail/domain.tld/user Sep 18 12:11:22 mail deliver(user(a)domain.tld): auth input: uid=8 Sep 18 12:11:22 mail deliver(user(a)domain.tld): auth input: gid=8 I guess that it's only a configuration option but right now I can't figure out which one I need to change to turn this off. Any help would be appreciated. Thanks in advance. Best Regards Dominik

3 3

[Dovecot] UIDL and IMAP
by Kenneth Porter 04 Oct '07

04 Oct '07

I finally got my aging FC2 box retired and moved all email to my new CentOS 5 box. My site is all-IMAP, no POP3. I have one user who downloads all email to Thunderbird on his laptop so that he can work offline while away from a network connection (eg. on an airplane). I forgot to change the pop3_uidl_format setting as described here: <http://wiki.dovecot.org/Upgrading/1.0> So he was seeing repeated downloads of all his mail (about 300 MBytes) every time he connected. (I'm not sure why it didn't happen only the first time.) I changed the setting and haven't heard back whether if fixed things for him. Does this setting in fact get used by IMAP? It's in the POP3 section, so I'm wondering if it takes effect when one is using IMAP from the client. CentOS 5 is currently shipping with: dovecot-1.0-1.2.rc15.el5 I may look for a newer release. CentOS, based on RHEL, is intended to be a conservative distro, so I'll probably need to look at RPMForge (an addon repository of more exotic and bleeding edge software) to see if it offers a newer release.

2 1

[Dovecot] Dovceot user pop3 last connect info?
by Tim Tyler 04 Oct '07

04 Oct '07

Dovecot experts, I am a newbie to Dovecot. I am in the process of replacing qpopper with dovecot to support pop 3 clients. I have installed the latest version of Dovecot on Fedora Core 6. Everything seems to be working fine using ldap, etc. However, with qpopper, I used to have .pop.username files which would give me a time stamp of the last time a user established a pop3 connection. I know that Dovecot has logs of connection in the /var/log/maillog files, but these files rotate out over a relatively short period of time. Is there a method by which one can keep track of the last time a pop3 connection was established for each user when using Dovecot? Tim Tyler Network Engineer - Beloit College tyler(a)beloit.edu

2 1

[Dovecot] Namespace "hidden" option not working?
by Ed W 04 Oct '07

04 Oct '07

I either misunderstand the namespace hidden option, or else perhaps it's not working correctly in 1.0.5? dovecot.conf # default namespace namespace private { separator = / prefix = inbox = yes hidden = yes } # for backwards compatibility: namespace private { separator = . prefix = INBOX. inbox = yes } Then login and test s6jh LIST "" "*" SND: <<< len(939) Comp_len(118) Time:0.137985 * LIST (\HasNoChildren) "/" "Diary" * LIST (\HasNoChildren) "/" "Spam" * LIST (\HasNoChildren) "/" "Sent" * LIST (\HasNoChildren) "/" "Archive" * LIST (\HasNoChildren) "/" "Sent Items" * LIST (\HasNoChildren) "/" "Subdir" * LIST (\HasNoChildren) "/" "Junk E-mail" * LIST (\HasNoChildren) "/" "Trash" * LIST (\HasNoChildren) "/" "Drafts" * LIST (\HasNoChildren) "/" "Deleted Items" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\HasNoChildren) "." "INBOX.Diary" * LIST (\HasNoChildren) "." "INBOX.Spam" * LIST (\HasNoChildren) "." "INBOX.Sent" * LIST (\HasNoChildren) "." "INBOX.Archive" * LIST (\HasNoChildren) "." "INBOX.Sent Items" * LIST (\HasNoChildren) "." "INBOX.Subdir" * LIST (\HasNoChildren) "." "INBOX.Junk E-mail" * LIST (\HasNoChildren) "." "INBOX.Trash" * LIST (\HasNoChildren) "." "INBOX.Drafts" * LIST (\HasNoChildren) "." "INBOX.Deleted Items" * LIST (\HasChildren) "." "INBOX" The idea was to support an old client using Courier like access whilst still letting new clients access using the normal process Ed W

3 6

[Dovecot] Disable imap proxy access
by Dominique Feyer 04 Oct '07

04 Oct '07

I work on a dovecot cluster (15 servers) we need to add a new storage array and move the data for a list of user from the old storage to the new one. We use dovecot proxy to redirect imap and pop3 to the same server everytime. How to disable pop3 and imap access during the data migration process (duration 5 minutes to 10 minutes). Can i send a custom error message to our users ? Thanks for your help Dominique Feyer

4 4

[Dovecot] Postfix with Deliver (LDA) - user unknown
by Karin Gregorec 04 Oct '07

04 Oct '07

Good Day All! I am attempting to configure deliver as our LDA. I am also configuring the server to use Postfix instead of Sendmail. I have followed the all the documentation and examples I could find. Below are my Dovecot and Postfix configs. Can someone please smack me upside the head and tell me why I am getting "user unknown" errors? If i don't use deliver as the LDA, all works perfectly. Help... TIA, glenn ========== *** Dovecot Config *** dovecot -n # 1.0.5: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/maillogs/dovecot.log protocols: imap imaps pop3 pop3s ssl_cipher_list: ALL:!LOW disable_plaintext_auth: no verbose_ssl: yes login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting: GID Ready login_log_format_elements: user=<%u> service=%s authMethod=%m rIP=%r lIP=%l encryption=%c login_max_processes_count: 256 verbose_proctitle: yes first_valid_uid: 5000 last_valid_uid: 10000 first_valid_gid: 0 mail_extra_groups: mail mail_location: maildir:~/Maildir dotlock_use_excl: yes fsync_disable: yes maildir_copy_with_hardlinks: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_process_size: 1024 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_logout_format(default): top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_logout_format(imap): top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_logout_format(pop3): top=%t/%T, retr=%r/%R, del=%d/%m, size=%s auth default: cache_size: 1024 cache_ttl: 604800 verbose: yes passdb: driver: pam args: cache_key=%Lu userdb: driver: passwd socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: maildrop plugin: quota: maildir:storage=10000000:ignore=Trash *** Postfix main.cf *** alias_database = hash:/etc/mail/postfix/aliases alias_maps = hash:/etc/mail/postfix/aliases biff = no command_directory = /usr/local/sbin daemon_directory = /usr/local/libexec/postfix debug_peer_level = 2 debugger_command = PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont; echo where) | gdb $daemon_directory/$process_name $process_id 2>&1 >$config_directory/$process_name.$process_id.log & sleep 5 #### Dovecot LDA Service - http://wiki.dovecot.org/LDA/Postfix dovecot_destination_recipient_limit = 1 home_mailbox = Maildir/ html_directory = no inet_interfaces = all mail_owner = postfix mail_spool_directory = /var/mail mailq_path = /usr/local/bin/mailq manpage_directory = /usr/local/man message_size_limit = 12000000 mydestination = $myhostname, localhost.$mydomain, localhost mydomain = geekinternetdevelopment.com myhostname = superman.geekinternetdevelopment.com mynetworks = 72.18.193.0/24, 127.0.0.0/8 newaliases_path = /usr/local/bin/newaliases queue_directory = /var/spool/postfix readme_directory = no sample_directory = /usr/local/etc/postfix sendmail_path = /usr/local/sbin/sendmail setgid_group = maildrop smtpd_banner = $myhostname NO WHAMMIES!!! virtual_gid_maps = static:5000 virtual_mailbox_base = /var/mailboxes virtual_mailbox_domains = hash:/etc/mail/postfix/vdomains virtual_mailbox_maps = hash:/etc/mail/postfix/vmailboxes virtual_minimum_uid = 1000 virtual_transport = dovecot virtual_uid_maps = static:5000 unknown_local_recipient_reject_code = 550 *** Postfix master.cf *** ...snip... dovecot unix - n n - - pipe flags=DRhu user=maildrop:maildrop argv=/usr/local/libexec/dovecot/deliver -e -d ${recipient}

4 3