- dovecot - dovecot.org

[Dovecot] ldap: No password in reply
by Rudy Gevaert 21 Sep '05

21 Sep '05

Greetings, I'm trying to set up dovecot with ldap (and postfix) by following the page on the wiki. I configured everything, but something is wrong: dovecot: Sep 21 12:03:59 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=157.193.40.36 rip=157.193.44.68 dovecot: Sep 21 12:03:59 Info: auth(default): client out: CONT 1 dovecot: Sep 21 12:03:59 Info: auth(default): client in: CONT 1 b2xlX3dvYmJsZQBvbGVfd29iYmxlAHdvYmJsZQ== dovecot: Sep 21 12:03:59 Info: auth(default): ldap(ole_wobble,157.193.44.68): base=ou=accounts,dc=zalm,dc=UGent,dc=be scope=subtree filter=(&(objectClass=posixAccount)(uid=ole_wobble)) fields=uid,userPassword dovecot: Sep 21 12:03:59 Info: auth(default): ldap(ole_wobble,157.193.44.68): uid(user)=ole_wobble dovecot: Sep 21 12:03:59 Error: auth(default): ldap(ole_wobble,157.193.44.68): No password in reply dovecot: Sep 21 12:03:59 Info: auth(default): client out: FAIL 1 user=ole_wobble temp dovecot: Sep 21 12:04:01 Info: imap-login: Disconnected: user=<ole_wobble>, method=PLAIN, rip=157.193.44.68, lip=157.193.40.36, TLS This is my database: dn: dc=zalm,dc=UGent,dc=be objectClass: top objectClass: dcObject objectClass: organization o: Universiteit Gent dc: zalm dn: cn=admin,dc=zalm,dc=UGent,dc=be objectClass: simpleSecurityObject objectClass: organizationalRole cn: admin description: LDAP administrator userPassword:: e2NyeXB0fVpsbWpDb21kL3JSbkU= dn: ou=accounts,dc=zalm,dc=UGent,dc=be objectClass: top objectClass: organizationalUnit ou: accounts dn: cn=dovecot,ou=accounts,dc=zalm,dc=UGent,dc=be objectClass: top objectClass: person cn: dovecot sn: dovecot userPassword:: e0NSWVBUfXp6bGxQa1JoV1Nmb00= dn: uid=ole_wobble,ou=accounts,dc=zalm,dc=UGent,dc=be objectClass: top objectClass: person objectClass: posixAccount cn: Ole Wobble Olson sn: Olson uid: ole_wobble uidNumber: 3000 gidNumber: 8 homeDirectory: /home/postoffice userPassword:: e0NSWVBUfXBrOGN6SnlZVG5IL28= dn: uid=ole_wubble,ou=accounts,dc=zalm,dc=UGent,dc=be objectClass: top objectClass: person objectClass: posixAccount cn: Ole Wubble Olson sn: Olson uid: ole_wubble uidNumber: 3001 gidNumber: 8 homeDirectory: /home/postoffice What could be wrong? Thanks in advance, -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Rudy Gevaert e-mail: Rudy.Gevaert(a)UGent.be Directie ICT, Afdeling Infrastructuur Groep Systemen tel: +32 9 264 4734 Universiteit Gent fax: +32 9 264 4994 Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

1 1

[Dovecot] ALL TCP/IP connection REST when one mail contains format error
by Yi Xuan 20 Sep '05

20 Sep '05

Hi, I have setup a dovecot pop3 server on IP_A and using mbox format I have 6 users behind a NATed network, the public IP is IP_B. And one mail of one user seems contain format error. He always cannot receive the 5th mail from anywhere. Then when he receive mail in the intranet, all the TCP/IP connection REST between IP_A and IP_B. http/ssh/pop/smtp etc. all NG. After I delete the 5th mail from webmail, then the services work well. 1.It seems unreasonable, Can dovecot improve it and let it donot influence other users and other service? 2.What may cause mbox format error? and how can we avoid it? Best regards,

1 0

