- dovecot - dovecot.org

[Dovecot] 2.0.14 doveadm proxy list segfault
by Tom Pawlowski 09 Feb '12

09 Feb '12

Hi Timo, Periodic segfaults with doveadm proxy list: root@director1:~) doveadm proxy list doveadm(root): Error: LIST failed: Disconnected Segmentation fault (core dumped) Sometimes it's just the 'LIST failed' error, other times it's the error with the segfault. Usually the first attempt to call it works, subsequent attempts fail. I've attached a strace log of it in action. -- Tom Pawlowski OIT-CSS System Administrator office: Hill 147 email: tompru(a)jla.rutgers.edu phone: (732) 445-2634

2 1

[Dovecot] Syncing shared mailboxes
by Knud Dombrowsky 09 Feb '12

09 Feb '12

Hi, while trying to sync the mailboxes of several users who use and share their mailboxes dsync prints this message: dsync-local(<user-who-uses-shared-mailbox>): Warning: Subscriptions file /home/<user-who-uses-shared-mailbox>/Maildir/subscriptions: Removing invalid entry: shared/<sharing-user>/<shared-folder> The problem is: Every user has to subscribe the shared folder again after each run of dsync... Is dsync capable of syncing shared mailboxes? Are there any preliminaries to do so? thanks in advance, Knud

2 1

[Dovecot] crash on shared folders if remote user has empty $home
by Peer Heinlein 09 Feb '12

09 Feb '12

Hi, in seldom cirumstances it's possible that the imap-process is crashing without write something usefule into the logfile. a) User foo exists, is happy and everything's alright b) He had a shared folder given from bar c) In our setup we have mailforwarding adresses without a valid $home in LDAP c) if user bar is changed from a user with into a mailforwarding adress, the user foo won't have an entry for $home any more, but still exists in LDAP. d) If foo logs in, dovecot's exploring the shared folders given from the non-existing user bar. But bar's entry in LDAP doesn't have $home any more. imap crashes and closes the TCP-connection immediately. root@dobby2:/etc/dovecot# telnet xxxxxxxx 143 Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE ACL UIDPLUS STARTTLS AUTH=PLAIN AUTH=LOGIN AUTH=CRAM-MD5 AUTH=DIGEST-MD5] Dovecot ready. Testing. a LOGIN foo xxxxx a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS ACL UIDPLUS QUOTA ACL RIGHTS=texk] Logged in a LIST "" "*" * BYE Internal error occurred. Refer to server log for more information. Connection closed by foreign host. Dec 22 21:57:41 dobby2 dovecot: master: Error: service(imap): child 18095 killed with signal 11 (core dumps disabled) e) This happens if mail_location=mdbox:%%h/mdbox is set in the shared folder namespace. If I set "mail_location=auto:" then Dovecot logs an error message, but is still possible to continue without any problems. Dec 22 21:33:59 dobby2 dovecot: imap(bar): Error: Namespace 'shared/bar/': Autodetection failed for auto: (home=/mail/foo/) -- Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030 / 40 50 51 - 0 Fax: 030 / 40 50 51 - 19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

2 2

[Dovecot] LSUB and subscribed folders
by Peer Heinlein 09 Feb '12

09 Feb '12

I have a strange behavior on a customer's server and I don't understand that: User "bar" has some folders and one shared folder from "foo" if I use the "LIST"-command, which should list AFAIK *all* folders: # telnet localhost 143 a login bar xxxx a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH LIST-STATUS ACL RIGHTS=texk] Logged in a LIST "" "*" * LIST (\HasNoChildren) "/" "Gesendete Objekte" * LIST (\HasNoChildren) "/" "Papierkorb" * LIST (\HasNoChildren) "/" "INBOX" * LIST (\HasNoChildren) "/" "Trash" * LIST (\HasNoChildren) "/" "Entw&APw-rfe" * LIST (\HasNoChildren) "/" "Spam" * LIST (\Noselect \HasChildren) "/" "shared/foo" * LIST (\HasNoChildren) "/" "shared/foo/INBOX" a OK List completed. Using the LSUB-command, which should only list subscribed folders I can see some more shared folders. AFAIK the output of LSUB must be always less then LIST: a LSUB "" "*" * LSUB () "/" "Entw&APw-rfe" * LSUB () "/" "Gesendete Objekte" * LSUB () "/" "INBOX" * LSUB () "/" "Papierkorb" * LSUB () "/" "Spam" * LSUB () "/" "Trash" * LSUB (\Noselect) "/" "shared/amerkel" * LSUB () "/" "shared/foo/Papierkorb/Ungelesene Mails" * LSUB () "/" "shared/foo/INBOX" * LSUB () "/" "shared/foo/INBOX/abc/Unterebene 1" * LSUB () "/" "shared/foo/INBOX/abc/Unterebene 1/Test6789" * LSUB () "/" "shared/foo/INBOX/abc/Unterebene 1/Test Unterornder" * LSUB () "/" "shared/foo/INBOX/abc/Unterebene 1/Tsfgnksfgnk" a OK Lsub completed. a logout * BYE Logging out a OK Logout completed. And why is /shared/foo/INBOX listed with "HasNoChildren"? IMHO that's looking buggy. And, btw: Looks like's not possible to use the "doveadm"-command to get a list of a user's complete folder list. Maybe "doveadm mailbox" should get some extra parameters to geht all folders / only subscribe folders / only shared folders: # doveadm mailbox list -u bar Gesendete Objekte Papierkorb INBOX Trash Entwürfe Spam -- Heinlein Professional Linux Support GmbH Linux: Akademie - Support - Hosting http://www.heinlein-support.de Tel: 030/405051-42 Fax: 030/405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

