- dovecot - dovecot.org

[Dovecot] Thunderbird got "Mail Server does not support secure authentication" ???
by Adrian Mak 23 Aug '05

23 Aug '05

System: Redhat AS3 postfix 2.2.5 cyrus-sasl 2.1.15 pam-mysql 0.6 dovecot 0.99.14 ( compile from source tarball) The same email account and machine, using thunderbird 1.06 to get email thru dovecot pop3, it returned "Mail Server does not support secure authentication" But in outlook express , there is no such problem I have tested SASL thru pam-mysql is work properly before install dovecot Below is my dovecot.conf /etc/dovecot.conf base_dir = /var/run/dovecot/ protocols = imap pop3 imap_listen = * pop3_listen = * ssl_disable = yes login = imap login = pop3 login_dir = /var/run/dovecot-login login_executable = /usr/local/libexec/dovecot/imap-login login_executable = /usr/local/libexec/dovecot/pop3-login imap_executable = /usr/local/libexec/dovecot/imap pop3_executable = /usr/local/libexec/dovecot/pop3 disable_plaintext_auth = no login_user = dovecot first_valid_uid = 1000 last_valid_uid = 1000 valid_chroot_dirs = /var/spool/virtual default_mail_env = /var/spool/virtual/%u auth = default auth_mechanisms = plain auth_userdb = mysql /etc/dovecot/mysql.conf auth_passdb = mysql /etc/dovecot/mysql.conf auth_executable = /usr/local/libexec/dovecot/dovecot-auth auth_user = dovecot-auth /etc/dovecot/mysql.conf db_host = localhost db_port = 3306 db_unix_socket = /tmp/mysql.sock db = postfix db_user = postfixuser db_passwd = userpostfix db_client_flags = 0 password_query = SELECT password FROM mailbox WHERE username = '%u' user_query = SELECT maildir, 1000 AS uid, 1000 AS gid FROM mailbox WHERE username = '%u'

2 1

[Dovecot] Problem with AUTH causes serverside lockup
by Tom Sommer 23 Aug '05

23 Aug '05

Hello all, I am running Dovecot alpha1, and after about 24 hours of the server working fine, it starts to lock up when I open Thunderbird to check mail. Basically I can see new mail, but when I click it, it just hangs at "Loading message...". I get the following in my maillog: Aug 23 09:25:28 palantir dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=194.192.14.150 rip=80.197.147.147 Aug 23 09:25:28 palantir dovecot: auth(default): client out: CONT 1 Aug 23 09:25:28 palantir dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=194.192.14.150 rip=80.197.147.147 Aug 23 09:25:28 palantir dovecot: auth(default): client out: CONT 1 Aug 23 09:25:28 palantir dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=194.192.14.150 rip=80.197.147.147 Aug 23 09:25:28 palantir dovecot: auth(default): client out: CONT 1 Aug 23 09:25:28 palantir dovecot: auth(default): client in: CONT 1 [BASE64 SUM] Aug 23 09:25:28 palantir last message repeated 2 times Aug 23 09:25:28 palantir dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=194.192.14.150 rip=80.197.147.147 Aug 23 09:25:28 palantir dovecot: auth(default): client out: CONT 1 Aug 23 09:25:28 palantir dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=194.192.14.150 rip=80.197.147.147 Aug 23 09:25:28 palantir dovecot: auth(default): client out: CONT 1 Aug 23 09:25:28 palantir dovecot: auth(default): client in: CONT 1 [BASE64 SUM] And then it just hangs untill it finally says Aug 23 09:26:17 palantir dovecot: imap-login: Disconnected: Inactivity: method=plain, rip=80.197.147.147, lip=194.192.14.150 When I do: # killall dovecot # dovecot (restarting dovecot) then it works fine again. -- Tom Sommer

1 1

[Dovecot] Wiki of dovecot.conf file
by Marc Perkel 23 Aug '05

23 Aug '05

I made yet another new wiki page documenting the mail configuration file. Looks really nice. We can all start working on improving the docs in this file and eventually merge the docs here back into the example config file. http://wiki.dovecot.org/moin.cgi/MainConfig -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

1 0

[Dovecot] Segfault in imap
by Todd Burroughs 23 Aug '05

