- dovecot - dovecot.org

[Dovecot] dsync 2.0.x versus 2.1.x field report
by Michael Grimm 24 Feb '12

24 Feb '12

Hi -- I used to run two mailservers with identical MX priorities (poor man's fail-over approach) with Maildir mail folders accessed by Dovecot. Synchronization has been achieved using unison, mirroring all files except dovecot index files. Once in a while some oddities could be observed, like reappearing of deleted mails, duplicates and such alike. But the all-over performance was quite good. Then I wanted to migrate to mdbox, and I became interested in dsync. I did start with 2.0.16 a couple of month ago, and recently upgraded to 2.0.18. My experience with the 2.0.x dsync version is as follows (synchronization time: every minute): -- As long as mail is not stored in corresponding mailboxes at both servers at the same time, all mailboxes become synchronized perfectly well, and no oddites like reappearing of deleted mails or generation of duplicates can be observed. -- If mail is stored into corresponding mailboxes at both servers simultaneously in between two synching runs, it gets worrying. -- If I do run dsync without '-f' those two mailboxes end up in becoming asynchronous. -- If I do run dsync with '-f' both mailboxes will become synchronized let's say in 95% of all synchronization runs. BUT in 5%, I do experience asynchronicity. Here a 'doveadm force-resync' sometimes works, but not always, what worries me a lot. -- I can see the missing mail in the mdbox storage file using UNIX' little helpers but not with the help of dovecot tools. (Or I was unable to use them properly.) -- Modifying MX priorities in a way, that I do now have a primary and backup mailserver scenario, very much reduced the risk of losing legitimate mail. -- But sometimes I do lose some syslog mail being produced at the same time. Therefore I modified runtimes in way to omit synchronicity. Ok, I could have lived with that, but I was anxious to learn, if 2.1.x dsync would perform better ;-) Here my observations sofar (synchronization time: every minute): -- No losses sofar using 'doveadm sync' with '-f' -- A *lot* of reappearing deleted mails or mails moved from one mailbox to the other. -- Quite often I am unable to delete those mails using client functionality (Mail.app, Roundcube). -- In those cases one needs to stop synchronization, run 'doveadm force-resync', delete all reappearing mail (quite a lot sometimes), empty 'Deleted' folders, and finally run 'doveadm purge'. -- Running of 'doveadm sync' without '-f' doesn't improve the situation. Still I do have to struggle with reappearing mails, and sometimes with appearing duplicates. -- I do have a test setup running for 24 hours now, where I do generate test mails in a 6 minutes interval at both servers. Mails become synchronized perfectly well, irrespectively if '-f' is set or not. This is a major improvement to 2.0x. dsync (sofar). -- But running the synchronization without '-f' still shows a *lot* of reappering mail, though. I do have the feeling that dsync became very much improved with regard to missing mail in synchronization, good. But those reappearing mails make me think about switching back to 2.0.x dsync and live with the drawback of preventing mail to arrive synchronously at both servers. Is someone out there experiencing a similar behaviour with dsync 2.1.x regarding reappearing, thus indelible mail? Regards, Michael

1 0

[Dovecot] Creating and interacting with array inside plugin
by Alex Baule 24 Feb '12

24 Feb '12

Hi Timo.... I Follow your instruction to look inside quota plugin to get the notification from dovecot that expunged a message, that's Ok. Follow the quota, it's use a array to keep all uids from a email expunged, to compare with uid that is got in notify_sync, that's OK too, but to me i need to keep uid and a char* with my body name, to erase it too. I made this: struct emexis_ids_x_uis{ uint32_t ids; char *uis_file; }; struct emexis_mailbox { union mailbox_module_context module_ctx; ARRAY_DEFINE(expunge_uids, struct emexis_ids_x_uis); }; ok, inside my expunged rewrite function i create the array like quota does, and append it to my array. struct emexis_ids_x_uis append_uis; append_uis.ids = _mail->uid; append_uis.uis_file = bodyFile; array_append(&ebox->expunge_uids, &append_uis, 1); But when i do a foreach in this Array, my ids is OK, but my uis_file has tha same value every time (the value is the lasted value inserted). Append to UID array (156) --> (/storage/gss/emexis/common/t/33/88/t33889eb1bccd28fd6643ebc3ecf548b12a1ad095) Append to UID array (157) --> (/storage/gss/emexis/common/t/e3/35/te335c20e978e12d37ad0a35ae009245cd34080c0) Append to UID array (158) --> (/storage/gss/emexis/common/t/0b/83/t0b83efc253c34db35843fc89b655586d628cccaf) Calling Sync Expunged --> (156) Sync Expunged (156 == 156) --> (/storage/gss/emexis/common/t/0b/83/t0b83efc253c34db35843fc89b655586d628cccaf) Sync Expunged Match (156 == 156) --> (/storage/gss/emexis/common/t/0b/83/t0b83efc253c34db35843fc89b655586d628cccaf) Sync Expunged (157 == 156) --> (/storage/gss/emexis/common/t/0b/83/t0b83efc253c34db35843fc89b655586d628cccaf) Sync Expunged (158 == 156) --> (/storage/gss/emexis/common/t/0b/83/t0b83efc253c34db35843fc89b655586d628cccaf) Finish Calling Sync Expunged --> (156) Can i use a struct as a array Item ?? something is wrong with my array creation, append and etc ? Tks Timo !!

2 2

Re: [Dovecot] Why is dovecot involved in my smtp process
by Joseph Tam 23 Feb '12

23 Feb '12

From: "Peter A. Giessel" <pgiessel(a)mac.com>: > Not totally true. Typical cyrus sasl2 implementation used with > sendmail uses an imap server for smtp authentication. I recall having > to tweak the sasl2 configuration on my own sendmail server to talk > correctly with dovecot. I don't recall the exact tweaks. Just to make it clear to the OP, I have a Dovecot/Sendmail/SASL working just fine (which is independent of dovecot). I suspect Peter hit the nail on the head here. Look at the contents of $SASL_INSTALL/lib/Sendmail.conf Mine is (only) pwcheck_method:saslauthd which I think looks up my name service backend via the login and plain plugins. I'm a little hazy on how this was set up, but if you are able to successfully login without dovecot, then it appears you have some sort of authentication stack that will try IMAP first, then fallback to your the other method. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] Settings for authentication without an extra password file
by Keith Christian 23 Feb '12

