- dovecot - dovecot.org

[Dovecot] Linux should be as easy as Windows
by Dennis Clarke 19 Aug '10

19 Aug '10

>From a "Standards" thread I saw this : "Linux should be as easy as Windows" I would like to point out that this is a thinking problem. A shift in thinking is required. That should say : "Open source and Free software should be as easy as Windows" In this way we allow someone running BSD, Solaris or some port of Debian to an old Dec AlphaServer will have the same level of functionality provided standards are adhered to. Once programmers begin to see everything in the light of Linux then we can also kiss goodbye the opportunity for portability to other OS types. Dennis

10 12

[Dovecot] Pigeonhole: error while loading shared libraries
by Sebastian Köhler 19 Aug '10

19 Aug '10

Hi, I built pigeonhole from the hg repo for Dovecot 2.0. Local sieve scripts work fine. But as soon as I try to connect via managesieve I get this errror: managesieve-login: Error: dovecot/managesieve-login: error while loading shared libraries: libdovecot-login.so.0: cannot open shared object file: No such file or directory My dovecot install is in /usr/lib/dovecot and I had to symlink the libs in the dovecot folder to /usr/lib to make managesieve work. My configure options were: "--prefix=/usr --with-dovecot=/usr/lib/dovecot" Sebastian -- The best thing about a boolean is even if you are wrong, you are only off by a bit.

2 4

[Dovecot] OT [Fwd: Fwd: Re: EVERYONE USING DOVECOT PLEASE SIGN: Thanks, Administrators of Dovecot!]
by Noel Butler 18 Aug '10

18 Aug '10

CharlesMarcus LOL, you kinda contradicted yourself here charlie boy and personal RBL? yup, but its not just used by me, its used by a few if you read the link, a few involving millions of emails a day, but shouldnt be a problem giving the geographical locations... and lied? list msgs caught in spam rules, I guess you dont know how to configure SA URI's... now, please stop trying to avoid bans or i shall notify your isp you have violated their T%C ------- Forwarded Message -------- From: Charles <libertytrek(a)gmail.com> To: noel.butler(a)ausics.net Subject: Fwd: Re: [Dovecot] EVERYONE USING DOVECOT PLEASE SIGN: Thanks, Administrators of Dovecot! Date: Wed, 18 Aug 2010 07:52:35 -0400 So, you're a liar as well. You lied when you said my messages were getting caught in your anti-spam filter. They weren't, they were getting blocked by your silly little personal rbl. If you weren't blocking list traffic, you would have seen that I already corrected the record on that myself. Don't bother replying - I won't be rejecting your messages on this account, I just give them the attention they deserve (straight to the shit-can).

3 2

[Dovecot] Unexpectedly lost message
by Tom Goerger 18 Aug '10

18 Aug '10

Hi, We're having some issues with certain messages not being able to be read by Dovecot. Can anyone tell me under what conditions the error messages below could be caused? Aug 17 15:58:26 server.tc.umn.edu imap(user): : [ID 887855 local6.error] Next message unexpectedly lost from 1913995 Aug 17 15:58:26 server.tc.umn.edu last message repeated 2 times Aug 17 15:58:26 server.tc.umn.edu imap(user): : [ID 107833 local6.crit] Panic: file istream.c: line 76: assertion failed: (_stream->skip != _stream->pos) Aug 17 15:58:26 server.tc.umn.edu dovecot: [ID 684838 local6.error] child 13169 (imap) killed with signal 6 Thanks, -- Tom Goerger University of Minnesota - Internet Services

2 1

[Dovecot] rare index cache error with dovecot 1.2.10
by Wolfgang.Friebel＠desy.de 18 Aug '10

18 Aug '10