23 Aug '05

Found a new segfault in imap. The first log entry always happens on my mailbox, but doesn't seem to affect anything. This is CVS version from Aug. 15. dovecot: Aug 21 17:16:56 Error: 28017 IMAP(todd): Corrupted index cache file /mailhome/new/t/b/todd/.imap/INBOX/dovecot.index.cache: Duplicated field in header: hdr.RESENT-TO dovecot: Aug 21 17:19:44 Error: child 28017 (imap) killed with signal 11 (gdb) bt full #0 0x08076b50 in index_mail_get_flags (_mail=0x80cbd20) at index-mail.c:152 data = (struct index_mail_data *) 0x80cbd84 #1 0x0808eb4d in mail_get_flags (mail=0xb7de7088) at mail.c:32 No locals. #2 0x0805a9d5 in fetch_flags (ctx=0x80c1ed0, mail=0x80cbd20, context=0x0) at imap-fetch.c:445 flags = Variable "flags" is not available. (gdb) bt #0 0x08076b50 in index_mail_get_flags (_mail=0x80cbd20) at index-mail.c:152 #1 0x0808eb4d in mail_get_flags (mail=0xb7de7088) at mail.c:32 #2 0x0805a9d5 in fetch_flags (ctx=0x80c1ed0, mail=0x80cbd20, context=0x0) at imap-fetch.c:445 #3 0x0805af0c in imap_fetch (ctx=0x80c1ed0) at imap-fetch.c:265 #4 0x0805693b in cmd_fetch (cmd=0x80bfba8) at cmd-fetch.c:166 #5 0x0805999b in _client_input (context=0x80bfb68) at client.c:334 #6 0x080a045a in io_loop_handler_run (ioloop=0x80be9b0) at ioloop-poll.c:184 #7 0x0809f9d9 in io_loop_run (ioloop=0x80be9b0) at ioloop.c:230 #8 0x08060877 in main (argc=1, argv=0xbffffa44, envp=0xbffffa4c) at main.c:229 (gdb) p *data $1 = {flags = 0, date = 0, received_date = 1124608407, virtual_size = 2870, physical_size = 2856, sent_date = {time = -1, timezone = 0}, parse_line = { field_idx = 0, start_pos = 0, end_pos = 0, line_num = 0, cache = 0}, parse_line_num = 0, parts = 0x0, envelope = 0x0, body = 0x0, bodystructure = 0x0, uid_string = 0x0, envelope_data = 0x0, seq = 11473, rec = 0xb7de7088, cache_flags = 0, access_part = 3, stream = 0x80cc224, filter_stream = 0x0, hdr_size = {physical_size = 2545, virtual_size = 2545, lines = 57}, body_size = {physical_size = 311, virtual_size = 325, lines = 14}, parser_ctx = 0x0, parsing_count = 0, keywords = { buffer = 0x0, element_size = 0}, all_cache_fields = 0x0, all_cache_fields_count = 0, save_sent_date = 0, save_envelope = 0, save_bodystructure_header = 0, save_bodystructure_body = 0, parsed_bodystructure = 0, hdr_size_set = 1, body_size_set = 1, messageparts_saved_to_cache = 0} (gdb) p *data->rec Cannot access memory at address 0xb7de7088

1 0

[Dovecot] pop-before-smtp in SQL?
by Lorens 23 Aug '05

23 Aug '05