3 2

[Dovecot] doveadm altmove fails to pack messages?
by Lauri Alanko 09 Feb '12

09 Feb '12

Hello again. When I use doveadm altmove, I notice that it may result in some very small storage files in either the primary or the alternate storage location. I'm not quite sure, but it almost seems like every storage file that contains messages to be moved is simply split into two parts, even if a part might only contain a single message. This seems quite curious, since the idea of mdbox is after all to store as many messages in a single file as fits in mdbox_rotate_size, and dovecot-lda can quite successfully append messages to existing storage files. So why can't doveadm altmove? Is this the expected behavior, or is there something wrong with my setup? Thanks again, Lauri

2 1

[Dovecot] force-resync fails to recover all messages in mdbox
by Lauri Alanko 09 Feb '12

09 Feb '12

To my understanding, when using mdbox, doveadm force-resync should be able to recover all the messages from the storage files alone, though of course losing all metadata except the initial delivery folder. However, this does not seem to be the case. For me, force-resync creates only partial indices that lose messages. The message contents are of course still in the storage files, but dovecot just doesn't seem to be aware of some of them after recreating the indices. Here is an example. I created a test mdbox by syncing a mailing list folder from a mbox location: $ dsync -m haskell-cafe backup mdbox:~/dbox Then I switched the location to the new mdbox: $ /usr/sbin/dovecot -n # 2.0.15: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-0.bpo.1-amd64 x86_64 Debian wheezy/sid mail_fsync = never mail_location = mdbox:~/dbox mail_plugins = zlib passdb { driver = pam } plugin { sieve = ~/etc/sieve/dovecot.sieve sieve_dir = ~/etc/sieve zlib_save = bz2 zlib_save_level = 9 } protocols = " imap" ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol lda { mail_plugins = zlib sieve } Then I checked the number of messages we had in the new location: $ doveadm search all | wc 93236 186472 3625098 This was indeed the correct number, so the sync was fine: $ grep -c '^From .*..:..:.. ....$' ../mbox/haskell-cafe 93237 Then I removed all the indices and rebuilt them: $ mkdir bak $ mv mailboxes bak $ mv storage/dovecot.map.index* bak/ $ doveadm force-resync inbox doveadm(la): Warning: mdbox /home/la/dbox/storage: rebuilding indexes And what have we now: $ doveadm search all | wc 43864 87728 1699590 Somehow dovecot lost over half of the messages! This is really worrisome. It should always be possible to extract the plain mail content out from the storage, but currently it only _looks_ like it is possible: you get a problem in the indices, rebuild them, and then later migrate somewhere else. If you don't notice that you are missing mails, you may then eventually destroy the original mdbox storage files, thinking that their content is now safely elsewhere, when it really isn't. Lauri

2 3

[Dovecot] Fedora 16 configuration
by Cliff Hayes 09 Feb '12

09 Feb '12

Hello, I am trying to get dovecot to work on a fedora 16 install with sendmail. I have been able to get it to work in the past with dovecot.conf but not with the new conf.d directory and associated config files. I keep seeing this in maillog: Feb 7 14:28:59 sendmail dovecot: pop3-login: Aborted login (no auth attempts): rip=x.x.x.x, lip=x.x.x.x And the mail client comes back with username or password invalid. Is there instructions somewhere regarding fedora 16 installs? I found this one and tried it to no avail: http://www.server-world.info/en/note?os=Fedora_16&p=mail&f=2 Thanks in advance, Cliff

2 1

[Dovecot] openbsd and dovecot
by User Max 09 Feb '12

09 Feb '12

