- dovecot - dovecot.org

[Dovecot] upgrade from 1.0rc7
by Zbigniew Szalbot 17 Feb '07

17 Feb '07

Hello, Have been to dovecot website but could not find information on what I need to check before I upgrade from the current 1.0rc7 which I am using on a FreeBSD 6.2 system. Will the old conf (virtual users, no ssl) file work with upgraded dovecot? Many thanks! -- Zbigniew Szalbot

2 1

Re: [Dovecot] Reply-To header
by Kenny Dail 17 Feb '07

17 Feb '07

> On Saturday 17 February 2007 00:13, Mark E. Mallett wrote: > > On Sat, Feb 17, 2007 at 12:33:40AM +0200, Timo Sirainen wrote: > > > On Fri, 2007-02-16 at 15:16 -0600, Richard Laager wrote: > > > > I see you've added a Reply-To header later. The canonical response in > > > > this case is for someone to reference: > > > > http://www.unicom.com/pw/reply-to-harmful.html > > > > A canonical response to that is > > > > http://www.metasystema.net/essays/reply-to.mhtml > > My mind was not changed, sorry. First, RFC 822 is obsolete, and RFC 2822 does > not contain the quoted paragraph. Instead it says that '[w]hen > the "Reply-To:" field is present, it indicates the mailbox(es) to which the > author of the message suggests that replies be sent.' - the author, not the > mailing list software. There are other fields for that. Fortunately Dovecot's set-up, does make it the author's choice. -- Kenny Dail <kend(a)amigo.net>

2 1

[Dovecot] Problem/workaround with X-Keywords and Apple's Mail.app
by Joey Coleman 17 Feb '07

17 Feb '07

Hello, I've just switched from UW-IMAP to Dovecot, and for the most part, things are good. However, I encountered the problem with the X-Keywords header not being written back into individual messages in an mbox file (originally described in [1], and Timo gave a clue as to maybe why in [2]). What was happening for me is that Apple's Mail.app would flag a message as spam, which happily sets a couple keywords in the message, but those weren't being written back (at least, I didn't see them in the file on the server). The "DO NOT DELETE..." message had a perfectly fine X-IMAP header, and up until I switched things were working great. The user visible symptom of this happened every time new spam arrived in my Junk folder [3] --- the new spam would arrive, be flagged as spam by Mail.app, and the earlier pieces of mail would promptly be unflagged! Anyway, Timo's clue in [2] prompted me to turn off both mbox_lazy_writes and mbox_dirty_syncs (the latter just on the off- chance... it's a low-volume server, so I can deal with the inefficiency). Lo and behold, Mail.app started acting sane again *and* the X-Keywords header appeared immediately. Oddly, during all of this, the Status and X-UID keywords would appear in the messages just fine; no clue as to why those and not X- Keywords. Version details are: - Dovecot 1.0rc13 [4] - FreeBSD 5.3-RELEASE - Apple Mail.app 2.1 (752/752.2) cheers, --joey [1] http://dovecot.org/list/dovecot/2006-March/011872.html [2] http://dovecot.org/list/dovecot/2006-June/014126.html [3] And it felt really strange while troubleshooting this as I found myself *hoping* for another piece of spam to arrive. Bleh. [4] Yes, two versions behind current, but in my defense, I did check the announcements and they didn't seem to mention the problem.

2 1

[Dovecot] DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA
by Gerhard Wiesinger 17 Feb '07

17 Feb '07

Hello! I see the internal message from pine with the following subject (mbox format, dovecot 1.0rc22): DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA As far as I know this message should be filtered. I never saw this before in previous 1.0 betas and 1.0rc (nearly every version tested). Any ideas Timo? Ciao, Gerhard -- http://www.wiesinger.com/

3 3

[Dovecot] Going nuts
by Mário Gamito 17 Feb '07

17 Feb '07

