- dovecot - dovecot.org

[Dovecot] triggering multiple actions on pop-3 request
by Eric S. Johansson 17 Mar '04

17 Mar '04

I want to trigger fetchmail when a user makes a pop-3 request. The reason for this is so that the messages retrieved by fetchmail can be filtered via an anti spam service before depositing them into the inbox. The way I figure it, since I need to know who the user is and that they authenticated in order to make the correct fetchmail call, I need to spawn the fetchmail process somewhere between the authentication and the pop 3 process. since I'm currently unfamiliar with code at that level, could I get a suggestion as to where to start looking?. apologies if I haven't explained is clearly enough. I'm still just kind of exploring the idea myself to see if it's the right way to approach this problem (pop 3 anti spam Gateway). If it works out right, it may even end up as part of a firewall (IPCop) as a way of making anti spam trivially easy for the technically challenged. (I.e. put it in a box, said it up right, don't let them touch it) I know it is also somewhat off topic for the group but since I want to modify dovecot (the IMAP server that rescued me from UW), I figured I would give it a shot. thanks in advance, ---eric

1 0

[Dovecot] Corrupted Indexes and File Permissions
by Dominic Marks 16 Mar '04

16 Mar '04

Hello, I'm using Dovecot to provide an IMAP service to a small number of users and I'm seeing two recurring errors which look like they might be related. Environment: o FreeBSD 5.2.1 / Postfix 2.0.18 / Dovecot 0.99.10.4 o Maildir mailboxes Problem: On logging in all the folders under the users mailbox are empty. This has happened with both MS Outlook 2000 clients as well as Squirrelmail which uses c-client. When you look at the mail log it shows errors from Dovecot about index file corruption and file permissions (see attached sample section). I've checked the permissions on the maildir and it seems at the moment that the user has rw permssion on every file under cur, could this error be caused by an interaction between Postfix and Dovecot? Any comments / suggestions greatly appreciated, -- Dominic Marks

2 3

[Dovecot] index file corruption
by mat＠reynerie.org 16 Mar '04

16 Mar '04

Hi, I'm using Dovecot (dovecot-0.99.10p0) on OpenBSD-3.4 for few weeks now. When i connect to my IMAP account the connection is often closed by dovecot when i try to delete mails. I can see messages like this in log: Feb 29 18:47:00 po imap(mat(a)reynerie.org): Corrupted binary tree file /home/mat/Maildir//.INBOX/.imap.index.tree: used_file_size larger than real file size (1772 vs 1556) I tried to remove all index files, but the problem still occur. I also tried Maildir and Mbox, same problem (i can't remember if the log are similar with mbox, if needed i will test again). I have ktraced the imap process and try (succesfully) to reproduce this behaviour: I have re-send a lot of spam and delete few of them from mailbox until the problem occur. All logs/kdump/config are here: http://mat.reynerie.org/dovecot/ In the kdump file, the problem is visible at the end, Dovecot is compiled (via ports) with: env CFLAGS="-I/usr/local/include -L/usr/local/lib" CONFIGURE_ARGS="--with-ldap --with-ldap-includes=/usr/local/include --with-ldap-lib=/usr/local/lib" make Searching the mailing list archives, i have not found any solutions. -- mat

3 3

Re: [Dovecot] Mysql patch question
by Skye Poier 16 Mar '04

16 Mar '04

Last question of the day I promise :) If dovecot is configured to use the MySQL patch, ie: auth_userdb = mysql /path/to/dovecot-mysql.conf auth_passdb = mysql /path/to/dovecot-mysql.conf Its not possible to "chain" authentication methods is it? I mean, if its using MySQL it _cannot_ be configured to check passwd (via "pam *") first, and then check mysql, right? So, if I want to support real shell users (who are in /etc/passwd) I will have to have them in mysql along with the "virtual" users. ...... OK I lied, one more question! I love the feature that you can login with a username user@domain and the domain is automatically parsed out. Do these options have anything to do with the @domain part (referred to as a realm in auth.txt) or are they for something else completely? I'm not sure what SASL is that it refers to in the example .conf #auth_realms = #auth_default_realm = Thanks, Skye

1 0

[Dovecot] Help with dovecot+passwd+pam_mysql
by Skye Poier 15 Mar '04

15 Mar '04

Hi again, I'm on Freebsd 4.x and instead of using the mysql patch, it seems like it would be easier to just use "auth_passdb = pam *" with the pam_mysql drop-in. I'm not really a pam.conf writing expert though. Here's what it currently contains (works for /etc/passwd users) imap auth required pam_unix.so imap account required pam_unix.so try_first_pass imap session required pam_deny.so How would I set it up so that it first checks to see if the user is in /etc/passwd (as above) and then checks pam_mysql.so? Example from the pam_mysql readme: auth optional pam_mysql.so user=root passwd=password account required pam_mysql.so user=root passwd=password Is anyone else using this setup? Any disadvantages? Thanks, Skye

1 1

[Dovecot] Next version features?
by Skye Poier 15 Mar '04

15 Mar '04

Hello, sorry if this gets asked a lot :) When is the next version of dovecot planned for release? Will it include non-patched MySQL support? Can I make a donation to speed up the process? I have used about 5 different IMAP servers in the last month trying to find one that didn't suck.. and I'm happy to say dovecot is the best!! Thanks, Skye

1 0

[Dovecot] dovecot & vpopmail
by Dirk Jäckel 12 Mar '04

12 Mar '04

Hi! Authentication works, but default_mail_env = maildir:/usr/local/vpopmail/domains/%d/%n/Maildir/ is translated by the "imap"-process to /usr/local/vpopmail/domains//testerhorst/Maildir/ although I succesfully log in as testerhorst(a)elektropost.org. Is there a manual how to use dovecot with vpopmail? We have here: FreeBSD 4.9-STABLE, vpopmail-5.4.0 and dovecot-0.99.10.4_2. Thank you for your help! Regards, Dirk Jaeckel

2 1

RE: [Dovecot] MySQL Auth and default_mail_env
by dovecot＠technicalabuse.com 10 Mar '04

10 Mar '04

Well I've tried a number of different permissions , uid , gid What I have are mail server permissions on the spool folders where the users are virtual. The mail server runs under exim:mail and I have tried unique uid:gid and exim:mail uid:gid To access the directories as well as the folder permissions 770 750 etc. Dovecot is running as it's own user (imapd) What should they be working as ? Maybe I missed something in the docs. Gary -----Original Message----- From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] On Behalf Of David S. Madole Sent: Tuesday, March 09, 2004 1:30 PM To: dovecot(a)technicalabuse.com Cc: dovecot(a)dovecot.org Subject: Re: [Dovecot] MySQL Auth and default_mail_env > From: <dovecot(a)technicalabuse.com> > Sent: Tuesday, March 09, 2004 3:04 PM > > Now I get chdir fatals but at least it's dynamic. > > failed with uid Permission denied > So what are the permissions on the directories? David ____________________________________________________________________________ This message is spam and virus free. Filtering solutions by http://omd3.com Expert computer system support and development by http://baysidenetworks.com

2 2

[Dovecot] imap internaldate
by Payton 10 Mar '04

10 Mar '04

I think I found a bug in dovecot which I'm not sure where to fix. (I may even have found a reference to it in an archived list message from Jul 2003.) Here is the situation: dovecot (dovecot-0.99.10.4) running with an imap server on an mbox system is queried by a local client program, like Mail.app, and is told the "Received" date of the message (presumably sent through INTERNALDATE), however, that date is being passed on in GMT (-0000) instead of the server or client's local time zone (EST -0500, in this case). Maybe it's assumed that the local client will convert this time to the local zone, but no clients I know actually do that. Anyone know how/where to fix this? Thanks! - Payton - payton(a)repligen.com

3 2

[Dovecot] MySQL Auth and default_mail_env
by dovecot＠technicalabuse.com 09 Mar '04

09 Mar '04

Hi Not sure how much support you guys can offer but when I use default_mail_env = mbox:/var/spool/mail/%d/imap/%n/:INBOX=/var/spool/mail/%d/%n I get the login error .. Fatal: Failed to create storage with data: mbox:/var/spool/mail/DOMAIN/imap/USER/:INBOX=/var/spool/mail/DOMAIN/USER It is grabbing the right values for %d and %n from the mysql query 65 Query SELECT password FROM users WHERE username = 'USER' AND domainname = 'DOMAIN' 65 Query SELECT home, uid, gid FROM users where username = 'USER' AND domainname = 'DOMAIN' Anyone have the same experience. Any help is appreciated. Gary TechnicalAbuse.com

2 4

[Dovecot] Problems with Mozilla
by Tres! 09 Mar '04

09 Mar '04

Hello, I've some problems with Dovecot and Mozilla. First of all i have to mention, that Dovecot is installed on SuSE Linux 8.2 and uses up to 20 Win32 Mozilla clients. If you need further information, please let me know. My problem is, that I got one or two times a week a login failure from Mozilla, and the clients can't connect anymore. The error message from Mozilla after a long time "checking server capabilities" is "server is not an imap4 server". I haven't found something usable in the logs except for a login timeout of the clients who want to connect. If i kill the imap and imap-login tasks and restart redove, everything works well for some days. Is there anyone who knows something about my problem? regards Tres!

1 0

[Dovecot] RE: imap segv trying to list inbox
by Sam Powers 09 Mar '04

09 Mar '04

