- dovecot - dovecot.org

[Dovecot] MUA notifications on new mail in a new folder?
by Kārlis Repsons 20 Jan '10

20 Jan '10

If deliver gets run with a non-root userid like this: < | deliver -m path/to/NEWmaildir >, I wonder, is a connected IMAP MUA automatically notified, that the new message has arrived in the new folder? As I see from some experiments with Thunderbird, it has no problems with immediate notifications of new mail in previously existing folders, however, it has problems with the case of new folder.

2 4

[Dovecot] outlook 2007 can't see public folders more than 1 deep
by Frank Cusack 20 Jan '10

20 Jan '10

dovecot-1.2.9 I have a public folder using ACLs to determine who can access it. namespace public { separator = / prefix = shared/ location = maildir:/var/maildir/shared subscriptions = no } Outlook 2007 can't see any folders except at the top level. It can create them just fine, but can't see them after quit and restart. For example, I can create the folder shared/foo/bar but on restart outlook only sees foo as a folder without subfolders (no + to expand it) and doesn't see bar anymore. In fact I can delete the folder foo in outlook and then BOTH .foo and .foo.bar directories are removed on the server. When you click on foo, the error message in the mail pane is "Cannot display the folder. The folder 'foo' cannot contain items. This is most likely a limitation of your IMAP server. In order to create a folder that can contain items, be sure not to append '/' to its name as you create it." -frank

2 2

[Dovecot] md5_verify(...): Not a valid MD5-CRYPT or PLAIN-MD5 password
by BaQs 20 Jan '10

20 Jan '10

'afternoon list! I use mysql as userdb, which contains two type of password schemes: DES and MD5-CRYPT. I read there : http://wiki.dovecot.org/Authentication/PasswordSchemes that both are supported by dovecot. Unfortunately, dovecot keeps saying: Not a valid MD5-CRYPT or PLAIN-MD5 password when looking for a user with DES encrypted password. Is dovecot able to recognize password scheme, or do I have to do something else ? I can't add {DES} to DES passwords, as this database is used with many other softwares. Thanks a lot for your help Pierre

3 2

[Dovecot] Two different issues with dovecot 1.1.13
by Stuart Rowan 20 Jan '10

20 Jan '10

Hi Timo, I'm using Debian backports.org dovecot-imapd, 1:1.1.13-2~bpo50+1. I've got two different issues, a reoccurring, seemingly harmless one about "Corrupted index cache file" (boring.txt) and one that went bonkers over the least few days (bt.txt) causing much spamming of the logs. I've made bt.txt stop happening by just rm'ing dovecot.index* : find Maildir/ -type f -name 'dovecot.index*' -print0 | xargs -0r rm ... which I realise may not be the most helpful thing to have done from your point of view. Anyway I just wanted to let you know about both of these. If one or both are already known about or already fixed by a later version of Dovecot, great and sorry for the noise! If not, and you want any more information etc., let me know. Many thanks, Stu. dovecot: 2009-07-28 10:23:16 Error: IMAP(strr): Corrupted index cache file /home/local/strr/Maildir/dovecot.index.cache: record continues outside its allocated size dovecot: 2009-07-28 10:23:56 Error: IMAP(strr): Corrupted index cache file /home/local/strr/Maildir/dovecot.index.cache: record continues outside its allocated size dovecot: 2009-07-28 08:05:54 Panic: IMAP(strr): file index-mail-headers.c: line 77 (index_mail_parse_header_finish): assertion failed: ((match[match_idx] & HEADER_MAT CH_FLAG_FOUND) == 0) dovecot: 2009-07-28 08:05:54 Error: IMAP(strr): Raw backtrace: imap [0x48dbf2] -> imap [0x48dc73] -> imap [0x48d346] -> imap(index_mail_parse_header+0x617) [0x4545f7] -> imap [0x483284] -> imap [0x483478] -> imap(i_stream_read+0x2c) [0x491d7c] -> imap(i_stream_read_data+0x46) [0x491f16] -> imap(message_get_body_size+0x108) [0x4885 a8] -> imap [0x4226c3] -> imap(imap_fetch+0x162) [0x420852] -> imap(cmd_fetch+0x23c) [0x41a27c] -> imap [0x41e46c] -> imap [0x41e51d] -> imap [0x41eb25] -> imap(clien t_input+0x63) [0x41efd3] -> imap(io_loop_handler_run+0xcb) [0x49515b] -> imap(io_loop_run+0x18) [0x4945c8] -> imap(main+0x3da) [0x426bea] -> /lib/libc.so.6(__libc_sta rt_main+0xe6) [0x7f0e851941a6] -> imap [0x418859] dovecot: 2009-07-28 08:05:54 Error: child 20007 (imap) killed with signal 6 (core dumps disabled) dovecot: 2009-07-28 08:05:56 Panic: IMAP(strr): file index-mail-headers.c: line 77 (index_mail_parse_header_finish): assertion failed: ((match[match_idx] & HEADER_MAT CH_FLAG_FOUND) == 0) dovecot: 2009-07-28 08:05:56 Error: IMAP(strr): Raw backtrace: imap [0x48dbf2] -> imap [0x48dc73] -> imap [0x48d346] -> imap(index_mail_parse_header+0x617) [0x4545f7] -> imap [0x483284] -> imap [0x483478] -> imap(i_stream_read+0x2c) [0x491d7c] -> imap(i_stream_read_data+0x46) [0x491f16] -> imap(message_get_body_size+0x108) [0x4885 a8] -> imap [0x4226c3] -> imap(imap_fetch+0x162) [0x420852] -> imap(cmd_fetch+0x23c) [0x41a27c] -> imap [0x41e46c] -> imap [0x41e51d] -> imap [0x41eb25] -> imap(clien t_input+0x63) [0x41efd3] -> imap(io_loop_handler_run+0xcb) [0x49515b] -> imap(io_loop_run+0x18) [0x4945c8] -> imap(main+0x3da) [0x426bea] -> /lib/libc.so.6(__libc_sta rt_main+0xe6) [0x7f2edf08b1a6] -> imap [0x418859] dovecot: 2009-07-28 08:05:56 Error: child 20984 (imap) killed with signal 6 (core dumps disabled)