Hi, since some time for a single user updating the Maildir/dovecot.index.cache file produced errors whenever it needed to be updated: Aug 15 04:16:40 imapsrv dovecot: deliver(user): pwrite() failed: File too large Aug 15 04:16:40 imapsrv dovecot: deliver(user): file_set_size() failed with index cache file /var/spool/mail/mamuzic/Maildir/dovecot.index.cache: File too large The file itself was 55115776 bytes and a test program using pwrite with any reasonable size or offset does not produce the EFBIG error. Looking to the file contents the start of the file looks correct to me ( according to src/lib-index/mail-cache-private.h ) and despite of the error message the file gets updated and contains always the headers of the most recent incoming mail near the end of the file. After removing the file the cache was rebuilt properly (currently at 9MB). As this happened only for a single user out of approx 500 and after more than one year of using dovecot without any other problems I guess this is a very rare case. As pwrite tests do not show the error this seems not to be an issue with low file limits (as suggested in another mail on this topic) but maybe a lookup of corrupt addresses from the index.cache. I have saved the dovecot.index.cache, but as it is rather large (55MB) and does contain a lot of privacy information I would rather not make it accessible. Is there something I can further check to see whether dovecot is missing a sanity check? -- Wolfgang Friebel Deutsches Elektronen-Synchrotron DESY Phone/Fax: +49 33762 77372/216 Platanenallee 6 Mail: Wolfgang.Friebel AT desy.de D-15738 Zeuthen Germany

2 1

[Dovecot] REpeated e-mail
by The Doctor 18 Aug '10

18 Aug '10

Using 1.2.11 I am getting some people repeating that they are getting repeated POP3 e-mails. My configuration is # 1.2.11: /usr/dovecot/etc/dovecot.conf # OS: BSD/OS 4.3 i386 base_dir: /var/run/dovecot/ protocols: pop3 pop3s imap imaps ssl_listen: 204.209.81.1 ssl_cipher_list: ALL:!LOW:!SSLv2 disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/dovecot/libexec/dovecot/imap-login login_executable(imap): /usr/dovecot/libexec/dovecot/imap-login login_executable(pop3): /usr/dovecot/libexec/dovecot/pop3-login mail_max_userip_connections(default): 10 mail_max_userip_connections(imap): 10 mail_max_userip_connections(pop3): 3 first_valid_uid: 100 mail_location: mbox:~/mail:INBOX=/var/mail/%u dbox_rotate_days: 0 mail_executable(default): /usr/dovecot/libexec/dovecot/imap mail_executable(imap): /usr/dovecot/libexec/dovecot/imap mail_executable(pop3): /usr/dovecot/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /usr/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /usr/dovecot/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_no_flag_updates(default): no pop3_no_flag_updates(imap): no pop3_no_flag_updates(pop3): yes pop3_enable_last(default): no pop3_enable_last(imap): no pop3_enable_last(pop3): yes pop3_save_uidl(default): no pop3_save_uidl(imap): no pop3_save_uidl(pop3): yes pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: executable: /usr/contrib/libexec/dovecot/dovecot-auth passdb: driver: passwd-file args: /etc/master.passwd userdb: driver: passwd userdb: driver: passwd-file args: /etc/passwd -- Member - Liberal International This is doctor(a)nl2k.ab.ca Ici doctor(a)nl2k.ab.ca God, Queen and country! Never Satan President Republic! Beware AntiChrist rising! http://twitter.com/rootnl2k http://www.facebook.com/dyadallee Australia!! Vote to throw the REpublicans to the sharks!

3 2

[Dovecot] Error: Index file too large ? 904 bytes ?
by Dennis Clarke 18 Aug '10

18 Aug '10