[Dovecot] Two strange behaviours with dovecot+postfix+squirrelmail
by Francisco Neira 20 Sep '05

20 Sep '05

Hi all, About a week ago I was forced to migrate my main (production) email server from RH9 to Centos4.1. The installation has dovecot-0.99.11 + postfix-2.1.5 and >600 mbox accessed email accounts. Number 1. Some users accessing thru squirremail (installed in my webserver) can read their INBOX at /var/spool/mail directory but when trying to delete a message they receive the following error message from squirrelmail: ERROR: Could not complete request. Consulta: COPY 1279 "mail/Trash" Reason Given: Internal error occured. Error report written to server log. [2005-09-16 15:08:04] and the error logged is the following: Sep 16 15:09:27 mail imap(username): mkdir_parents(/home/username//mail/.imap/Trash) failed: Permission denied I never stated that .imap/Trash when configuring dovecot and the strangest thing is that my account, as most of others, can delete messages moving from /var/spool/mail/my_name to /home/my_name/mail/Trash Number 2. Randomly, some users connecting from Mozilla Thunderbird via IMAP get an error message telling that there has been an error connecting to INBOX. Watching the maillog I found the following: Sep 16 13:07:43 mail imap(otheruser): File isn't in mbox format: /var/spool/mail/otheruser I accessed the user's inbox file with vi and found that there was a "--604" at the beginning of the file. In other case I found that the file was beginning with a truncated email message. Trying to "walk on the safer side", I changed the mbox_lock setting from "fcntl" to "dotlock" in the /etc/dovecot.conf file. Any suggestions and comments about his will be highly appreciated. Forgive me about my English, it is not my native lanaguage. Regards, -- Francisco Neira B. Administrador de Red Defensoria del Pueblo Lima, Peru, -05:00 UTC

2 1

[Dovecot] NO: Unsupported authentication mechanism
by Steve [Dovecot] 19 Sep '05

19 Sep '05

I'm happily using dovecot as my IMAP server and accessing mails using Thunderbird... but I want to use the Net::IMAP facilities in the Ruby standard library to write some scripts to automate various spam-related tasks & housekeeping. My Ruby script: require "net/imap" imap = Net::IMAP.new('localhost') imap.authenticate('LOGIN','myuser','mypassword') # More stuff using imap... From the documentation LOGIN uses plaintext authentication - which I understand is always acceptable for Dovecot when connecting from localhost. On the 3rd line I get a "NO response" exception raised (indicating that the IMAP server replied "NO") and the error message "Net::IMAP::NoResponseError: Unsupported authentication mechanism" If I change 'LOGIN' to 'CRAM-MD5' (the other value supported by Net::IMAP) then I get a similar (but not identical) error: "Net::IMAP::NoResponseError: Authentication failed: Unsupported authentication mechanism" If I use anything other than either 'LOGIN' or 'CRAM-MD5' I get an error from the Net::IMAP library saying "Unknown auth type" - which is reasonable. N.B. I've tried both where 'myuser' and 'mypassword' are valid - and not... this doesn't affect the error messages. There doesn't seem to be anything of interest in /var/log/messages... Can anyone tell me what is going wrong, and how to resolve this?

4 5

[Dovecot] FreeBSD port
by David King 19 Sep '05

19 Sep '05

FreeBSD users: I notice that the version of Dovecot in the FreeBSD ports system is back at .99. Are there any objections to my submitting an update to the FreeBSD ports for version 1.0a? Is it better to wait for 1.0 to be progressed a little or is it considered to be ready? 1.0a compiles and seems to run fine (on 5.3), so are there any obvious patches that would be needed for the FreeBSD build? -- Don't forget that 19 September is National Talk-Like-A-Pirate Day! http://www.talklikeapirate.com/piratehome.html

2 1

[Dovecot] 1.0alpha2: two asserts/cores
by Jeff A. Earickson 19 Sep '05

19 Sep '05

Hi, Two cores over the weekend, same assert message in syslog: imap(user): file message-body-search.c: line 393 (message_body_search_ctx): assertion failed: (input->v_offset <= part->physical_pos) Setup: Solaris 9, imap usage only, mbox format, dovecot compiled with gcc 4.0.1. gdb sessions of the two core files attached. Let me know if you need further analysis of the cores. Jeff Earickson Colby College

1 0

[Dovecot] vmailmgr user database
by Mij 19 Sep '05

19 Sep '05

hola guys Is a module for vmailmgr userdb being under work by someone? If not, i'd like to help out. Is there a standard API to implement or such? Is there some further documentation to avoid a full inspection of the sources? thank you

2 2

[Dovecot] Very minor feature request
by Steffen Kaiser 19 Sep '05

19 Sep '05

Hello, I'd suggest a way to get to know the "capabilities" of a compiled Dovecot. The background is that I've run the sequence ./configure --with-ldap && make && make install twice, all three commands tell me that all is fine (ldap is listed in the modules), but still dovecot told me that ldap is no Usedb module. A "make clean" before solved the problem -- well, something one should anyway. Besides, the "dovecot --capabilities" should also list all the defaults. Bye, -- Steffen Kaiser

3 4

[Dovecot] support multiple files.
by David Willoughby 19 Sep '05

19 Sep '05

i currently use procmail to sort my different mailing lists into differnet files for sanity puproses is there a way dovecot can find all these files? i have default_mail_env set to mbox:~/Mail/ could i use *:~/Mail/ as every file in /Mail is a mail file? -- David Willoughby email: dlw(a)d1w.org icq: 1852393

1 0

Re: [Dovecot] Misbehavior with Dovecot and Mulberry
by Jon Roma 18 Sep '05

18 Sep '05

Well, ironically after my tests succeeded, my reply to the Dovecot list just now failed to append to the Dovecot maildir folder. So I guess it works sometimes and not other times. :( The error message is the same "failed: Invalid argument". Jon Roma <roma(a)uiuc.edu> wrote: > > > Timo Sirainen <tss(a)iki.fi> wrote: > >> On Mon, 2005-09-05 at 23:57 -0500, Jon Roma wrote: >>> --> #6.3408 Mon Sep 5 23:25:13 2005 >>> A00092 APPEND Sent (\Seen) {610+} >>> A00092 NO >> >> That happens if some function returned -1 but didn't set any error. >> Shouldn't happen.. >> >>> I am running 1.0-test80 with Timo's patch to fix the "time off by >>> 200 minutes" error with mbox. All my folders are maildir at this >>> point -- I've converted them out of my UW mbx format store. My >>> client is Mulberry 3.1.6 for Windows and the OS is AIX 5.1. >> >> So, they are maildirs? Do these changes help: >> >> Index: src/imap/cmd-append.c >> =================================================================== >> RCS file: /var/lib/cvs/dovecot/src/imap/cmd-append.c,v >> retrieving revision 1.64 >> retrieving revision 1.65 >> diff -u -r1.64 -r1.65 >> --- src/imap/cmd-append.c 28 Jun 2005 11:15:57 -0000 1.64 >> +++ src/imap/cmd-append.c 18 Sep 2005 16:58:01 -0000 1.65 >> @@ -292,8 +292,7 @@ >> int failed; >> >> if (ctx->save_ctx != NULL) { >> - if (mailbox_save_continue(ctx->save_ctx) < 0 || >> - client->input->closed) { >> + if (mailbox_save_continue(ctx->save_ctx) < 0) { >> /* we still have to finish reading the message >> from client */ >> mailbox_save_cancel(ctx->save_ctx); >> Index: src/lib-storage/index/maildir/maildir-save.c >> =================================================================== >> RCS file: >> /var/lib/cvs/dovecot/src/lib-storage/index/maildir/maildir-save.c,v >> retrieving revision 1.57 >> retrieving revision 1.58 >> diff -u -r1.57 -r1.58 >> --- src/lib-storage/index/maildir/maildir-save.c 14 Aug 2005 19:02:54 >> -0000 1.57 +++ src/lib-storage/index/maildir/maildir-save.c 18 Sep 2005 >> 16:58:31 -0000 1.58 @@ -217,6 +217,10 @@ >> return -1; >> >> if (o_stream_send_istream(ctx->output, ctx->input) < 0) { >> + mail_storage_set_critical(STORAGE(ctx->mbox->storage), >> + "o_stream_send_istream(%s) failed: %m", >> + t_strconcat(ctx->tmpdir, "/", >> + ctx->files->basename, NULL)); >> ctx->failed = TRUE; >> return -1; >> } >> > > Timo: > > Yes, my mailboxes are maildirs. > > Your patch seems to have fixed the problem -- I can now append outgoing > mail to a Dovecot maildir 'Sent' mailbox as it gets sent. And I can now > also save a draft in my Dovecot maildir 'Drafts' mailbox when desired. > > What this means is that I no longer need UW (Yay!) -- I was saving my > outgoing mail and drafts in a skeletal UW tree pending resolution of > this problem. > > There is still an anomaly when using the Mulberry client to move mail > from the UW tree to Dovecot (which I now want to do in preparation for > getting rid of UW imapd. > > Using Mulberry to move mail from UW to Dovecot only works with some > messages and not others. Maybe this is not important -- I can slurp > my last two UW mboxes into a Dovecot namespace and then move them as > desired into the default namespace. > > But perhaps this behavior is something you are interested in -- here's > the transcript on the client side. > > First a copy/move that succeeded. I am in the source folder (under UW) > and have chosen a message that I want to move to the Dovecot 'Sent' > folder is the destination. > > --> #25.2768 Sun Sep 18 13:10:26 2005 > A00145 FETCH 170 (BODY[1]) > * 170 FETCH (BODY[1] {280} > ) > A00145 OK FETCH completed > > --> #1.2768 Sun Sep 18 13:10:34 2005 > A00010 APPEND Sent (\Seen) "15-Sep-2005 18:00:43 -0500" {813+} > --> #25.2768 Sun Sep 18 13:10:34 2005 > A00146 FETCH 170 (BODY.PEEK[]) > * 170 FETCH (BODY[] {813} > ) > A00146 OK FETCH completed > > A00010 OK Append completed. > > --> #1.2768 Sun Sep 18 13:10:35 2005 > A00011 STATUS Sent (MESSAGES RECENT UNSEEN UIDVALIDITY UIDNEXT) > * STATUS "Sent" (MESSAGES 5547 RECENT 1 UIDNEXT 5552 UIDVALIDITY > 1125869336 UNSEEN 0) > A00011 OK Status completed. > > --> #25.2768 Sun Sep 18 13:10:35 2005 > A00147 STORE 170 +FLAGS (\Deleted) > * 170 FETCH (FLAGS (\Seen \Deleted)) > A00147 OK STORE completed > > This move succeeded. > > Now I choose a different message in Mulberry and try to do the same > move operation. This one fails. > > --> #25.2768 Sun Sep 18 13:10:35 2005 > A00148 FETCH 171 (BODY[1]) > * 171 FETCH (BODY[1] {268} > ) > A00148 OK FETCH completed > > --> #1.2768 Sun Sep 18 13:10:44 2005 > A00012 APPEND Sent (\Seen) "15-Sep-2005 19:52:14 -0500" {832+} > --> #25.2768 Sun Sep 18 13:10:44 2005 > A00149 FETCH 171 (BODY.PEEK[]) > * 171 FETCH (BODY[] {832} > ) > A00149 OK FETCH completed > > A00012 NO Internal error occurred. Refer to server log for more > information. [2005-09-18 13:10:44] > > The corresponding syslog message is > > Sep 18 13:10:44 zippy dovecot: IMAP(roma): o_stream_send_istrea > (/var/imap/dovecot/roma/.Sent/tmp/1127067044.P44216Q3.zippy.cso.uiuc.edu) > failed: Invalid argument > > Maybe this isn't important, but I send it in case you think it's something > you want to look at. > > I'll leave the relevant mailbox around so I can try this again if > necessary. > > Thanks for the patch!

1 0