23 Feb '12

Hello, I'm new to dovecot, and, due to having an older version of an OS installed on a test server, I'll be using an older version of dovecot (dovecot-1.0-1.2) to provide IMAP services. On this wiki page (http://wiki.dovecot.org/BasicConfiguration?highlight=%28passwd.dovecot%29) There are instructions for creating a separate dovecot password file: echo "$USER:{PLAIN}password" > passwd.dovecot sudo mv passwd.dovecot /etc So, it appears that two password files will be needed, one for dovecot and one for regular system logins. Is the statement above correct, or am I misreading something? Is there a setting in dovecot.conf which will authenticate IMAP using /etc/password and /etc/shadow, without a separate dovecot password file? ========Keith

2 1

[Dovecot] Why is dovecot involved in my smtp process
by Steve Campbell 23 Feb '12

23 Feb '12

I've been trying to get smtp auth set up for days. All my sendmail and sasl2 stuff seems to be proper, but the user can't use the system on port 587, which is where I require authorization. Now I see where messages are in my maillog of the type: auth: pam_unix(dovecot:auth) : authentication failure ........ Why is dovecot involved in my smtp processes and how do I fix this. I've got some very mad users. The 10-auth.conf file is pretty much stock except for allowing plain text logins. steve campbell

7 12

[Dovecot] Can't connect to my mail server (postfix + dovecot, IMAP) with Thunderbird
by GASPARD Kévin 23 Feb '12

23 Feb '12

I'm sorry, some one tell me my netstat (on IRC) is useless. Also my pastes will be destroyed in something like one day, that's stupid (that's originally for IRC), so this is the output of my : dovecot -n : http://pastebin.com/Tewcb7bm telnet : http://pastebin.com/6gY2puxF netstat -Nnap | grep "dovecot" : http://pastebin.com/yx2wxfWf Sorry for the error.

2 1

[Dovecot] Can't connect to my mail server (postfix + dovecot, IMAP) with Thunderbird
by GASPARD Kévin 23 Feb '12

23 Feb '12

Hi, I've a problem with Dovecot and Thunderbird. Actually I'm trying to setup a virtual host server mail with postfix + dovecot (2.0.9) on CentOS 6.2. This is my dovecot -n : http://pastebin.com/wZWAE5Cj (I guess the errors are not important, that's just saying there is some obsoletes values, I will fix that later until it's not inconvenient to setup correctly dovecot). I've a file to store password (/etc/dovecot/passwd) and when I'm trying to connect with telnet to my host on port 143 it works, after I can log myself with the command «a login user(a)domain.tld passwd» and it works, this is the entire output of the telnet connection : http://pastebin.com/h10cQVqf but actually when I'm trying to connect with thunderbird I've an error about the password and the login, this is a screenshoot : http://images.koshie.fr/TB_problem.png and to finish, there is nothing into the log... The password and the user are corrects ! Of course, dovecot and postfix are started, this is the netstat -a | grep "dovecot" : http://pastebin.com/bwfsS4Tf If you need more informations tell me. PS : Excuse me for my bad english, also I'm new with dovecot. Cordially, GASPARD Kévin

1 0

[Dovecot] v2.1.1 released
by Timo Sirainen 23 Feb '12

23 Feb '12

http://dovecot.org/releases/2.1/dovecot-2.1.1.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.1.tar.gz.sig v2.1.0 had a couple of bugs, but overall people have been pretty quiet about it. I'm hoping v2.1.2 won't need to be released for many more weeks. :) BTW. v2.2 branch has also been opened in hg. Not much stuff in there yet though. + dsync: If message with same GUID is saved multiple times in session, copy it instead of re-saving. - acl plugin + autocreated mailboxes crashed when listing mailboxes - doveadm force-resync: Don't skip autocreated mailboxes (especially INBOX). - If process runs out of fds, stop listening for new connections only temporarily, not permanently (avoids hangs with process_limit=1 services) - auth: passdb imap crashed for non-login authentication (e.g. smtp).

1 0

Re: [Dovecot] Problem with Postfix + Dovecot + MySQL + Squirrelmail
by Gustavo 22 Feb '12

22 Feb '12

Ok, I study the wikki and the dovecot works. But when I try to send a mail using squirrel, I get this error on logs: Feb 11 18:41:55 jubileu postfix/smtpd[19522]: connect from localhost.localdomain[127.0.0.1] Feb 11 18:41:55 jubileu postfix/smtpd[19522]: warning: xsasl_cyrus_server_get_mechanism_list: no applicable SASL mechanisms Feb 11 18:41:55 jubileu postfix/smtpd[19522]: fatal: no SASL authentication mechanisms Feb 11 18:41:56 jubileu postfix/master[18383]: warning: process /usr/lib/postfix/smtpd pid 19522 exit status 1 Feb 11 18:41:56 jubileu postfix/master[18383]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling How can I fix this? My conf files seems to be ok: ## Diretorio Base ## base_dir = /var/run/dovecot/ ## Protocolos que ele ira executar ## protocols = imap imaps pop3 pop3s log_timestamp = '%Y-%m-%d %H:%M:%S ' syslog_facility = mail ## Dados do SSL ## ssl_listen = localhost ssl_cert_file = /etc/postfix/mail-cert.pem ssl_key_file = /etc/postfix/mail-key.pem ssl_parameters_regenerate = 168 verbose_ssl = no mail_location = maildir:/var/vmail/%d/%u mail_access_groups = mail mail_debug = no first_valid_uid = 150 last_valid_uid = 150 maildir_copy_with_hardlinks = yes protocol imap { } protocol pop3 { # Login executable location. login_executable = /usr/lib/dovecot/pop3-login mail_executable = /usr/lib/dovecot/pop3 pop3_uidl_format = %08Xu%08Xv } protocol lda { sendmail_path = /usr/lib/sendmail auth_socket_path = /tmp/auth-master } auth_verbose = no auth_debug = no auth default { mechanisms = plain login passdb pam { } passdb sql { args = /etc/dovecot/dovecot-sql.conf } userdb passwd { } userdb sql { args = /etc/dovecot/dovecot-sql.conf } socket listen { master { path = /tmp/auth-master mode = 0600 user = vmail group = mail } client { path = /tmp/auth-client mode = 0660 user = vmail group = mail } } } dict { } plugin { } ######################################### And Postfix conf: # SASL Authentication smtpd_sasl_auth_enable = yes smtpd_sasl2_auth_enable = yes smtpd_sasl_exceptions_networks = $mynetworks smtpd_sasl_security_options = noanonymous broken_sasl_auth_clients = yes smtpd_sasl_path = private/auth smtpd_sasl_application_name = smtpd smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination permit_mynetworks = 127.0.0.0/8, 184.22.103.88/32, 184.22.103.87/32 Thanks!!! > -----Mensagem Original----- From: Timo Sirainen > Sent: Saturday, January 28, 2012 3:51 PM > To: Gustavo > Cc: dovecot(a)dovecot.org > Subject: Re: [Dovecot] Problem with Postfix + Dovecot + MySQL + > Squirrelmail > > On 27.1.2012, at 14.32, Gustavo wrote: > > #service dovecot start >> Starting IMAP/POP3 mail server: dovecotLast died with error (see error >> log for more information): Auth process died too early - shutting down >> > > No need to keep guessing the problem. "See error log for more information" > like it says. http://wiki.dovecot.org/**Logging<http://wiki.dovecot.org/Logging> > > -- Gustavo - clube03(a)gmail.com

2 2

[Dovecot] Where did the message end up?
by Dag Nygren 22 Feb '12

22 Feb '12

Hi all! Just migrated out UW-IMAP installation to Dovecot and so far so good. Had small teething problems though which left me with one question. The scenario was that I have a set of public folders that are only needed by the main company group (gid = company). Then there are some external users as well, not directly in the company group. I set up the public mailbox with permissions 660, owner me and group "company". That is the externals didn't have access to the mail folder. At this point all looked fine, but later there was an email to an external person and this was passed on to deliver by procmail. Procmail logs says all was OK, but there is an entry about the public folder not accessible in the Dovecot log. The email is nowhere to be found. My question: Where is the delivered email? Best Dag

2 5