My 1.2.13 build is giving me errors based on the same conf file that was working perfectly for 1.2.12 : Aug 18 03:28:27 IMAP(dclarke): Error: Index file too large: /var/mail/dclarke/dovecot.index Aug 18 03:28:27 IMAP(dclarke): Fatal: block_alloc(2147483648): Out of memory Aug 18 03:28:27 dovecot: Error: child 12560 (imap) returned error 83 (Out of memory - see mail_process_size setting) The file in question is 904 bytes in size : bash-4.1# ls -l /export/home/dclarke/mail/.Sent/dovecot.index -rw------- 1 dclarke csw 904 Aug 4 16:05 /export/home/dclarke/mail/.Sent/dovecot.index So this seems insane. SO I made sure the conf file had this in it : mail_process_size = 256 I then restart the daemon and see this : Aug 18 03:37:02 IMAP(dclarke): Fatal: block_alloc(1073741824): Out of memory Aug 18 03:37:02 dovecot: Error: child 12620 (imap) returned error 83 (Out of memory - see mail_process_size setting) Aug 18 03:37:07 IMAP(dclarke): Error: Index file too large: /export/home/dclarke/mail/.Sent/dovecot.index Aug 18 03:37:07 IMAP(dclarke): Warning: Created dotlock file's timestamp is different than current time (837089755 vs 1282102627): /export/home/dclarke/mail/.Sent/dovecot-uidlist Aug 18 03:37:07 IMAP(dclarke): Fatal: block_alloc(1073741824): Out of memory Aug 18 03:37:07 dovecot: Error: child 12622 (imap) returned error 83 (Out of memory - see mail_process_size setting) Aug 18 03:37:09 IMAP(dclarke): Error: Index file too large: /export/home/dclarke/mail/.Sent/dovecot.index Aug 18 03:37:09 IMAP(dclarke): Warning: Created dotlock file's timestamp is different than current time (527779909 vs 1282102629): /export/home/dclarke/mail/.Sent/dovecot-uidlist Aug 18 03:37:09 IMAP(dclarke): Fatal: block_alloc(1073741824): Out of memory Aug 18 03:37:09 dovecot: Error: child 12624 (imap) returned error 83 (Out of memory - see mail_process_size setting) Sure enough dovecot catches a timestamp issue : bash-4.1# date Wed Aug 18 03:39:24 GMT 2010 bash-4.1# ls -lapE /export/home/dclarke/mail/.Sent/dovecot-uidlist -rw------- 1 dclarke csw 1806 2010-08-16 13:52:16.442510077 +0000 /export/home/dclarke/mail/.Sent/dovecot-uidlist bash-4.1# touch /export/home/dclarke/mail/.Sent/dovecot-uidlist bash-4.1# ls -lapE /export/home/dclarke/mail/.Sent/dovecot-uidlist -rw------- 1 dclarke csw 1806 2010-08-18 03:39:53.263345256 +0000 /export/home/dclarke/mail/.Sent/dovecot-uidlist However the inability to deal with a 904 byte file is a bit of an issue here. Anyone know why mail_process_size = 256 is the wrong thing to look at ? Dennis

2 2

[Dovecot] Extension for sorting mails by Displayname
by Michael Kliewe 18 Aug '10

18 Aug '10

Hi everybody, first of all, thanks Timo for version 2.0. Currently I want to sort mails server-side by displayname of FROM and TO. There is an extension for it, but I think dovecot does not support it at the moment. It is defined in RFC 5957: https://www.tools.ietf.org/html/rfc5957 Is there an dovecot extension for it, how can I get that running? Michael

2 2

Re: [Dovecot] wake up getamail on imap request
by Timo Sirainen 18 Aug '10

18 Aug '10

On Wed, 2010-08-18 at 14:28 +0200, Peter Dungel wrote: > The only issue I'm still facing is, that I don't like to run getmail as a > cronjob that connects to my online mailboxes every minute or so, I'd rather > want it to do so every thirty minutes and whenever I request so by fetching > my mails at my mailclient (e.g. outlook), I've font the Fetchmail Wakeup > plugin, but according to the description this only works for version 1.1.x > and 1.2.x but I'm running 1.0.13. You could create a plugin that triggers getmail every time IMAP's STATUS command is sent. Or probably best to do it on mailbox_opened hook (in v2.0).

1 0

Re: [Dovecot] wake up getamail on imap request
by William Blunn 18 Aug '10

18 Aug '10

On 18/08/2010 13:28, Peter Dungel wrote: > i've set up a little mailserver for my homeoffice, and after some > problems everything works fine for me, I've some virtual users which > get their mail delivered via getmail, and I can access my mails from > my windows mailclient. > > The only issue I'm still facing is, that I don't like to run getmail > as a cronjob that connects to my online mailboxes every minute or so, > I'd rather want it to do so every thirty minutes and whenever I > request so by fetching my mails at my mailclient (e.g. outlook), I've > font the Fetchmail Wakeup plugin, but according to the description > this only works for version 1.1.x and 1.2.x but I'm running 1.0.13. > > Anyone has any idea how to solve this or has a workaround? Upgrade to 1.1.x or 1.2.x? I believe that many people consider 1.0.x to be hideously ancient. I believe that many people on this list will be significantly reluctant to help you with anything before 1.2.x. Version 2.0.0 was declared the current release version last Monday (16 Aug 2010), with the previous current release version before that being 1.2.13. I believe that many people on this will not consider "But My Distro Provides Version X!" to be a valid excuse. Find a more up-to-date binary package, upgrade your distro, install from source; there is always a way. Bill

1 0