I'm setting up dovecot in OpenBSD OS. The problem is that I can't set up dovecot to use kerberos authentication via bsdauth which is "similar to pam" I try to test dovecot via telnet: telnet localhost pop3 user test +OK pass password -ERR [IN-USE] Temporary authentication failure and some strings from logs Feb 3 15:02:37 srv-mx-00 dovecot: auth: Error: bsdauth(rodin.m,127.0.0.1): getpwnam() failed: Operation not permitted Feb 3 15:02:46 srv-mx-00 dovecot: pop3-login: Disconnected (auth failed, 1 attempts): user=<rodin.m>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Feb 3 15:29:13 srv-mx-00 dovecot: auth: Error: bsdauth(test,127.0.0.1): getpwnam() failed: Operation not permitted What am I doing wrong? Here is the output of dovecot -n auth_krb5_keytab = /etc/kerberosV/krb5.keytab auth_mechanisms = plain login default_internal_user = _dovecot default_login_user = _dovenull disable_plaintext_auth = no first_valid_gid = 2000 first_valid_uid = 2000 last_valid_gid = 2000 last_valid_uid = 2000 mail_gid = vmail mail_location = maildir:/var/vmail/%u%Ud/Maildir mail_uid = vmail mbox_write_locks = fcntl mmap_disable = yes passdb { driver = bsdauth } service auth { unix_listener /var/spool/postfix/private/auth { group = _postfix mode = 0666 user = _postfix } } ssl_cert = </etc/ssl/dovecotcert.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } userdb { args = uid=2000 gid=2000 home=/var/mail/%Lu driver = static } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv }

3 3

[Dovecot] Slightly more intelligent way of handling issues in sdbox?
by Mark Zealey 09 Feb '12

09 Feb '12

Hi there, I was doing some testing on sdbox yesterday. Basically I did the following procedure: 1) Create new sdbox; deliver 2 messages into it (u.1, u.2) 2) Create a copy of the index file (no cache file created yet) 3) deliver another message to the mailbox (u.3) 4) copy back index file from stage (2) 5) deliver new mail Then the message delivered in stage 3 ie u.3 gets replaced with the message delivered in (5) also called u.3. Is it possible to try an open/access call on the mail file before overwriting it with the new message in case we have an issue where an older version of the index file is present (eg due to nfs latencies) ? I notice when you are expunging files you very carefully open them and read the header contents to make sure the guid is the same as in the index - any reason that this is not done when delivering? This is with lmtp on dovecot 2.0.16. I also noticed that index corruption in sdbox does not get automatically repaired. I know this is because the flags are stored in the index files so you'd get some loss of flags, but in many situations for us this auto-repair with flag loss would be better than having the mailbox locked out until we manually do a force-resync on it. (speaking of which, it would be great if force-resync also rebuilt the cache files if there are valid cache files around, rather than just doing away with them) Thanks, Mark

3 4

[Dovecot] user login on behalf of another user
by rog7993＠web.de 08 Feb '12

08 Feb '12

Hello, we are searching for a possibility to configure a user login on behalf of another user with a PAM backend. This reminds to the behavior of a master user. But a master user can access the mailboxes of all users. We need this more restricted. Example: User "user1" and "user2" shall get access to the mailbox "info". We define the accounts "info~user1" and "info~user2" with the same home directory like "info". Until now, we use a passwd-file backend. With this setup we can simply copy the password hash from "user1" to "info~user1" and from "user2" to "info~user2". But we intend to change the passdb backend from a flat file to PAM for authentication against Active Directory. This seems to be simple with pam_krb5. But then we can't simply copy password hashes anymore. Is their another possibility for configuring this? Surely the preferable alternative would be the use of ACLs to give acccess to other users mailboxes. But we started this setup with Dovecot 1.0 or 1.1. And with these versions, ACLs weren't available. And now we have too much accounts and clients, which are configured this way and can't change this for the short term. The passdb/userdb file from the above example looks like this: info:!:501:501:Info:/home/mail01/info:: info~user1:PASSWORD_USER1:501:501:Info:/home/mail01/info:: \ userdb_mail=maildir:~/Maildir: \ INDEX=/srv/dovecot/index/info: \ CONTROL=/srv/dovecot/control/info info~user2:PASSWORD_USER2:501:501:Info:/home/mail01/info:: \ userdb_mail=maildir:~/Maildir: \ INDEX=/srv/dovecot/index/info: \ CONTROL=/srv/dovecot/control/info user1:PASSWORD_USER1:501:501:Info:/home/mail01/user1:: user2:PASSWORD_USER2:501:501:Info:/home/mail01/user2:: Ingo Rogalsky

4 5

[Dovecot] Multiple userdb possible?
by Nikolaos Milas 07 Feb '12