I need pop-before-smtp (let's not discuss the advisability of the method), but I'm annoyed at the inefficiency of the classical perl script that parses the logs. A long time ago I modified the perl to add the tuple (IP, time) to an SQL table that the MTA looks at, and to clean up periodically. I found that this was the best way to deal with multiple servers that have to share an SQL database anyway. Wouldn't it be quite trivial to make dovecot write to an SQL table upon sucessful login, instead of all this log file parsing by an additional daemon?

2 4

[Dovecot] Poprelayd released for Dovecot
by dan1 22 Aug '05

22 Aug '05

Hello all. I just wanted to tell you that poprelayd is now compatible with Dovecot. I have just created a parser for the Dovecot server. This might be interesting either for you or your future customers. Maybe you will want to make some advertisement for it ? I remind that poprelayd is a service that allows a POP user to use the SMTP server of the same machine to send e-mails (making relays) for 15 minutes long after the pop login. This comes very handy for people wanting to send e-mails through their servers and also for a larger use. If you could try it that would also give some interesting feedbacks. This is the link: http://sourceforge.net/forum/forum.php?thread_id=1338704&forum_id=21494 BTW, I would need something from you: The POP login information that we can find for Dovecot in the /var/log/maillog is [::ffff:IP_ADDRESS]. Here is an example: Aug 19 23:23:02 anoigo pop3-login: Login: john [::ffff:82.208.12.243] Will this be kept the same all the time or is this ffff value a variable ? Will it be kept like this all the life of Dovecot ? Also, I would need to know if the 'pop3-login' and 'Login:' information there will also be kept. Thanks. Regards, Daniel

3 2

[Dovecot] dovecot-lda user quota
by Renzetti Federico 22 Aug '05

22 Aug '05

Sorry again people! Now my trouble is: /Your message was automatically rejected by Sieve, a mail filtering language. The following reason was given: Internal quota calculation error/ Any ideas? THK.

1 0

[Dovecot] Re: Dovecot inotify problem
by Johannes Berg 22 Aug '05

22 Aug '05

Hi Reuben, I hope you don't mind me copying the dovecot list again. > dovecot: Aug 21 04:08:22 Error: IMAP(reuben): inotify_rm_watch() failed: > Invalid argument Odd. > This is with a 2.6.13-rc6-mm1 release. I've posted to LKML because there is > also a kernel stack produced at one point which looks inotify related (but the > messages above are contant). > See http://www.ussg.iu.edu/hypermail/linux/kernel/0508.2/1180.html and the > followup from akpm. Thanks for the link. I don't think akpm is right, unless something is really odd here. Could you add debugging output for me please? Maybe something like (this is not a patch you can apply, look at line 164 in src/lib/ioloop-notify-inotify.c) ctx->inotify_fd = inotify_init(); + i_warning("inotify_init returned fd %d", ctx->inotify_fd); if (ctx->inotify_fd == -1) { and line 106: IN_CLOSE | IN_MODIFY); + i_warning("inotify_add_watch returned %d", watchdescriptor); if (watchdescriptor < 0) { and line 145: } + inotify_rm_watch("removing wd %d from inotify fd %d", io->notify_context, ctx->inotify_fd); if (inotify_rm_watch(ctx->inotify_fd, io->notify_context) < 0) Or something similar. If that doesn't help and output looks consistent (we're not removing a watch descriptor from a wrong fd etc.), can you try removing the fd_close_on_exec call please (line 171)? I don't know if that could cause trouble (I don't even think that the imap binary ever forks) but you never know. johannes

2 4

[Dovecot] Created Testimonials Page in wiki
by Marc Perkel 22 Aug '05

22 Aug '05

I created a testimonials page. Feel free to add to this. http://wiki.dovecot.org/moin.cgi/Testimonials -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

6 7

Dovecot IDLE problem (was Re: [Dovecot] inotify support in dovecot)
by Reuben Farrelly 22 Aug '05

22 Aug '05

Hi, I've come across some possibly buggy behaviour with regards to Dovecot and the use of the IDLE keyword. Found this while testing out inotify support for Johannes - although after asking him and him reproducing it, he is of the opinion that it's not a inotify specific problem. The behaviour is that when the client is idling, Dovecot seems to only alert to the first new message received, and if a subsequent new message comes in before the client finishes idling, that second new message is not notified to the connected client. To reproduce: $ maildirmake /tmp/imap-test $ cat >/tmp/1 <<EOF From: test To: test Subject: test test! <Ctrl-D> $ MAIL=Maildir:/tmp/imap-test /usr/libexec/dovecot/imap ... A SELECT INBOX B IDLE [now, in a different terminal, copy /tmp/1 to /tmp/imap-test/new, you should instantly be notified of it in your imap session] ** Dovecot correctly responds with: * 1 EXISTS * 1 RECENT [if a second message is delivered, eg by copying /tmp/1 to /tmp/imap-test/new/2 then you should be notified as well, but this never occurs] DONE C LOGOUT $ Timo - what do you think? Reuben

4 5