(This is releveant information to the one that Alex Moore just posted, but I'm not subscribed yet so I can't properly reply to that thread. Sorry for creating a new one.) I've got a crash in dovecot-imap when trying to list the inbox on a nonexistant directory. I'm not sure how it should be handled, but basically it's only happening when the directory in imap's MAIL environment doesn't exist. This is a problem for me because I'm trying to have dovecot create all the necessary directories in the specified environment, as I don't know if the user will pop/imap or recieve an email first, and the dir needs to either be already ready, or created upon reciept. I've already got postfix to create a ~/Maildir when a new mail comes in, but for my migration plan to work, I need dovecot to create this directory instead of segfaulting. ;) dante:/usr/lib/dovecot# MAIL=maildir:/tmp/nonexistant gdb ./imap (gdb) run Starting program: /usr/lib/dovecot/imap (no debugging symbols found)...(no debugging symbols found)... * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED] Logged in as root 1 list "" inbox (no debugging symbols found)... Program received signal SIGSEGV, Segmentation fault. 0x400c32ef in readdir64 () from /lib/libc.so.6 (gdb) bt #0 0x400c32ef in readdir64 () from /lib/libc.so.6 #1 0x0805c70b in maildir_expunge_locked () #2 0x0805cda1 in maildir_list_mailbox_init () #3 0x08052a60 in cmd_idle () #4 0x08052d4a in _cmd_list_full () #5 0x08052ea7 in cmd_list () #6 0x08054a19 in _client_reset_command () #7 0x08054aa8 in _client_input () #8 0x0808adb8 in io_loop_handler_run () #9 0x0808a748 in io_loop_run () #10 0x0805aab9 in main () #11 0x40034dc6 in __libc_start_main () from /lib/libc.so.6 If I use MAIL=maildir:/tmp/nonexistant, it crashes, but what I'm really trying to do is MAIL=maildir:/home/staff/%u/Maildir/, which will necessarily be nonexistant, and I'd like to see dovecot create this in the manner that postfix does; with the logged in user's uid/gid. Now, if I leave default_mail_env blank, and let dovecot's autodetection do the work, it seems to create a maildir in ~/mail. This works just fine, except it's the wrong directory. Otherwise, dovecot rocks, and in another, less automatic setup, I've been using it for the better part of a year with nothing but happy results, and appreciate your work. (Irssi too :) -Sam

1 0

[Dovecot] RE: imap process abends
by Alex S Moore 08 Mar '04

08 Mar '04

I am trying to setup dovecot imap on a test Solaris 8 box. I have dovecot POP3S running fine on another box, but I want to switch to IMAP. I see a successful login with a message like: Mar 8 13:22:47 sws601.mcsun.local imap-login: [ID 457029 mail.info] Login: sunuser1 [192.168.1.17] Then the Mozilla Mail client gets a message that the server disconnected. It appears to be from a segfault on the imap process. Here is the next message in syslog: Mar 8 13:22:47 sws601.mcsun.local dovecot: [ID 684838 mail.error] child 14108 (imap) killed with signal 11 On my ldap server, I see all of the appropriate entries for logging in getting the userdb info. So I think that I am past the login process, but I could be wrong. I setup a maildir environment on this server as follows: maildir:/export/home/imap/%u:INDEX=/var/indexes/%d/%n I have a test message to pickup and the maildir folders seem OK to me. Help, Alex

1 0

[Dovecot] Mails manipulation and indices
by Giacomo Cariello 06 Mar '04

06 Mar '04

I've recently manipulated the contents of my maildir, changing the content of some mail files (mime handling and such...). This broke dovecot since it expected different filesizes while reading contents of files that were previously indexed. Therefore dovecot returned some assert like this: imap(jwk(a)bug.it): file istream.c: line 163 (i_stream_seek): assertion failed: (v_offset <= stream->v_size) Obviously, the solution was to remove indices and have dovecot recreate them. I suppose it would be more "polite" to have this kind of routines (i_stream_seek etc) handle this case by requesting indices recreation for indices that are no longer "real", instead of just dropping connection with some "internal error" message. Giacomo Cariello, jwk(a)bug.it KeyID: 3072/1024/0x409C9044 Fingerprint: 7984 10FD 0460 4202 BF90 3881 CDE4 D78E 409C 9044 "Put that mic in my hand and let me kick out the jams!" - MC5

1 0

[Dovecot] OS X 10.3, SSL, client connection hangs?
by Chad Bergeron 05 Mar '04

05 Mar '04

Ok, I've just installed Dovecot, and got it set up in xinetd for ssl and plain/pam. Everything looks good, I even got to the point where my client (mail.app) asked if I wanted to accept the new certificate I'd made. All good. But then the imap connection seems to hang right after negotiating. Nothing shows up in my logs except a disconnect, usually for inactivity. Has anyone else managed to set Dovecot up on 10.3, and has anyone seen this issue, or ones like it? Trying to figure out where to go from here... -Chad Bergeron

2 1

[Dovecot] imap MUA received
by Payton 04 Mar '04

04 Mar '04

Does anyone know where MUAs like Outlook, Entourage, and Mail.app get their 'Received' or 'Date Received' information from? It certainly doesn't appear to correspond with the mail headers, at least in my case, so I'm guessing it's possibly getting that data from the IMAP server? My mail clients (MUAs) show the 'Receieved' time as 5 hours off. I have qmail running as my MTA, and since it stamps emails' "Received" header with time in GMT (-0000) and I'm in EST (-0500) I thought that was the problem. However, I patched qmail to set the headers in -0500 instead, which worked as far as I can tell, but the MUAs *still* report the time incorrectly! (Time on both the client and the server are correct as well.) Here is my setup: dovecot running pop/imap mbox files (yes, i know this is bad) qmail as my MTA (used to list time as GMT in headers, but I patched it and now the headers list time in the local zone instead) -- ;; Payton Swick ;; ;; Repligen Corporation ;; ;; IT Systems Administrator ;; ;; payton(a)repligen.com ;;

1 0

[Dovecot] RFE: more graceful handling of startup errors
by Matthias Andree 04 Mar '04

04 Mar '04

Hi, I've just had a funny (but not amusing) incident after boot-up on a Dovecot server. rpc.mountd (NFS server) grabbed port 995 (POP3-SSL), and the whole Dovecot lot (POP3-SSL, IMAP-SSL, IMAP) refused to start up, rather than just letting POP3-SSL fail with "address in use". May I request to kindly consider letting Dovecot services fail individually rather than all of them, at least optionally? TIA, -- Matthias Andree Encrypt your mail: my GnuPG key ID is 0x052E7D95

1 0

[Dovecot] libpam-pwdfile
by Pahlevanzadeh Mohsen 04 Mar '04

04 Mar '04

hi Where are libpam-pwdfile on my hard? Please guide me... Yours,Mohsen. ===== ---------DIGITAL SIGNATURE------------------- ///Mohsen Pahlevanzadeh//////// Network administrator & programmer My work phone is : +98216054096-7 My home phone is: +98213810146 My emails is m_pahlevanzadeh(a)yahoo.com My website is: http://webnegar.net ---------------------------------------------------------------- __________________________________ Do you Yahoo!? Yahoo! Search - Find what you�re looking for faster http://search.yahoo.com

1 0

[Dovecot] user
by Pahlevanzadeh Mohsen 04 Mar '04

04 Mar '04

Hi. I want to test my users. This means when i login via telnet or other,i can login into imapo server. Please guide me..... Yours,Mohsen. ===== ---------DIGITAL SIGNATURE------------------- ///Mohsen Pahlevanzadeh//////// Network administrator & programmer My work phone is : +98216054096-7 My home phone is: +98213810146 My emails is m_pahlevanzadeh(a)yahoo.com My website is: http://webnegar.net ---------------------------------------------------------------- __________________________________ Do you Yahoo!? Yahoo! Search - Find what you�re looking for faster http://search.yahoo.com

1 0

Re: [Dovecot] UW-IMAP -> Dovecot : patch to remove nasty
by Joseph Teichman 03 Mar '04

03 Mar '04

> I've also heard of some actual mbox corruption from one large > installation, but I don't know if it really was Dovecot's problem as > I've never heard of it from others. Might have been some problem related > to their specific environment. I have also had a similar problem where there was partial curroption of an mbox folder. After that point in time, I could not properly read some messags using Openwebmail. I did not have time to fully investigate the exact cause and the exact form of the curroption, but I did want to let you know that it is an issue. Thanks, Joe

1 0

[Dovecot] debian unstable : mutt polling imap mailboxes
by Kai Hendry 02 Mar '04

02 Mar '04

Package: dovecot Version: 0.99.10.4-2 I am accessing my IMAP folder on my ~/Maildir using mutt via Dovecot and I have this problem whereby mutt incorrectly reports I have new mail in a "mailboxes" polled mailbox. This happens all the time when I press the key bound to change mailbox. I use courier IMAP at school, and I have not experienced this problem. A bug with dovecot or mutt?

3 3

[Dovecot] Dovecot failing silently on startup
by Julian Melville 02 Mar '04

02 Mar '04

I'm puzzled... I'm running the Debian package of Dovecot 0.99.10.4 on a Debian (testing) server, and it's basically doing nothing on startup for an extended period. After a while (maybe 10 minutes or more) it all suddenly starts working, all without logging anything untoward. All the dovecot processes appear to start OK, and 'Dovecot starting up' is logged to the syslog. If you telnet to an IMAP or POP3 port at this point, it will successfully connect but there's no response (i.e. no '* OK dovecot ready'). Nothing else on this server is failing in this way; e.g. Apache and PostgreSQL are running fine throughout this period. Has anyone else seen anything like this? Cheers, Julian.

2 1

[Dovecot] severe problem
by Ewald Geschwinde 01 Mar '04

01 Mar '04

I have debian knoppix and postfix + dovecot imap My problem is the following: Feb 29 18:51:14 cybserv imap-login: Login: xx(a)xxx.xx [xx.xx.xx.xx] Feb 29 18:51:14 cybserv dovecot: child 13959 (imap) killed with signal 11 Feb 29 18:52:41 cybserv imap-login: Disconnected [xx.xxx.xx.xx] Feb 29 18:52:41 cybserv dovecot: child 13952 (login) killed with signal 11 I'm using the debian package for the version 0.99.10.4-2 Always when someone tries to login the server throws this error I don't know whats going wrong I'm using a postgresql backend Regards Ewald Geschwinde

2 1

[Dovecot] SSL 143/notls stuff
by Mark Williamson 27 Feb '04

27 Feb '04

Hi Everyone, Just trying to work out how totally disable SSL/TLS support on port 143 while enabling SSL support on port 993 In the config file when I comment out the setting "ssl_disable = yes", I have Webmail client that will no longer be able to auth against port 143, Now I can get the Webmail client to sort of work via using the setting the port to "143/notls" but the main problem with that is that the WEbmail client does not support that setting correctly, giving the Webmail issues in other areas. Anyway is there a way of enabling SSL support on 993, and a way to let port 143 to auth with out the need of using a setting port "143/notls" Cheers Mark Williamson

2 3

[Dovecot] [OT] How is the Changelog file created?
by Sven Kirmess 26 Feb '04