07 Feb '12

Hello, I am running v2.0.13. In my dovecot.conf I have: userdb { args = /etc/dovecot/dovecot-usrdb-ldap.conf driver = ldap } passdb { args = /etc/dovecot/dovecot-passdb-ldap.conf driver = ldap } Is it legitimate to include multiple ldap userdb's, like: userdb { args = /etc/dovecot/dovecot-usrdb-ldap1.conf driver = ldap } passdb { args = /etc/dovecot/dovecot-passdb-ldap1.conf driver = ldap } userdb { args = /etc/dovecot/dovecot-usrdb-ldap2.conf driver = ldap } passdb { args = /etc/dovecot/dovecot-passdb-ldap2.conf driver = ldap } If it is legitimate (in case configuration is different, please correct me), in which sequence userdb's are evaluated? Thanks, Nick

2 2

[Dovecot] Configuration problem?
by Anne Wilson 07 Feb '12

07 Feb '12

I have a new Scientific Linux 6.1 mail server (dovecot -n below) and am seeing the following in the logs, with no idea what is happening: --------------------- Dovecot Begin ------------------------ Dovecot was killed, and not restarted afterwards. **Unmatched Entries** dovecot: imap(anne): Connection closed bytes=205614/894243: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=24296/89310: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=24526/76772: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=26254/75778: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=27948/134120: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=29304/116087: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=34802/914087: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=4457/11719: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=5322/184434: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=61388/106618: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=6164/21347: 1 Time(s) dovecot: imap(anne): Disconnected: Logged out bytes=7914/89868: 1 Time(s) dovecot: imap: Server shutting down. bytes=1309821/4473013: 1 Time(s) dovecot: imap: Server shutting down. bytes=14215/97371: 1 Time(s) dovecot: imap: Server shutting down. bytes=1459/9382: 1 Time(s) dovecot: imap: Server shutting down. bytes=1688/26161: 1 Time(s) dovecot: imap: Server shutting down. bytes=1705/5038: 1 Time(s) dovecot: imap: Server shutting down. bytes=3146/79269: 1 Time(s) dovecot: master: Dovecot v2.0.9 starting up (core dumps disabled): 1 Time(s) ---------------------- Dovecot End ------------------------- dovecot -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-131.0.15.el6.x86_64 x86_64 Scientific Linux release 6.1 (Carbon) mail_location = maildir:~/Maildir/ mbox_write_locks = fcntl passdb { driver = pam } protocols = imap ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } /etc/dovecot/dovecot.conf: - everything being defaults, as far as I can see, apart from these lines: # Protocols we want to be serving. protocols = imap listen = *, :: mail_location = maildir:~/Maildir/ maildir_copy_with_hardlinks = yes Is it really expecting an mbox file? I'm completely bogged down with this - my previous setup was fine, but the old config file doesn't work with this system. Any help and/or pointers would be greatly appreciated. Anne

2 4

[Dovecot] dsync error Mailbox has children, delete them first
by Jürgen Obermann 07 Feb '12

07 Feb '12

Hi, I use dsync to backup mailboxes from mbox format to mdbox on a remote system. The first run for a user with dsync is OK, but during the second there are lots of the following errors: dsync-remote(user): Error: Can't delete mailbox directory Example: Mailbox has children, delete them first I see no way how I could influence the order dsync deletes mailboxes. This happens with dovecot version 2.0.16 Thank you, Juergen Obermann

1 1

[Dovecot] ENVELOPE mishandling of Subject lines with quote(s)?
by Dinh Le 07 Feb '12

07 Feb '12