Hi, The subject says it all. For two days i've been trying to get IMAP and IMAPS working and nothing. I'm running CentOS 4.4 with qmail-ldap I just can't login in dovecot. Following my signature is some info. You can find my dovecot.conf at http://www.gamito.org/dovecot.conf I'm about to give up :( Any help would be appreciated. Warm Regards, Mário Gamito --------------------------------------------------------------------- [root@mail login]# telnet mail.sincity.lan 143 Trying 192.168.5.129... Connected to mail.sincity.lan (192.168.5.129). Escape character is '^]'. * OK Dovecot ready. O LOGIN gamito(a)mail.sincity.lan 143 O NO Temporary authentication failure. O LOGOUT * BYE Logging out O OK Logout completed. Connection closed by foreign host. -------------------------------------------------- [root@mail login]# tail /var/log/dovecot/dovecot.log dovecot: Feb 17 00:01:02 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=192.168.5.129 rip=192.168.5.129 resp=<hidden> dovecot: Feb 17 00:01:02 Info: auth(default): checkpassword(gamito(a)mail.sincity.lan,192.168.5.129): Executed: /usr/local/bin/auth_imap /usr/local/libexec/dovecot/checkpassword-reply dovecot: Feb 17 00:01:02 Info: auth(default): checkpassword(gamito(a)mail.sincity.lan,192.168.5.129): Received no input dovecot: Feb 17 00:01:02 Error: auth(default): checkpassword: Child 31122 died with signal 11 dovecot: Feb 17 00:01:04 Info: auth(default): client out: FAIL 1 user=gamito(a)mail.sincity.lan temp dovecot: Feb 17 00:01:10 Info: imap-login: Aborted login: user=<gamito(a)mail.sincity.lan>, method=PLAIN, rip=192.168.5.129, lip=192.168.5.129, secured -------------------------------------------------------------------------

3 10

[Dovecot] again... cross compiling
by Martin Höfling 17 Feb '07

17 Feb '07

> Create a cache file with the right values, or call configure with those > values set in the environment. OK, i ran configure with -C one time without cross compiler env set, to obtain the variables another time with -C to use the config.cache . I could not find anything related to the check whether size_t is signed. I found a variable which i set that way: ignored_signed_size=${ignore_signed_size=1} What's wrong with that? Cheers Martin P.S.: Is there a way to obtain all variables in an easy way, or to obtain the variable that has to be set by hand? -- Frag' nicht - Du könntest eine Antwort erhalten. (Markus Mehring in d.a.arnooo)

3 2

Re: [Dovecot] Reply-To header
by Kenny Dail 17 Feb '07

17 Feb '07

> On Fri, 2007-02-16 at 15:16 -0600, Richard Laager wrote: > > I see you've added a Reply-To header later. The canonical response in > > this case is for someone to reference: > > http://www.unicom.com/pw/reply-to-harmful.html > > Yes, I've read that page. It says basically that it makes replying > privately to the sender difficult. I'm sure it does, but in this list I > don't think pretty much anyone ever wants to reply to someone only > privately. Since deliberate choice is required to go in and set the maillist option, this is no different than if I configure my MUA to set the reply-to header on messages I send to the list. So the way it has been implemented for this list is not a problem at all. If people feel the need to reply to me off list, I feel that should be a deliberate choice on their part. -- Kenny Dail <kend(a)amigo.net>

1 0

Re: [Dovecot] Bug tracking system
by Kenny Dail 17 Feb '07

17 Feb '07

> > > I don't think I want an anonymous user to be able to create bugs. Maybe > > > what I'm after is an automatic user creation based on the given email > > > address, but the user won't be able to log in before verifying the > > > email. If a user already exists for the given email address, that bug > > > also belongs to that existing user even though no password was asked > > > (but it could mention that it was created anonymously and log the IP). > > > > But that's how most othe rregstration systems work too. All > > bugzilla/mailman etc. typically want is to verify the autheticity of > > the given email address. > > But why? If all you're doing is just adding a new bug, what's the point > of verifying the email address? It's just annoying to the user. Especially if someone like myself is already registered to the mailing list, I don't feel the need to go and register into a bugtracking system and have my email verified yet again. > I just made a simple mockup of what I'd like the "Enter new bug" page to > be like: http://dovecot.org/tmp/bug.html Nice and simple is good. I'd include a couple of other fields to make it easy to get useful info, like dovecot version and OS. But I'd really prefer to just email reports in to the list. > The log in page would then allow logging in with email/password, or > allow "registering" the user by sending a new password to the email. Perhaps it can just be integrated with the maillist login page? -- Kenny Dail <kend(a)amigo.net>

1 0

[Dovecot] filtering out LIST cruft?
by Dan Price 17 Feb '07

17 Feb '07

In planning our migration, I've noticed that lots of users have bits of lint in their ~/mail and/or ~/Mail. For example-- for an mbox called "blah" we may see: blah blah.msf (from Thunderbird) .blah.summary (from... I'm not sure, dtmail maybe) .blah_SIMS_index0003 (from our old IMAP server). When the user goes to "subscribe" they are often overloaded with too many items to choose from-- because all of these files are selectable in the UI-- LIST happily returns them. Is there a way to get dovecot to skip over these, by regex? Could it optionally "taste" files to see if they look like mboxes? I looked at the wiki and the source but didn't find anything. In the absence of this feature, I wonder how other sites have handled this? Obviously I can do some cleanup during migration, but I find that those pesky msf files like to come back. -dp -- Daniel Price - Solaris Kernel Engineering - dp(a)eng.sun.com - blogs.sun.com/dp