26 Feb '04

How is the Changelog file created? I assume there is a tool which grabs this information from the CVS repository. What's the name of this tool? Sven

3 3

[Dovecot] Set only INDEX path
by Kilian CAVALOTTI 26 Feb '04

26 Feb '04

Hi folks, I'd like to know if I can set the INDEX path in the default_mail_env, without setting the format and location of mailboxes (something like default_mail_env = :INDEX=/var/mail/indexes/%u) I want to let each user choose whether he prefers to store his mail in mbox or maildir format, so I don't want to /force/ the configuration in the default_mail_env variable, but let the autodetection feature of Dovecot do the job. The problem is that home folders are NFS mounted on the mail server. So I'd like to put the indexes somewhere locally on the mail server. I tried to set the default_mail_env with various combinations of ':' and INDEX, but with no success, I invariably get "Fatal: Failed to create storage with data..." error messages. Is there any solution to my problem ? ;) TIA, -- Kilian

1 0

[Dovecot] More than one auth method with dovevot 0.99.10.4 - how?
by Raymond Scholz 25 Feb '04

25 Feb '04

We're setting up a server with qmail/vpopmail and dovecot. In addition to vpopmail users we want non-virtual, local users to be able to authenticate and have them read the Maildir in their real $HOME. vpopmail userdb/passwd works fine. Now how do I tell dovecot to use passwd (or PAM) userdb/passdb authentication too? /etc/dovecot.conf: [...] auth = default auth_mechanisms = plain auth_userdb = vpopmail auth_passdb = vpopmail auth_user = root auth_verbose = yes auth = local auth_mechanisms = plain auth_userdb = passwd /etc/passwd auth_passdb = pam auth_user = root auth_verbose = yes #auth_methods = default local EOF I think, I'm supposed to put the auth_methods line somewhere. Without it, dovecot only tries authentication using the first auth process definition: | Feb 25 00:01:49 server1 dovecot-auth: vpopmail(rscholz): unknown user (rscholz@) after loggin in with ". login rscholz secret_password" at the IMAP server. Putting the auth_methods line behind the two auth processes (or somewhere in the middle) gives me: | Starting mail server: dovecotFatal: Error in configuration file /etc/dovecot.conf line 456: Unknown setting: methods Putting it above all auth processes gives me: | Starting mail server: dovecotFatal: Error in configuration file /etc/dovecot.conf line 362: Authentication process name not defined yet Hm, I'm lost here. System is Debian i386 stable (woody) with dovecot_0.99.10.4-2.deb backported from Debian unstable. Cheers, Ray -- Hfr fgebat rapelcgvba!

2 2

[Dovecot] Mailbox formats
by Kenneth Porter 25 Feb '04

25 Feb '04