Hi, I am running dovecot version 1.2.9 on a Ubuntu 10.04 server. To obtain the message's header info from this dovecot imap server, I run the following imap command on a client side's imap session: . fetch 88:90 (envelope) which returns (in this case) ------------------------------------------------------------- * 88 FETCH (ENVELOPE ("Tue, 28 Oct 2008 15:45:35 -0500" "Linear Actuators Bring Flexibility to Packaging" (("Design World" NIL "subscription" "designworldonline.com")) (("Design World" NIL "subscription" "designworldonline.com")) (("Design World" NIL "subscription" "designworldonline.com")) ((NIL NIL "dinh" "flic.net")) NIL NIL NIL "<490779CF.00000E7D(a)ak119.mta.exacttarget.com>")) * 89 FETCH (ENVELOPE ("29 Oct 2008 15:44:03 -0500" {65} 2nd Edition of Brennesholtz/Stupp "Projection Displays" Available (("Insight Media" NIL "administrator" "insightmedia.info")) (("Insight Media" NIL "administrator" "insightmedia.info")) (("Insight Media" NIL "administrator" "insightmedia.info")) ((NIL NIL "dinh" "flic.net")) NIL NIL NIL "<20081029154358.0C359AE169595F1B(a)insightmedia.info>")) * 90 FETCH (ENVELOPE ("Thu, 30 Oct 2008 04:24:31 +0800 (SGT)" "6 new products Now Online!" (("Global Sources Product Alert" NIL "paservices" "globalsources.com")) (("Global Sources Product Alert" NIL "paservices" "globalsources.com")) (("Global Sources Product Alert" NIL "paservices" "globalsources.com")) (("Dinh Le" NIL "dinh" "flic.net")) NIL NIL NIL "<352725277.1225311871753.JavaMail.web(a)fuchsia3.globalsources.com>")) . OK Fetch completed. -------------------------------------------------------------- Notice that message 89's Subject line Subject: 2nd Edition of Brennesholtz/Stupp "Projection Displays" Available has quotes and this dovecot's ENVELOPE response failed to get parsed by a popular Perl module (Mail::IMAPClient::BodyStructure::Envelope). I have a hunch that this is dovecot's fault but I could be wrong. How should dovecot (or any imap server) deal with Subject lines with quotes inside ENVELOPE? ENVELOPE seems to encapsulate most of the important information and its format can be parsed cleanly and quickly. I prefer to fetch ENVELOP, at this point, rather than the other alternatives. Thanks for your help, Dinh

4 7

[Dovecot] Question about quota configuration
by przemek.orzechowski＠makolab.pl 06 Feb '12

06 Feb '12

Hi This is my first post here so i will be as precise as i can I'm trying to setup a quota system using dovecot postfix and procmail dovecot version 1.2.9 postfix version 2.7.0 I have succesfully modified dovecot config to use fs quota system (so far imap and pop3) It reports correct quotas to imap and pop3 clients (both user and group) What im tryin to do now is to modify postfix->procmail->dovecot config in a way that if user is over quota mail delivery is delayed instead of bouncing. (is this possible?) Second thing i would like to achive is that when authenticated users close to quota/group quota for example 10MB to quota limit try sending email theyr mail is rejected and preferably an email is generated telling them to free some space for new mails first. (is such a thing possible?) MS Exchange servers have such a feature and I would like to get such a functionality on my linux mailserver I'm trying to prevent a situation when mails are lost due to quota problems. This setup was initially a typical virtualmin installation with a system on single partition. Thanks in advance for all Your suggestions

7 8

[Dovecot] dovecot-antispam 1.3 and dovecot 1.2.17 fails with spool2dir
by Benny Pedersen 06 Feb '12

06 Feb '12

or have i missed something in compile or configure in dovecot.conf ? running on gentoo so i can compile if need another option, i just like to have it working so each user can train bayes global db no matter what user agent users using

1 0

[Dovecot] doveadm purge on shared storage
by Jan-Frode Myklebust 06 Feb '12

06 Feb '12

We've finally (!) started to put some users on mdbox instead of maildir, and now I'm wondering about the purge step. As we're running GPFS for the mailboxes (and dovecot director in front of every dovecot service), is it important to run the "doveadm purge -u $user" on the same host as $user is logged into to avoid index corruption ? If so, will we need to run the "doveadm purge" trough the dovecot director as well? -jf

2 1

Re: [Dovecot] Sieve notify messages
by Stephan Bosch 05 Feb '12

05 Feb '12

