- dovecot - dovecot.org

Re: [Dovecot] auth socket goes away on reload
by David Jonas 03 Jun '10

03 Jun '10

On 6/3/10 , Jun 3, 9:45 AM, Jerrale Gayle wrote: > On 6/3/2010 12:35 PM, David Jonas wrote: >> We're using the SQLite backend for authentication of Postfix SASL. When >> the db is replaced we HUP dovecot to close and reopen its connection. >> During this time it appears the socket file is removed and Postfix >> rejects the authentication attempt. From the logs: >> >> Jun 3 00:23:02 xxx dovecot: dovecot: SIGHUP received - reloading >> configuration >> Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: SASL: Connect to >> private/auth failed: Connection refused >> Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: unknown[dd.dd.dd.dd]: >> SASL LOGIN authentication failed: >> Jun 3 00:23:02 xxx postfix/smtpd[14746]: NOQUEUE: reject: RCPT from >> unknown[dd.dd.dd.dd]: 554 5.7.1<user(a)example.com>: Relay access denied; >> from=<user2(a)example.com> to=<user(a)example.com> proto=ESMTP >> helo=<localhost.localdomain> >> >> Jun 3 00:23:02 xxx postfix/smtpd[14930]: warning: unknown[dd.dd.dd.dd]: >> SASL LOGIN authentication failed: Connection lost to authentication >> server >> Jun 3 00:23:02 xxx postfix/smtpd[14930]: lost connection after AUTH >> from unknown[dd.dd.dd.dd] >> >> Is there an obvious way around this? I know I could somehow merge the >> changes into the running sqlite db but that undermines the simplicity of >> the design I have. Maybe a patch to reopen the db if it's replaced? Or >> perhaps I should just switch to a different db format -- that's probably >> the quickest/easiest solution. Any other ideas? There are about 20k >> entries to deal with. >> >> Thanks, >> >> David >> >> > the HUP reload method is only available on dovecot 2.0. Make sure > you're using that version to do that; otherwise, killall dovecot and > then dovecot. I should have specified that this is dovecot 1.2.7. The sighup seems to work just fine except for the effect I've outlined.

2 1

[Dovecot] Sieve GUI
by Gerhard Waldemair 03 Jun '10

03 Jun '10

> Is there à GUI for sieve. > > I don't have installed Squrielmail, but won't like to manage the > Rules per ssh

13 19

[Dovecot] auth socket goes away on reload
by David Jonas 03 Jun '10

03 Jun '10

We're using the SQLite backend for authentication of Postfix SASL. When the db is replaced we HUP dovecot to close and reopen its connection. During this time it appears the socket file is removed and Postfix rejects the authentication attempt. From the logs: Jun 3 00:23:02 xxx dovecot: dovecot: SIGHUP received - reloading configuration Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: SASL: Connect to private/auth failed: Connection refused Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: unknown[dd.dd.dd.dd]: SASL LOGIN authentication failed: Jun 3 00:23:02 xxx postfix/smtpd[14746]: NOQUEUE: reject: RCPT from unknown[dd.dd.dd.dd]: 554 5.7.1 <user(a)example.com>: Relay access denied; from=<user2(a)example.com> to=<user(a)example.com> proto=ESMTP helo=<localhost.localdomain> Jun 3 00:23:02 xxx postfix/smtpd[14930]: warning: unknown[dd.dd.dd.dd]: SASL LOGIN authentication failed: Connection lost to authentication server Jun 3 00:23:02 xxx postfix/smtpd[14930]: lost connection after AUTH from unknown[dd.dd.dd.dd] Is there an obvious way around this? I know I could somehow merge the changes into the running sqlite db but that undermines the simplicity of the design I have. Maybe a patch to reopen the db if it's replaced? Or perhaps I should just switch to a different db format -- that's probably the quickest/easiest solution. Any other ideas? There are about 20k entries to deal with. Thanks, David

2 1

Re: [Dovecot] auth socket goes away on reload
by William Blunn 03 Jun '10

03 Jun '10