I'm currently using mbox and mbx with UW-IMAP, mbox for space efficiency and mbx for folders with lots of messages for time efficiency without a large space cost. I've avoided maildir because it has a relatively high space cost; mbox has no inter-message cost while maildir wastes on average half a sector plus an inode for each message. What other formats are there, and has anyone come up with a good format that gives both good time and space characteristics without sacrificing reliability? (I'm aware of the file format list in the UW-IMAP distro: <http://www.washington.edu/imap/documentation/formats.txt.html>)

2 2

[Dovecot] Pam trouble
by Benjamin Dabelow 25 Feb '04

25 Feb '04

Hi folks, I can't get dovecot to authenticate properly against ldap/pam. I've been fiddling with it for several days now, to no avail. It keeps crashing with: Child died with signal 11 The system is Solaris9. Enclosed is a trace of dovecot-auth for a connection to pop with correct username and password and my config. Any help is appreciated. Cheers Benjamin Trace----------------------------------------------------- 29964: poll(0x00052E28, 9, 4999) (sleeping...) 29964: poll(0x00052E28, 9, 4999) = 0 29964: poll(0x00052E28, 9, 0) = 0 29964: poll(0x00052E28, 9, 4999) (sleeping...) 29964: poll(0x00052E28, 9, 4999) = 1 29964: accept(3, 0xFFBFFAD0, 0xFFBFFAC8, 1) = 13 29964: fstat64(13, 0xFFBFF920) = 0 29964: getsockopt(13, SOL_SOCKET, 0x2000, 0xFFBFFA20, 0xFFBFFA1C, 0) = 0 29964: setsockopt(13, SOL_SOCKET, 0x2000, 0xFFBFFA20, 4, 0) = 0 29964: fcntl(13, F_SETFL, 0x00000080) = 0 29964: fstat64(13, 0xFFBFF9D8) = 0 29964: llseek(13, 0, SEEK_CUR) Err#29 ESPIPE 29964: getsockname(13, 0xFFBFF928, 0xFFBFF924, 1) = 0 29964: write(13, "\0\0 u\f\0\0\001", 8) = 8 29964: poll(0x00052E28, 10, 2917) = 1 29964: read(13, "\0\0 u1C", 4096) = 4 29964: poll(0x00052E28, 10, 2917) (sleeping...) 29964: poll(0x00052E28, 10, 2917) = 0 29964: poll(0x00052E28, 10, 0) = 0 29964: poll(0x00052E28, 10, 4999) (sleeping...) 29964: poll(0x00052E28, 10, 4999) = 1 29964: read(14, "\0\0\001\0\0\001\0\0\001".., 4092) = 16 29964: write(14, "\0\0\001\0\0\001\0\0\0\0".., 20) = 20 29964: poll(0x00052E28, 10, 1664) = 1 29964: read(14, "\0\0\002\0\0\001\0\0\011".., 4076) = 29 29964: pipe() = 15 [16] 29964: fork1() = 29981 29964: lwp_schedctl(SC_STATE|SC_PREEMPT, 0, 0xFFBFF7AC) = 0 29964: close(16) = 0 29981: fork1() (returning as child ...) = 29964 29981: getpid() = 29981 [29964] 29981: close(15) = 0 29981: lwp_schedctl(SC_STATE|SC_PREEMPT, 0, 0xFFBFF4A4) = 0 29981: open("/etc/pam_debug", O_RDONLY) Err#2 ENOENT 29981: stat64("/etc/pam.conf", 0xFFBFF4C0) = 0 29981: open("/etc/pam.conf", O_RDONLY) = 15 29981: mmap(0x00000000, 1893, PROT_READ, MAP_PRIVATE, 15, 0) = 0xFEBA0000 29981: munmap(0xFEBA0000, 1893) = 0 29981: close(15) = 0 29981: stat64("/usr/lib/security/pam_unix.so.1", 0xFFBFF400) = 0 29981: stat("/usr/lib/security/pam_unix.so.1", 0xFFBFED44) = 0 29981: open("/usr/lib/security/pam_unix.so.1", O_RDONLY) = 15 29981: fstat(15, 0xFFBFED44) = 0 29981: mmap(0x00000000, 8192, PROT_READ|PROT_EXEC, MAP_PRIVATE, 15, 0) = 0xFEBA0000 29981: mmap(0x00000000, 212992, PROT_READ|PROT_EXEC, MAP_PRIVATE, 15, 0) = 0xFEB40000 29981: mmap(0xFEB6A000, 36767, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 15, 106496) = 0xFEB6A000 29981: munmap(0xFEB5A000, 65536) = 0 29981: resolvepath("/usr/lib/security/pam_unix.so.1", "/usr/lib/security/pam_unix.so.1", 1023) = 31 29981: memcntl(0xFEB40000, 24652, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0 29981: close(15) = 0 29981: stat("/usr/lib/libc.so.1", 0xFFBFEC84) = 0 29981: stat("/usr/lib/libpam.so.1", 0xFFBFEC84) = 0 29981: stat("/usr/lib/libnsl.so.1", 0xFFBFEC84) = 0 29981: stat("/usr/lib/libcmd.so.1", 0xFFBFEC84) = 0 29981: stat("/usr/lib/libmp.so.2", 0xFFBFEC84) = 0 29981: munmap(0xFEBA0000, 8192) = 0 29981: stat64("/usr/lib/security/pam_openldap.so.1", 0xFFBFF400) = 0 29981: stat("/usr/lib/security/pam_openldap.so.1", 0xFFBFED44) = 0 29981: open("/usr/lib/security/pam_openldap.so.1", O_RDONLY) = 15 29981: fstat(15, 0xFFBFED44) = 0 29981: mmap(0x00000000, 8192, PROT_READ|PROT_EXEC, MAP_PRIVATE, 15, 0) = 0xFEBA0000 29981: mmap(0x00000000, 106496, PROT_READ|PROT_EXEC, MAP_PRIVATE, 15, 0) = 0xFEB20000 29981: mmap(0xFEB38000, 3928, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 15, 32768) = 0xFEB38000 29981: munmap(0xFEB2A000, 57344) = 0 29981: resolvepath("/usr/lib/security/pam_openldap.so.1", "/usr/lib/security/pam_openldap.so.1", 1023) = 35 29981: memcntl(0xFEB20000, 6704, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0 29981: close(15) = 0 29981: stat("/opt/OpenLDAP2/lib/libc.so.1", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/local/ssl/lib/libc.so.1", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/lib/libc.so.1", 0xFFBFEC84) = 0 29981: stat("/opt/OpenLDAP2/lib/libldap.so.2", 0xFFBFEC84) = 0 29981: mmap(0x00000000, 8192, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_ANON, -1, 0) = 0xFEB10000 29981: stat("/opt/OpenLDAP2/lib/liblber.so.2", 0xFFBFEC84) = 0 29981: stat("/opt/OpenLDAP2/lib/libnsl.so.1", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/local/ssl/lib/libnsl.so.1", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/lib/libnsl.so.1", 0xFFBFEC84) = 0 29981: stat("/opt/OpenLDAP2/lib/libcrypt_i.so.1", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/local/ssl/lib/libcrypt_i.so.1", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/lib/libcrypt_i.so.1", 0xFFBFEC84) = 0 29981: stat("/opt/OpenLDAP2/lib/libresolv.so.2", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/local/ssl/lib/libresolv.so.2", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/lib/libresolv.so.2", 0xFFBFEC84) = 0 29981: stat("/opt/OpenLDAP2/lib/libpam.so.1", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/local/ssl/lib/libpam.so.1", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/lib/libpam.so.1", 0xFFBFEC84) = 0 29981: stat("/opt/OpenLDAP2/lib/libdl.so.1", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/local/ssl/lib/libdl.so.1", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/lib/libdl.so.1", 0xFFBFEC84) = 0 29981: stat("/opt/OpenLDAP2/lib/libpthread.so.1", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/local/ssl/lib/libpthread.so.1", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/lib/libpthread.so.1", 0xFFBFEC84) = 0 29981: stat("/opt/OpenLDAP2/lib/librt.so.1", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/local/ssl/lib/librt.so.1", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/lib/librt.so.1", 0xFFBFEC84) = 0 29981: stat("/opt/OpenLDAP2/lib/libdb-4.0.so", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/local/ssl/lib/libdb-4.0.so", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/lib/libdb-4.0.so", 0xFFBFEC84) = 0 29981: stat("/opt/OpenLDAP2/lib/libssl.so.0.9.7", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/local/ssl/lib/libssl.so.0.9.7", 0xFFBFEC84) = 0 29981: stat("/opt/OpenLDAP2/lib/libcrypto.so.0.9.7", 0xFFBFEC84) Err#2 ENOENT 29981: stat("/usr/local/ssl/lib/libcrypto.so.0.9.7", 0xFFBFEC84) = 0 29981: munmap(0xFEBA0000, 8192) = 0 29981: open64("/var/run/name_service_door", O_RDONLY) = 15 29981: fcntl(15, F_SETFD, 0x00000001) = 0 29981: door_info(15, 0xFEEC2668) = 0 29981: close(15) = 0 29981: stat("/usr/lib/nss_files.so.1", 0xFFBFDE64) = 0 29981: open("/etc/passwd", O_RDONLY) = 15 29981: fstat64(15, 0xFFBFE2D8) = 0 29981: brk(0x00081460) = 0 29981: brk(0x00083460) = 0 29981: fstat64(15, 0xFFBFE180) = 0 29981: ioctl(15, TCGETA, 0xFFBFE264) Err#25 ENOTTY 29981: read(15, " r o o t : x : 0 : 1 : Z".., 8192) = 710 29981: read(15, 0x00080594, 8192) = 0 29981: llseek(15, 0, SEEK_CUR) = 710 29981: close(15) = 0 29981: stat("/usr/lib/nss_ldap.so.1", 0xFFBFDE64) = 0 29981: open("/usr/lib/nss_ldap.so.1", O_RDONLY) = 15 29981: fstat(15, 0xFFBFDE64) = 0 29981: mmap(0x00000000, 8192, PROT_READ|PROT_EXEC, MAP_PRIVATE, 15, 0) = 0xFEBA0000 29981: mmap(0x00000000, 163840, PROT_READ|PROT_EXEC, MAP_PRIVATE, 15, 0) = 0xFEAE0000 29981: mmap(0xFEAFC000, 4828, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED, 15, 49152) = 0xFEAFC000 29981: mmap(0xFEAFE000, 35640, PROT_READ|PROT_WRITE|PROT_EXEC, MAP_PRIVATE|MAP_FIXED|MAP_ANON, -1, 0) = 0xFEAFE000 29981: munmap(0xFEAEE000, 57344) = 0 29981: resolvepath("/usr/lib/nss_ldap.so.1", "/usr/lib/nss_ldap.so.1", 1023) = 22 29981: memcntl(0xFEAE0000, 9792, MC_ADVISE, MADV_WILLNEED, 0, 0) = 0 29981: close(15) = 0 29981: stat("/opt/OpenLDAP2/lib/libldap.so.2", 0xFFBFDDA4) = 0 29981: stat("/opt/OpenLDAP2/lib/liblber.so.2", 0xFFBFDDA4) = 0 29981: stat("/opt/OpenLDAP2/lib/libdb-4.0.so", 0xFFBFDDA4) Err#2 ENOENT 29981: stat("/usr/local/ssl/lib/libdb-4.0.so", 0xFFBFDDA4) Err#2 ENOENT 29981: stat("/usr/lib/libdb-4.0.so", 0xFFBFDDA4) = 0 29981: stat("/opt/OpenLDAP2/lib/libdl.so.1", 0xFFBFDDA4) Err#2 ENOENT 29981: stat("/usr/local/ssl/lib/libdl.so.1", 0xFFBFDDA4) Err#2 ENOENT 29981: stat("/usr/lib/libdl.so.1", 0xFFBFDDA4) = 0 29981: stat("/opt/OpenLDAP2/lib/libnsl.so.1", 0xFFBFDDA4) Err#2 ENOENT 29981: stat("/usr/local/ssl/lib/libnsl.so.1", 0xFFBFDDA4) Err#2 ENOENT 29981: stat("/usr/lib/libnsl.so.1", 0xFFBFDDA4) = 0 29981: stat("/opt/OpenLDAP2/lib/libresolv.so.2", 0xFFBFDDA4) Err#2 ENOENT 29981: stat("/usr/local/ssl/lib/libresolv.so.2", 0xFFBFDDA4) Err#2 ENOENT 29981: stat("/usr/lib/libresolv.so.2", 0xFFBFDDA4) = 0 29981: stat("/opt/OpenLDAP2/lib/libpthread.so.1", 0xFFBFDDA4) Err#2 ENOENT 29981: stat("/usr/local/ssl/lib/libpthread.so.1", 0xFFBFDDA4) Err#2 ENOENT 29981: stat("/usr/lib/libpthread.so.1", 0xFFBFDDA4) = 0 29981: stat("/opt/OpenLDAP2/lib/librt.so.1", 0xFFBFDDA4) Err#2 ENOENT 29981: stat("/usr/local/ssl/lib/librt.so.1", 0xFFBFDDA4) Err#2 ENOENT 29981: stat("/usr/lib/librt.so.1", 0xFFBFDDA4) = 0 29981: stat("/opt/OpenLDAP2/lib/libssl.so.0.9.7", 0xFFBFDDA4) Err#2 ENOENT 29981: stat("/usr/local/ssl/lib/libssl.so.0.9.7", 0xFFBFDDA4) = 0 29981: stat("/opt/OpenLDAP2/lib/libcrypto.so.0.9.7", 0xFFBFDDA4) Err#2 ENOENT 29981: stat("/usr/local/ssl/lib/libcrypto.so.0.9.7", 0xFFBFDDA4) = 0 29981: munmap(0xFEBA0000, 8192) = 0 29981: sigaction(SIGPIPE, 0xFFBFE2B8, 0xFFBFE3F8) = 0 29981: sigprocmask(SIG_SETMASK, 0xFEBEA0B4, 0xFFBFE308) = 0 29981: sigprocmask(SIG_SETMASK, 0xFFBFE2F4, 0x00000000) = 0 29981: getpid() = 29981 [29964] 29981: getuid() = 0 [0] 29981: open("/etc/ldap.conf", O_RDONLY) = 15 29981: fstat64(15, 0xFFBFCA38) = 0 29981: fstat64(15, 0xFFBFC8E0) = 0 29981: ioctl(15, TCGETA, 0xFFBFC9C4) Err#25 ENOTTY 29981: read(15, " # @ ( # ) $ I d : l".., 8192) = 6190 29981: read(15, 0x0008018C, 8192) = 0 29981: llseek(15, 0, SEEK_CUR) = 6190 29981: close(15) = 0 29981: open64("/var/run/name_service_door", O_RDONLY) = 15 29981: fcntl(15, F_SETFD, 0x00000001) = 0 29981: door_info(15, 0xFEEC2668) = 0 29981: close(15) = 0 29981: open("/etc/inet/ipnodes", O_RDONLY) = 15 29981: fstat64(15, 0xFFBFADA8) = 0 29981: brk(0x00083460) = 0 29981: brk(0x00085460) = 0 29981: fstat64(15, 0xFFBFAC50) = 0 29981: ioctl(15, TCGETA, 0xFFBFAD34) Err#25 ENOTTY 29981: read(15, " #\n # I n t e r n e t".., 8192) = 61 29981: read(15, 0x0008257C, 8192) = 0 29981: llseek(15, 0, SEEK_CUR) = 61 29981: close(15) = 0 29981: open64("/var/run/name_service_door", O_RDONLY) = 15 29981: fcntl(15, F_SETFD, 0x00000001) = 0 29981: door_info(15, 0xFEEC2668) = 0 29981: close(15) = 0 29981: open("/etc/hosts", O_RDONLY) = 15 29981: fstat64(15, 0xFFBFAD28) = 0 29981: fstat64(15, 0xFFBFABD0) = 0 29981: ioctl(15, TCGETA, 0xFFBFACB4) Err#25 ENOTTY 29981: read(15, " #\n # I n t e r n e t".., 8192) = 107 29981: read(15, 0x0008257C, 8192) = 0 29981: llseek(15, 0, SEEK_CUR) = 107 29981: close(15) = 0 29981: so_socket(PF_INET, SOCK_STREAM, IPPROTO_IP, "", 1) = 15 29981: setsockopt(15, tcp, TCP_NODELAY, 0xFFBFD724, 4, 1) = 0 29981: fcntl(15, F_GETFL, 0xFF1FE9E0) = 2 29981: fstat64(15, 0xFFBFD468) = 0 29981: getsockopt(15, SOL_SOCKET, 0x2000, 0xFFBFD568, 0xFFBFD560, 0) = 0 29981: fstat64(15, 0xFFBFD4D8) = 0 29981: getsockopt(15, SOL_SOCKET, 0x2000, 0xFFBFD5D8, 0xFFBFD5D4, 0) = 0 29981: setsockopt(15, SOL_SOCKET, 0x2000, 0xFFBFD5D8, 4, 0) = 0 29981: fcntl(15, F_SETFL, 0x00000082) = 0 29981: connect(15, 0x0007F9E8, 16, 1) = 0 29981: fcntl(15, F_GETFL, 0xFF1FE9F8) = 130 29981: fstat64(15, 0xFFBFD468) = 0 29981: getsockopt(15, SOL_SOCKET, 0x2000, 0xFFBFD568, 0xFFBFD560, 0) = 0 29981: fstat64(15, 0xFFBFD4D8) = 0 29981: getsockopt(15, SOL_SOCKET, 0x2000, 0xFFBFD5D8, 0xFFBFD5D4, 0) = 0 29981: setsockopt(15, SOL_SOCKET, 0x2000, 0xFFBFD5D8, 4, 0) = 0 29981: fcntl(15, F_SETFL, 0x00000002) = 0 29981: getpeername(15, 0xFFBFD708, 0xFFBFD2E8, 1) = 0 29981: open64("/var/run/name_service_door", O_RDONLY) = 17 29981: fcntl(17, F_SETFD, 0x00000001) = 0 29981: door_info(17, 0xFEEC2668) = 0 29981: close(17) = 0 29981: open("/etc/inet/ipnodes", O_RDONLY) = 17 29981: fstat64(17, 0xFFBFAC98) = 0 29981: fstat64(17, 0xFFBFAB40) = 0 29981: ioctl(17, TCGETA, 0xFFBFAC24) Err#25 ENOTTY 29981: read(17, " #\n # I n t e r n e t".., 8192) = 61 29981: read(17, 0x0008257C, 8192) = 0 29981: llseek(17, 0, SEEK_CUR) = 61 29981: close(17) = 0 29981: open64("/var/run/name_service_door", O_RDONLY) = 17 29981: fcntl(17, F_SETFD, 0x00000001) = 0 29981: door_info(17, 0xFEEC2668) = 0 29981: close(17) = 0 29981: open("/etc/hosts", O_RDONLY) = 17 29981: fstat64(17, 0xFFBFAC18) = 0 29981: fstat64(17, 0xFFBFAAC0) = 0 29981: ioctl(17, TCGETA, 0xFFBFABA4) Err#25 ENOTTY 29981: read(17, " #\n # I n t e r n e t".., 8192) = 107 29981: llseek(17, 0, SEEK_CUR) = 107 29981: close(17) = 0 29981: uname(0xFFBFD110) = 1 29981: time() = 1077620847 29981: write(15, " 01D020101 w188016 1 . 3".., 31) = 31 29981: poll(0xFFBFD1C0, 1, -1) = 1 29981: read(15, " 0\f020101 x07\n", 8) = 8 29981: read(15, "01\004\004\0", 6) = 6 29981: time() = 1077620847 29981: brk(0x00085460) = 0 29981: brk(0x00087460) = 0 29981: brk(0x00087460) = 0 29981: brk(0x00089460) = 0 29981: brk(0x00089460) = 0 29981: brk(0x0008B460) = 0 29981: brk(0x0008B460) = 0 29981: brk(0x0008D460) = 0 29981: time() = 1077620847 29981: getpid() = 29981 [29964] 29981: brk(0x0008D460) = 0 29981: brk(0x00093460) = 0 29981: brk(0x00093460) = 0 29981: brk(0x00097460) = 0 29981: brk(0x00097460) = 0 29981: brk(0x0009B460) = 0 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: open("/dev/urandom", O_RDONLY|O_NONBLOCK|O_NOCTTY) = 17 29981: poll(0xFFBFD3B0, 1, 10) = 1 29981: read(17, "029F\0 XA5B2F0C7 U &1FE6".., 32) = 32 29981: close(17) = 0 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getuid() = 0 [0] 29981: getpid() = 29981 [29964] 29981: time() = 1077620847 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: write(15, "8095010301\0 l\0\0\0 \0".., 151) = 151 29981: read(15, "160301\0 J02\0", 7) = 7 29981: brk(0x0009B460) = 0 29981: brk(0x0009D460) = 0 29981: time() = 1077620847 29981: time() = 1077620847 29981: getpid() = 29981 [29964] 29981: read(15, "\0 F0301 @ ; 0 oBFEE1DE1".., 72) = 72 29981: read(15, "1603010412", 5) = 5 29981: read(15, "\v\0040E\004\v\004\b 082".., 1042) = 1042 29981: brk(0x0009D460) = 0 29981: brk(0x0009F460) = 0 29981: getpid() = 29981 [29964] 29981: read(15, "160301\004", 5) = 5 29981: read(15, "0E\0\0\0", 4) = 4 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: getpid() = 29981 [29964] 29981: brk(0x0009F460) = 0 29981: brk(0x000A1460) = 0 29981: write(15, "160301\08610\0\082\080 /".., 198) = 198 29981: read(15, "140301\001", 5) = 5 29981: read(15, "01", 1) = 1 29981: read(15, "160301\0 0", 5) = 5 29981: read(15, "9197ADECFE9AFB )DF83 $8A".., 48) = 48 29981: time() = 1077620847 29981: write(15, "170301\0 DF0F1E H pC386".., 90) = 90 29981: time() = 1077620847 29981: poll(0xFFBFD230, 1, 30000) = 1 29981: read(15, "170301\0 ", 5) = 5 29981: read(15, "DBFFF9B9EC g WEE iE0 , Z".., 32) = 32 29981: read(15, "170301\0 0", 5) = 5 29981: read(15, "7F >BDCE96B4 = zE587F1 ]".., 48) = 48 29981: time() = 1077620847 29981: setsockopt(15, SOL_SOCKET, SO_KEEPALIVE, 0xFFBFDB88, 4, 1) = 0 29981: fcntl(15, F_SETFD, 0x00000001) = 0 29981: getsockname(15, 0xFEAFE2F8, 0xFFBFDB84, 1) = 0 29981: getpeername(15, 0xFEAFE308, 0xFFBFDB84, 1) = 0 29981: time() = 1077620847 29981: getpid() = 29981 [29964] 29981: getuid() = 0 [0] 29981: time() = 1077620847 29981: write(15, "170301\0 $1D1086B7 { #".., 266) = 266 29981: poll(0xFFBFD1E0, 1, -1) = 1 29981: read(15, "170301\0 ", 5) = 5 29981: read(15, " 3 0 @B7AA14 j9284E2D4\t".., 32) = 32 29981: read(15, "1703010180", 5) = 5 29981: read(15, "92 | e850589C27F <CDB0 a".., 384) = 384 29981: poll(0xFFBFD1E0, 1, -1) = 1 29981: read(15, "170301\0 ", 5) = 5 29981: read(15, "DABDA1 `8DBDD795B117E4D3".., 32) = 32 29981: read(15, "170301\0 0", 5) = 5 29981: read(15, "8AA2B9 y1A MFEC3FCDB J".., 48) = 48 29981: time() = 1077620847 29981: time() = 1077620847 29981: stat("/usr/lib/nss_files.so.1", 0xFFBFE2D4) = 0 29981: open("/etc/shadow", O_RDONLY) = 17 29981: fstat64(17, 0xFFBFE878) = 0 29981: fstat64(17, 0xFFBFE720) = 0 29981: ioctl(17, TCGETA, 0xFFBFE804) Err#25 ENOTTY 29981: read(17, " r o o t : f s i o o X 9".., 8192) = 308 29981: read(17, 0x0008CB34, 8192) = 0 29981: llseek(17, 0, SEEK_CUR) = 308 29981: close(17) = 0 29981: stat("/usr/lib/nss_ldap.so.1", 0xFFBFE2D4) = 0 29981: sigaction(SIGPIPE, 0xFFBFE728, 0xFFBFE868) = 0 29981: sigprocmask(SIG_SETMASK, 0xFEBEA0B4, 0xFFBFE778) = 0 29981: sigprocmask(SIG_SETMASK, 0xFFBFE764, 0x00000000) = 0 29981: getpid() = 29981 [29964] 29981: getuid() = 0 [0] 29981: getpid() = 29981 [29964] 29981: getuid() = 0 [0] 29981: time() = 1077620847 29981: write(15, "170301\0 8D81 R r r89".., 266) = 266 29981: poll(0xFFBFD650, 1, -1) = 1 29981: read(15, "170301\0 ", 5) = 5 29981: read(15, " 61ED503E3C40EC7A3 R\t (".., 32) = 32 29981: read(15, "170301\0F0", 5) = 5 29981: read(15, "D61F k # \F1\v l wFFE3 r".., 240) = 240 29981: poll(0xFFBFD650, 1, -1) = 1 29981: read(15, "170301\0 ", 5) = 5 29981: read(15, " 898 8DB2CD bB9 m8B84C5".., 32) = 32 29981: read(15, "170301\0 0", 5) = 5 29981: read(15, "9F >C5BCA687 X .EEA2 > i".., 48) = 48 29981: time() = 1077620847 29981: time() = 1077620847 29981: Incurred fault #6, FLTBOUNDS %pc = 0xFF053364 29981: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000004 29981: Received signal #11, SIGSEGV [default] 29981: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000004 29964: poll(0x00052E28, 11, 999) = 1 29964: read(15, 0xFFBFF958, 512) = 0 29964: time() = 1077620847 29964: write(4, " d o v e c o t - a u t h".., 61) = 61 29964: write(14, "\0\0\001\0\0\003\0\0\0\0".., 20) = 20 29964: close(15) = 0 29964: poll(0x00052E28, 10, 446) = 0 29964: poll(0x00052E28, 10, 0) = 0 29964: waitid(P_ALL, 0, 0xFFBFF998, WEXITED|WTRAPPED|WNOHANG) = 0 29964: time() = 1077620848 29964: write(4, " d o v e c o t - a u t h".., 74) = 74 29964: waitid(P_ALL, 0, 0xFFBFF998, WEXITED|WTRAPPED|WNOHANG) Err#10 ECHILD 29964: poll(0x00052E28, 10, 998) = 0 29964: poll(0x00052E28, 10, 0) = 0 29964: poll(0x00052E28, 10, 4999) (sleeping...) 29964: poll(0x00052E28, 10, 4999) = 1 29964: read(14, 0x0007C051, 4047) = 0 29964: close(14) = 0 29964: poll(0x00052E28, 9, 2885) (sleeping...) dovecot.conf---------------------------------------------------- ## Dovecot 1.0 configuration file # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var # --with-ssldir=/etc/ssl # Base directory where to store runtime data. base_dir = /usr/local/dovecot/run/ # Protocols we want to be serving: # imap imaps pop3 pop3s protocols = imap pop3 imaps pop3s # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. You can specify ports with # "host:port". imap_listen = * pop3_listen = * # IP or host address where to listen in for SSL connections. Defaults # to above non-SSL equilevants if not specified. #imaps_listen = #pop3s_listen = # Disable SSL/TLS support. ssl_disable = yes # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf #ssl_cert_file = /etc/ssl/certs/dovecot.pem #ssl_key_file = /etc/ssl/private/dovecot.pem # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. ssl_parameters_file = /usr/local/dovecot/run/ssl-parameters.dat # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. ssl_parameters_regenerate = 24 # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability) #disable_plaintext_auth = no # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). log_path = /var/log/dovecot.log # For informational messages, use this logfile instead of the default info_log_path = /var/log/dovecot.info # Prefix for each line written to log file. % codes are in strftime(3) # format. Note the extra space at the end of line. #log_timestamp = "%b %d %H:%M:%S " ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. #login_dir = /usr/local/dovecot/run/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. #login_chroot = yes ## ## IMAP login process ## login = imap # Executable location. #login_executable = /usr/local/dovecot/libexec/dovecot/imap-login # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 16 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. #login_process_per_connection = yes # Number of login processes to create. If login_process_per_user is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # IN AT THE SAME time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_user # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 ## ## POP3 login process ## # Settings default to same as above, so you don't have to set anything # unless you want to override them. login = pop3 # Exception to above rule being the executable location. #login_executable = /usr/libexec/dovecot/pop3-login ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. #first_valid_uid = 500 #last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See doc/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden by # giving /./ in user's home directory (eg. /home/./user chroots into /home). #mail_chroot = # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # doc/mail-storages.txt. There's a few special variables you can use: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if user there's no domain # %h - home directory # # You can also limit a width of string by giving the number of max. characters # after the '%' character. For example %1u gives the first character of # username. Some examples: # # maildir:/var/mail/%1u/%u/Maildir # mbox:~/mail/:INBOX=/var/mail/%u # mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # default_mail_env = maildir:/maildir/%u/Maildir # Space-separated list of fields to cache for all mails. Currently these # fields are allowed followed by a list of commands they speed up: # # Envelope - FETCH ENVELOPE and SEARCH FROM, TO, CC, BCC, SUBJECT, # SENTBEFORE, SENTON, SENTSINCE, HEADER MESSAGE-ID, # HEADER IN-REPLY-TO # Body - FETCH BODY # Bodystructure - FETCH BODY, BODYSTRUCTURE # MessagePart - FETCH BODY[1.2.3] (ie. body parts), RFC822.SIZE, # SEARCH SMALLER, LARGER, also speeds up BODY/BODYSTRUCTURE # generation. This is always set with mbox mailboxes, and # also default with Maildir. # # Different IMAP clients work in different ways, that's why Dovecot by default # only caches MessagePart which speeds up most operations. Whenever client # does something where caching could be used, the field is automatically marked # to be cached later. For example after FETCH BODY the BODY will be cached # for all new messages. Normally you should leave this alone, unless you know # what most of your IMAP clients are. Caching more fields than needed makes # the index files larger and generate useless I/O. # # With maildir there's one extra optimization - if nothing is cached, indexing # the maildir becomes much faster since it's not opening any of the mail files. # This could be useful if your IMAP clients access only new mails. #mail_cache_fields = MessagePart # Space-separated list of fields that Dovecot should never set to be cached. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Workarounds for various client bugs: # oe6-fetch-no-newmail: # Never send EXISTS/RECENT when replying to FETCH command. Outlook Express # seems to think they are FETCH replies and gives user "Message no longer # in server" error. Note that OE6 still breaks even with this workaround # if synchronization is set to "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. #client_workarounds = # Dovecot can notify client of new mail in selected mailbox soon after it's # received. This setting specifies the minimum interval in seconds between # new mail notifications to client - internally they may be checked more or # less often. Setting this to 0 disables the checking. # NOTE: Evolution client breaks with this option when it's trying to APPEND. #mailbox_check_interval = 0 # Like mailbox_check_interval, but used for IDLE command. #mailbox_idle_check_interval = 30 # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. mail_full_filesystem_access = no # Maximum allowed length for custom flag name. It's only forced when trying # to create new flags. #mail_max_flag_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. #mail_read_mmaped = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing message are immutable. #maildir_check_content_changes = no # Which locking methods to use for locking mbox. There's three available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # # You can use both fcntl and flock too; if you do the order they're declared # with is important to avoid deadlocks if other MTAs/MUAs are using both fcntl # and flock. Some operating systems don't allow using both of them # simultaneously, eg. BSDs. If dotlock is used, it's always created first. #mbox_locks = dotlock fcntl # Should we create dotlock file even when we want only a read-lock? Setting # this to yes hurts the performance when the mailbox is accessed simultaneously # by multiple processes, but it's needed for reliable reading if no other # locking methods are available. #mbox_read_dotlock = no # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. Note that setting # this to yes means that log file is opened as the logged in user, which # might not work. It could also be a small security risk if you use single UID # for multiple users, as the users could ptrace() each others processes then. #mail_drop_priv_before_exec = no ## ## IMAP process ## # Executable location #imap_executable = /usr/libexec/dovecot/imap # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #imap_process_size = 256 # Support for dynamically loadable modules. #imap_use_modules = no #imap_modules = /usr/lib/dovecot/imap ## ## POP3 process ## # Executable location #pop3_executable = /usr/libexec/dovecot/pop3 # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #pop3_process_size = 256 # Support for dynamically loadable modules. #pop3_use_modules = no #pop3_modules = /usr/lib/dovecot/pop3 ## ## Authentication processes ## # You can have multiple processes; each time "auth = xx" is seen, a new # process definition is started. The point of multiple processes is to be # able to set stricter permissions to others. For example, plain/PAM # authentication requires roots, but if you also use digest-md5 authentication # for some users, you can authenticate them without any privileges in a # separate auth process. Just remember that only one auth process is asked # for the password, so you can't have different passwords with different # processes (unless they have different auth methods, and you're ok with # having different password for each method). # Authentication process name. auth = default # Space separated list of wanted authentication mechanisms: # plain digest-md5 anonymous auth_mechanisms = plain # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm to use if none was specified. #auth_default_realm = # Where user database is kept: # passwd: /etc/passwd or similiar, using getpwnam() # passwd-file <path>: passwd-like file with specified location # static uid=<uid> gid=<gid> home=<dir template>: static settings # vpopmail: vpopmail library # ldap <config path>: LDAP, see doc/dovecot-ldap.conf # pgsql <config path>: a PostgreSQL database, see doc/dovecot-pgsql.conf #auth_userdb = passwd auth_userdb = ldap /usr/local/dovecot/etc/dovecot-ldap.conf # Where password database is kept: # passwd: /etc/passwd or similiar, using getpwnam() # shadow: /etc/shadow or similiar, using getspnam() # pam [<service> | *]: PAM authentication # passwd-file <path>: passwd-like file with specified location # vpopmail: vpopmail authentication # ldap <config path>: LDAP, see doc/dovecot-ldap.conf # pgsql <config path>: a PostgreSQL database, see doc/dovecot-pgsql.conf auth_passdb = pam imap #auth_passdb = ldap /usr/local/dovecot/etc/dovecot-ldap.conf #auth_executable = /usr/libexec/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. auth_user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. #auth_chroot = # Number of authentication processes to create #auth_count = 1 # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. auth_verbose = yes # digest-md5 authentication process. It requires special MD5 passwords which # /etc/shadow and PAM doesn't support, so we never need roots to handle it. # Note that the passwd-file is opened before chrooting and dropping root # privileges, so it may be 0600-root owned file. #auth = digest_md5 #auth_methods = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = # if you plan to use only passwd-file, you don't need the two auth processes, # simply set "auth_methods = plain digest-md5" -- Benjamin Dabelow benja.dabelow(a)gmx.net Staufenbergstr. 88 benja-dabelow.gmxhome.de/start.html 74081 Heilbronn Germany

3 3

[Dovecot] help: The current command did not succeed. The mail server responded: Invalid mask.
by Bodo Gelbe 25 Feb '04

25 Feb '04

Am tryin to move from uw-imapd to dovecot, using dovecot ver 0.99.10.4. Reading with Mozilla Mail v 1.4. I made some test accounts and they seem to be working fine, but my older existing accounts give error messages whenever I connect or subscribe to mailboxes within them. The message that appears on the client is: "The current command did not succeed. The mail server responded: Invalid mask." it appears two or three times in an alert box (on windows) then everything seems to work. The masks (I've put a syslog call into the code) are: "~%", "~%~%" and "~*". The test accounts I created don't have this problem. Thanks in advance for any advice, -- Bodo Gelbe

2 1

[Dovecot] Dovecot and Mulberry
by Kenneth Porter 25 Feb '04

25 Feb '04

FYI. Does Dovecot implement BODYSTRUCTURE? An eval copy of Mulberry can be downloaded from <http://www.cyrusoft.com/mulberry/>. ------------ Forwarded Message ------------ Date: Tuesday, February 10, 2004 6:56 PM +0100 From: Lennart Petersson <lennart(a)informatik.gu.se> To: mulberry-discuss(a)cyrusoft.com Subject: Dovecot and Mulberry I've recently changed my imap-server from Courier to Dovecot <http://dovecot.procontrol.fi/> for testing purposes and have seen some strange behaviour from Mulberry. Most annoying is that suddenly some incoming mail are parsed wrong, i.e. even if the mail has has proper Content-Type: text/plain; charset="iso-8859-1" and Content-Transfer-Encoding: quoted-printable, it is displayed as 7bit and us-ascii. All these =F6 and so on is irritating. The only way remedy the problem is to quit mulberry and start again and almost always the email is displayed properly. And if the mail that gets misinterpreted is a multi-part email mulberry only reports that it has one part. But if you view the mail in raw all the parts are there. I've yet to see a pattern in then mulberry starts this misinterpretations. Sometimes it is a email from pine or a mail from a mailinglist or from outlook or ... A collegue that also uses dovecot but mutt instead of mulberry doesn't have this problems. Should I blame Dovecot or Mulberry? Anyone one with experience with dovecot (or any other imap-server that supports Maildirs)? Lennart ---------- End Forwarded Message ---------- ------------ Forwarded Message ------------ Date: Tuesday, February 10, 2004 1:12 PM -0500 From: Cyrus Daboo <daboo(a)cyrusoft.com> To: Lennart Petersson <lennart(a)informatik.gu.se>, mulberry-discuss(a)cyrusoft.com Subject: Re: Dovecot and Mulberry Hi Lennart, --On Tuesday, February 10, 2004 6:56 PM +0100 Lennart Petersson <lennart(a)informatik.gu.se> wrote: | A collegue that also uses dovecot but mutt instead of mulberry doesn't | have this problems. Should I blame Dovecot or Mulberry? | | Anyone one with experience with dovecot (or any other imap-server that | supports Maildirs)? If you see problems with proper interpretation of MIME structure and MIME parameters etc, then it is almost certainly a server bug. Mulberry uses the IMAP server's BODYSTRUCTURE response to determine the MIME structure of a message on the server without having to download the entire message and parse it locally - that is one of the major benefits of IMAP. The details you see listed in the mailbox pane (addresses, subject, attachment types) and the parts listed in the message pane's Parts list are all derived from the server response. If the server gets it wrong, then you will see the incorrect data/structure in Mulberry too. To confirm that it really is a server bug, try copying the message to a local Mulberry mailbox and look at it from the local mailbox. It should appear correctly in that case, because Mulberry will do MIME parsing itself for local messages. To fully diagnose this, put the problem messages in their own IMAP mailbox, then turn protocol logging for IMAP on in Mulberry using <http://www.cyrusoft.com/mulberry/faq/logging.html> and open the mailbox to show the list of message. Then turn logging off and send me (or inspect yourself) the log files. NB Clients that do not take advantage of IMAP's benefits by using BODYSTRUCTURE (and other similar features) will not 'expose' the server bug as they never use that data from the server. PS Getting the BODYSTRUCTURE response wrong is the most common server bug that we see - particularly in relatively new servers. -- Cyrus Daboo ---------- End Forwarded Message ----------

2 1

[Dovecot] X-UID
by Paul Adams 25 Feb '04

25 Feb '04

What is the function of the X-UID header in mbox format? Mozilla Thunderbird 0.5 seems to regard it as a simple numbering of the messages; i.e., that the first message in the mbox should have X-UID: 1. Dovecot seems to treat it simply as an ordered unique identifier. Thus, the first message in my actual mbox has X-UID: 3849658. (There are only a few dozen messages in the box.) Running Thunderbird 0.5 against a Dovecot IMAP server with mbox format, Thunderbird displays these UID numbers in the message list, which is fairly useless -- I want a numbered list of my messages starting at 1 (which Pine, for example, is happy to provide). I'm just wondering whether this is Dovecot's fault, Thunderbird's fault, or an ambiguity in the mbox standard. thanks, Paul

2 1

[Dovecot] auth_executable
by Helmut Zeilinger 25 Feb '04

25 Feb '04

Hi, i am new to dovecot and i don't know what i can do with the "auth_executable" setting in the "dovecot.conf" file. Can i invoke an external program for authentification? If yes, is there a description what this program/script has to do? Thanks Helmut

2 1

[Dovecot] [PATCH] POP3: Fix RFC1939 non-compliance in STAT, LIST and UIDL commands
by Nic Bellamy 25 Feb '04

25 Feb '04

Hi all, attached is a patch against 0.99.10.4 that fixes the STAT, LIST and UIDL POP3 command output in the case that they're issued after one or more messages have been deleted. Examples of incorrect behavior (bad spots marked with '***') C: STAT S: +OK 2 806 C: LIST S: +OK 2 messages: S: 1 403 S: 2 403 S: . C: UIDL S: +OK S: 1 1076749908.12 S: 2 1076749908.13 S: . C: DELE 1 S: +OK Marked to be deleted. C: STAT *** S: +OK 2 806 C: LIST *** S: +OK 2 messages: *** S: 1 403 S: 2 403 S: . C: UIDL S: +OK *** S: 1 1076749908.12 S: 2 1076749908.13 S: . What it should have been is: [snip] C: DELE 1 S: +OK Marked to be deleted. C: STAT S: +OK 1 403 C: LIST S: +OK 1 messages: S: 2 403 S: . C: UIDL S: +OK S: 2 1076749908.13 S: . It's unlikely the above issue has been causing much in the way of problems, as it's very rare for mail clients to use any of the faulty commands after they've deleted messages (they tend to do it once at the beginning of the POP3 session and cache the results). Regards, Nic. -- Nic Bellamy <nic(a)bellamy.co.nz> Bellamy Consulting -- Software & Security -- http://www.bellamy.co.nz/ -- Phone: +64-6-377-4957 Fax: +64-6-377-0505 Mobile: +64-21-251-8954 --

2 1

[Dovecot] RE: Question on folders
by Alex S Moore 25 Feb '04

25 Feb '04

I have read and read the dovecot docs on maildir folders and think that this is what I want. However, the MUA programs that I use, SylpheedClaws, Evolution, Mozilla seem to react differently to how I setup the folders. Is there a good FAQ on this subject somewhere? I think that I want to setup a virtual domain and am looking for documents. Alex

4 4

[Dovecot] too large imap.index.data files
by Network Wizards 25 Feb '04

25 Feb '04

Hi, I have noticed that imap.index.data are often too large files (several MiBs). Is there a way to limit their size or to shrink dimension or to assign another directory where those file are stored? thank you will

5 4

Re: [Dovecot] Pam trouble
by Benjamin Dabelow 25 Feb '04

25 Feb '04

Hi Alex, > Are you using Solaris 9 native ldap? What configure options did you use > when building dovecot? I'm using OpenLDAP, but I think it's a pam rather than ldap problem. Dovecot check for the existance of a user alright, but fails when checking the password. My build script is enclosed. Cheers Benjamin Buildscript----------------------------------------------------- #!/bin/bash ## Defaults CC="gcc" CXX="g++" LDPATH="/usr/local/lib:/usr/sfw/lib:/usr/local/lib/gcc-lib/sparc-sun-solaris2.9/3.3" CPPFLAGS="-I/usr/local/include -I/usr/sfw/include" LDFLAGS="-L/usr/local/lib -L/usr/sfw/lib" CFLAGS= #SSL LDPATH="$LDPATH:/usr/local/ssl/lib" CPPFLAGS="$CPPFLAGS -I/usr/local/ssl/include" LDFLAGS="$LDFLAGS -L/usr/local/ssl/lib -lssl -lcrypto" #BerkeleyDB LDPATH="$LDPATH:/usr/local/BerkeleyDB/lib" CPPFLAGS="$CPPFLAGS -I/usr/local/BerkeleyDB/include" LDFLAGS="$LDFLAGS -L/usr/local/BerkeleyDB/lib -ldb" CFLAGS="$CFLAGS -ldb" AUTH_CFLAGS="-I/usr/local/BerkeleyDB/include -L/usr/local/BerkeleyDB/lib -ldb" AUTH_LIBS="-ldb" #GDBM LDPATH="$LDPATH:/usr/local/gdbm/lib" CPPFLAGS="$CPPFLAGS -I/usr/local/gdbm/include" LDFLAGS="$LDFLAGS -L/usr/local/gdbm/lib -lgdbm" #LDAP LDPATH="$LDPATH:/opt/OpenLDAP/lib" CPPFLAGS="$CPPFLAGS -I/opt/OpenLDAP/include" LDFLAGS="$LDFLAGS -L/opt/OpenLDAP/lib -lldap -llber -lresolv" #Finishing LDFLAGS="-R$LDPATH $LDFLAGS" export LDFLAGS CPPFLAGS CFLAGS echo -e "\nLDFLAGS=$LDFLAGS" echo -e "\nCPPFLAGS=$CPPFLAGS" echo -e "\nCFLAGS=$CFLAGS" cd dovecot-0.99.10.4 echo -e "\nPress RETURN to configure or CTRL+C to cancel." read ./configure --prefix=/usr/local/dovecot --with-ldap=/opt/OpenLDAP --with-ssl=openssl --with-storages=maildir echo -e "\nPress RETURN to make or CTRL+C to cancel." read make -- Benjamin Dabelow benja.dabelow(a)gmx.net Staufenbergstr. 88 benja-dabelow.gmxhome.de/start.html 74081 Heilbronn Germany

2 3

[Dovecot] IMAP subfolders
by Manuel Moran Vaquero 25 Feb '04

25 Feb '04

Hi: I am using dovecot since the first day on my server (so I have no other mailbox formats). I can't create any subfolders under any IMAP folders. Is this still an issue of dovecot? In mozilla, the operation is simply ignored. With outlook, you can't even click "Accept" if you select to create a subfolder, rather than a top level folder. I have Fedora Core 1, and didn't touch anything special in the configuration file (just one line which enabled pop3 and imap). I have seen the list archives but the existing thread about the issue seems to say that the problem is solved. (?) Thanks in advance for replies Manuel Moran

5 6

Re: [Dovecot] ":" in filenames
by Timo Sirainen 24 Feb '04

24 Feb '04

On Tue, 2004-02-24 at 05:57, Lars Hansson wrote: > dovecot seems to have an issue with :'s in pathnames: > imap(test.user): Fatal: Failed to create storage with data: /home/ > hosted/example.com/users/test:user > > This causes a bit of a problem with vmailmgr since it, by default, > replaces .'s in maildir path with :'s. > I'm curious as to why :'s in paths are an issue? Do they have special > meaning to dovecot? Hmm.. They do. default_mail_env format is: "storage_format:data" and both mbox and maildir in "data" part treat it as "path:option:option2:..". So, Dovecot above thought "/home/hosted/example.com/users/test" was the storage format and "user" the data part for it. You could change default_mail_env = maildir:~/ but then Dovecot would think "user" as being unknown option.. I'm not sure what to do about this.. ':' was selected because it's PATH separator as well, so people rarely have directories containing ':' in it's name. Maybe it could be escaped as "\:"..

1 0

[Dovecot] ":" in filenames
by Lars Hansson 24 Feb '04

24 Feb '04

dovecot seems to have an issue with :'s in pathnames: imap(test.user): Fatal: Failed to create storage with data: /home/ hosted/example.com/users/test:user This causes a bit of a problem with vmailmgr since it, by default, replaces .'s in maildir path with :'s. I'm curious as to why :'s in paths are an issue? Do they have special meaning to dovecot? --- Lars Hansson

1 0

[Dovecot] dovecot-nightly/NetBSD - Fwd: CVS commit: wip/dovecot-nightly
by tom＠replic8.net 22 Feb '04

22 Feb '04

hello everybody, i just commited a pkgsrc for dovecot nightly cvs-snapshots to the pkgsrc-wip repository for NetBSD - this will hopefully go into base pkgsrc, soon. please see http://pkgsrc-wip.sourceforge.net/ on how to obtain pkgsrc-wip. ----- Forwarded message from Tom Hensel <tomhensel(a)users.sourceforge.net> ----- Date: Sun, 22 Feb 2004 11:18:52 -0800 From: Tom Hensel <tomhensel(a)users.sourceforge.net> Reply-To: pkgsrc-wip-discuss(a)lists.sourceforge.net Subject: CVS commit: wip/dovecot-nightly To: pkgsrc-wip-cvs(a)lists.sourceforge.net Module name: pkgsrc-wip Committed by: tomhensel Date: Sun Feb 22 19:18:52 UTC 2004 Import into wip/dovecot-nightly Log Message: Dovecot is an IMAP and POP3 server for Linux/UNIX-like systems, written with security primarily in mind. Although it's written in C, it uses several coding techniques to avoid most of the common pitfalls. A nightly CVS-snapshot is available at http://dovecot.procontrol.fi/nightly/ which includes major changes from Dovecot 0.99.10.4; please see the ChangeLog file inside the distribution archive. For more information on Dovecot see http://dovecot.procontrol.fi/ Status: Vendor Tag: tomhensel Release Tags: tomhensel_20040222 N wip/dovecot-nightly/PLIST N wip/dovecot-nightly/distinfo N wip/dovecot-nightly/Makefile N wip/dovecot-nightly/DESCR N wip/dovecot-nightly/files/dovecot.sh N wip/dovecot-nightly/patches/patch-aa N wip/dovecot-nightly/patches/patch-ab No conflicts created by this import To generate a diff of this commit: Please note that diffs are not public domain; they are subject to the copyright notices on the relevant files. ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ pkgsrc-wip-cvs mailing list pkgsrc-wip-cvs(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pkgsrc-wip-cvs ----- End forwarded message -----

1 0

[Dovecot] Dovecot -- basic setup
by Tom 19 Feb '04

19 Feb '04

Hey all, After some kind soul made me understand what I can expect from Dovecot, I feel really embarassed for not being able to set it up correctly. What I already had was ~/Mail, containing about six maildirs. Exim got mail, delivered it to procmail, and procmail dropped it in my inbox; a needless extra step that I keep for future, ehm, needs that I might start to care about when I can just succesfully use the most basic mail configuration I can think of. As far as I understood, I just have to point Dovecot to my maildir for it to serve my mail when I connect appropriately with a client. When I test that with KMail connecting to localhost, I get a bizarre overview of my mailfolders, that looks like this: http://www.xs4all.be/~verbreyt/img/scrots/dovecot-kmail.jpg The error message on top is what I get when I try to catch up with any possible new mail: "Unable to get information about folder antwort.index. The server replied: Internal error." Syslog says "lstat(/home/tom/Mail/.antwort.index/cur) failed: Not a directory". Could be, of course: the directory should be ~/Mail/antwort/cur. After I ran KMail and got those errors, ~/Mail, previously only containing some folders, each in turn containing cur/, new/ and tmp/, is stuffed with index files, and three new folders (cur/, new/ and tmp/) directly in the toplevel. ##### $ ls -a Mail . .drafts.index.ids .sent.index.ids .. inbox sent-mail antwort .INBOX .sent-mail.index .antwort.index .inbox.index .sent-mail.index.ids .antwort.index.ids .inbox.index.ids spam check .inbox.index.sorted .spam.index .check.index new .spam.index.ids .check.index.ids outbox tmp cur .outbox.index trash .customflags .outbox.index.ids .trash.index drafts sent .trash.index.ids .drafts.index .sent.index ##### I'm not sure just where it all goes wrong. Yes, I feel stupid about that, but what did, then, did I misunderstand? The only relevant thing in /etc/dovecot.conf I guess would be "default_mail_env" which I have set to "maildir:~/Mail:INBOX=~/Mail/inbox". Documentation may be sparse, it'd still make me sad to be the cause of it being extended for use by the clueless. :-/ Grateful for any corrections, Tom -- "Mongolian drivers do not care much about pedestrians." -- np: Predominance - Luftschiffe (flac)

2 1

[Dovecot] File synchronization friendly indexes
by Aredridel 18 Feb '04

18 Feb '04

I've been doing some tests of file synchronization with Unison (think "two way rsync"), and run into one problem: Synching between servers has conflicts on the index file. I can manually exclude, but what seems to me to be a really wonderful feature would be to, preferably, make the indexes somewhat atomic, so that files, once written, don't change (this is a feature of maildirs in general), and barring that, that they include the machine name as part of the filename, so there's no conflicts. Also, on a completely unrelated and somewhat offtopic note: I'd love to hear some brainstorms on how to prevent duplicate messages when maildirs are synched, files are moved from new on one or more ends, flags are changed inconsistently, and synched back. Ari

2 1

[Dovecot] More Benchmarks, and a question about indexing
by Anthony Wendell Kay 18 Feb '04

18 Feb '04

Hi, We are thinking of converting to Dovecot to lighten our I/O load. I have done some performace tests comparing UW-IMAP to Dovecot when using mbox format if anyone is interested. They primarily examine the I/O improvements that can be gained from using Dovecot over UW when staying with mbox format: http://whizzo.uoregon.edu/public/src/mailperf/results.html I had too much cached for this set of tests, and I am going to re-run some with the recommended cache settings...so stay tuned. Anyway, we are stuck with the mbox format for the forseeable future, and I noticed how hard hitting Dovecot is on initial access to a large mailbox, so we need a way to pre-create some of those indexes. I saw in the docs that such an indexer has been planned, but does anyone have a hack for doing it now? -- Anthony Kay Phone: (541) 346-1719 Student Consultant Key Signature: 7195 40B9 FC4F 6F43 C04A University of Oregon Computing Center B4D9 BAF1 C76E AB6E 33E5 "Don't wish your life away." - Mom's best advice

4 4

[Dovecot] LDAP configuration
by Giacomo Cariello 18 Feb '04

18 Feb '04

Hello, I've just installed dovecot to replace courier-imap and I've found out it didn't support some of the typical LDAP userPassword schemes, so I've written some based on OpenSSL API. Furthermore I noticed that the MD5 one seems broken. If it isn't a requirement to ship its own implementation of a crypto algorithm, I would send in a patch to replace schema checks with those based on libcrypto. I also noticed that if I try connecting to an account that doesn't contain a real maildir (es. maildir:%h/.mail, but .mail doesn't exist), the imap segv's. I suppose it would be cool to ship a maildirmake program and have imap use it whenever necessary, if a flag allows it to do so. Giacomo Cariello, jwk(a)bug.it KeyID: 3072/1024/0x409C9044 Fingerprint: 7984 10FD 0460 4202 BF90 3881 CDE4 D78E 409C 9044 "Put that mic in my hand and let me kick out the jams!" - MC5

2 2

[Dovecot] Basic questions concerning mail...
by Tom 16 Feb '04

16 Feb '04

Hey all, A few minutes ago, I installed Dovecot, hoping things would get clear by just looking at the relevant config files, but since they don't, I hope someone here could give me a clue... What I want to achieve is really only basic functionality. It's just for personal use, so it shouldn't get too complicated. Up til now, I have been using fetchmail to get my mail off of several POP3-accounts, exim to hand it over to procmail and procmail to drop it in the mail directories of my girlfriend and I. I'd like to be able to remotely use a webmail program of some kind to check mail without having to use ssh to login. So I thought an IMAP-server might be the way to go, but, embarassing though it may be, I can't quite grasp how Dovecot (any IMAPd of course, for that matter) fits in the whole. Should Dovecot receive mail from fetchmail and put in it it's proper place in the user's home directories? Or does Dovecot merely read any mail that might belong to users, told where to look by dovecot.conf? Since I now notice my questions are put in a way that is equally embarassing as the questions themselves, I'll keep it short: could anyone enlighten me about the role of Dovecot / an IMAPd it the whole of a mail system (mail directories for each user, fetchmail, procmail, an MTA, a MUA)? Sincerely apologizing for wasting your undoubtedly valuable time, Tom -- "Mongolian drivers do not care much about pedestrians." -- np: Vive La Fête - Assez (flac)

2 3

[Dovecot] your /etc/dovecot.conf
by Pahlevanzadeh Mohsen 14 Feb '04

14 Feb '04

Hi. Please send me your /etc/dovecot.conf what edited. Yours,Mohsen. ===== ---------DIGITAL SIGNATURE------------------- ///Mohsen Pahlevanzadeh//////// Network administrator & programmer My work phone is : +98216054096-7 My home phone is: +98213810146 My emails is m_pahlevanzadeh(a)yahoo.com My website is: http://webnegar.net ---------------------------------------------------------------- __________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html

3 2

[Dovecot] SOS
by Pahlevanzadeh Mohsen 14 Feb '04

14 Feb '04

Hi,When i run "service dovecot start",I receive following line: Starting IMAP daemon (dovecot): Fatal: Can't use SSL key file /usr/share/ssl/private/dovecot.pem: No such file or directory [FAILED] Please guide me until i can make a key file.... Yours,Mohsen. ===== ---------DIGITAL SIGNATURE------------------- ///Mohsen Pahlevanzadeh//////// Network administrator & programmer My work phone is : +98216054096-7 My home phone is: +98213810146 My emails is m_pahlevanzadeh(a)yahoo.com My website is: http://webnegar.net ---------------------------------------------------------------- __________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html

3 2

[Dovecot] Configure dovecot.
by Pahlevanzadeh Mohsen 14 Feb '04

14 Feb '04

Hi. I installed dovecot,via RPM.But i don't know that i how to configure it. Please guide me...... ===== ---------DIGITAL SIGNATURE------------------- ///Mohsen Pahlevanzadeh//////// Network administrator & programmer My work phone is : +98216054096-7 My home phone is: +98213810146 My emails is m_pahlevanzadeh(a)yahoo.com My website is: http://webnegar.net ---------------------------------------------------------------- __________________________________ Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online. http://taxes.yahoo.com/filing.html

2 1

[Dovecot] dovecot..
by Cami 13 Feb '04

13 Feb '04

Hi All.. Has anyone got any experimental patches for mysql auth? Regards, Cami

3 7