On 2/5/2012 4:57 PM, Andreas Muehlemann wrote: > Hi Stephan > > Thank you very much, the encodeurl and ?body= are the trick! > For posterity, please reply to the mailing list as well, especially when it is a success message ;) Regards, Stephan. > > On 02/05/2012 04:46 PM, Stephan Bosch wrote: >> On 2/5/2012 4:00 PM, Andreas Muehlemann wrote: >>> Hi All >>> >>> I'm using dovecot 2.0.16 with the pigeonhole plugin 0.25. >>> >>> I'm trying to use the notifiy mechanism from sieve to send >>> notifications when a mail arrives in the mailbox. The message is >>> checked to be a 8bit message, otherwise it is replaced by the >>> default message "Notification of new message." How can I create a >>> 8bit message body within the sieve script that is accepted by the >>> notification process? >>> >>> e.g. >>> notify >>> :message "Subject: ${subject}" >>> "mailto:email@domain.com"; >>> >>> Do I have to put the message body into the :message string? Or how >>> can I define a custom message body that is accepted by notify? >> >> If I understand you correctly, the following should be the solution >> for your issue: >> >> <SCRIPT> >> require "enotify"; >> require "variables"; >> require "encoded-character"; >> >> # Percent-encode the UTF-8 message >> # (I'm using encoded-character here, but you can use UTF8 directly of >> course) >> set :encodeurl "message" "In ${unicode:d6}sterreich m${unicode:e4}ht >> Herr M${unicode:fc}ller seinen Rasen ${unicode:fc}brigens auch >> ${unicode:fc}ber dem Durchschnitt schnell."; >> >> # Send the notification >> notify :message "Herr M${unicode:fc}ller m${unicode:e4}ht seinen >> Rasen" "mailto:user@example.com?body=${message}"; >> </SCRIPT> >> >> This sends the following message: >> >> <MESSAGE> >> X-Sieve: Pigeonhole Sieve 0.3.0 >> Message-ID: <dovecot-sieve-1328456217-863910-0(a)host.example.com> >> Date: Sun, 05 Feb 2012 16:36:57 +0100 >> Subject: Herr =?utf-8?q?M=C3=BCller_m=C3=A4ht?= seinen Rasen >> From: Postmaster <postmaster(a)example.com> >> To: user(a)example.com >> Auto-Submitted: auto-notified; >> owner-email="234234234234(a)ext2.domain.tld" >> Precedence: bulk >> X-Priority: 3 (Normal) >> Importance: Normal >> MIME-Version: 1.0 >> Content-Type: text/plain; charset=UTF-8 >> Content-Transfer-Encoding: 8bit >> >> In Österreich mäht Herr Müller seinen Rasen übrigens auch über dem >> Durchschnitt schnell. >> </MESSAGE> >> >> Regards, >> >> Stephan >

1 0

[Dovecot] Sieve notify messages
by Andreas Muehlemann 05 Feb '12

05 Feb '12

Hi All I'm using dovecot 2.0.16 with the pigeonhole plugin 0.25. I'm trying to use the notifiy mechanism from sieve to send notifications when a mail arrives in the mailbox. The message is checked to be a 8bit message, otherwise it is replaced by the default message "Notification of new message." How can I create a 8bit message body within the sieve script that is accepted by the notification process? e.g. notify :message "Subject: ${subject}" "mailto:email@domain.com"; Do I have to put the message body into the :message string? Or how can I define a custom message body that is accepted by notify? Best regards Andreas

2 1

[Dovecot] What does this /var/log/maillog message means?
by Andre Lopes 04 Feb '12

04 Feb '12

Hi, I'm, trying to configure Devcot(2.0.9). Here is my dovecot.conf: [code] protocols = imap pop3 lmtp log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/home/vmail/%d/%n/Maildir ssl_cert = /etc/pki/dovecot/certs/dovecot.pem ssl_key = /etc/pki/dovecot/private/dovecot.pem namespace { type = private separator = . prefix = INBOX. inbox = yes } protocol lda { log_path = /home/vmail/dovecot-deliver.log auth_socket_path = /var/run/dovecot/auth-master postmaster_address = postmaster(a)mailserver.com } service auth { user = root } passdb { driver = sql args = /etc/dovecot/dovecot-sql.conf } userdb { driver = static args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes } [/code] I can start the service correctly: [code] [root@mailserver dovecot]# service dovecot start Starting Dovecot Imap: [ OK ] [/code] But when I go to "/var/log/maillog" I get this: [code] Feb 3 14:37:59 www dovecot: master: Warning: Killed with signal 15 (by pid=16757 uid=0 code=kill) Feb 3 14:38:03 www dovecot: master: Dovecot v2.0.9 starting up (core dumps disabled) [/code] What does this mean? I'm doing something that is not correct? Best Regards,

2 1

[Dovecot] Managesieve Build failure
by Ralf Hildebrandt 04 Feb '12

04 Feb '12

