- dovecot - dovecot.org

[Dovecot] The Status: header is forced
by Olivier Tharan 21 Jun '04

21 Jun '04

Hi, I started testing dovecot for our next POP/IMAP server (nearing production state), and noticed that the Status: header is always added, with a value of 'O' or 'RO'. This happens in `lib-index/mbox/mbox-rewrite.c'. This does not seem to happen in the Maildir case. Is the Status: header really needed in every case? This breaks mutt which displays mails with a 'O' flag instead of 'N'. My dovecot is 0.99.10.4 (FreeBSD port), but the behavior is still the same in the CVS version. -- olive

3 6

[Dovecot] 1.0-test19
by Timo Sirainen 21 Jun '04

21 Jun '04

http://dovecot.org/test/ I'm finally using this release myself with mboxes. So far no crashes or corruption. :) - several mbox fixes and optimizations - maildir syncing fix - solaris fixes - create mbox root dir if it doesn't exist

2 3

[Dovecot] 0.99.10.6 released
by Timo Sirainen 20 Jun '04

20 Jun '04

Since no-one have complained about previous RCs, I guess it's release time. Since -rc2 I added the ioloop.c assert fix, and 64bit Solaris fix. Here's the full change summary again: v0.99.10.6 2004-06-20 Timo Sirainen <tss(a)iki.fi> + SHA1 password support using OpenSSL crypto library + mail_extra_groups setting + maildir_stat_dirs setting + Added NAMESPACE capability and command - Autocreate missing maildirs (instead of crashing) - Fixed occational crash in maildir synchronization - Fixed occational assertion crash in ioloop.c - Fixed FreeBSD compiling issue - Fixed issues with 64bit Solaris binary

2 1

[Dovecot] Re: [dovecot-cvs] dovecot/src/lib fdpass.c,1.28,1.29
by Charlie Allom 20 Jun '04

20 Jun '04

Will this perhaps fix these? imap-login: Jun 15 12:28:16 Panic: file ioloop.c: line 90: assertion failed: (i o->fd <= current_ioloop->highest_fd) dovecot: Jun 15 12:28:16 Error: child 17987 (login) killed with signal 6 imap-login: Jun 15 13:14:58 Panic: file ioloop.c: line 90: assertion failed: (i o->fd <= current_ioloop->highest_fd) dovecot: Jun 15 13:14:58 Error: child 13002 (login) killed with signal 6 On Tue, Jun 15, 2004 at 02:42:25AM +0300, cras(a)procontrol.fi wrote: > Update of /home/cvs/dovecot/src/lib > In directory talvi:/tmp/cvs-serv11171 > > Modified Files: > fdpass.c > Log Message: > Solaris fix by Tim Hurman > > > > Index: fdpass.c > =================================================================== > RCS file: /home/cvs/dovecot/src/lib/fdpass.c,v > retrieving revision 1.28 > retrieving revision 1.29 > diff -u -d -r1.28 -r1.29 > --- fdpass.c 1 Dec 2003 19:07:34 -0000 1.28 > +++ fdpass.c 14 Jun 2004 23:42:23 -0000 1.29 > @@ -31,12 +31,20 @@ > #include <sys/uio.h> > > #ifndef CMSG_SPACE > -# define CMSG_ALIGN(len) \ > +# if defined(_CMSG_DATA_ALIGN) && defined(_CMSG_HDR_ALIGN) /* for Solaris */ > +# define CMSG_ALIGN(len) _CMSG_DATA_ALIGN(len) > +# define CMSG_SPACE(len) \ > + (_CMSG_DATA_ALIGN(len) + _CMSG_HDR_ALIGN(sizeof(struct cmsghdr))) > +# define CMSG_LEN(len) \ > + (_CMSG_HDR_ALIGN(sizeof(struct cmsghdr)) + (len)) > +# else > +# define CMSG_ALIGN(len) \ > (((len) + sizeof(size_t) - 1) & ~(sizeof(size_t) - 1)) > -# define CMSG_SPACE(len) \ > +# define CMSG_SPACE(len) \ > (CMSG_ALIGN(len) + CMSG_ALIGN(sizeof(struct cmsghdr))) > -# define CMSG_LEN(len) \ > +# define CMSG_LEN(len) \ > (CMSG_ALIGN(sizeof(struct cmsghdr)) + (len)) > +# endif > #endif > > #ifdef SCM_RIGHTS > -- .signature 0x14AA7941

2 4

[Dovecot] 0.99.10.5 released
by Timo Sirainen 19 Jun '04

19 Jun '04

One more bugfix since rc2: - Maildir: synchronization might have sometimes set wrong flags to messages, or crash completely Quite rare because we were lucky before :) And list of all the changes one more time: v0.99.10.5 2003-12-27 Timo Sirainen <tss(a)iki.fi> + MySQL authentication, patch by Matthew Reimer + --with-moduledir configure option - mbox: APPEND reversed given \Draft and \Deleted flags - mbox: "LF not found" errors happened sometimes when X-IMAPbase header was updated. Possibly corrupted mbox sometimes. Thanks to Fabrice Bellet for finding this bug. - Custom flags couldn't be unset - Maildir: make sure ":2," is appended to filename when moving mails from new/ to cur/. - Maildir: synchronization might have sometimes set wrong flags to messages, or crash completely - Maildir: RENAME xx inbox.xx didn't result as uppercased ".INBOX.xx" directory which then couldn't be accessed - Don't crash with RAND_bytes() error messages anymore. This mostly happened with Fedora/RedHat.

6 13

[Dovecot] 1.0-test17
by Timo Sirainen 19 Jun '04

19 Jun '04

http://dovecot.org/test/ Just mbox fixes since 1.0-test16. The logic is simpler and more correct now. Can anyone break it anymore? I actually tested it a while with Evolution and several mailboxes and it didn't break at least immediately. :) Now maybe a few more days and I dare trying this thing myself with my real mboxes (yes, I'm still using them). Dovecot mailing list archives could soon be served with 1.0-tests too, as soon as I get support for read-only mboxes working again (storing and comparing MD5 summed headers).

5 17

[Dovecot] 1.0-test18
by Timo Sirainen 19 Jun '04

19 Jun '04

http://dovecot.org/test/ Again mostly just mbox fixes. The good thing is that the code is only getting cleaner and more understandable with every release. But I think it's clean enough now that this release should work :) It also has checkpassword passdb support. Supporting it as userdb isn't yet implemented. I think I'll make some generic caching thingy, so that if passdb is same as userdb, they both could be queried from database in one query. Probably by allowing pass_query/pass_filter to return them.

1 0

[Dovecot] 0.99.10.6-rc1 released
by Timo Sirainen 19 Jun '04

19 Jun '04

http://dovecot.org/rc/ Fixes the crashes people had been getting more often with 0.99.10.5. Also included all the patches in dovecot.org/patches/old: - SHA1 passwords - mail_extra_groups setting (Debian people can finally fix #185335 :) - autocreate missing maildirs (and don't crash) - maildir_stat_dirs setting If no problems are found within few days this will simply be renamed to 0.99.10.6.

3 5

[Dovecot] 0.99.10.6-rc2
by Timo Sirainen 18 Jun '04

18 Jun '04

http://dovecot.org/rc/ Since rc1: - Changed a few comments in dovecot-example.conf - Changed a few error messages. Most importantly: "Internal error occured. Error report written to server log." .. maybe that would get more people to look for the real error in the log file :) - Added NAMESPACE command - Fixed SHA1 compiling issue - Fixed FreeBSD compiling issue

1 0

[Dovecot] dovecot startup failure - dovecot-auth unable to open passwd-file
by Stephen Hillier 18 Jun '04

18 Jun '04

Hi all, I'm stuck on getting dovecot to work for 2 days. Here's the logfile entries from the startup process(es) dovecot: Jun 18 14:48:43 Info: Dovecot starting up dovecot-auth: Jun 18 14:48:44 Fatal: Can't open passwd-file /var/run/dclogin/mail-passwd: No such file or directory dovecot: Jun 18 14:48:44 Error: Auth process died too early - shutting down dovecot: Jun 18 14:48:44 Error: child 7313 (auth) returned error 89 imap-login: Jun 18 14:48:44 Fatal: fd_send(-1) failed: Broken pipe pop3-login: Jun 18 14:48:44 Fatal: fd_send(-1) failed: Broken pipe The strange thing is, the file I've specified does exist -- i created it manually -- and the 1 entry in that file is this: steve:s13fj3NHakds.:10001:5000::/var/run/dovecot/home/steve:/sbin/nologin::~/Mail/:INBOX=/var/spool/mail/steve What's even stranger -> every time I try to startup dovecot, the passwd-file that is seen to be "missing" gets deleted!!!! why??? Here's a copy of my current (broken) conf: base_dir = /var/run/dovecot/ protocols = imap imaps pop3 pop3s ssl_disable = yes log_path = /var/log/maillog login_dir = /var/run/dclogin login_chroot = no login = imap login_executable = /usr/libexec/dovecot/imap-login login_user = doveauth login_process_per_connection = yes login_processes_count = 5 login = pop3 login_executable = /usr/libexec/dovecot/pop3-login first_valid_uid = 10000 last_valid_uid = 20000 first_valid_gid = 5000 last_valid_gid = 5100 default_mail_env = mbox:~/Mail/:INBOX=/var/spool/mail/%u mbox_locks = fcntl imap_executable = /usr/libexec/dovecot/imap pop3_executable = /usr/libexec/dovecot/pop3 auth = default auth_mechanisms = plain digest-md5 auth_userdb = passwd-file /var/run/dclogin/mail-passwd auth_passdb = passwd-file /var/run/dclogin/mail-passwd auth_executable = /usr/libexec/dovecot/dovecot-auth auth_verbose = yes I'm sure I did something silly in my conf that's causing the problem but I'm not sure what that might be. Thanks in advance for any and all help. Steve. ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca

2 1

[Dovecot] Info: Internal login failure:
by Nico De Beer - MWEB 18 Jun '04

18 Jun '04

I get the following error on auth with mysql on pop3 what am i missing or doing wrong mysql config file db_host = localhost #db_port = 3306 db_unix_socket = /var/lib/mysql/mysql.sock db = ADMIN db_user = mailmaster db_passwd = ******** db_client_flags = 0 default_pass_scheme = PLAIN password_query = SELECT MAILBOX_PASSWORD AS password FROM MAIL WHERE MAILBOX_USERNAME = '%n' AND MAILBOX_DOMAIN = '%d' #user_query = SELECT MAILBOX_ROOT AS home,uid,gid FROM MAIL WHERE MAILBOX_USERNAME = '%n' and MAILBOX_DOMAIN='%d' dovecot config file base_dir = /var/run/dovecot/ protocols = imap pop3 imap_listen = * pop3_listen = * ssl_disable = yes log_path = /var/log/dovecot_log info_log_path = /var/log/dovecot_info_log log_timestamp = "%b %d %H:%M:%S " login_dir = /var/run/dovecot/login login = imap login_executable = /usr/local/libexec/dovecot/imap-login login_user = dovecot login_process_size = 16 login_process_per_connection = yes login_processes_count = 3 login_max_processes_count = 128 login_max_logging_users = 256 login = pop3 max_mail_processes = 1024 verbose_proctitle = no first_valid_uid = 500 #last_valid_uid = 0 default_mail_env = maildir:/home/mail/%d/%n/Maildir mail_cache_fields = MessagePart client_workarounds = oe6-fetch-no-newmail:outlook-idle: mailbox_check_interval = 300 mailbox_idle_check_interval = 30 mail_save_crlf = yes mail_read_mmaped = no maildir_copy_with_hardlinks = yes mbox_locks = dotlock fcntl mbox_read_dotlock = yes mbox_lock_timeout = 120 mbox_dotlock_change_timeout = 30 umask = 0077 mail_drop_priv_before_exec = no imap_executable = /usr/local/libexec/dovecot/imap imap_process_size = 256 pop3_executable = /usr/local/libexec/dovecot/pop3 pop3_process_size = 256 auth = default auth_mechanisms = plain auth_passdb = mysql /usr/local/etc/dovecot-mysql.conf auth_user = mailmaster auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ Are you ready for Telkom's 10-digit dialling? To find out how this will affect your Internet connection in the not too distant future, go to www.mweb.co.za/ten

2 1

[Dovecot] Maildir + Evolution
by mkortela＠cc.hut.fi 18 Jun '04

18 Jun '04

I don't know if this is an Evolution bug or not, but when I use the maildir format with Dovecot 0.99.10p2 (from OpenBSD packages collection) and connect to it from Evolution 1.4 using IMAP, Evolution displays subfolders incorrectly. It actually does not show any subfolders, only root folders with names like "Folder.Subfolder" and "Folder.Subfolder.Subsubfolder". There's no such problem when using traditional mailboxes. Is this an Evolution bug or one of Dovecot's? I had thought the IMAP protocol should act the same no matter which mail dir structure was used... -- Mikko Kortelainen mkortela(a)cc.hut.fi

3 2

[Dovecot] Add SSL to Dovecot & SquirrelMail
by Eric Kahklen 18 Jun '04

18 Jun '04

I am relatively new to setting up mail servers and wondered how difficult it would be to add SSL to my current Dovecot & SquirrelMail setup. Would I just add SSL to the squirrelmail directory under appache with my certificate? Does Dovecot need any changes to the configuration? I have it working fine without SSL. Thanks, Eric

1 0

[Dovecot] IMAP and webmail applications
by Tom Allison 18 Jun '04

18 Jun '04

I've been hunting around for a webmail application other than squirrelmail for reasons that really don't matter. But I'm seeing that a lot of these applications tend to sometimes access servers via IMAP, but they always seem to have a touch more information needed than might be for an IMAP session. An example is openwebmail. It authenticates very similar to how dovecot authenticates, with a userdb and passdb specifications. It reads directly off the disk for some of it's activities. As for squirrelmail, they seem to want a lot of information regarding the mail architecture (mbox, maildir, folder locations...) and I don't really see where this could come into play with an IMAP implimentation. So, not actually having read all 82 pages of RFC 2060 (but I did print them!), I'm trying to see what I might miss if I were to attempt a web mail application that was based entirely upon IMAPv4 with the only information known prior to connection is the server name. Kind of like my mail client. Will I get into trouble with mail directories/folders if I start accessing different IMAP servers other than dovecot? Can I discover this without any hints from the user? I'm not sure exactly what I'm asking for here, other than some thoughts on what I might have to watch out for or do without (when comparing to squirrelmail as an example). I know I'll have to do something different if someone wants an addressbook, but I'm not there yet.

5 6

[Dovecot] 1.0-test16 - nearing usable state
by Timo Sirainen 18 Jun '04

18 Jun '04

http://dovecot.org/test/ Here you go, maildir syncing problems finally fixed (I hope). Well, except there's this "new-dir-only syncing" optimization which I'm not really sure if it works as it should. The bug really was in index code as I was beginning to suspect. The good thing is that while trying to figure it out over the last several weeks I thought of many other potential problems (race conditions) which got fixed. Those would have been much harder to find than this one :) Finally I thought I'd stop looking at the code and just begin dumping tons of debugging data to see where exactly it goes wrong. After few hours of debugging I figured out it was because message was being removed from index but not from maildir. 5 hours of sleep later I woke up, thought a while, figured out where it must be, got up, half an hour more debugging and found it. :) Code merging two UID range buffers into one was buggy, inserting one line of code fixed it. So .. Maybe I'll finally start using this myself now. The next important problems seem to be some random error messages about index locking timeouts and some asserts in some situations.

3 2

Re: [Dovecot] IMAP and webmail applications
by durango99 18 Jun '04

18 Jun '04

i thought squirrelmail would be way too much of an overkill for my needs also but i went for it. i'm using debian and i got the squirrelmail package installed and working within 15 minutes. what really makes life easy is that squirrelmail comes with a configuration utility (squirrelmail-configure). it was very easy to get things configured without worry about a lot of conf files :) i also like the many plugins that people have created for squirrelmail. it's also very simple to add these plugins into squirrelmail using squirrelmail-configure. i had originally been ssh and mutt to check my mail, but i decided it be nice to have a web front-end and squirrelmail /apache /dovecot /procmail /spamassassin /gotmail /getmail /fetchyahoo have been a good mix for me. the hardest part for me was figuring out procmail and not squirrelmail :) my 2 cents, dan > I've been hunting around for a webmail application other than > squirrelmail for reasons that really don't matter. > > But I'm seeing that a lot of these applications tend to sometimes access servers via IMAP, but they always seem to have a touch more information needed than might be for an IMAP session. > > An example is openwebmail. It authenticates very similar to how dovecot authenticates, with a userdb and passdb specifications. It reads directly off the disk for some of it's activities. > > As for squirrelmail, they seem to want a lot of information regarding the mail architecture (mbox, maildir, folder locations...) and I don't really see where this could come into play with an IMAP implimentation. > > So, not actually having read all 82 pages of RFC 2060 (but I did print them!), I'm trying to see what I might miss if I were to attempt a web mail application that was based entirely upon IMAPv4 with the only information known prior to connection is the server name. Kind of like my mail client. > > Will I get into trouble with mail directories/folders if I start accessing different IMAP servers other than dovecot? Can I discover this without any hints from the user? > > I'm not sure exactly what I'm asking for here, other than some thoughts on what I might have to watch out for or do without (when comparing to squirrelmail as an example). I know I'll have to do something different if someone wants an addressbook, but I'm not there yet. >

1 0

[Dovecot] shared authentication
by Kevin 16 Jun '04

16 Jun '04

whats the recommended way to share a user auth info between dovecot and postfix? sasldb seems like it could work but nobody really seems to like using the giant mass that is sasl. i also cant find any information on actually getting dovecot to use sasl past the configure options. i looked at timo's patch for postfix to use dovecot-auth but it doesnt apply correctly on the 2.1 branch. so what are people using to share passwords between the two without using the system passwd?

3 3

[Dovecot] POP3 LAST command?
by Christian Balzer 16 Jun '04

16 Jun '04

Hello, any plans to support this in the future? Seems the inability to use LAST breaks that Yahoo remote mailbox slurper thing, not that I care too much about that, but some mail clients might miss it as well. ;) Regards, Christian Balzer -- Christian Balzer Network/Systems Engineer NOC chibi(a)gol.com Global OnLine Japan/Fusion Network Services http://www.gol.com/

4 4

[Dovecot] Return (revenge?) of the "pop-lock".
by Christian Balzer 16 Jun '04

16 Jun '04

Hello, The users here have been migrated to the new mail system with dovecot 0.99.10.5 (Debian package) on the backends. Storage is maildir, only pop3 access for now. I see very seldom occurrences (compared to the session wide pop lock of qpopper on the old system) like this: --- Jun 16 14:35:52 mb01 pop3(user(a)gol.com): Timeout while waiting for release of exclusive fcntl() lock for index file /mail/spool/mb01/9ef/f73/af.user/.INBOX/.imap.index --- These are people with slow connections and at least one large mail in the box, with their client aborting w/o terminating the session properly. I presume the timeout for this is hardcoded, as all the config parameters for timeouts are mbox related, rite? Regards, Christian Balzer -- Christian Balzer Network/Systems Engineer NOC chibi(a)gol.com Global OnLine Japan/Fusion Network Services http://www.gol.com/

2 2

[Dovecot] /var/mail dotlocking workaround
by Timo Sirainen 16 Jun '04

16 Jun '04

I added "mail_extra_groups" setting which can be used to give imap/pop3 process access to additional groups. So what this means is if you set it to "mail" you can finally remove o-w access from /var/mail directory. Leaving the sticky bit could still be a good idea, so there's no way users to be able to delete each others inboxes. Here's a patch against 0.99.10.5: http://dovecot.org/patches/mail-extra-groups.diff

1 0

[Dovecot] dovecot non-local users
by Tom Allison 16 Jun '04

16 Jun '04

From the docs: System without local users -------------------------- <snip> Having one uid per user would mean that in case of a security hole in Dovecot, the user still couldn't read other peoples mails. Use this if possible. ----- I don't quite understand this one. If you aren't a local user, what's the uid all about? Do I do something like: create a user for mydomain in /etc/passwd (eg: user:domain_dude, home:/var/dovecot) with a valid home/uid/gid. Plug in the uid/gid/home for domain_dude in the authentication and have a data structure of /var/dovecot/%d/%n/Maildir or %h/%d/%d/Maildir where %h = "/var/dovecot" via /etc/passwd. Something like that?

2 1

[Dovecot] review of my configuration
by Tom Allison 16 Jun '04

16 Jun '04

Over the last week I've set up dovecot and imap and imaps support. I've even tried to break it but it's been doing very well. Now I'm trying to set up a webmail interface. Rather than use the common squirrelmail, I thought I would try openwebmail. Mainly because it's written in perl, of which I am a big fan. However, I ran into some errors in openwebmail that actually may tie back to dovecot. Here's how: dovecot configuration userdb = /etc/passwd passdb = pgsql.... ---this allows me to use the $HOME, uid, gid from the passwd file and not have to carry two copies of it (/etc/passwd and pgsql) However, under openwebmail I don't seem to have this option as they are really determined to require a home, uid, gid for each user that logs in. As witnessed by the following line: Tue Jun 15 20:23:34 2004 - [31572] (unknown) tallison - userinfo error - auth_pgsql.pl, ret -3, Can't execute SQL statement: ERROR: column "uid" does not exist Sure looks familiar doesn't it? (see, it's relevant!) Since I was thinking that maybe it might be interesting to do some email set up to support multiple domains and users some day, and I want to try out the openwebmail sooner than that. I'm getting the impression that it might be easier if I just made the leap today and started to reconfigure everything for multiple domain hosting and all the cool stuff. Now, I can probably muddle through this without too much internal damage. But I keep getting stuck on one point. How can I filter the delivery of email like I do with procmail, when I am delivering mail to many users, none of whom have a /etc/passwd entry? Are there any alternative ideas on how to do this?

1 0

[Dovecot] cvs changelog
by Geo Carncross 15 Jun '04

15 Jun '04

FEI: the CVS changelog is no longer updating. cras's commits look like this: date: YYYY-MM-DD HH:MM:SS +TZDD; author cras; state Exp; lines +1 -0 but cvs2cl.pl (2.50) demands: date: YYYY/MM/DD HH:MM:SS; author cras; state: Exp; lines +1 -0 cvs2cl.pl version 2.55 still can't parse these lines. I patched my cvs2cl.pl so I could still follow dovecot, but I'm not certain these changes actually belong in cvs2cl.pl --- /s/2.55-orig/cvs2cl.pl 2004-06-15 18:58:54.000000000 +0000 +++ /s/2.55/cvs2cl.pl 2004-06-15 18:59:14.000000000 +0000 @@ -2286,7 +2286,7 @@ my ($year, $mon, $mday, $hours, $min, $secs, $author, $state, $rest) = $line =~ - m!(\d+)/(\d+)/(\d+)\s+(\d+):(\d+):(\d+);\s+ + m!(\d+)[/-](\d+)[/-](\d+)\s+(\d+):(\d+):(\d+)(?:.*?);\s+ author:\s+([^;]+);\s+state:\s+([^;]+);(.*)!x or die "Couldn't parse date ``$line''"; die "Bad date or Y2K issues"

2 1

[Dovecot] SSL problems with imap-login
by Terje Rosten 15 Jun '04

15 Jun '04

I am using dovecot-0.99.10.5-1 on RHEL 3 for x86-64: $ uname -a Linux localhost 2.4.21-15.ELsmp #1 SMP Thu Apr 22 00:09:01 EDT 2004 x86_64 x86_64 x86_64 GNU/Linux The client is Horde-2.2.5/IMP-3.2 on Fedora Core 2 on i386. At random imap-login fails with the following error message: $ grep imap /var/log/maillog: Jun 15 18:01:08 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:01:17 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:15:25 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:15:25 anne imap-login: SSL_accept() failed: error:1409C041:SSL routines:SSL3_SETUP_BUFFERS:malloc failure [10.0.0.1] Jun 15 18:15:47 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:15:47 anne imap-login: SSL_accept() failed: error:1409C041:SSL routines:SSL3_SETUP_BUFFERS:malloc failure [10.0.0.1] Jun 15 18:16:00 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:16:00 anne imap-login: SSL_accept() failed: error:1409C041:SSL routines:SSL3_SETUP_BUFFERS:malloc failure [10.0.0.1] Jun 15 18:16:25 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:17:35 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:19:43 anne imap-login: SSL_accept() failed: error:1409C041:SSL routines:SSL3_SETUP_BUFFERS:malloc failure [10.0.0.1] Jun 15 18:52:01 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:52:01 anne imap-login: SSL_accept() failed: error:1409C041:SSL routines:SSL3_SETUP_BUFFERS:malloc failure [10.0.0.1] Jun 15 18:52:31 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:52:53 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:53:33 anne imap-login: Login: terjeros [10.0.0.1] Jun 15 18:54:30 anne imap-login: SSL_accept() failed: error:1409C041:SSL routines:SSL3_SETUP_BUFFERS:malloc failure [10.0.0.1] The box has plenty of memory: $ free | grep Mem Mem: 4016976 3696888 320088 0 731608 2279704 Any ideas? OpenSSL or dovecot issue? - Terje

2 2

[Dovecot] flat file mailbox formats
by Timo Sirainen 15 Jun '04

15 Jun '04

I've tried to write the new mbox code in a way that it could be moved into generic flat-file library with mbox-specific code being implemented on top of that. The code would be useful for all formats that require modifying message headers to store the metadata. How many such are there? I suppose all such formats could be implemented by separating mails into 3 logical parts: - header ("From ...\n") - mail data (headers and body) - footer ("\n") Except keeping a separate header and footer is kind of annoying, my current code uses: - mail separator ("\nFrom ...\n") - first message header's skip counter: how many characters to remove from mail separator for the first message (1, for \n before the "From ..") - last message's footer Somewhat uglier, but I think all needed formats could be implemented with it? It's also simper and more efficient to implement.. Besides mbox, I know at least two variations which are used: AAAA-box: - I remember seeing this somewhere years ago, but I'm not sure if it's still used or if it has a real name.. - separator is four ^A characters (ascii 1) and LF - header skip counter is 5 - last message footer would be the same ^A^A^A^A\n dotbox: - mails are stored in SMTP format, ie. lines beginning with '.' are prefixed with another '.'. the '.' prefixes will have to be removed for IMAP, so this isn't as simple as others to implement. - separator is ".\n" - header skip counter is 2 - last message footer is ".\n" Any thoughts?

2 1