On 03/06/2010 19:08, David Jonas wrote: > On 6/3/10 , Jun 3, 10:16 AM, William Blunn wrote: > >> On 03/06/2010 17:35, David Jonas wrote: >> >>> We're using the SQLite backend for authentication of Postfix SASL. When >>> the db is replaced we HUP dovecot to close and reopen its connection. >>> During this time it appears the socket file is removed and Postfix >>> rejects the authentication attempt. From the logs: >>> >>> Jun 3 00:23:02 xxx dovecot: dovecot: SIGHUP received - reloading >>> configuration >>> Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: SASL: Connect to >>> private/auth failed: Connection refused >>> Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: unknown[dd.dd.dd.dd]: >>> SASL LOGIN authentication failed: >>> Jun 3 00:23:02 xxx postfix/smtpd[14746]: NOQUEUE: reject: RCPT from >>> unknown[dd.dd.dd.dd]: 554 5.7.1<user(a)example.com>: Relay access denied; >>> from=<user2(a)example.com> to=<user(a)example.com> proto=ESMTP >>> helo=<localhost.localdomain> >>> >>> Jun 3 00:23:02 xxx postfix/smtpd[14930]: warning: unknown[dd.dd.dd.dd]: >>> SASL LOGIN authentication failed: Connection lost to authentication >>> server >>> Jun 3 00:23:02 xxx postfix/smtpd[14930]: lost connection after AUTH >>> from unknown[dd.dd.dd.dd] >>> >>> Is there an obvious way around this? I know I could somehow merge the >>> changes into the running sqlite db but that undermines the simplicity of >>> the design I have. Maybe a patch to reopen the db if it's replaced? Or >>> perhaps I should just switch to a different db format -- that's probably >>> the quickest/easiest solution. Any other ideas? There are about 20k >>> entries to deal with. >>> >> It sounds like your updates arrive in the shape of entire-table updates. >> >> That is no problem. You can easily apply entire-table updates to the >> database without having to re-create the SQLite database file, and >> without having to tell Dovecot. >> >> Just create a new table (with a different name) inside the SQLite >> database file, with the new content, then snap it into place using a >> pair of table renames inside a transaction; then delete the old table. >> >> That way you don't need to re-create the database file or HUP Dovecot, >> and Dovecot will only ever see the old data or the new data. >> > That sounds reasonable, not sure why I didn't think of it! Thanks. > If you are going to keep the SQLite database around, you might want to look at vacuuming it periodically using either VACUUM or the auto_vacuum PRAGMA depending on what fits your context best. http://sqlite.org/lang_vacuum.html http://sqlite.org/pragma.html#pragma_auto_vacuum Bill

2 2

Re: [Dovecot] auth socket goes away on reload
by David Jonas 03 Jun '10

03 Jun '10

On 6/3/10 , Jun 3, 10:16 AM, William Blunn wrote: > On 03/06/2010 17:35, David Jonas wrote: >> We're using the SQLite backend for authentication of Postfix SASL. When >> the db is replaced we HUP dovecot to close and reopen its connection. >> During this time it appears the socket file is removed and Postfix >> rejects the authentication attempt. From the logs: >> >> Jun 3 00:23:02 xxx dovecot: dovecot: SIGHUP received - reloading >> configuration >> Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: SASL: Connect to >> private/auth failed: Connection refused >> Jun 3 00:23:02 xxx postfix/smtpd[14746]: warning: unknown[dd.dd.dd.dd]: >> SASL LOGIN authentication failed: >> Jun 3 00:23:02 xxx postfix/smtpd[14746]: NOQUEUE: reject: RCPT from >> unknown[dd.dd.dd.dd]: 554 5.7.1<user(a)example.com>: Relay access denied; >> from=<user2(a)example.com> to=<user(a)example.com> proto=ESMTP >> helo=<localhost.localdomain> >> >> Jun 3 00:23:02 xxx postfix/smtpd[14930]: warning: unknown[dd.dd.dd.dd]: >> SASL LOGIN authentication failed: Connection lost to authentication >> server >> Jun 3 00:23:02 xxx postfix/smtpd[14930]: lost connection after AUTH >> from unknown[dd.dd.dd.dd] >> >> Is there an obvious way around this? I know I could somehow merge the >> changes into the running sqlite db but that undermines the simplicity of >> the design I have. Maybe a patch to reopen the db if it's replaced? Or >> perhaps I should just switch to a different db format -- that's probably >> the quickest/easiest solution. Any other ideas? There are about 20k >> entries to deal with. > > It sounds like your updates arrive in the shape of entire-table updates. > > That is no problem. You can easily apply entire-table updates to the > database without having to re-create the SQLite database file, and > without having to tell Dovecot. > > Just create a new table (with a different name) inside the SQLite > database file, with the new content, then snap it into place using a > pair of table renames inside a transaction; then delete the old table. > > That way you don't need to re-create the database file or HUP Dovecot, > and Dovecot will only ever see the old data or the new data. That sounds reasonable, not sure why I didn't think of it! Thanks.

1 0

[Dovecot] Configure unsuccessful login attempts
by Greg Pearson 03 Jun '10

03 Jun '10

Hi, using PAM, how can I configure how many attempts a user can make to connect, and if exceeding a certain number, block him for a specified amount of time? Any idea what the defaults are?

4 6

[Dovecot] master users with dovecot2 braek down to allowed domain
by Robert Schetterer 03 Jun '10

