Re: [Dovecot] Capability problems dovecot 2.0
Timo Sirainen schrieb: > Oh, yes, that's it! When I wrote the code I noticed that the line looked > a bit short. I thought it might have been because it was missing '.' at > the end that all other commands had, but it must have been the lack of > OK that kept nagging my subconsciousness. :) > > Fixed: http://hg.dovecot.org/dovecot-2.0/rev/02679d365af7 > > Cool! That did the trick. I'll investigate about the capability stuff now... Regards, Sebastian
Re: [Dovecot] For the record: Postfix+Spamassassin+ClamAV+Dovecot
Egbert Jan van den Bussche wrote: >> -Oorspronkelijk bericht- >> Van: dovecot-bounces+egbert=vandenbussche...@dovecot.org >> [mailto:dovecot-bounces+egbert=vandenbussche...@dovecot.org] >> Namens James Butler >> Verzonden: vrijdag 17 april 2009 20:58 >> Aan: Dovecot Mailing List >> Onderwerp: [Dovecot] For the record: >> Postfix+Spamassassin+ClamAV+Dovecot >> >> >> Postfix 2.5.5 >> SpamAssassin 3.2.5 (under Perl 5.10.0) >> ClamAV 0.95.1 >> Dovecot 1.2.rc2 >> >> works fine on Fedora 10. >> >> Installed Dovecot and ClamAV from source and everything else >> using yum. >> >> I'm using the ClamAV plugin for Spamassassin: >> http://wiki.apache.org/spamassassin/ClamAVPlugin >> >> I'm calling Spamassassin with: >> >> /etc/postfix/main.cf: >> mailbox_command = /usr/bin/spamc -f -e >> /usr/local/libexec/dovecot/deliver >> >> Postfix hands off to Spamassassin, which processes ALL mail (not just >> attachments) through the ClamAV plugin before parsing for >> spam, and then hands the whole mess off to Dovecot for >> 'deliver' to handle. >> >> How simple is that? >> >> Since ClamAV scanns all mail, it might be too >> processor-intensive for really large mail systems, but it is >> working great for our 120+ user system with lots of spam >> coming in. If you're using Procmail or some other >> preprocessor that can hand off to a pipe, then you could skip >> the plugin and pipe messages over a certain size (i.e. >1024) >> to clamd, instead. >> >> Enjoy! >> >> James > > Hi! > > Apologies for digging an old thread from the bin. I was wondering how this > relates to Amavisd? Should I regard the proposed plugin solution as a 'poor > mans' solution when one does not want to install amavis? > > Thanks! > Egbert Jan (NL) > > The plugin setup is required for my solution because of issues between Procmail and Postfix when Postfix is running in a QMail-style Maildir setup, which Procmail seems to have issues with, at least for me. (I couldn't get Procmail to recognize environment variables correctly in my Fedora 10 installation, so I just stopped using it in favor of Dovecot's Sieve.) Amavisd would *replace* Procmail, similar to what Sieve would do. You would pipe your mail to Amavisd, test messages there, and then send qualified messages to 'deliver' or to another program for further processing/flagging. For example, under Amavisd, you would want to test for messages >1024 bytes (1 MB) and pipe them through your anti-virus app and then from there *back* to Amavisd to check for virus flags (into the bit bucket or 'deliver' to the user's 'Possible Virus' directory) and then on to 'deliver' for normal delivery if there were no flags. I've never used Amavisd, but this seems to be its purpose. FYI, the above setup is easy to administer and since additional apps are not required, it keeps the overhead down a bit. It could be considered a "poor man's replacement" for Amavisd in that it makes Amavisd irrelevant, AFAIK ... but Amavisd probably does other stuff that I simply haven't found the need for, so I really couldn't tell you. James
Re: [Dovecot] Capability problems dovecot 2.0
On Mon, 2009-06-01 at 21:05 +0200, reg9009 wrote: > Note the answer to the login request. I think dovecot 2.0 always missed > the starting "OK ...". Maybe this is the problem? Oh, yes, that's it! When I wrote the code I noticed that the line looked a bit short. I thought it might have been because it was missing '.' at the end that all other commands had, but it must have been the lack of OK that kept nagging my subconsciousness. :) Fixed: http://hg.dovecot.org/dovecot-2.0/rev/02679d365af7 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Capability problems dovecot 2.0
Timo Sirainen schrieb: > On Mon, 2009-06-01 at 20:29 +0200, reg9009 wrote: > >> The effect on Outlook/OE is that it keeps asking for the password... >> > > Hmh. What about with the attached patch? I guess it then at least logs > in, but does it use IDLE? > > unfortunately the patch doesn't work either. But I think I've got the cause: Outlook Express working with dovecot 1.2: 0.010098 10.4.1.172 -> 10.4.1.100 IMAP Response: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. 0.031029 10.4.1.100 -> 10.4.1.172 IMAP Request: 447p CAPABILITY 0.031086 10.4.1.172 -> 10.4.1.100 IMAP Response: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH QUOTA AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 0.044316 10.4.1.100 -> 10.4.1.172 IMAP Request: 4q67 LOGIN "i...@.com" "mypassword" 0.066054 10.4.1.172 -> 10.4.1.100 IMAP Response: 4q67 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT 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 0.080616 10.4.1.100 -> 10.4.1.172 IMAP Request: gb5g IDLE same Outlook Express not working with dovecot 2.0: 59.755482 10.4.1.171 -> 10.4.1.100 IMAP Response: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. 59.764561 10.4.1.100 -> 10.4.1.171 IMAP Request: 2rzz CAPABILITY 59.764624 10.4.1.171 -> 10.4.1.100 IMAP Response: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 59.786662 10.4.1.100 -> 10.4.1.171 IMAP Request: lfjo LOGIN "i...@.com" "mypassword" 59.790349 10.4.1.171 -> 10.4.1.100 IMAP Response: lfjo Logged in Note the answer to the login request. I think dovecot 2.0 always missed the starting "OK ...". Maybe this is the problem? Regards, Sebastian
Re: [Dovecot] uid fetch error with revision 9112:9d634c93d28a
On Jun 1, 2009, at 2:37 PM, Timo Sirainen wrote:
On Mon, 2009-06-01 at 14:31 -0400, Timo Sirainen wrote:
On Mon, 2009-06-01 at 14:20 -0400, Jonathan Siegle wrote:
2 uid fetch somevaliduid 5 uid fetch 4 (BODYSTRUCTURE
BODY.PEEK[])
5 BAD Error in IMAP command UID: Unknown command BODYSTRUCTURE
This should fix it: http://hg.dovecot.org/dovecot-1.2/rev/
4d2b2adfd415
And http://hg.dovecot.org/dovecot-1.2/rev/9ae55b68cf61
3 fetch 1 bodystructure
* 1 FETCH (BODYSTRUCTURE ("text" "plain" ("charset" "iso-8859-1") NIL
NIL "7bit" 555 13 NIL ("inline" NIL) NIL NIL))
3 OK Fetch completed.
4 uid fetch 1 (BODYSTRUCTURE BODY.PEEK[])
* 1 FETCH (UID 1 BODYSTRUCTURE ("text" "plain" ("charset"
"iso-8859-1") NIL NIL "7bit" 555 13 NIL ("inline" NIL) NIL NIL) BODY[]
{3953}
.
.
.
.
4 OK Fetch completed.
And there was much cheering in central Pennsylvania...
thanks,
Jonathan
smime.p7s
Description: S/MIME cryptographic signature
Re: [Dovecot] Capability problems dovecot 2.0
On Mon, 2009-06-01 at 20:29 +0200, reg9009 wrote:
> The effect on Outlook/OE is that it keeps asking for the password...
Hmh. What about with the attached patch? I guess it then at least logs
in, but does it use IDLE?
diff -r 36311318a958 src/imap/main.c
--- a/src/imap/main.c Mon Jun 01 14:37:18 2009 -0400
+++ b/src/imap/main.c Mon Jun 01 14:40:37 2009 -0400
@@ -109,9 +109,9 @@
/* client doesn't seem to understand tagged capabilities. send
untagged instead and hope that it works. */
o_stream_cork(client->output);
+ client_send_line(client, t_strconcat(tag, " Logged in", NULL));
client_send_line(client, t_strconcat("* CAPABILITY ",
str_c(client->capability_string), NULL));
- client_send_line(client, t_strconcat(tag, " Logged in", NULL));
o_stream_uncork(client->output);
} else {
client_send_line(client, t_strconcat(
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] uid fetch error with revision 9112:9d634c93d28a
On Mon, 2009-06-01 at 14:31 -0400, Timo Sirainen wrote: > On Mon, 2009-06-01 at 14:20 -0400, Jonathan Siegle wrote: > > 2 uid fetch somevaliduid 5 uid fetch 4 (BODYSTRUCTURE BODY.PEEK[]) > > > 5 BAD Error in IMAP command UID: Unknown command BODYSTRUCTURE > > This should fix it: http://hg.dovecot.org/dovecot-1.2/rev/4d2b2adfd415 And http://hg.dovecot.org/dovecot-1.2/rev/9ae55b68cf61 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] uid fetch error with revision 9112:9d634c93d28a
On Mon, 2009-06-01 at 14:20 -0400, Jonathan Siegle wrote: > 2 uid fetch somevaliduid 5 uid fetch 4 (BODYSTRUCTURE BODY.PEEK[]) > > 5 BAD Error in IMAP command UID: Unknown command BODYSTRUCTURE This should fix it: http://hg.dovecot.org/dovecot-1.2/rev/4d2b2adfd415 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Capability problems dovecot 2.0
> So it saw the CAPABILITY response, but apparently not the tagged OK > response, and then it timed out and tried again later? But two things: > > 1) The post-login CAPABILITY reply is wrong. Did you set imap_capability > setting manually? Remove it. > > 2) Did Dovecot really not send OK reply or did Outlook just ignore it? > Hmm. Does this help? http://hg.dovecot.org/dovecot-2.0/rev/8ecbc7fefeb2 > > Hi, 1) hihi, sorry, I had one line left. I removed it, but still no luck. 2) I tried your patch, unfortunately no lock, too. The effect on Outlook/OE is that it keeps asking for the password... Again, TB ok. Here's the Output from Outlook Express and Outlook (10.4.1.100 being the client). Outlook Express: 0.00 10.4.1.100 -> 10.4.1.171 TCP 4666 > 143 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 0.24 10.4.1.171 -> 10.4.1.100 TCP 143 > 4666 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460 0.009113 10.4.1.100 -> 10.4.1.171 TCP 4666 > 143 [ACK] Seq=1 Ack=1 Win=65535 Len=0 0.009390 10.4.1.171 -> 10.4.1.100 IMAP Response: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. 0.017003 10.4.1.100 -> 10.4.1.171 IMAP Request: ekbc CAPABILITY 0.017016 10.4.1.171 -> 10.4.1.100 TCP 143 > 4666 [ACK] Seq=140 Ack=18 Win=5840 Len=0 0.017064 10.4.1.171 -> 10.4.1.100 IMAP Response: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 0.031096 10.4.1.100 -> 10.4.1.171 IMAP Request: f1pb LOGIN "i...@.com" "mypassword" 0.034449 10.4.1.171 -> 10.4.1.100 IMAP Response: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH 0.190491 10.4.1.100 -> 10.4.1.171 TCP 4666 > 143 [ACK] Seq=57 Ack=551 Win=64985 Len=0 Outlook: 0.00 10.4.1.100 -> 10.4.1.171 TCP 6106 > 143 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 0.23 10.4.1.171 -> 10.4.1.100 TCP 143 > 6106 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460 0.004025 10.4.1.100 -> 10.4.1.171 TCP 5521 > 143 [SYN] Seq=0 Win=65535 Len=0 MSS=1460 0.004033 10.4.1.171 -> 10.4.1.100 TCP 143 > 5521 [SYN, ACK] Seq=0 Ack=1 Win=5840 Len=0 MSS=1460 0.012960 10.4.1.100 -> 10.4.1.171 TCP 6106 > 143 [ACK] Seq=1 Ack=1 Win=65535 Len=0 0.013235 10.4.1.171 -> 10.4.1.100 IMAP Response: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. 0.016882 10.4.1.100 -> 10.4.1.171 TCP 5521 > 143 [ACK] Seq=1 Ack=1 Win=65535 Len=0 0.017119 10.4.1.171 -> 10.4.1.100 IMAP Response: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. 0.073274 10.4.1.100 -> 10.4.1.171 IMAP Request: 4zn6 CAPABILITY 0.073299 10.4.1.171 -> 10.4.1.100 TCP 143 > 6106 [ACK] Seq=140 Ack=18 Win=5840 Len=0 0.073371 10.4.1.171 -> 10.4.1.100 IMAP Response: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 0.076474 10.4.1.100 -> 10.4.1.171 IMAP Request: knp1 CAPABILITY 0.076485 10.4.1.171 -> 10.4.1.100 TCP 143 > 5521 [ACK] Seq=140 Ack=18 Win=5840 Len=0 0.076546 10.4.1.171 -> 10.4.1.100 IMAP Response: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 0.079959 10.4.1.100 -> 10.4.1.171 IMAP Request: o5bw LOGIN "i...@.com" "mypassword" 0.083921 10.4.1.100 -> 10.4.1.171 IMAP Request: ed0l LOGIN "i...@.com" "mypassword" 0.086463 10.4.1.171 -> 10.4.1.100 IMAP Response: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH 0.089829 10.4.1.171 -> 10.4.1.100 IMAP Response: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH 0.280062 10.4.1.100 -> 10.4.1.171 TCP 5521 > 143 [ACK] Seq=57 Ack=551 Win=64985 Len=0 0.280156 10.4.1.100 -> 10.4.1.171 TCP 6106 > 143 [ACK] Seq=57 Ack=551 Win=64985 Len=0 Regards, Sebastian
Re: [Dovecot] uid fetch error with revision 9112:9d634c93d28a
On Jun 1, 2009, at 1:59 PM, Timo Sirainen wrote: On Mon, 2009-06-01 at 12:59 -0400, Jonathan Siegle wrote: On Jun 1, 2009, at 12:27 PM, Timo Sirainen wrote: On Mon, 2009-06-01 at 11:03 -0400, Jonathan Siegle wrote: This command fails: 2 uid fetch somevaliduid 5 uid fetch 4 (BODYSTRUCTURE BODY.PEEK[]) 5 BAD Error in IMAP command UID: Unknown command BODYSTRUCTURE 2 BAD Error in IMAP command UID: Unknown command BODYSTRUCTURE http://hg.dovecot.org/dovecot-1.2/rev/f1a6c9dd4c33 ? Nope. I can tell you that it definitely works in 1.2rc3 from May 4th and I think it _might_ have worked as of early last week. This is using mbox storage. The client doing this is OSX Mail.app version 3.6(935/935.3). I can't seem to be able to reproduce this. What plugins do you have loaded? Can you manually try a few commands? telnet localhost 143 1 login user pass 2 select inbox 3 fetch 1:* flags 4 uid fetch 1:* flags 5 fetch 1 bodystructure Sure. The problem for me is somewhere between revision 9061(works) and 9098(doesn't work). I don't select inbox. I select a folder to try to take plugins out of the picture. I'll keep doing my binary search to find the changeset that breaks.. 2 select foo4 * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $NotJunk NonJunk) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $NotJunk NonJunk \*)] Flags permitted. * 10 EXISTS * 0 RECENT * OK [UIDVALIDITY 1] UIDs valid * OK [UIDNEXT 11] Predicted next UID * OK [HIGHESTMODSEQ 1] 2 OK [READ-WRITE] Select completed. 3 fetch 1:* flags * 1 FETCH (FLAGS (\Seen $NotJunk)) * 2 FETCH (FLAGS (\Seen $NotJunk)) * 3 FETCH (FLAGS (\Seen $NotJunk NonJunk)) * 4 FETCH (FLAGS (\Seen $NotJunk NonJunk)) * 5 FETCH (FLAGS (\Seen $NotJunk NonJunk)) * 6 FETCH (FLAGS (\Seen $NotJunk NonJunk)) * 7 FETCH (FLAGS (\Seen $NotJunk)) * 8 FETCH (FLAGS (\Seen $NotJunk)) * 9 FETCH (FLAGS (\Seen $NotJunk)) * 10 FETCH (FLAGS (\Seen $NotJunk)) 3 OK Fetch completed. 4 fetch 1 bodystructure 4 BAD Error in IMAP command FETCH: Unknown command BODYSTRUCTURE 4 uid fetch 1:* flags * 1 FETCH (UID 1 FLAGS (\Seen $NotJunk)) * 2 FETCH (UID 2 FLAGS (\Seen $NotJunk)) * 3 FETCH (UID 3 FLAGS (\Seen $NotJunk NonJunk)) * 4 FETCH (UID 4 FLAGS (\Seen $NotJunk NonJunk)) * 5 FETCH (UID 5 FLAGS (\Seen $NotJunk NonJunk)) * 6 FETCH (UID 6 FLAGS (\Seen $NotJunk NonJunk)) * 7 FETCH (UID 7 FLAGS (\Seen $NotJunk)) * 8 FETCH (UID 8 FLAGS (\Seen $NotJunk)) * 9 FETCH (UID 9 FLAGS (\Seen $NotJunk)) * 10 FETCH (UID 10 FLAGS (\Seen $NotJunk)) 4 OK Fetch completed. 5 uid fetch 4 (BODYSTRUCTURE BODY.PEEK[]) 5 BAD Error in IMAP command UID: Unknown command BODYSTRUCTURE ./dovecot -n # 1.2.rc4: /usr/ladmin3/etc/dovecot.conf # OS: AIX 3 0001112AD300 syslog_facility: local0 protocols: imap listen: *:someport ssl: no disable_plaintext_auth: no login_dir: /usr/ladmin3/var/run/dovecot/login login_executable: /usr/ladmin3/libexec/dovecot/imap-login login_greeting: Dovecot baseline ready. login_processes_count: 30 max_mail_processes: 4096 mail_location: mbox:%h mmap_disable: yes dotlock_use_excl: no mbox_write_locks: fcntl mail_plugins: mbox_snarf mail_plugin_dir: /usr/ladmin3/lib/dovecot/imap/ imap_client_workarounds: tb-extra-mailbox-sep imap_id_log: * namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: ~/ hidden: yes list: no subscriptions: yes auth default: krb5_keytab: /etc/myfavoritekeytab verbose: yes debug: yes passdb: driver: pam userdb: driver: passwd plugin: mbox_snarf: %h/SNARF smime.p7s Description: S/MIME cryptographic signature
Re: [Dovecot] Namespace delimiter...
Timo Sirainen pisze: OK, then I think you'll just have to end up patching that small part of Dovecot. Supporting NIL separator seems like more trouble than worth. Maybe you can also do something similar to how Maildir++ works, just decide that e.g. ^ character is a hierarchy separator and have Dovecot use that? Thanks for your help and some advices. Decision is not my. As I said IMAP must earn some cash, before we start seriously think about it. Now we have NIL hardcoded (print NIL instead of ns->separator in strings) and this works for us. It is possible to have ns->separator in our storage, but we must have time (and cash) to implement this functionality in MySQL functions and Webmail. Redgards, Konrad
Re: [Dovecot] Can expire-tool skip folders with "expire time in future" errors?
On Mon, 2009-06-01 at 13:09 -0400, Charles Marcus wrote: > On 6/1/2009 12:40 PM, Timo Sirainen wrote: > >>> Were the messages moved there before expire plugin was loaded? Those > >>> aren't tracked. > > >> Is there a simple way to fix this? Ie, maybe a script that could be run > >> the first time a folder is added to the list, to add all of the current > >> messages as of that date? > > > Does it really matter if it just takes a couple of weeks to start > > working? Seems like too much extra work for little gain. :) > > I'm thinking about when expire is enabled on a folder that already has > lots of mail in it... But does it matter if they're deleted immediately or only 2 weeks from now? It gets done eventually anyway. > But I guess this could just be scripted by the local admin when > needed... but what would be the proper way to do this? Would a simple > 'touch' do it without breaking anything? Expire plugin won't add old mails to the database no matter what you do. Admin could of course just manually delete those old mails. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] uid fetch error with revision 9112:9d634c93d28a
On Mon, 2009-06-01 at 12:59 -0400, Jonathan Siegle wrote: > On Jun 1, 2009, at 12:27 PM, Timo Sirainen wrote: > > > On Mon, 2009-06-01 at 11:03 -0400, Jonathan Siegle wrote: > >> This command fails: > >> 2 uid fetch somevaliduid (BODYSTRUCTURE BODY.PEEK[]) > >> 2 BAD Error in IMAP command UID: Unknown command BODYSTRUCTURE > > > > http://hg.dovecot.org/dovecot-1.2/rev/f1a6c9dd4c33 ? > > > > Nope. I can tell you that it definitely works in 1.2rc3 from May 4th > and I think it _might_ have worked as of early last week. This is > using mbox storage. The client doing this is OSX Mail.app version > 3.6(935/935.3). I can't seem to be able to reproduce this. What plugins do you have loaded? Can you manually try a few commands? telnet localhost 143 1 login user pass 2 select inbox 3 fetch 1:* flags 4 uid fetch 1:* flags 5 fetch 1 bodystructure signature.asc Description: This is a digitally signed message part
Re: [Dovecot] uid fetch error with revision 9112:9d634c93d28a
On Jun 1, 2009, at 12:59 PM, Jonathan Siegle wrote: On Jun 1, 2009, at 12:27 PM, Timo Sirainen wrote: On Mon, 2009-06-01 at 11:03 -0400, Jonathan Siegle wrote: This command fails: 2 uid fetch somevaliduid (BODYSTRUCTURE BODY.PEEK[]) 2 BAD Error in IMAP command UID: Unknown command BODYSTRUCTURE http://hg.dovecot.org/dovecot-1.2/rev/f1a6c9dd4c33 ? Nope. I can tell you that it definitely works in 1.2rc3 from May 4th and I think it _might_ have worked as of early last week. This is using mbox storage. The client doing this is OSX Mail.app version 3.6(935/935.3). Thanks, Jonathan I can also tell you that it worked on the May 14th revision. smime.p7s Description: S/MIME cryptographic signature
Re: [Dovecot] Can expire-tool skip folders with "expire time in future" errors?
On 6/1/2009 12:40 PM, Timo Sirainen wrote: >>> Were the messages moved there before expire plugin was loaded? Those >>> aren't tracked. >> Is there a simple way to fix this? Ie, maybe a script that could be run >> the first time a folder is added to the list, to add all of the current >> messages as of that date? > Does it really matter if it just takes a couple of weeks to start > working? Seems like too much extra work for little gain. :) I'm thinking about when expire is enabled on a folder that already has lots of mail in it... But I guess this could just be scripted by the local admin when needed... but what would be the proper way to do this? Would a simple 'touch' do it without breaking anything? -- Best regards, Charles
Re: [Dovecot] 1.2.beta1: expire-tool and 'mail_location' setting
Timo Sirainen schrieb:
> On Mon, 2009-06-01 at 17:43 +0200, e-frog wrote:
Thanks Timo! It works now as long as there is no namespace for the virtual
plugin defined:
>>> http://hg.dovecot.org/dovecot-1.2/rev/6fd725b94504
>>> http://hg.dovecot.org/dovecot-1.2/rev/531083e6e84a
>> The above doesn't seem to fix it completely. However after adding
>> module_dir_init(modules) it works:
>
> OK, added.
>
>>> Then put mail_plugins setting outside protocol {}.
>>>
>> It looks like the mail_plugins setting outside protocol has no effect.
> ..
>> These are the settings from the protocol imap section.
>
> Oh, right. That's because of how it's implemented in v1.2. Kind of ugly,
> but I don't know if I'll bother fixing it until it becomes a real
> problem for someone. :) v2.0 implements this properly.
Sure, the current implementation works for me. Thanks again Timo!
Re: [Dovecot] uid fetch error with revision 9112:9d634c93d28a
On Jun 1, 2009, at 12:27 PM, Timo Sirainen wrote: On Mon, 2009-06-01 at 11:03 -0400, Jonathan Siegle wrote: This command fails: 2 uid fetch somevaliduid (BODYSTRUCTURE BODY.PEEK[]) 2 BAD Error in IMAP command UID: Unknown command BODYSTRUCTURE http://hg.dovecot.org/dovecot-1.2/rev/f1a6c9dd4c33 ? Nope. I can tell you that it definitely works in 1.2rc3 from May 4th and I think it _might_ have worked as of early last week. This is using mbox storage. The client doing this is OSX Mail.app version 3.6(935/935.3). Thanks, Jonathan smime.p7s Description: S/MIME cryptographic signature
[Dovecot] Feature Missing OUTBOX Folder
At 1:13 PM +0200 4/2/07, Frank Doege wrote: >/thanks steffen, this will work for me till we have a plugin :-)/ What do you see as the benefit of a Dovecot plugin over a free-standing sending gadget? Also, Dovecot could advertise an ad-hoc IMAP capacity, which could be understood by MUAs.
Re: [Dovecot] Users with large (4GB) inboxes crippling dovecot
on 5-30-2009 2:25 PM Roy Sigurd Karlsbakk spake the following: > On 30. mai. 2009, at 00.03, Scott Silva wrote: > >> # e2fsck -D -f /dev/hdXY >> >> Note: This should work with both ext2 and ext3 filesystems. Depending >> on the >> size of your filesystem, this could take a long time. Perhaps you >> should go >> get some coffee... > > > AFAIK an "updatedb" (as in locate/slocate), or perhaps just a "find /" > should access all directories and make and index in each of them. That > way you won't need to umount the fs. > If you look at the quoted text, an fsck is required on pre-existing directories. They don't have the proper extents or index structures if created before directory_index is turned on. No other program is going to update the directory indexes. You can read those directories as many times as you want, it won't change it. signature.asc Description: OpenPGP digital signature
Re: [Dovecot] IMAP labeling sometimes not taken into account
On Mon, 2009-06-01 at 12:43 +0200, Olivier Cailloux wrote: > Since the change for dovecot, however, things are going strange. > Sometimes the labels disappear for some reasons. Sometimes they stay > there. And I can't reproduce the behavior, it just seems random. This is > very annoying as it totally breaks my e-mail management. Yes, there have been some bugs related to handling them. > clients agree: this e-mail has a "5" label. BUT when I open the mbox > file directly on the imap server (using "less"), and scroll to that > given e-mail, I see NO "X-Keywords: " line. How then can the e-mail > clients know that this e-mail is labeled? The keywords are also stored in Dovecot's index files. Although they should still be written to mbox files too. > 2-12h38-~#dovecot --version > 1.0.15 I'd first try a recent v1.1 release. It might have already fixed this bug. Also you could try if setting mbox_lazy_writes=no helps. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Can expire-tool skip folders with "expire time in future" errors?
On Mon, 2009-06-01 at 06:33 -0400, Charles Marcus wrote: > On 5/31/2009, Timo Sirainen (t...@iki.fi) wrote: > > Were the messages moved there before expire plugin was loaded? Those > > aren't tracked. > > Is there a simple way to fix this? Ie, maybe a script that could be run > the first time a folder is added to the list, to add all of the current > messages as of that date? Does it really matter if it just takes a couple of weeks to start working? Seems like too much extra work for little gain. :) signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Capability problems dovecot 2.0
On Mon, 2009-06-01 at 12:40 +0200, reg9009 wrote: > 0.074466 10.4.1.100 -> 10.4.1.171 IMAP Request: ydqb LOGIN > "i...@.com" "mypassword" > 0.085791 10.4.1.171 -> 10.4.1.100 IMAP Response: * CAPABILITY > IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN > AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 > 70.430669 10.4.1.100 -> 10.4.1.171 IMAP Request: 6atb LOGIN > "i...@.com" "mypassword" So it saw the CAPABILITY response, but apparently not the tagged OK response, and then it timed out and tried again later? But two things: 1) The post-login CAPABILITY reply is wrong. Did you set imap_capability setting manually? Remove it. 2) Did Dovecot really not send OK reply or did Outlook just ignore it? Hmm. Does this help? http://hg.dovecot.org/dovecot-2.0/rev/8ecbc7fefeb2 signature.asc Description: This is a digitally signed message part
Re: [Dovecot] 1.2.beta1: expire-tool and 'mail_location' setting
On Mon, 2009-06-01 at 17:43 +0200, e-frog wrote:
> >> Thanks Timo! It works now as long as there is no namespace for the virtual
> >> plugin defined:
> >
> > http://hg.dovecot.org/dovecot-1.2/rev/6fd725b94504
> > http://hg.dovecot.org/dovecot-1.2/rev/531083e6e84a
>
> The above doesn't seem to fix it completely. However after adding
> module_dir_init(modules) it works:
OK, added.
> > Then put mail_plugins setting outside protocol {}.
> >
>
> It looks like the mail_plugins setting outside protocol has no effect.
..
> These are the settings from the protocol imap section.
Oh, right. That's because of how it's implemented in v1.2. Kind of ugly,
but I don't know if I'll bother fixing it until it becomes a real
problem for someone. :) v2.0 implements this properly.
signature.asc
Description: This is a digitally signed message part
Re: [Dovecot] uid fetch error with revision 9112:9d634c93d28a
On Mon, 2009-06-01 at 11:03 -0400, Jonathan Siegle wrote: > This command fails: > 2 uid fetch somevaliduid (BODYSTRUCTURE BODY.PEEK[]) > 2 BAD Error in IMAP command UID: Unknown command BODYSTRUCTURE http://hg.dovecot.org/dovecot-1.2/rev/f1a6c9dd4c33 ? signature.asc Description: This is a digitally signed message part
Re: [Dovecot] 1.2.beta1: expire-tool and 'mail_location' setting
Timo Sirainen wrote:
> On Mon, 2009-05-18 at 21:23 +0200, e-frog wrote:
>> Timo Sirainen wrote:
>>> On Sun, 2009-02-22 at 12:49 +0100, e-frog wrote:
Trying 1.2.beta1 with expire plugin currently:
When I set mail_location = maildir:~/.maildir the expire plugin doesn't
delete messages.
>>> Should be fixed in hg now.
>>>
My guess is that mail_location is not respected by expire-tool for some
reason and in second
case mailbox auto-detection makes it working?
>>> Yes.
>>>
>> Thanks Timo! It works now as long as there is no namespace for the virtual
>> plugin defined:
>
> http://hg.dovecot.org/dovecot-1.2/rev/6fd725b94504
> http://hg.dovecot.org/dovecot-1.2/rev/531083e6e84a
The above doesn't seem to fix it completely. However after adding
module_dir_init(modules) it works:
--- expire-tool.c.old 2009-06-01 17:14:54.0 +0200
+++ expire-tool.c 2009-06-01 17:16:50.0 +0200
@@ -263,6 +263,8 @@ static void expire_run(bool testrun)
mail_storage_init();
mail_storage_register_all();
mailbox_list_register_all();
+
+ module_dir_init(modules);
expire_get_global_mail_ids();
>
> Then put mail_plugins setting outside protocol {}.
>
It looks like the mail_plugins setting outside protocol has no effect.
Checking the environment of expire-tool as following
/usr/sbin/dovecot --exec-mail ext /opt/bin/expire-tool.sh
expire-tool.sh:
#!/bin/sh
set > /tmp/dovecot-environment
/usr/lib/dovecot/expire-tool $1
dovecot-environment:
...
MAIL_PLUGINS='virtual expire'
MAIL_PLUGIN_DIR='/usr/lib/dovecot/modules/imap'
...
These are the settings from the protocol imap section.
In addition I noticed that dovecot -n also shows the same settings as
for protocol imap for mail_plugins(default). However dovecot.conf
definitely contains mail_plugins = virtual outside the protocol sections.
I would have expected to see mail_plugins(default): virtual then.
mail_plugins(default): virtual expire
mail_plugins(imap): virtual expire
mail_plugins(managesieve):
mail_plugin_dir(default): /usr/lib/dovecot/modules/imap
mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap
mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve
Re: [Dovecot] v1.1.16 released
ChangeLog contains somewhat more exact entries. But I don't think many people care about the exact reason. For example the last 3 could have been instead (their hg commit messages): - Maildir: Use i_stream_stat() instead of i_stream_get_fd()+fstat(). Fixes zlib plugin. - Maildir: Make sure messages are removed from index if they are deleted externally from new/. - message header parser: Don't set hdr->continues=TRUE when hdr- >eoh=TRUE. But no one would have any idea what last 2 of those would be useful for. On Jun 1, 2009, at 7:25 AM, Roy Sigurd Karlsbakk wrote: Hi Sorry if this a FAQ, but this updates report looks rather vague. The four statements all say that "in case of xxx, yyy /could/ happen". Wouldn't it be better to document what the actual bug in in the old version, as in "buffer overflow at xxx" etc? roy On 1. juni. 2009, at 07.50, Timo Sirainen wrote: http://dovecot.org/releases/1.1/dovecot-1.1.16.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.16.tar.gz.sig Fixes a couple of bugs in v1.1.15's changes. Hopefully the last v1.1 release before v1.2.0. - v1.1.15 could have crashed if mailbox-closing command was pipelined after a mailbox-accessing command. - v1.1.15's zlib plugin may have caused crashes when fetching INTERNALDATE. - Maildir: If messages had been deleted externally from new/ directory and mailbox was opened with EXAMINE, Dovecot didn't immediately notice that the messages were deleted. - If message body started with a space, some operations could have assert-crashed. -- Roy Sigurd Karlsbakk (+47) 97542685 / 98013356 r...@karlsbakk.net http://blogg.karlsbakk.net/ -- I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med fremmed opprinnelse. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk.
[Dovecot] uid fetch error with revision 9112:9d634c93d28a
This command fails: 2 uid fetch somevaliduid (BODYSTRUCTURE BODY.PEEK[]) 2 BAD Error in IMAP command UID: Unknown command BODYSTRUCTURE Thanks, Jonathan smime.p7s Description: S/MIME cryptographic signature
Re: [Dovecot] v1.1.16 released
Hi Sorry if this a FAQ, but this updates report looks rather vague. The four statements all say that "in case of xxx, yyy /could/ happen". Wouldn't it be better to document what the actual bug in in the old version, as in "buffer overflow at xxx" etc? roy On 1. juni. 2009, at 07.50, Timo Sirainen wrote: http://dovecot.org/releases/1.1/dovecot-1.1.16.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.16.tar.gz.sig Fixes a couple of bugs in v1.1.15's changes. Hopefully the last v1.1 release before v1.2.0. - v1.1.15 could have crashed if mailbox-closing command was pipelined after a mailbox-accessing command. - v1.1.15's zlib plugin may have caused crashes when fetching INTERNALDATE. - Maildir: If messages had been deleted externally from new/ directory and mailbox was opened with EXAMINE, Dovecot didn't immediately notice that the messages were deleted. - If message body started with a space, some operations could have assert-crashed. -- Roy Sigurd Karlsbakk (+47) 97542685 / 98013356 r...@karlsbakk.net http://blogg.karlsbakk.net/ -- I all pedagogikk er det essensielt at pensum presenteres intelligibelt. Det er et elementært imperativ for alle pedagoger å unngå eksessiv anvendelse av idiomer med fremmed opprinnelse. I de fleste tilfeller eksisterer adekvate og relevante synonymer på norsk.
[Dovecot] IMAP labeling sometimes not taken into account
Dear Dovecot list, I recently switched from uw-imapd to dovecot to manage my huge mbox files (about 1 GB). I now observe a very strange behavior, difficult to reproduce reliably, which might be related to some misunderstanding on my part on how either dovecot works or imap labeling works. What I call "labeling" is the fact of marking some e-mail, in my e-mail client (currently Thunderbird), with a label, which can be chosen among five labels (plus the "no-label" case). Evolution also supports labeling. As far as I understood until a few days ago, when I put a label, say, number five, on an e-mail, a keyword "$Label5" is added on the "X-Keywords:" line of the corresponding e-mail in my mbox file. Removing the label simply removes the keyword on the same line. That is, at least, what happened with uw-imapd (not that I have seen that documented somewhere but this is what I observed). The label is thus stored on the e-mail server, not on the client hard disk, which is important for me as I extensively use that feature to sort e-mails, and need to access them from several different places (and find the same labels at the same places, naturally, whatever client I use). Since the change for dovecot, however, things are going strange. Sometimes the labels disappear for some reasons. Sometimes they stay there. And I can't reproduce the behavior, it just seems random. This is very annoying as it totally breaks my e-mail management. Currently there is something strange I can reproduce however, and if someone could explain me what is happening I guess it would be a good step towards a solution. I see a specific e-mail as being labeled in thunderbird, having label number five. I also tried with evolution, accessing the same imap folder, evolution also sees that e-mail as having a label number five. I tried running these clients from my imap server, and I tried thunderbird on a Windows box at home, and every clients agree: this e-mail has a "5" label. BUT when I open the mbox file directly on the imap server (using "less"), and scroll to that given e-mail, I see NO "X-Keywords: " line. How then can the e-mail clients know that this e-mail is labeled? Please note that this behavior does not happen with only one specific e-mail, but I take it as an example of what is strange. In fact I can see, especially at the end of the mbox file (thus the latest e-mails), that plenty of e-mails have either no "X-Keywords: " line or a line with "X-Keywords: " and nothing else, whereas they are seen as being labeled (and indeed I remember having labeled most of those through thunderbird). The former e-mails I checked in the m-box (for example, one month ago) all correctly have an X-Keywords line indicating "$Label5" or other appropriate labels. It seems like dovecot is keeping some track of labeled e-mails somewhere which is NOT in the mbox file, probably related to its indexing capabilities. But I don't know how that works and where these index files are stored, how to purge them and rebuild the index, and so on. Apparently these index files have remembered some e-mails as being labeled (which is good, because I indeed labeled them). But I'd like to know how that works to be able to better troubleshoot why sometimes the label disappear. Note that restarting dovecot does not change the label status of the e-mail, so the status must be stored somewhere on disk and not only in memory. Or is all these labeling stuff some unsupported, non-standard extension to IMAP that only uw-imapd supports? (I hope not because I find it very practical and I'd like to use it with dovecot as well!) Thank you for any help. (Technical informations follow.) Olivier -- 2-12h38-~#dovecot --version 1.0.15 -- 2-12h38-~#dovecot -n # 1.0.15: /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S ssl_cert_file: /etc/ssl/certs/imapd.pem ssl_key_file: /etc/ssl/private/imapd.pem login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail auth default: passdb: driver: pam userdb: driver: passwd --
Re: [Dovecot] Capability problems dovecot 2.0
Timo Sirainen schrieb: > Implemented it now to v2.0: > http://hg.dovecot.org/dovecot-2.0/rev/5f64f935e64b > > You could test this by first verifying with older Dovecot or another > IMAP server that Outlook/OE/etc. actually uses some IMAP extension, such > as IDLE. Use e.g. Dovecot's rawlog or some traffic sniffer. After this > try Dovecot v2.0 and see if it's still using the extension. > Ok, here are my first results. Unfortunately, Outlook/OE actually doesn't work with dovecot 2.0. Here are the traffic logs in comparison to doveot 1.2. Tell me, if you need more detailed traffic. Plain and login mechanisms are enabled on both versions. Note that dovecot 2.0 complains about login command... With TB 2.x/3, everything works fine. Dovecot 2.0: 0.010447 10.4.1.171 -> 10.4.1.100 IMAP Response: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. 0.066383 10.4.1.100 -> 10.4.1.171 IMAP Request: ipxc CAPABILITY 0.066459 10.4.1.171 -> 10.4.1.100 IMAP Response: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 0.074466 10.4.1.100 -> 10.4.1.171 IMAP Request: ydqb LOGIN "i...@.com" "mypassword" 0.085791 10.4.1.171 -> 10.4.1.100 IMAP Response: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 70.430669 10.4.1.100 -> 10.4.1.171 IMAP Request: 6atb LOGIN "i...@.com" "mypassword" 70.430837 10.4.1.171 -> 10.4.1.100 IMAP Response: 6atb BAD Error in IMAP command LOGIN: Unknown command. 71.572186 10.4.1.171 -> 10.4.1.100 IMAP Response: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. 71.583362 10.4.1.100 -> 10.4.1.171 IMAP Request: rf7f CAPABILITY 71.583447 10.4.1.171 -> 10.4.1.100 IMAP Response: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 71.591756 10.4.1.100 -> 10.4.1.171 IMAP Request: 3zq7 LOGIN "i...@.com" "mypassword" 71.595471 10.4.1.171 -> 10.4.1.100 IMAP Response: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 72.547817 10.4.1.171 -> 10.4.1.100 IMAP Response: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. 72.557798 10.4.1.100 -> 10.4.1.171 IMAP Request: wavo CAPABILITY 72.557859 10.4.1.171 -> 10.4.1.100 IMAP Response: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 72.564687 10.4.1.100 -> 10.4.1.171 IMAP Request: zvi8 LOGIN "i...@.com" "mypassword" 72.568293 10.4.1.171 -> 10.4.1.100 IMAP Response: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 72.773022 10.4.1.171 -> 10.4.1.100 IMAP [TCP Retransmission] Response: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 Dovecot 1.2: 0.011031 10.4.1.172 -> 10.4.1.100 IMAP Response: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. 0.016913 10.4.1.172 -> 10.4.1.100 IMAP Response: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. 0.065276 10.4.1.100 -> 10.4.1.172 IMAP Request: u4j5 CAPABILITY 0.065406 10.4.1.172 -> 10.4.1.100 IMAP Response: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH QUOTA AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 0.069692 10.4.1.100 -> 10.4.1.172 IMAP Request: rukl CAPABILITY 0.069810 10.4.1.172 -> 10.4.1.100 IMAP Response: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH QUOTA AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 0.075379 10.4.1.100 -> 10.4.1.172 IMAP Request: gdwb LOGIN "i...@.com" "mypassword" 0.079922 10.4.1.100 -> 10.4.1.172 IMAP Request: 3ihn LOGIN "i...@.com" "mypassword" 0.370437 10.4.1.172 -> 10.4.1.100 IMAP Response: 3ihn OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT 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 0.370540 10.4.1.172
Re: [Dovecot] recipient delimiter and lmtp
On 5/29/2009, Charles Marcus (cmar...@media-brokers.com) wrote:
Hmm. Stephan, you currently have sieve_subaddress_sep setting. Should we
instead use a common setting here? Like:
protocol lda {
recipient_delimiter = +
}
>>> With v1.2 it probably wouldn't do anything, but with v2.0 LMTP could use
>>> it.
>> Sounds sensible. I can for instance make the plugin use this setting if
>> sieve_subaddress_sep is not set.
> How hard would it be to allow the use of more than one delimiter?
> Obviously this would have to be well documented, explaining the
> pitfalls, and sysadmins would have to make sure that that character was
> illegal when it came to creating the actual accounts...
The reason I ask is, some sites don't allow the use of the '+'
delimiter, so having a second optional character, and/or the ability to
use a dot anywhere in the local part, would provide a workaround to
these site...
--
Best regards,
Crles
Re: [Dovecot] namespace problem with dovecot 2.0
Timo Sirainen schrieb: > On Tue, 2009-05-26 at 10:24 +0200, reg9009 wrote: > >>> Fixed: http://hg.dovecot.org/dovecot-2.0/rev/0b3225f7b3a6 >>> >>> >>> >> Hi Timo, >> >> hmm, partly. It show up as expected now, but I cannot subscribe to >> subfolders of subfolder of INBOX. >> > > Show me the IMAP traffic? > > well, it seems it was some kind of caching problem with Thunderbird. It works flawlessly. Regards, Sebastian
Re: [Dovecot] Can expire-tool skip folders with "expire time in future" errors?
On 5/31/2009, Timo Sirainen (t...@iki.fi) wrote: > Were the messages moved there before expire plugin was loaded? Those > aren't tracked. Is there a simple way to fix this? Ie, maybe a script that could be run the first time a folder is added to the list, to add all of the current messages as of that date? -- Best regards, Charles
Re: [Dovecot] Connection queue full on dovecot 1.1.14 and 1.1.15
Am 28.05.2009 um 09:36 schrieb Sven Eulberg: Hello, sometimes we get the following errors on out dovecot proxies: dovecot: May 27 20:06:10 Info: imap-login: Disconnected: Connection queue full (no auth attempts): REMOTE= LOCAL= TLS handshaking dovecot: May 27 20:06:10 Info: imap-login: Disconnected: Connection queue full (no auth attempts): REMOTE= LOCAL= TLS handshaking dovecot: May 27 20:06:10 Info: imap-login: Disconnected: Connection queue full (auth failed, 1 attempts): user=, method=PLAIN, REMOTE= LOCAL= dovecot: May 27 20:06:10 Info: imap-login: Disconnected: Connection queue full (no auth attempts): REMOTE= LOCAL= TLS handshaking dovecot: May 27 20:06:10 Info: imap-login: Disconnected: Connection queue full (no auth attempts): REMOTE= LOCAL= TLS handshaking dovecot: May 27 20:06:10 Info: imap-login: Disconnected: Connection queue full (auth failed, 1 attempts): user=, method=PLAIN, REMOTE= LOCAL= dovecot: May 27 20:06:10 Info: imap-login: Disconnected: Connection queue full (no auth attempts): REMOTE= LOCAL= TLS handshaking dovecot: May 27 20:06:10 Info: imap-login: Disconnected: Connection queue full (no auth attempts): REMOTE= LOCAL= TLS dovecot: May 27 20:06:11 Info: imap-login: Disconnected: Connection queue full (auth failed, 1 attempts): user=, method=PLAIN, REMOTE= LOCAL= TLS dovecot: May 27 20:06:12 Info: imap-login: Disconnected: Connection queue full (auth failed, 1 attempts): user=, method=PLAIN, REMOTE= LOCAL= TLS dovecot: May 27 20:06:15 Info: imap-login: Disconnected: Connection queue full (auth failed, 1 attempts): user=, method=PLAIN, REMOTE= LOCAL= dovecot: May 27 20:09:36 Info: imap-login: Disconnected: Connection queue full (no auth attempts): REMOTE= LOCAL= TLS dovecot: May 27 20:09:36 Info: imap-login: Disconnected: Connection queue full (no auth attempts): REMOTE= LOCAL= dovecot: May 27 20:09:36 Info: imap-login: Disconnected: Connection queue full (no auth attempts): REMOTE= LOCAL= TLS handshaking dovecot: May 27 20:09:36 Info: imap-login: Disconnected: Connection queue full (no auth attempts): REMOTE= LOCAL= TLS handshaking dovecot: May 27 20:09:36 Info: imap-login: Disconnected: Connection queue full (no auth attempts): REMOTE= LOCAL= TLS handshaking dovecot: May 27 20:11:18 Info: imap-login: Disconnected: Connection queue full (no auth attempts): REMOTE= LOCAL= TLS dovecot: May 27 20:11:18 Info: imap-login: Disconnected: Connection queue full (auth failed, 1 attempts): user=, method=PLAIN, REMOTE= LOCAL= TLS dovecot: May 27 20:39:22 Info: imap-login: Disconnected: Connection queue full (no auth attempts): REMOTE= LOCAL= TLS handshaking dovecot: May 27 20:39:22 Info: imap-login: Disconnected: Connection queue full (auth failed, 1 attempts): user=, method=PLAIN, REMOTE= LOCAL= TLS dovecot: May 27 20:39:23 Info: imap-login: Disconnected: Connection queue full (auth failed, 1 attempts): user=, method=PLAIN, REMOTE= LOCAL= Our config: ./dovecot -n # 1.1.15: /usr/local/dovecot-1.1.15/etc/dovecot.conf # OS: Linux 2.6.18-6-686 i686 Debian 4.0 base_dir: /usr/local/dovecot/var/run/dovecot/ log_path: /var/log/dovecot-1.1.log protocols: pop3 pop3s imap imaps ssl_ca_file: /usr/local/dovecot/etc/ssl/de.TR_CRT ssl_cert_file: /usr/local/dovecot/etc/ssl/de.CRT ssl_key_file: /usr/local/dovecot/etc/ssl/de.PKEY disable_plaintext_auth: no login_dir: /usr/local/dovecot/var/run/dovecot/login login_executable(default): /usr/local/dovecot-1.1.15/libexec/dovecot/ imap-login login_executable(imap): /usr/local/dovecot-1.1.15/libexec/dovecot/ imap-login login_executable(pop3): /usr/local/dovecot-1.1.15/libexec/dovecot/ pop3-login login_log_format_elements: user=<%u> method=%m REMOTE=%r LOCAL=%l %c login_process_per_connection: no login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_processes_count: 10 login_max_processes_count: 256 verbose_proctitle: yes mail_location: maildir:/home/email/%u/Maildir mailbox_idle_check_interval: 60 mmap_disable: yes fsync_disable: yes mail_executable(default): /usr/local/dovecot-1.1.15/libexec/dovecot/ imap mail_executable(imap): /usr/local/dovecot-1.1.15/libexec/dovecot/imap mail_executable(pop3): /usr/local/dovecot-1.1.15/libexec/dovecot/pop3 mail_process_size: 512 mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota mail_plugin_dir(default): /usr/local/dovecot-1.1.15/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/dovecot-1.1.15/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/dovecot-1.1.15/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape- eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_lock_session(default): no pop3_lock_session(imap): no pop3_lock_session(pop3): yes pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %
Re: [Dovecot] For the record: Postfix+Spamassassin+ClamAV+Dovecot
> -Oorspronkelijk bericht- > Van: dovecot-bounces+egbert=vandenbussche...@dovecot.org > [mailto:dovecot-bounces+egbert=vandenbussche...@dovecot.org] > Namens James Butler > Verzonden: vrijdag 17 april 2009 20:58 > Aan: Dovecot Mailing List > Onderwerp: [Dovecot] For the record: > Postfix+Spamassassin+ClamAV+Dovecot > > > Postfix 2.5.5 > SpamAssassin 3.2.5 (under Perl 5.10.0) > ClamAV 0.95.1 > Dovecot 1.2.rc2 > > works fine on Fedora 10. > > Installed Dovecot and ClamAV from source and everything else > using yum. > > I'm using the ClamAV plugin for Spamassassin: > http://wiki.apache.org/spamassassin/ClamAVPlugin > > I'm calling Spamassassin with: > > /etc/postfix/main.cf: > mailbox_command = /usr/bin/spamc -f -e > /usr/local/libexec/dovecot/deliver > > Postfix hands off to Spamassassin, which processes ALL mail (not just > attachments) through the ClamAV plugin before parsing for > spam, and then hands the whole mess off to Dovecot for > 'deliver' to handle. > > How simple is that? > > Since ClamAV scanns all mail, it might be too > processor-intensive for really large mail systems, but it is > working great for our 120+ user system with lots of spam > coming in. If you're using Procmail or some other > preprocessor that can hand off to a pipe, then you could skip > the plugin and pipe messages over a certain size (i.e. >1024) > to clamd, instead. > > Enjoy! > > James Hi! Apologies for digging an old thread from the bin. I was wondering how this relates to Amavisd? Should I regard the proposed plugin solution as a 'poor mans' solution when one does not want to install amavis? Thanks! Egbert Jan (NL)
Re: [Dovecot] Namespace delimiter...
On Jun 1, 2009, at 3:40 AM, Lenthir wrote: Our storage has two parts... MySQL database and files with mails. Very complicated, and I can't talk about it... Do you mean you've implemented your own storage backend to Dovecot? Yep, we implemented storage backend to Dovecot. Now Dovecot is compatible with our storage system, and it works for about 3 mln users (or even more) :] OK, then I think you'll just have to end up patching that small part of Dovecot. Supporting NIL separator seems like more trouble than worth. Maybe you can also do something similar to how Maildir++ works, just decide that e.g. ^ character is a hierarchy separator and have Dovecot use that?
Re: [Dovecot] Namespace delimiter...
Timo Sirainen pisze: Alternatively you can unset "Server supports folders that contain sub-folders and messages" setting in Thunderbird. It's impossible, we can't change anything on the client side. The configuration must be the simpliest as it can be... Our storage has two parts... MySQL database and files with mails. Very complicated, and I can't talk about it... Do you mean you've implemented your own storage backend to Dovecot? Yep, we implemented storage backend to Dovecot. Now Dovecot is compatible with our storage system, and it works for about 3 mln users (or even more) :] (only POP works, we're working to deploy IMAP) Konrad