I pulled the recent dovecot-2.0-pigeonhole and dovecot 2.0.x trees and rebuild, got this error today: ... make[3]: Leaving directory /usr/src/dovecot-2.0/dovecot-2.0-pigeonhole/src/managesieve' make[2]: Leaving directory /usr/src/dovecot-2.0/dovecot-2.0-pigeonhole/src/managesieve' Making install in managesieve-login make[2]: Entering directory /usr/src/dovecot-2.0/dovecot-2.0-pigeonhole/src/managesieve-login' /bin/bash ../../libtool --tag=CC --mode=link gcc -I/usr/src/dovecot-2.0/dovecot-2.0/src/config -DPKG_LIBEXECDIR=\""/usr/local/libexec/dovecot"\" -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -module -avoid-version -g -Wl,--as-needed -o libmanagesieve_login_settings.la -rpath /usr/local/lib/dovecot/settings libmanagesieve_login_settings_la-managesieve-login-settings.lo libmanagesieve_login_settings_la-managesieve-login-settings-plugin.lo -lrt gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/src/dovecot-2.0/dovecot-2.0 -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-dict -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-dns -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-mail -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-imap -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-fs -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-charset -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-index -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-storage -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-storage/index -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-storage/index/raw -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-master -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-settings -I/usr/src/dovecot-2.0/dovecot-2.0/src/lib-auth -I/usr/src/dovecot-2.0/dovecot-2.0/src/login-common -I../.. -I../../src/lib-managesieve -g -Wl,--as-needed -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -MT managesieve-proxy.o -MD -MP -MF .deps/managesieve-proxy.Tpo -c -o managesieve-proxy.o managesieve-proxy.c managesieve-proxy.c: In function ‘managesieve_proxy_parse_line’: managesieve-proxy.c:334:19: error: ‘const struct login_settings’ has no member named ‘verbose_auth’ make[2]: *** [managesieve-proxy.o] Error 1 -- Ralf Hildebrandt Geschäftsbereich IT | Abteilung Netzwerk Charité - Universitätsmedizin Berlin Campus Benjamin Franklin Hindenburgdamm 30 | D-12203 Berlin Tel. +49 30 450 570 155 | Fax: +49 30 450 570 962 ralf.hildebrandt(a)charite.de | http://www.charite.de

2 1

[Dovecot] Vacation via database
by list＠airstreamcomm.net 04 Feb '12

04 Feb '12

We are moving our inbound mail to use dovecot LMTP in the near future and we are looking for suggestions on how to implement a mysql based vacation system. If anyone has experience with this, good or bad please let us know.

5 6

[Dovecot] LDAP auth improvements
by Timo Sirainen 03 Feb '12

03 Feb '12

v2.1 supports now multiple LDAP fields in a template e.g.: user_attrs = \ homeDirectory=home, \ uidNumber=uid, \ gidNumber=gid, \ =mail=%{ldap:mailboxFormat}:%{ldap:homeDirectory} which is the same as: user_attrs = \ =home=%{ldap:homeDirectory}, \ =uid=%{ldap:uidNumber}, \ =gid=%{ldap:gidNumber}, \ =mail=%{ldap:mailboxFormat}:%{ldap:homeDirectory} I was also thinking about adding an alternative simplified syntax for this: user_attrs { home = %{ldap:homeDirectory} uid = %{ldap:uidNumber} gid = %{ldap:gidNumber} mail = %{ldap:mailboxFormat}:%{ldap:homeDirectory} } Any ideas for further improvements before I do this change? One thing I'm still wondering about is what I should do when LDAP returns multiple values. Like perhaps: acl_groups = %{ldap:aclGroups:,} Which would mean that all the aclGroups values would be joined together separated by "," characters. And a bit more complex with multiple gidNumbers: gid = %{ldap:gidNumber[0]} mail_access_groups = %{ldap:gidNumber[1:]:,}

2 1

[Dovecot] Errors starting Dovecot
by Andre Lopes 03 Feb '12

03 Feb '12

Hi, I'm new to Dovecot. I'm trying to start Dovecot(2.0.9) but I'm getting an error. I think the error is because I'm doing a tutorial for an old version of Devcot(1.x.x). What I get is the following: [code] [root@mailserver dovecot]# service dovecot start Starting Dovecot Imap: doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1: protocols=imaps is no longer necessary, remove it doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:1: protocols=pop3s is no longer necessary, remove it doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:5: ssl_cert_file has been replaced by ssl_cert = <file doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:6: ssl_key_file has been replaced by ssl_key = <file doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:8: namespace private {} has been replaced by namespace { type=private } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:24: add auth_ prefix to all settings inside auth {} and remove the auth {} section completely doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:25: auth_user has been replaced by service auth { user } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:27: passdb sql {} has been replaced by passdb { driver=sql } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:31: userdb static {} has been replaced by userdb { driver=static } [ OK ] [/code] My dovecot.conf have the following: [code] protocols = imap imaps pop3 pop3s log_timestamp = "%Y-%m-%d %H:%M:%S " mail_location = maildir:/home/vmail/%d/%n/Maildir ssl_cert_file = /etc/pki/dovecot/certs/dovecot.pem ssl_key_file = /etc/pki/dovecot/private/dovecot.pem namespace private { separator = . prefix = INBOX. inbox = yes } protocol lda { log_path = /home/vmail/dovecot-deliver.log auth_socket_path = /var/run/dovecot/auth-master postmaster_address = postmaster(a)example.com } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } auth default { user = root passdb sql { args = /etc/dovecot-sql.conf } userdb static { args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes } socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = vmail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } [/code] Any clues on how can I adapt this configuration file to Dovecot 2.0.9? Best Regards,