03 Jun '10

Hi, i think ive asked it before perhaps this feature can be included in dovecot2 couldnt get it run with dovecot 1.2.x if i use the postfixadmin superuser,domainadmin,domainuser layout so there are domainadmins defined in a sql table it would be a nice feature to break it down to be master only at there related domains via sql lookup at recent i think there is only the chance to give master rights to all adresses for users defined as masters -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

2 2

[Dovecot] Dovecot aspects of fighting spam
by Phil Howard 02 Jun '10

02 Jun '10

I see no documents in the Dovecot documents wiki on how Dovecot features can be used in the fight against spam. One hit came up in a search, and it was about how to fight spam in the MoinMoin Wiki itself (e.g. TextCHAs and such). I already asked in another thread about removing message files at the search from a designated "learn-spam" folder. My next question would be how to automatically place detected spam into a specific folder for the user to access or ignore as they deem fit. That would seem to me to be something for the deliver command and its -m option. But this might be more of a Dovecot and MTA coordination issue, too (e.g. how to get the spam detection done in the MTA ... Postfix in my case ... to become a label of some sort that ends deciding the folder. The -m option might be harder to get it dynamically set since it would be hard coded in master.cf for Postfix (so a variable has to be able to direct it to INBOX in this case). But maybe the "standard" way of doing this is to shim another program between the MTA (Postfix for me) and the LDA (Dovecot deliver) to dynamically add the -m option on the fly? Lacking any other clever solution, this seems to me to be the way I could make it work. Maybe there is a special header deliver could detect, such as "X-Spam: yes"? A wiki document on how Dovecot helps (or how to help Dovecot) in the fight against spam, I think, would be helpful.

10 28

[Dovecot] returned error 83 (Out of memory)
by J Contad 02 Jun '10

02 Jun '10

Hello! I've setup dovecot a few months ago, and it was working pretty swimmingly. Then, out of nowhere, we started getting this error: Apr 21 19:15:17 IMAP(xx(a)xxx.com): Fatal: block_alloc(1073741824): Out of memory Apr 21 19:15:17 IMAP(xx(a)xxx.com): Error: Raw backtrace: imap [0x49e5e0] -> imap [0x49e643] -> imap [0x49dba1] -> imap [0x4a7f6d] -> imap [0x4a7f98] -> imap [0x4a8028] -> imap [0x49bf6f] -> imap(buffer_write+0xe4) [0x49c334] -> imap(mail_cache_lookup_headers+0x146) [0x46dcf6] -> imap [0x458162] -> imap(index_mail_get_first_header+0x45) [0x458685] -> imap [0x45fe44] -> imap [0x460008] -> imap [0x4796d1] -> imap(hash2_lookup+0x64) [0x4a1c94] -> imap(mail_index_strmap_view_sync_add+0x85) [0x47ab05] -> imap(mail_thread_init+0x2a5) [0x4602f5] -> imap(cmd_thread+0x161) [0x41f931] -> imap(cmd_uid+0x78) [0x41fb38] -> imap [0x42079c] -> imap [0x420852] -> imap(client_handle_input+0x3f) [0x42098f] -> imap(client_input+0x5f) [0x4214df] -> imap(io_loop_handler_run+0xf8) [0x4a63a8] -> imap(io_loop_run+0x1d) [0x4a54ed] -> imap(main+0x620) [0x428db0] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x3f75e1d8a4] -> imap [0x419969] Apr 21 19:15:17 dovecot: Error: child 25918 (imap) returned error 83 (Out of memory - see mail_process_size setting) The folder (which is shared) has about 8 thousand emails in it. I'm not sure if it's pertinent, but the dovecot.index.cache file is about 8MB. Help? Cheers, -- John

3 2

[Dovecot] Dovecot install problem
by David 02 Jun '10

02 Jun '10

I am trying to set up a new web and mail server i have postfix now working but dovecot will not allow me to login and retrieve the emails so below isa portion of the log file passwd-file /var/mail/vhosts/xxxx.net/shadow: stat() failed: Permission denied passwd-file(xxxxx@xxxx.net,::ffff:0.0.0.0): no passwd file: /var/mail/vhosts/xxxx.net/shadow Dovecot -n output # 1.0.7: /etc/dovecot.conf login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_location: Maildir:/var/mail/vhosts/%d/%n mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: mechanisms: plain login CRAM-MD5 verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /var/mail/vhosts/%d/shadow userdb: driver: passwd-file args: /var/mail/vhosts/%d/passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix The passwd shadow file -rw-r----- 1 root root 210 May 24 21:39 passwd -rw-r----- 1 root root 327 May 24 21:39 shadow So who whould own these files? What should the perrmissions be?

4 7