2 1

[Dovecot] imap core dump with rc18
by Nicolas STRANSKY 17 Feb '07

17 Feb '07

Hi, I had a core dump while using rc18. Here are the backtraces: Jan 23 01:01:44 rouge dovecot: IMAP(user): file mail-index-view.c: line 386 (_view_lookup_uid_range): assertion failed: (*last_seq_r >= *first_seq_r) Jan 23 01:01:44 rouge dovecot: IMAP(user): Raw backtrace: [0x47f25b00000000] Jan 23 01:01:44 rouge dovecot: child 24319 (imap) killed with signal 6 Core was generated by `imap'. Program terminated with signal 6, Aborted. Reading symbols from /lib/libdl.so.2...(no debugging symbols found)...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/libc.so.6...(no debugging symbols found)...done. Loaded symbols for /lib/libc.so.6 Reading symbols from /lib/ld-linux-x86-64.so.2...(no debugging symbols found)...done. Loaded symbols for /lib64/ld-linux-x86-64.so.2 #0 0x00002b3448083545 in raise () from /lib/libc.so.6 (gdb) bt full #0 0x00002b3448083545 in raise () from /lib/libc.so.6 No symbol table info available. #1 0x00002b3448084cce in abort () from /lib/libc.so.6 No symbol table info available. #2 0x0000000000465fd5 in i_set_failure_file () No symbol table info available. #3 0x000000000046585c in i_panic () No symbol table info available. #4 0x000000000044fff3 in mail_index_view_unref_maps () No symbol table info available. #5 0x00000000004505c7 in mail_index_lookup_uid_range () No symbol table info available. #6 0x000000000043be90 in index_storage_get_uids () No symbol table info available. #7 0x0000000000458d37 in mailbox_get_uids () No symbol table info available. #8 0x0000000000419eef in imap_messageset_parse () No symbol table info available. #9 0x000000000041aaae in imap_search_get_arg () No symbol table info available. #10 0x0000000000412e45 in cmd_fetch () No symbol table info available. #11 0x0000000000415910 in cmd_uid () No symbol table info available. #12 0x00000000004164a1 in _client_reset_command () No symbol table info available. #13 0x0000000000416430 in _client_reset_command () No symbol table info available. #14 0x0000000000416591 in _client_input () No symbol table info available. #15 0x000000000046b5bb in io_loop_handler_run () No symbol table info available. #16 0x000000000046ab4c in io_loop_run () No symbol table info available. ---Type <return> to continue, or q <return> to quit--- #17 0x000000000041dd1b in main () No symbol table info available. Regards, -- Nico Ce n'est pas en continuant de faire ce que l'on connaît que l'on pourra faire ce que l'on ne connaît pas

2 3