1 0

[Dovecot] Doubts about dsync, mdbox, SIS
by Jan-Frode Myklebust 03 Feb '12

03 Feb '12

I've been running continous dsync backups of our Maildirs for a few weeks now, with the destination dsync server using mdbox and SIS. The idea was that the destination server would act as a warm copy of all our active users data. The active servers are using Maildir, and has: $ df -h /usr/local/atmail/users/ Filesystem Size Used Avail Use% Mounted on /dev/atmailusers 14T 12T 2.2T 85% /usr/local/atmail/users $ df -hi /usr/local/atmail/users/ Filesystem Inodes IUsed IFree IUse% Mounted on /dev/atmailusers 145M 113M 33M 78% /usr/local/atmail/users very little of this is compressed (zlib plugin enabled during christmas). I'm surprised that the destination server is so large, was expecting zlib and mdbox and SIS would compress it down to much less than what we're seeing (12TB -> 5TB): $ df -h /srv/mailbackup Filesystem Size Used Avail Use% Mounted on /dev/mapper/mailbackupvg-mailbackuplv 5.7T 4.8T 882G 85% /srv/mailbackup Lots and lots of the attachement storage is duplicated into identical files, instead of hard linked. When running "doveadm purge -u $user", we're seeing lots of Error: unlink(/srv/mailbackup/attachments/c3/17/c317b32b97688c16859956f11b803e3bba434349-057274283bb51f4f917e0000bf34f6ab) failed: No such file or directory "/srv/mailbackup/attachments/c3/17/c317b32b97688c16859956f11b803e3bba434349-057274283bb51f4f917e0000bf34f6ab" is missing, but there are 205 other copies of this file named /srv/mailbackup/attachments/c3/17/c317b32b97688c16859956f11b803e3bba434349-* with identical sha1sum. Also we see corrupted indexes during the purge. This makes me quite uncertain if dsync is a workable backup solution.. or if we can trust mdboxes. Also on the source side, during dsync, we see too many problems. Some samples: Error: Mailboxes don't have unique GUIDs: 08b46439069d3d4db0490000e671bf84 is shared by INBOX and INBOX Error: command BOX-LIST failed Error: Worker server's mailbox iteration failed Error: read() from worker server failed: EOF Error: Failed to sync mailbox INBOX.ferie 2006.: Invalid mailbox name Error: read() from proxy client failed: EOF Error: Unexpected finish reply: 1 596fec275888dbd89f6d1f5356c22db6 3720 0 \dsync-expunged 0 Error: Unexpected reply from server: 1 12200572a70726fca946da6f9378dc03 3721 0 \dsync-expunged 0 Error: Failed to sync mailbox INBOX.INBOX.Gerda: Mailbox doesn't exist: INBOX/Gerda Error: command BOX-LIST failed Error: read() failed: Broken pipe Panic: file dsync-worker-local.c: line 1678 (local_worker_save_msg_continue): assertion failed: (ret == -1) Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0 [0x367703c680] -> /usr/lib64/dovecot/libdovecot.so.0(default_fatal_handler+0x35) [0x367703c765] -> /usr/lib64/dovecot/libdovecot.so.0 [0x367703bb93] -> /usr/bin/dsync [0x40f48d] -> /usr/bin/dsync [0x40f589] -> /usr/bin/dsync(dsync_worker_msg_save+0x8e) [0x40eb3e] -> /usr/bin/dsync [0x40d71a] -> /usr/bin/dsync [0x40cdbf] -> /usr/bin/dsync [0x40d105] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_call_io+0x48) [0x3677047278] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0xd5) [0x36770485c5] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x2d) [0x367704720d] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x3677035a83] -> /usr/bin/dsync(main+0x71e) [0x406c4e] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3e3941d994] -> /usr/bin/dsync [0x406369] Do you have any idea for what our problems might be? Should we: avoid SIS ? avoid doing Maildir on one side and mdbox on the other? try other dovecot version for dsync? anything else? -jf ------------- destination server, running dovecot v2.0.14 -------- mail_attachment_dir = /srv/mailbackup/attachments mail_location = mdbox:~/mdbox mail_plugins = zlib mdbox_rotate_size = 5 M namespace { inbox = yes location = prefix = INBOX. separator = . type = private } passdb { driver = static } plugin { zlib_save = gz zlib_save_level = 9 } protocols = service auth-worker { user = $default_internal_user } service auth { unix_listener auth-userdb { mode = 0600 user = mailbackup } } ssl = no userdb { args = home=/srv/mailbackup/%256Hu/%d/%n driver = static } -------------/destination server -------- -jf

3 7