2 5

[Dovecot] Autobuilder packages for Debian stable/i386 now available
by Stephan Bosch 20 Jan '10

20 Jan '10

Hi, A few days back I started the first automated slave builder that produces bleeding edge Debian stable packages for Dovecot v1.2 and v2.0. It uses the source packages already provided by the automated master repository (which builds binary packages for Debian testing), so that the version numbers and content are equal throughout all Debian releases. The repository is available as follows: deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-1.2 main Or, for Dovecot v2.0: deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.0 main Read this for more information: http://wiki.dovecot.org/PrebuiltBinaries#Automatically_Built_Packages I hope to add amd64 binary support soon. Regards, Stephan.

1 0

Re: [Dovecot] Oracle SQL driver
by Alexander Bukharov 20 Jan '10

20 Jan '10

> The transaction handling doesn't look correct to me. The sql_update()s > just add the change to a linked list and commit() is then supposed to > run them in one transaction and either everything should succeed or > fail. Your commit appears to ignore errors and just commit everything > that goes through? Also since nothing is actually sent before commit(), > your rollback() shouldn't need to send ROLLBACK. You right. I've corrected the transaction handling mechanism. The only thing I couldn't understand: why rollback() shouldn't need to make real ROLLBACK? In case when whole transaction was failed succeded statements will remain uncommited. Then they will be commited later on next successful transaction. May be ROLLBACK is still needed? > The "VARCHAR sqltext[2048]" seems like an unnecessary restriction on the > query length. Wasn't there a way to do this without the limit? Or in AFAIK there is no possibility to use C types in PREPARE statement. Also Oracle cannot handle unsized VARCHARs. I've increased VARCHAR size to 65535. > test_connection() seems unnecessary. Right you are. > Couldn't driver_oracle_generate_name() be simply: > static unsigned int counter = 0; > return i_strdup_printf("ORACONN_%x", ++counter); =) Right. > driver_oracle_escape_string() really should be escaping the string. I made this function to replace single quote in string with two single quotes. IMHO this should be enough. How do you think? > Kind of annoying that each query needs a cursor, even though nearly all > queries are expected to return only a single row, but I guess that can't > be helped with the current API.. Yes. There are no other ways to work with untyped statements in OCI. But Oracle claims that all these statements shouldn't produce significant performance impact. The new version attached.

2 3

[Dovecot] ManageSieve doe not work
by Mike Werner 20 Jan '10

20 Jan '10

Hi, I use MailScanner 4.74.16 (Ubuntu karmic). I convigured ManageSieve as discribed in http://wiki.dovecot.org/ManageSieve/Configuration. But sieve scripts are not applied to incoming mail. How can I determin what went wrong? -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

2 1

[Dovecot] Dovecot 2.0 beta imap session crash report
by wenjie zheng 20 Jan '10

20 Jan '10

System config: RHEL 5.3, 64 bit Dovecot 2.0 beta (changeset "2882650531e0", 10 days old) installed with lda and lmtp Symptom: IMAP session crashed when I tried to delete a non-exist mailbox, e.g., Trash in my test [root@mail4a LocalIntegrationTest]# telnet localhost 143 * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN] Dovecot ready. a login testmail4a2(a)dev.p4nt5.com xxxxxx a OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT SORT=DISPLAY THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH QUOTA] Logged in a delete Trash Connection closed by foreign host. Error log: Jan 12 12:33:26 mail4a dovecot: imap(testmail4a2(a)dev.p4nt5.com): maildir++: root=/data/mail/de/dev.p4nt5.com/te/testmail4a2, index=, control=, inbox= Jan 12 12:33:31 mail4a dovecot: imap(testmail4a2(a)dev.p4nt5.com): open() failed with index file (null): Bad address Jan 12 12:33:31 mail4a dovecot: master: service(imap): child 20867 killed with signal 11 (core dumps disabled) How to reproduce: Delete a non-exist mailbox after login Thanks, Wenjie

2 3

Re: [Dovecot] ManageSieve doe not work
by Nick Rosier 20 Jan '10

20 Jan '10

Mike Werner wrote: > Hi, > > I use MailScanner 4.74.16 (Ubuntu karmic). I convigured ManageSieve as > discribed in http://wiki.dovecot.org/ManageSieve/Configuration. But sieve > scripts are not applied to incoming mail. How can I determin what went > wrong? ManageSieve is to manage sieve filters. Your MDA does the filtering. Have you configured Dovecot deliver as your MDA? See: http://wiki.dovecot.org/LDA N.

1 0

Re: [Dovecot] How can I configure dovecot as gmail imap proxy
by Supratik Goswami 20 Jan '10

20 Jan '10

Here the proxy server should authenticate the user. If the user is in the list of authenticated users then dovecot will allow to connect to imap.gmail.com. Consider a scenario where a client tries to read his mailbox from imap.gmail.com:993. Client executes the command "mutt -f imaps://imap.gmail.com", the request is first authenticated at the proxy server. If the request is coming from a valid user, dovecot will allow to connect to imap.gmail.com and fetch mails for that user. Can you please help me with the steps to configure the server. Warm Regards Supratik

2 1