- dovecot - dovecot.org

Re: [Dovecot] SSL Certificate Chains?
by Matthew Reimer 29 Oct '03

29 Oct '03

Timo Sirainen wrote: > On Mon, 2003-10-27 at 15:01, Steve Gare wrote: > >>Just a quicky, I can't see anything about how Dovecot handles >>certificate chains. >> >>1, Does it handle them? >>2, How, if if does? >> >>(Just got a cert from www.instantssl.com and I need there intermediate >>cert do validate it.., Works fine with Apache and Exim ) > > > Dovecot doesn't check client's certificate. It's client's job to check > server's certificate and check the chains. Or at least I don't think > there's anything special Dovecot should do with them.. I had trouble with an instantssl cert, and found that what I needed to do was to also include all the certs up the chain, in a certain order, to keep the client from complaining about an invalid certificate. The first certificate in the pem file should be the the server certificate, followed by its chain starting from the root certificate down. Matt

1 0

[Dovecot] Copy from INBOX to INBOX corrupts file
by Andreas Jaekel 29 Oct '03

29 Oct '03

Aloha, again, Timo. Concerning the problem of copying within one folder... I'm still not sure it's not a problem I created myself, but I think it's caused by the use of the buffered IO routines in ostream-file.c ... you use io_add() to schedule write operations for later while simultanously reading new chunks from the very same file. This seems to confuse dovecot and make it write the copy to the strangest locations. I think when working within one folder I should use either blocking IO or a lot of calls to o_stream_flush()... what do you think? Greetings, Andy

2 3

[Dovecot] SSL Certificate Chains?
by Steve Gare 29 Oct '03

29 Oct '03

Hi, Just a quicky, I can't see anything about how Dovecot handles certificate chains. 1, Does it handle them? 2, How, if if does? (Just got a cert from www.instantssl.com and I need there intermediate cert do validate it.., Works fine with Apache and Exim ) Cheers, Steve Gare - Xantara.Net -- 0845 123 5707

2 1

[Dovecot] root privilidge issues?
by lists＠netxp.com.au 24 Oct '03

24 Oct '03

hi all, i am migrating from imap-uw to dovecot on a freebsd machine and i am getting this error message: imap(phil): Oct 22 19:24:01 Fatal: We couldn't drop root group privileges imap-login: Oct 22 19:24:01 Info: Login: phil [220.240.217.2] dovecot: Oct 22 19:24:01 Error: child 1019 (imap) returned error 89 when it trie manually logining in this is what i see telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK dovecot ready. 1 login phil password 1 OK Logged in. Connection closed by foreign host. any ideas? thansk in advance phil

2 1

[Dovecot] Shared Folders
by D Canfield 21 Oct '03

21 Oct '03

I was just wondering if any thought has been given to shared folders and how they might be implemented yet? True shared folders are compelling enough to our organization that I've been looking into moving to Cyrus from Courier, but transparent folder migration looks to be nearly impossible for more than a handful of accounts... so that leaves me back at hoping courier or dovecot can eventually do what we want. We have a lot of organizations on campus that have a generic mail address such as "maintenance" of "physics." We don't like the idea of shared accounts (invariably either the mailbox gets forgotten about when a secretary changes, the password gets lost, or everyone on campus ends up with the password), so our policies require such generic accounts to be forwarded to a folder in a "real person's" account. This works well for us, but the users are clamoring for the ability to have more than one person access those folders. The problem with Courier's shared folders is that one person owns the folder and while others can see that mailbox, only the owner has write access. This kills most of the utility of shared folders, except for use as announcement areas. As I understand it, the reason Courier does it this way is that it uses the underlying unix permissions to control access to the mailbox. I'm thinking that even if dovecot uses the same concept for shared folders, it should be possible to allow multiple users to write to the folders if filesystem ACL support is used. At least ext3 and XFS both support ACL's, so there is a reasonable amount of support for them, and they would allow dovecot to give multiple users write access to the folders without having to manage it's own security system. The only issue would be that the delivery agent would have to make sure that that ACLs for a folder are kept consistent... I'm not even sure dovecot has to be ACL-aware. Anyway, if there is a completely different plan in the works, that's great too, but I wanted to at least voice an opinion and offer a suggestion of how to make it work. Thanks DC

4 5

[Dovecot] A view quirks
by Andreas Jaekel 21 Oct '03

21 Oct '03

Aloha Timo. I found a few odd things while playing with dovecot. At least one of them bugs me, but it might be a result of my own patches - I haven't testet it with mbox or maildir, yet. The details :) 1. * OK dovecot ready. A = (<return> Connection closed by foreign host. 2. * OK dovecot ready. A001 LOGIN xxxxxx xxxxxx A001 OK Logged in. A002 COPY 1 INBOX Connection closed by foreign host. (segfault) 3. [...] A003 SEARCH SUBJECT "test" * SEARCH 1 A003 OK Search completed. A004 SEARCH SUBJECT {6} + OK "test" * SEARCH A004 OK Search completed. I think these two searches should give identical results. 4. (my current nemesis) A002 CREATE bla A003 SELECT INBOX A004 COPY 1 bla A005 SELECT bla A006 COPY 1 bla * NO Internal error [2003-10-16 16:07:21] A006 OK Copy completed. If I copy from the current folder to the current folder I get a scrambled mailbox and an error. This might be selfmade, though. I'm currently trying to find this bug, but the various layers of [_oi]streams and callback and function pointer structs do not help :) I think the stream routines hide the mstream(istream(realstream(iostream))) and the ostream(_ostream(iostream)) behind the same file descriptor and the data gets written to the wrong position. BTW: what exactly is "max_pos"? Greetings and thanks! Andy

2 6

[Dovecot] move from imap-uw
by Sergey Matveychuk 18 Oct '03

18 Oct '03

Hello! I've just subscribed and I'd like to ask. Is there any troubles if I change my imap-uw with davecot? Will davecot pick up imap-uw created folders (mboxes)? I use all protocols: imap, imaps, pop and pops. I've seen some problems with mbox was mention on this maillist. What kind of problem? -- Sem.

2 1

[Dovecot] Re: Darwin Build (cvs)
by Jesse Peterson 16 Oct '03

16 Oct '03

On Thursday, October 9, 2003, at 02:00 AM, dovecot-request(a)procontrol.fi wrote: > From: Timo Sirainen <tss(a)iki.fi> > Subject: Re: [Dovecot] Darwin Build (cvs) > To: dovecot(a)procontrol.fi > Message-ID: <1065657988.1377.43.camel@hurina> > Content-Type: text/plain > > On Wed, 2003-10-08 at 17:23, Jesse Peterson wrote: >> Here's the deal: OpenDarwin 6.6 (closest relative being Mac OS X >> 10.2.6) won't build from CVS. Specifically libtoolize doesn't seem to >> exist (does it even come with libtool?) and the other parts of the >> "autogen.sh" fail miserably. > > So, the solution is to get libtoolize :) Mine seems to have come from > libtool14 package in Fink (although it is libtool v1.5, weird). Thought so. I wasn't sure if it came with libtool or not (OpenDarwin does ship with libtool). > > Also it looks like you're missing iconv.m4. It's in gettext package in > Fink. Ahh, I'll grab that as well. > > Did OpenDarwin use Fink? > Yes, although they've switched from 'DarwinPorts' to MetaPkg. Not sure the status on either of those, though. > Anyway, building from CVS requires some more packages to install which > aren't needed if you stick with tarballs. I could also build a new test > tarball if you need :) > This would be great. Maybe an automatically posted daily snapshot? Thanks Timo.

2 1

[Dovecot] problem getting mail from mbox
by Gavin Estey 16 Oct '03

16 Oct '03

I'm trying to set up dovecot and I'm running into a few problems. I just want to use IMAP for one user, everyone else gets POP3 from the existing (working server). $MAIL is set to /var/spool/mail/gavin_imap In my /var/spool/mail directory I now have a problem: -rw------- 1 gavin_im mail 1392 Oct 14 22:28 gavin_imap -rw------- 1 gavin_im popusers 0 Oct 14 21:54 gavin_imap When I try to get my mail, I guess it's checking the wrong file as I can't download anything. I also can't delete the file (which I find confusing as I am root): [root@chicken mail]# rm gavin_imap rm: cannot remove `gavin_imap': No such file or directory I actually have the same problem with the dovecot log file. I have this in my config: info_log_path = /tmp/dovecot -rw------- 1 root root 4436 Oct 14 22:40 dovecot [root@chicken tmp]# cat dovecot cat: dovecot: No such file or directory I don't get any obvious errors if I telnet in: [root@chicken tmp]# telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK dovecot ready. 1 LOGIN gavin_imap <pass> 1 OK Logged in. 1 SELECT Inbox * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 0 EXISTS * 0 RECENT * OK [UIDVALIDITY 1066184985] UIDs valid * OK [UIDNEXT 1] Predicted next UID 1 OK [READ-WRITE] Select completed. 1 LOGOUT * BYE Logging out 1 OK Logout completed. Connection closed by foreign host. This is confusing the hell out of me. Is there anything obvious that I've screwed up? Thanks! Gavin.

2 3

[Dovecot] exchange, dovecot, mutt, evolution
by Krammer Clemens 16 Oct '03

16 Oct '03

Dear all, When I "migrate" my outlook folders to imapd (dovecot) it works well from a Windoze perspective, but if I open a migrated folder via imap (mutt, evolution) a cannot see the Senders. If i open the folder locally via mutt, the Senders are displayed correctly. By examining one folder with vi I recognised that there are no valid From headers but Return-Paths. Is there a common way to see the senders when connecting with imap? Best Regards, Clemens

2 1

[Dovecot] Ordering mailboxes
by Ian Marlier 16 Oct '03

16 Oct '03

I have a really weird problem. To whit: I compiled dovecot 0.99.10 on two different systems: a linux-ppc box running Debian, and a Mac OS X Server v. 10.2.8. It compiled fine on both. The same Maildir's are being served up on both -- the OS X server exports home directories to the clients via NFS. BUT the OS X box orders mailboxes this way: INBOX Deleted Items Sent Items . . . And the Debian box orders mailboxes this way: INBOX INBOX/Deleted Items INBOX/Sent Items . . . The compilation options were the same in both cases. The dovecot.conf files are essentially identical -- the only changes are the names of the SSL certificates and the name of the dovecot user. What I can't figure out is, why is the ordering of the mailboxes different? This is the Maildir directory list: [network:/Users/foc/Maildir] root# ls -al /Network/Servers/network.uphamscornercs.net/Users/marlier/Maildir/ total 816 drwxrw---- 22 marlier staff 748 Oct 13 19:52 . drwxr-xr-x 64 marlier staff 2176 Oct 10 14:08 .. drwxrw---- 13 marlier staff 442 Oct 13 19:14 .Deleted Items drwxrwxr-x 9 marlier staff 306 Oct 13 19:14 .Dovecot drwxrw---- 12 marlier staff 408 Oct 8 12:26 .Drafts drwxrw---- 7 marlier staff 238 Oct 13 19:28 .INBOX drwxrw---- 13 marlier staff 442 Sep 16 22:59 .Jen drwxrw---- 13 marlier staff 442 Oct 13 18:30 .Klimas List drwxrw---- 13 marlier staff 442 Oct 13 17:57 .Rachel drwxrw---- 13 marlier staff 442 Oct 13 19:14 .Sent Items drwxrw---- 13 marlier staff 442 Oct 13 19:16 .UCCS -rw-rw---- 1 marlier staff 5 Sep 15 20:58 .customflags -rw-rw---- 1 marlier staff 120 Oct 13 18:16 .subscriptions -rw------- 1 marlier staff 296206 Oct 13 19:40 bincimap-cache -rw------- 1 marlier staff 534 Sep 22 17:45 bincimap-subscribed -rw------- 1 marlier staff 197 Sep 16 21:38 bincimap-subscribed.old -rw------- 1 marlier staff 59 Oct 13 19:40 bincimap-uidvalidity drwx------ 3582 marlier staff 121788 Oct 13 19:36 cur -rw------- 1 marlier staff 96421 Oct 13 19:36 dovecot-uidlist drwx------ 2 marlier staff 68 Oct 13 19:36 new drwxrw--w- 2 marlier staff 68 Sep 15 20:58 recov drwx------ 2 marlier staff 68 Oct 13 19:36 tmp [network:/Users/foc/Maildir] root# Any thoughts? (dovecot.conf files is included here, if it's helpful): [network:/Users/foc/Maildir] root# more /usr/local/etc/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 = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s protocols = imap imaps pop3 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 = no # 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/imapd.pem ssl_key_file = /etc/ssl/private/imapd.pem # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. ssl_parameters_file = /var/run/dovecot/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 = 0 # 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/mail.log # For informational messages, use this logfile instead of the default info_log_path = /var/log/mail.log # 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 dovecot: ## ## 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 = /var/run/dovecot/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/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 = 32 # 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 = 5 # 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/local/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 = yes # Show protocol level SSL errors. verbose_ssl = yes # 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 = 30 #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 = /var/mail # 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 # 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 Envelope Bodystructure Body # 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 = 30 # 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 = yes # 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 = 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/local/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/local/lib/dovecot/imap ## ## POP3 process ## # Executable location pop3_executable = /usr/local/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/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 dovecot # auth_passdb = ldap /usr/local/etc/dovecot-ldap.conf # Executable location auth_executable = /usr/local/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 = 2 # 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"

2 1

[Dovecot] Ignore purge and delete command
by vikrant＠linmark.com 16 Oct '03

16 Oct '03

Hi, Does anyone know how to ignore the purge or delete command from the imap clients. Actually I created a mail archive and using dovecot and so far I am happy with the performance. But the problem I am facing right now is I do not want the users to delete the mail by themselves and want to disable the purge or delete command. Thanks Vikrant

2 1

[Dovecot] dovecot crashes on start
by Timothy 16 Oct '03

16 Oct '03

Hello, I wasn't able to find anything about this on the site that could give me a definite answer, but when I start dovecot it dies immediately. The following is left in the logs. dovecot: Oct 06 20:59:30 Info: Dovecot starting up dovecot: Oct 06 20:59:32 Error: Auth process died too early - shutting down pop3-login: Oct 06 20:59:32 Fatal: fd_send(-1) failed: Broken pipe I thought this might have something to do with chrooting so I tried to disable all of that in the configuration. After that did not work I rebuilt dovecot with minimal configure options (compared to what I used originally) and used a stock configuration changing only the certificate locations so that dovecot would not complain about the certificates missing, still no luck and the same error. I've tried using strace on dovecot but it seems like it hardly ever hangs/dies at the same point. I'm trying to run this on a slackware 9.0 linux based machine. Any suggestions? Timothy, -- I put instant coffee in a microwave and almost went back in time. -- Steven Wright

2 3

[Dovecot] Dovecot pop3 and Outlook Express timeout
by Warren Togami 16 Oct '03

16 Oct '03

> Vince did some troubleshooting at my Dad's place and found that part of > the problem was related to dovecot timing out in communicating with > outlook express. Any ideas? You can do a raw pop3 connection which works > fine, but if you try to do the same from within outlook it times out or > gives "server not found". This sounds like what I was experiencing here > with my outlook express as well. > > thanks, > scott > Any idea what could be happening here? They insist that Outlook Express constant times out when trying to download POP3 from the latest stable dovecot. Thanks, Warren Togami warren(a)togami.com

2 1

[Dovecot] Tips to build from CVS?
by david＠madole.net 13 Oct '03

13 Oct '03

I am struggling to compile Dovecot from CVS. I don't seem to be able to get a good configure script, always ending up with an error during configure. # sh autogen.sh configure.in:13: warning: AC_ARG_PROGRAM invoked multiple times # ./configure checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes [...] checking build system type... i386-unknown-freebsd4.8 checking host system type... i386-unknown-freebsd4.8 [...] checking whether va_lists can be copied by value... yes checking for gnutls_global_init in -lgnutls... no ./configure.lineno: 25085: Syntax error: word unexpected (expecting ")") Looking at the script: cat >>confdefs.h <<\_ACEOF #define HAVE_GNUTLS _ACEOF SSL_LIBS="-lgnutls -lgcrypt" have_ssl="yes (GNUTLS)" have_gnutls=yes fi done <-- line 25085 fi fi if test "$want_openssl" = "yes" && test "$have_ssl" = "no"; then if pkg-config --exists openssl; then I have the following installed: autoconf-2.57 automake-1.7.7 libtool-1.5 I've alto tried: autoconf-2.13 automake-1.5 With similar results except a different line number and more warnings from autogen.sh Any ideas? David

1 0

[Dovecot] gzipped files in Mail directory
by Olivier Tharan 09 Oct '03

09 Oct '03

Hi, I have been testing dovecot on my own machine before a bigger deployment. Basically I have all my mbox mailboxes in ~/Mail, delivered by procmail. Some mbox's are gzipped because they are archives which I can grep into, but do not want to look at often. When I first launched an IMAP client, dovecot created the indexes (I think) and gave several errors when finding a gzipped file, such as: ,---- | Oct 1 19:53:21 mafate imap(olive): File isn't in mbox format: /home/olive/Mail//Archives/daily.d/mafate.2003.gz `---- After 19 gzipped mbox's, I had the following crash: ,---- | Oct 1 19:53:21 mafate dovecot: child 4923 (imap) killed with signal 10 `---- Does dovecot not like gzipped mbox's? For the moment, all gzipped files are in ~/Mail/.Archives and I can live with it. -- olive

1 0

[Dovecot] Line length limitation in dovecot leads to out-of-control process?
by Amelia A. Lewis 09 Oct '03

09 Oct '03

Heylas! I've been copying mailboxes from one dovecot server (on an alpha running debian testing, 0.99.10-9) to another (on an i686 running debian unstable, 0.99.10-9). I encountered a weird problem, which I seem to have resolved by moving a message with a To: line from hell out of the mailbox. Both machines are running maildir. They're not exactly identical, but they're fairly similar, apart from differences in distribution and architecture; they're running the same version of dovecot, supposedly. Specifically, when I copied this folder over to the new location, dovecot went into CPU-feeding frenzy (up to 99.7% of CPU), and stayed there. If I killed the client and tried to look at the same mailbox using a different client (mutt instead of sylpheed), without killing the imap processor on the server, the indexes would be locked, mutt would fall back to reading headers instead, and then would send its imap process into CPU-feeding frenzy when it got to one particular message. After some experimentation, I found the message. Once I moved it out of cur, I could access the mailbox without problems. The odd thing is that I can look at the message on the original machine, but on the machine it was copied to, its mere existence makes the mailbox inaccessible. After a little more exploration (grep ^To name-of-message | wc, on both machines) I seem to have found the issue: the original message has a To: line that is 16504 characters long. In the copy, it's 8192 characters long, and ends in the middle of a <email@address> (line in copy ends: user name <emai, chopped right there). I suspect that it is the *latter* that's causing dovecot to die a messy death. Or, actually, to turn into a very *rude* process that *doesn't* die. It's a really stupid trick to stuff that much into a header line (it's from helixcode in 2000, btw, notifying people that the promised CD is late), and perfectly reasonable to truncate (even to truncate to 1000 characters, per 282[12]). However, I kinda thing dovecot shouldn't choke on the results of truncation, which is what I think is the problem. Amy! -- Amelia A. Lewis amyzing {at} talsever.com I have spent nights with matches and knives, leaning over ledges, only two flights up. Cutting my heart, burning my soul. Nothing left to hold. Nothing left, but blood and fire. -- Indigo Girls

2 2

[Dovecot] Darwin Build (cvs)
by Jesse Peterson 09 Oct '03

09 Oct '03

Oops, I apologize for my short, breif message that didn't even include what I said it should inlcude =). Here's the deal: OpenDarwin 6.6 (closest relative being Mac OS X 10.2.6) won't build from CVS. Specifically libtoolize doesn't seem to exist (does it even come with libtool?) and the other parts of the "autogen.sh" fail miserably. This time (really) attached is a gzip of the log of autogen.sh: "./autogen.sh >& autogen.log". Thanks for any help! - Jesse

2 1

[Dovecot]
by Jesse Peterson 08 Oct '03

08 Oct '03

% uname -a Darwin xxx 6.6 Darwin Kernel Version 6.6: Sun Jul 6 05:12:51 PDT 2003; root:tmp/xnu-6.6.2-4-root.obj/RELEASE_PPC Power Macintosh powerpc Attached is a gzipped "sh autogen.sh >& autogen.log" for the above machine. What do you think? Jesse Peterson <jesse(a)mactechs.com> Office 206.441.7443 / Fax 206.441.8078 MacTechs / Macintosh System and Network Support 2121 First Avenue, Suite 103 / Seattle, Washington 98121 http://www.mactechs.com/

1 0

[Dovecot] those assertions
by dovecot＠spam.turbolink.net 06 Oct '03

06 Oct '03

Timo, Just FYI while you're working on the mbox code, I discovered a bug that occasionally causes dovecot to insert a single blank line at the beginning of the mbox, I'm not sure when/how/why. A single blank line seems to really confuse dovecot, and causes the server to crash when somebody connects to an afflicted mbox. ("Error indexing mbox" in the log, and disconects the user right away). I fixed it with lots of ugly code at our site (basically just remember that we skipped an intial blank line when doing other operations, instead of skipping it then forgetting later). I suspect there's a more elegant way to do it. - Mike

1 0

[Dovecot] SSL Client Certificate Support
by Bert Koelewijn 06 Oct '03

06 Oct '03

Dear Timo, most modern enterprises make use of a Public Key Infrastructure. It would be nice to have dovecot check a client certificate instead of a password. This makes life much easier and more secure. Mail clients like Mozilla and MS Outlook do support this. What do you think of the following feature request: - Client authenticates with a certificate via SSL. (Like stunnel can) - Dovecot looks the username up in a table with (public key, username) - The mailclient gives a name and password, but dovecot ignores them - Dovecot gives the client access by the username found in the table This way existing mail clients can use this system and you can save your username with an empty password. Best Regards, Bert Koelewijn

5 10

[Dovecot] those assertions
by Bernard Blackham 05 Oct '03

05 Oct '03

Hi, I did a bit of digging into the assertions from mbox-rewrite.c (hdr_parsed_size.physical_size == hdr_size). Every time it happens, hdr_size is 0, while hdr_parsed_size.physical_size is non-zero (presumably the correct value). Does this help track it down? I can't manage to get hold of an mbox that causes this though. Another infrequent assertion that's popped up: file message-address.c: line 262 (message_address_write): assertion failed: (addr->domain != NULL) And one that's only ever been spotted once in the last few weeks: file imap-bodystructure.c: line 278 (part_parse_headers): assertion failed: (part->physical_pos >= input->v_offset - start_offset) I'm waiting for them to happen again to provide some more info... Regards, Bernard. -- Bernard Blackham bernard at blackham dot com dot au

2 1

[Dovecot] another Dovecot problem
by Tim Miller 05 Oct '03

05 Oct '03

Hi All-- First, thanks to Timo for solving my last issue. I got dovecot up and running on one of my machines, and it does exactly what I want. Now I'm trying to install dovecot on an older box (glibc 2.0.7 Linux kernel 2.0.36), and encountering some problems: -- firstly autoconf/automake does not seem to correctly deal with the madvise function on this system. It detects that we don't have madvise, yet it's prototyped in /usr/include/sys/mman.h. This causes the compilation to fail when dovecot tries to redefine this function. -- I attempted to solve this problem by renaming the function dovecot prototypes to dc_madvise and then changed all the calls in the code (and the implementation) from madvise to dc_madvise. This allows the code to compile correctly. -- However, once the server is installed, it does not appear to work correctly. I can login, but when I try to list my folders or select any folder (one that exists or one that doesn't exist) the connection times out and the following entry is written to the log file: dovecot: Oct 03 05:38:56 Error: login: received another "not listening" notification (if you can't login at all, see src/lib/fdpass.c) I tracked this message down in the source, but didn't see any obvious way to trace back the problem. Does anyone have experience building on this older configuration (the glibc is a Red Hat version, if it makes any difference)? Any ideas on what might be causing this issue? Best, Tim Miller

2 5

mbox/maildir/directories [was: Re: [Dovecot] still getting weird .{inbox} folder creations with latest -test7]
by Miquel van Smoorenburg 05 Oct '03

05 Oct '03

This is a bit of a late reply, but still: On Thu, 2003-09-04 at 15:06, Timo Sirainen wrote: > CVS has been optimized to assume all files beginning with a dot (except > .subscriptions currently) are mailboxes. This is faster since it doesn't > have to stat() each file to figure out if it's a directory or not. > Perhaps that should be optional. New Linux systems (maybe others too) > wouldn't actually even need the stat().. > > I'll probably some day also add support for dotless directory-structured > mailbox locations, but it's not really high priority. Well, on our systems the mailbox is in /var/mail in maildir format, and in ~/Mail users have split up their folders in subdirs, in mixed maildir and mbox formats. So if dovecot could support both dotless directory-structured mailbox locations and maildir/mbox mix-n-match in the same tree, that would be excellent for us. Mbox is a better format for archiving. Now if Dovecot could also access (read-only ofcourse) compressed mbox archives ... Food for thought. Just put it on the wishlist ;) Mike.

2 1

[Dovecot] Patches
by Jaldhar H. Vyas 05 Oct '03

05 Oct '03

As the freeze for Debian sarge slowly approaches I want to make sure the Dovecot packages are in as good condition as possible. I see there have been a number of patches since 0.99.10. I have added the following patches: * segfault when user home directory is empty * Proper PAM service name * Make suid work on 2.6 kernels Any other patches thatI ought to add. Or better yet, will there be a 0.99.11 soon? -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

5 4

[Dovecot] Why does dovecot confuse mutt?
by Amelia A Lewis 04 Oct '03

04 Oct '03

Heylas, I just switched my primary mail server from courier imap to dovecot (I've been waiting to do this; dovecot showed up in debian testing for alpha, at last). So, using the same set of maildirs, there are slightly different behaviors. First, of course, dovecot displays the hierarchy as I thought it ought to be, such that INBOX is a sibling of all other top-level boxes, not the parent of everything. This is A Good Thing[tm]. That works as expected. However, as far as mutt is concerned, *every* mailbox has child folders. My muttrc contains the line: set folder=imap://localhost/. (and the home folder is set to imap://localhost/INBOX; the idea is to do all mail munging through the server, never directly touching the maildirs with an MUA). Oh, and I'm using maildir (~/Maildir). In mutt, from the currently-selected mailbox, one can use 'c' to change boxes, and ? displays a navigable folder hierarchy. If a folder contains only mail (no child folders), it shows up as "FolderName", if it has child folders (whether or not it has mail), it shows up as "FolderName.". You can display the mail in a folder that has child folders, but it requires a different keystroke than the default (enter selects a folder, which means showing child folders if there are any, showing mail if there aren't; to display mail in a folder that has child folders, space). This is tripping me up a little, because of course the commands are mostly bred into my fingertips, and it's a difficult adjustment. I hit return, and I see a folder that contains the "child" folder "../". Is this a glitch in mutt's handling of information that I ought to report to mutt maintainers? Is it a glitch in dovecot's presentation of information that I ought to report to ... err, well. *laugh* My other primary mail client seems to cope beautifully with the information that's supplied (sylpheed, if it matters). But then, sylpheed also coped perfectly when courier was supplying information. I gather that courier and dovecot are reporting something slightly different, somehow, but I don't really know what, and I don't know which should be considered "correct". Amy!

5 5

[Dovecot] mailbox sorting issue
by Paul 04 Oct '03

04 Oct '03

Thanks for the "junk at end" help. Now I'm having one more perplexing issue: When I sort a Dovecot mbox in Pine, the most recent messages tend to linger near the bottom of the message list, regardless of how they're sorted. Here's a snippet of the bottom of the list, sorted by arrival time: 448 2003-09-24 20:31 sprightly@e... Re: *hoopoe 449 2003-09-24 21:05 mlescaut@w... Re: yes! 450 2003-09-24 23:57 jackulysses@y... Re: oh my lord 451 2003-09-25 01:43 sprightly@e... attachments==take a look 452 2003-09-25 01:29 avantguild@m... Your Membership is Almost Up 453 2003-09-25 10:40 heidi@p... xhtml 454 2003-09-25 11:04 dembo@s. Re: bridge 455 2003-09-25 11:54 JKesner@m... Bombay 456 2003-09-25 12:05 cm2144@c... Re: bridge at linda's And here is a snippet of the same mbox list, sorted by From address: 449 2003-09-25 01:43 sprightly@e... attachments==take a look 450 2003-09-10 16:06 staff@c... Tribute in Light Shines 451 2003-09-08 18:44 starpiekat@y... Re: Sorry! 452 2003-09-23 22:01 starry@p... but... 453 2003-09-25 12:05 cm2144@c... Re: bridge at linda's 454 2003-09-17 17:07 wahrman@s... RE: bridge etc. 455 2003-09-19 13:11 wahrman@s... RE: bridge etc. 456 2003-09-15 23:39 waycross@u... waycross - the eagle Notice that message from cm2144 in both lists, way out of order in the second! I'm not 100% sure that this is a Dovecot issue, but I suspect it is, since this doesn't happen if I open the same mailbox locally or with UW-IMAP. I know that Pine makes use of IMAP server-based sorting if it is available. I tried deleting .imap-index* files, just in case, but that didn't help. thanks, Paul

3 2

Re: [Dovecot] PATCH: mysql authentication
by Matthew Reimer 03 Oct '03

03 Oct '03

> On Fri, 2003-10-03 at 19:54, Matthew Reimer wrote: > >Here's another patch. This one isn't much different from the last patch, >except it tries a little harder to make sure that the required fields >are returned by the query (like the pgsql module does). BTW, the patch lacks configure magic to detect mysql includes and libs, and to define USERDB_MYSQL and PASSDB_MYSQL in config.h. Matt

1 0

Re: [Dovecot] PATCH: mysql authentication
by Matthew Reimer 03 Oct '03

03 Oct '03

Timo Sirainen wrote: > On Fri, 2003-10-03 at 19:54, Matthew Reimer wrote: >>One question about how t_strdup works. How and who should memory >>returned by t_strdup be freed? My patch has a function my_get_str() >>which returns the value of t_strdup, and then I do this: >> >> user.uid = atoi(my_get_str(res, row, "uid")); /* XXX leak */ >> user.gid = atoi(my_get_str(res, row, "gid")); /* XXX leak */ >> >>Will this result in a memory leak? > > > No. > > Memory allocated by t_*() functions are freed "later". There's first > t_push(), then you allocate memory, then t_pop() frees it all. So they > never leak memory, but they could allocate more memory than necessary if > called inside loop. That can be fixed by adding t_push/t_pop calls > there. Nice! Thanks for the answer Timo. Matt

1 0

Re: [Dovecot] PATCH: mysql authentication
by Matthew Reimer 03 Oct '03

03 Oct '03

Here's another patch. This one isn't much different from the last patch, except it tries a little harder to make sure that the required fields are returned by the query (like the pgsql module does). One question about how t_strdup works. How and who should memory returned by t_strdup be freed? My patch has a function my_get_str() which returns the value of t_strdup, and then I do this: user.uid = atoi(my_get_str(res, row, "uid")); /* XXX leak */ user.gid = atoi(my_get_str(res, row, "gid")); /* XXX leak */ Will this result in a memory leak? Matt diff -u -r --new-file work/dovecot-0.99.10/doc/dovecot-mysql.conf work.patched/dovecot-0.99.10/doc/dovecot-mysql.conf --- work/dovecot-0.99.10/doc/dovecot-mysql.conf Wed Dec 31 16:00:00 1969 +++ work.patched/dovecot-0.99.10/doc/dovecot-mysql.conf Tue Sep 30 12:24:00 2003 @@ -0,0 +1,70 @@ +# For the mysql passdb module, you'll need a database with a table that +# contains fields for at least the userid and password. If you want to +# use the user@domain syntax, you might want to have a separate domain +# field as well. +# +# If your users all have the same uig/gid, and have predictable home +# directories, you can use the static userdb module to generate the home +# dir based on the userid and domain. In this case, you won't need fields +# for home, uid, or gid in the database. +# +# If you prefer to use the mysql userdb module, you'll want to add fields +# for home, uid, and gid. Here is an example table: +# +# CREATE TABLE users ( +# userid VARCHAR(128) NOT NULL, +# password VARCHAR(64) NOT NULL, +# home VARCHAR(256) NOT NULL, +# uid INTEGER NOT NULL, +# gid INTEGER NOT NULL, +# active CHAR(1) DEFAULT 'Y' NOT NULL +# ); + +db_host = localhost +db_port = 3306 +#db_unix_socket = /var/tmp/mysql.sock +db = users +db_user = dovecot-db +db_passwd = opensesame +db_client_flags = 0 + +# Default password scheme. +# +# Currently supported schemes include PLAIN, PLAIN-MD5, DIGEST-MD5, and CRYPT. +# +#default_pass_scheme = PLAIN-MD5 + +# Query to retrieve the password. +# +# The query should return one row, one column. If more than one row or column +# is returned, authentication will automatically fail. +# +# Available substitutions: +# %u = entire userid +# %n = user part of user@domain +# %d = domain part of user@domain +# +# Example: +# password_query = SELECT password FROM users WHERE userid = '%n' AND domain = '%d' +# password_query = SELECT password FROM users WHERE userid = '%u' AND active = 'Y' +# +#password_query = SELECT password FROM users WHERE userid = '%u' + +# Query to retrieve the user information. +# +# The query must return only one row. The columns to return are: +# home - Home directory +# mail - MAIL environment +# system_user - System user name (for initgroups()) +# uid - System UID +# gid - System GID +# +# Either home or mail is required. uid and gid are required. If more than one +# row is returned or there's missing fields, login will automatically fail. +# +# Examples +# user_query = SELECT home, uid, gid FROM users WHERE userid = '%n' AND domain = '%d' +# user_query = SELECT dir AS home, user AS uid, group AS gid FROM users where userid = '%u' +# user_query = SELECT home, 501 AS uid, 501 AS gid FROM users WHERE userid = '%u' +# +#user_query = SELECT home, uid, gid FROM users WHERE userid = '%u' diff -u -r --new-file work/dovecot-0.99.10/src/auth/Makefile.in work.patched/dovecot-0.99.10/src/auth/Makefile.in --- work/dovecot-0.99.10/src/auth/Makefile.in Thu Jun 26 09:15:11 2003 +++ work.patched/dovecot-0.99.10/src/auth/Makefile.in Tue Sep 30 12:24:00 2003 @@ -99,10 +99,10 @@ dovecot_auth_LDADD = ../lib-settings/libsettings.a ../lib/liblib.a $(AUTH_LIBS) $(RAND_LIBS) $(MODULE_LIBS) -dovecot_auth_SOURCES = auth-module.c db-ldap.c db-pgsql.c db-passwd-file.c login-connection.c main.c master-connection.c md5crypt.c mech.c mech-anonymous.c mech-cyrus-sasl2.c mech-plain.c mech-digest-md5.c mycrypt.c passdb.c passdb-ldap.c passdb-passwd.c passdb-passwd-file.c passdb-pam.c passdb-shadow.c passdb-vpopmail.c passdb-pgsql.c password-scheme.c userdb.c userdb-ldap.c userdb-passwd.c userdb-passwd-file.c userdb-static.c userdb-vpopmail.c userdb-pgsql.c +dovecot_auth_SOURCES = auth-module.c db-ldap.c db-pgsql.c db-mysql.c db-passwd-file.c login-connection.c main.c master-connection.c md5crypt.c mech.c mech-anonymous.c mech-cyrus-sasl2.c mech-plain.c mech-digest-md5.c mycrypt.c passdb.c passdb-ldap.c passdb-passwd.c passdb-passwd-file.c passdb-pam.c passdb-shadow.c passdb-vpopmail.c passdb-pgsql.c passdb-mysql.c password-scheme.c userdb.c userdb-ldap.c userdb-passwd.c userdb-passwd-file.c userdb-static.c userdb-vpopmail.c userdb-pgsql.c userdb-mysql.c -noinst_HEADERS = auth-login-interface.h auth-master-interface.h auth-mech-desc.h auth-module.h db-ldap.h db-pgsql.h db-passwd-file.h common.h login-connection.h master-connection.h md5crypt.h mech.h mycrypt.h passdb.h password-scheme.h userdb.h userdb-vpopmail.h +noinst_HEADERS = auth-login-interface.h auth-master-interface.h auth-mech-desc.h auth-module.h db-ldap.h db-pgsql.h db-mysql.h db-passwd-file.h common.h login-connection.h master-connection.h md5crypt.h mech.h mycrypt.h passdb.h password-scheme.h userdb.h userdb-vpopmail.h mkinstalldirs = $(SHELL) $(top_srcdir)/mkinstalldirs CONFIG_HEADER = ../../config.h @@ -116,17 +116,17 @@ LDFLAGS = @LDFLAGS@ LIBS = @LIBS@ dovecot_auth_OBJECTS = auth-module.$(OBJEXT) db-ldap.$(OBJEXT) \ -db-pgsql.$(OBJEXT) db-passwd-file.$(OBJEXT) login-connection.$(OBJEXT) \ +db-pgsql.$(OBJEXT) db-mysql.$(OBJEXT) db-passwd-file.$(OBJEXT) login-connection.$(OBJEXT) \ main.$(OBJEXT) master-connection.$(OBJEXT) md5crypt.$(OBJEXT) \ mech.$(OBJEXT) mech-anonymous.$(OBJEXT) mech-cyrus-sasl2.$(OBJEXT) \ mech-plain.$(OBJEXT) mech-digest-md5.$(OBJEXT) mycrypt.$(OBJEXT) \ passdb.$(OBJEXT) passdb-ldap.$(OBJEXT) passdb-passwd.$(OBJEXT) \ passdb-passwd-file.$(OBJEXT) passdb-pam.$(OBJEXT) \ passdb-shadow.$(OBJEXT) passdb-vpopmail.$(OBJEXT) \ -passdb-pgsql.$(OBJEXT) password-scheme.$(OBJEXT) userdb.$(OBJEXT) \ +passdb-pgsql.$(OBJEXT) passdb-mysql.$(OBJEXT) password-scheme.$(OBJEXT) userdb.$(OBJEXT) \ userdb-ldap.$(OBJEXT) userdb-passwd.$(OBJEXT) \ userdb-passwd-file.$(OBJEXT) userdb-static.$(OBJEXT) \ -userdb-vpopmail.$(OBJEXT) userdb-pgsql.$(OBJEXT) +userdb-vpopmail.$(OBJEXT) userdb-pgsql.$(OBJEXT) userdb-mysql.$(OBJEXT) dovecot_auth_DEPENDENCIES = ../lib-settings/libsettings.a \ ../lib/liblib.a dovecot_auth_LDFLAGS = @@ -295,6 +295,13 @@ ../../src/lib/strfuncs.h ../../src/lib/network.h \ ../../src/lib/str.h ../../src/lib-settings/settings.h \ db-pgsql.h +db-mysql.o: db-mysql.c ../../config.h common.h ../../src/lib/lib.h \ + ../../src/lib/compat.h ../../src/lib/macros.h \ + ../../src/lib/failures.h ../../src/lib/data-stack.h \ + ../../src/lib/mempool.h ../../src/lib/imem.h \ + ../../src/lib/strfuncs.h ../../src/lib/network.h \ + ../../src/lib/str.h ../../src/lib-settings/settings.h \ + db-mysql.h login-connection.o: login-connection.c common.h ../../src/lib/lib.h \ ../../config.h ../../src/lib/compat.h ../../src/lib/macros.h \ ../../src/lib/failures.h ../../src/lib/data-stack.h \ @@ -388,6 +395,14 @@ ../../src/lib/str.h ../../src/lib/strescape.h \ ../../src/lib/var-expand.h password-scheme.h db-pgsql.h \ passdb.h mech.h auth-login-interface.h +passdb-mysql.o: passdb-mysql.c ../../config.h common.h \ + ../../src/lib/lib.h ../../src/lib/compat.h \ + ../../src/lib/macros.h ../../src/lib/failures.h \ + ../../src/lib/data-stack.h ../../src/lib/mempool.h \ + ../../src/lib/imem.h ../../src/lib/strfuncs.h \ + ../../src/lib/str.h ../../src/lib/strescape.h \ + ../../src/lib/var-expand.h password-scheme.h db-mysql.h \ + passdb.h mech.h auth-login-interface.h passdb-shadow.o: passdb-shadow.c ../../config.h common.h \ ../../src/lib/lib.h ../../src/lib/compat.h \ ../../src/lib/macros.h ../../src/lib/failures.h \ @@ -428,6 +443,13 @@ ../../src/lib/imem.h ../../src/lib/strfuncs.h \ ../../src/lib/str.h ../../src/lib/strescape.h \ ../../src/lib/var-expand.h db-pgsql.h userdb.h +userdb-mysql.o: userdb-mysql.c ../../config.h common.h \ + ../../src/lib/lib.h ../../src/lib/compat.h \ + ../../src/lib/macros.h ../../src/lib/failures.h \ + ../../src/lib/data-stack.h ../../src/lib/mempool.h \ + ../../src/lib/imem.h ../../src/lib/strfuncs.h \ + ../../src/lib/str.h ../../src/lib/strescape.h \ + ../../src/lib/var-expand.h db-mysql.h userdb.h userdb-static.o: userdb-static.c ../../config.h common.h \ ../../src/lib/lib.h ../../src/lib/compat.h \ ../../src/lib/macros.h ../../src/lib/failures.h \ diff -u -r --new-file work/dovecot-0.99.10/src/auth/db-mysql.c work.patched/dovecot-0.99.10/src/auth/db-mysql.c --- work/dovecot-0.99.10/src/auth/db-mysql.c Wed Dec 31 16:00:00 1969 +++ work.patched/dovecot-0.99.10/src/auth/db-mysql.c Tue Sep 30 12:24:00 2003 @@ -0,0 +1,181 @@ +/* Copyright (C) 2003 Alex Howansky, Timo Sirainen */ + +#include "config.h" +#undef HAVE_CONFIG_H + +#if defined(PASSDB_MYSQL) || defined(USERDB_MYSQL) + +#include "common.h" +#include "network.h" +#include "str.h" +#include "settings.h" +#include "db-mysql.h" + +#include <limits.h> +#include <stddef.h> +#include <stdlib.h> + +#define DEF(type, name) { type, #name, offsetof(struct mysql_settings, name) } + +static struct setting_def setting_defs[] = { + DEF(SET_STR, db_host), + DEF(SET_STR, db_port), + DEF(SET_STR, db_unix_socket), + DEF(SET_STR, db), + DEF(SET_STR, db_user), + DEF(SET_STR, db_passwd), + DEF(SET_STR, db_client_flags), + DEF(SET_STR, password_query), + DEF(SET_STR, user_query), + DEF(SET_STR, default_pass_scheme) +}; + +struct mysql_settings default_mysql_settings = { + MEMBER(db_host) "localhost", + MEMBER(db_port) "0", + MEMBER(db_unix_socket) "/var/tmp/mysql.sock", + MEMBER(db) "email_accounts", + MEMBER(db_user) "dovecot", + MEMBER(db_passwd) "changeme", + MEMBER(db_client_flags) "0", + MEMBER(password_query) "SELECT password FROM users WHERE userid = '%u'", + MEMBER(user_query) "SELECT home, uid, gid FROM users WHERE userid = '%u'", + MEMBER(default_pass_scheme) "PLAIN-MD5" +}; + +static struct mysql_connection *mysql_connections = NULL; + +static int mysql_conn_open(struct mysql_connection *conn); +static void mysql_conn_close(struct mysql_connection *conn); + +void db_mysql_query(struct mysql_connection *conn, const char *query, + struct mysql_request *request) +{ + MYSQL_RES *res; + int failed; + + if (!conn->connected) { + if (!mysql_conn_open(conn)) { + request->callback(conn, request, NULL); + return; + } + } + + if (verbose_debug) + i_info("MYSQL: Performing query: %s", query); + + if (mysql_query(conn->mysql, query)) + i_info("MYSQL: Error executing query \"%s\": %s", query, + mysql_error(conn->mysql)); + + if ((res = mysql_store_result(conn->mysql))) + failed = FALSE; + else { + i_info("MYSQL: Error retrieving results: %s", + mysql_error(conn->mysql)); + failed = TRUE; + } + + request->callback(conn, request, failed ? NULL : res); + mysql_free_result(res); + i_free(request); +} + +static int mysql_conn_open(struct mysql_connection *conn) +{ + if (conn->connected) + return TRUE; + + if (conn->mysql == NULL) { + conn->mysql = mysql_init(NULL); + if (conn->mysql == NULL) { + i_error("MYSQL: mysql_init failed"); + return FALSE; + } + + if (!mysql_real_connect(conn->mysql, conn->set.db_host, + conn->set.db_user, conn->set.db_passwd, + conn->set.db, + atoi(conn->set.db_port), + conn->set.db_unix_socket, + strtoul(conn->set.db_client_flags, + NULL, 10))) { + i_error("MYSQL: Can't connect to database %s: %s", + conn->set.db, mysql_error(conn->mysql)); + return FALSE; + } + } + + conn->connected = TRUE; + return TRUE; +} + +static void mysql_conn_close(struct mysql_connection *conn) +{ + conn->connected = FALSE; + + if (conn->mysql != NULL) { + mysql_close(conn->mysql); + conn->mysql = NULL; + } +} + +static struct mysql_connection *mysql_conn_find(const char *config_path) +{ + struct mysql_connection *conn; + + for (conn = mysql_connections; conn != NULL; conn = conn->next) { + if (strcmp(conn->config_path, config_path) == 0) + return conn; + } + + return NULL; +} + +static const char *parse_setting(const char *key, const char *value, + void *context) +{ + struct mysql_connection *conn = context; + + return parse_setting_from_defs(conn->pool, setting_defs, + &conn->set, key, value); +} + +struct mysql_connection *db_mysql_init(const char *config_path) +{ + struct mysql_connection *conn; + pool_t pool; + + conn = mysql_conn_find(config_path); + if (conn != NULL) { + conn->refcount++; + return conn; + } + + pool = pool_alloconly_create("mysql_connection", 1024); + conn = p_new(pool, struct mysql_connection, 1); + conn->pool = pool; + + conn->refcount = 1; + + conn->config_path = p_strdup(pool, config_path); + conn->set = default_mysql_settings; + settings_read(config_path, parse_setting, conn); + + (void)mysql_conn_open(conn); + + conn->next = mysql_connections; + mysql_connections = conn; + return conn; +} + +void db_mysql_unref(struct mysql_connection *conn) +{ + if (--conn->refcount > 0) + return; + + mysql_conn_close(conn); + pool_unref(conn->pool); +} + +#endif diff -u -r --new-file work/dovecot-0.99.10/src/auth/db-mysql.h work.patched/dovecot-0.99.10/src/auth/db-mysql.h --- work/dovecot-0.99.10/src/auth/db-mysql.h Wed Dec 31 16:00:00 1969 +++ work.patched/dovecot-0.99.10/src/auth/db-mysql.h Tue Sep 30 12:24:00 2003 @@ -0,0 +1,51 @@ +#ifndef __DB_MYSQL_H +#define __DB_MYSQL_H + +#include <mysql.h> + +struct mysql_connection; +struct mysql_request; + +typedef void mysql_query_callback_t(struct mysql_connection *conn, + struct mysql_request *request, + MYSQL_RES *res); + +struct mysql_settings { + const char *db_host; + const char *db_port; + const char *db_unix_socket; + const char *db; + const char *db_user; + const char *db_passwd; + const char *db_client_flags; + const char *password_query; + const char *user_query; + const char *default_pass_scheme; +}; + +struct mysql_connection { + struct mysql_connection *next; + + pool_t pool; + int refcount; + + char *config_path; + struct mysql_settings set; + + MYSQL *mysql; + + unsigned int connected:1; +}; + +struct mysql_request { + mysql_query_callback_t *callback; + void *context; +}; + +void db_mysql_query(struct mysql_connection *conn, const char *query, + struct mysql_request *request); + +struct mysql_connection *db_mysql_init(const char *config_path); +void db_mysql_unref(struct mysql_connection *conn); + +#endif diff -u -r --new-file work/dovecot-0.99.10/src/auth/master-connection.c work.patched/dovecot-0.99.10/src/auth/master-connection.c --- work/dovecot-0.99.10/src/auth/master-connection.c Mon May 26 08:27:13 2003 +++ work.patched/dovecot-0.99.10/src/auth/master-connection.c Tue Sep 30 12:24:00 2003 @@ -55,7 +55,7 @@ reply.virtual_user_idx = reply_add(buf, user->virtual_user); reply.mail_idx = reply_add(buf, user->mail); - p = strstr(user->home, "/./"); + p = user->home ? strstr(user->home, "/./") : NULL; if (p == NULL) { reply.home_idx = reply_add(buf, user->home); reply.chroot_idx = reply_add(buf, NULL); diff -u -r --new-file work/dovecot-0.99.10/src/auth/passdb-mysql.c work.patched/dovecot-0.99.10/src/auth/passdb-mysql.c --- work/dovecot-0.99.10/src/auth/passdb-mysql.c Wed Dec 31 16:00:00 1969 +++ work.patched/dovecot-0.99.10/src/auth/passdb-mysql.c Tue Sep 30 12:24:00 2003 @@ -0,0 +1,171 @@ +/* Copyright (C) 2003 Alex Howansky, Timo Sirainen */ + +#include "config.h" +#undef HAVE_CONFIG_H + +#ifdef PASSDB_MYSQL + +#include "common.h" +#include "str.h" +#include "strescape.h" +#include "var-expand.h" +#include "password-scheme.h" +#include "db-mysql.h" +#include "passdb.h" + +#include <mysql.h> +#include <stdlib.h> +#include <string.h> + +struct passdb_mysql_connection { + struct mysql_connection *conn; +}; + +struct passdb_mysql_request { + struct mysql_request request; + + enum passdb_credentials credentials; + union { + verify_plain_callback_t *verify_plain; + lookup_credentials_callback_t *lookup_credentials; + } callback; + + char password[1]; +}; + +static struct passdb_mysql_connection *passdb_mysql_conn; + +static void mysql_handle_request(struct mysql_connection *conn, + struct mysql_request *request, MYSQL_RES *res) +{ + struct passdb_mysql_request *mysql_request = + (struct passdb_mysql_request *) request; + struct auth_request *auth_request = request->context; + const char *user, *password, *scheme; + int ret = 0; + + user = auth_request->user; + password = NULL; + + if (res != NULL) { + if (mysql_num_rows(res) == 0) { + if (verbose) + i_info("mysql(%s): Unknown user", user); + } else if (mysql_num_rows(res) > 1) { + i_error("mysql(%s): Multiple matches for user", user); + } else if (mysql_num_fields(res) != 1) { + i_error("mysql(%s): Password query returned " + "more than one field", user); + } else { + MYSQL_ROW row; + + row = mysql_fetch_row(res); + if (row) + password = t_strdup(row[0]); + } + } + + scheme = password_get_scheme(&password); + if (scheme == NULL) { + scheme = conn->set.default_pass_scheme; + i_assert(scheme != NULL); + } + + if (mysql_request->credentials != -1) { + passdb_handle_credentials(mysql_request->credentials, + user, password, scheme, + mysql_request->callback.lookup_credentials, + auth_request); + return; + } + + /* verify plain */ + if (password == NULL) { + mysql_request->callback.verify_plain(PASSDB_RESULT_USER_UNKNOWN, + auth_request); + return; + } + + ret = password_verify(mysql_request->password, password, + scheme, user); + if (ret < 0) + i_error("mysql(%s): Unknown password scheme %s", user, scheme); + else if (ret == 0) { + if (verbose) + i_info("mysql(%s): Password mismatch", user); + } + + mysql_request->callback.verify_plain(ret > 0 ? PASSDB_RESULT_OK : + PASSDB_RESULT_PASSWORD_MISMATCH, + auth_request); +} + +static void mysql_lookup_pass(struct auth_request *auth_request, + struct mysql_request *mysql_request) +{ + struct mysql_connection *conn = passdb_mysql_conn->conn; + const char *query; + string_t *str; + + str = t_str_new(512); + var_expand(str, conn->set.password_query, + str_escape(auth_request->user), NULL); + query = str_c(str); + + mysql_request->callback = mysql_handle_request; + mysql_request->context = auth_request; + + db_mysql_query(conn, query, mysql_request); +} + +static void +mysql_verify_plain(struct auth_request *request, const char *password, + verify_plain_callback_t *callback) +{ + struct passdb_mysql_request *mysql_request; + + mysql_request = i_malloc(sizeof(struct passdb_mysql_request) + + strlen(password)); + mysql_request->credentials = -1; + mysql_request->callback.verify_plain = callback; + strcpy(mysql_request->password, password); + + mysql_lookup_pass(request, &mysql_request->request); +} + +static void mysql_lookup_credentials(struct auth_request *request, + enum passdb_credentials credentials, + lookup_credentials_callback_t *callback) +{ + struct passdb_mysql_request *mysql_request; + + mysql_request = i_new(struct passdb_mysql_request, 1); + mysql_request->credentials = credentials; + mysql_request->callback.lookup_credentials = callback; + + mysql_lookup_pass(request, &mysql_request->request); +} + +static void passdb_mysql_init(const char *args) +{ + struct mysql_connection *conn; + + passdb_mysql_conn = i_new(struct passdb_mysql_connection, 1); + passdb_mysql_conn->conn = conn = db_mysql_init(args); +} + +static void passdb_mysql_deinit(void) +{ + db_mysql_unref(passdb_mysql_conn->conn); + i_free(passdb_mysql_conn); +} + +struct passdb_module passdb_mysql = { + passdb_mysql_init, + passdb_mysql_deinit, + + mysql_verify_plain, + mysql_lookup_credentials +}; + +#endif diff -u -r --new-file work/dovecot-0.99.10/src/auth/passdb.c work.patched/dovecot-0.99.10/src/auth/passdb.c --- work/dovecot-0.99.10/src/auth/passdb.c Sun May 18 05:26:28 2003 +++ work.patched/dovecot-0.99.10/src/auth/passdb.c Tue Sep 30 12:24:00 2003 @@ -110,6 +110,10 @@ if (strcasecmp(name, "pgsql") == 0) passdb = &passdb_pgsql; #endif +#ifdef PASSDB_MYSQL + if (strcasecmp(name, "mysql") == 0) + passdb = &passdb_mysql; +#endif #ifdef HAVE_MODULES passdb_module = passdb != NULL ? NULL : auth_module_open(name); if (passdb_module != NULL) { diff -u -r --new-file work/dovecot-0.99.10/src/auth/passdb.h work.patched/dovecot-0.99.10/src/auth/passdb.h --- work/dovecot-0.99.10/src/auth/passdb.h Thu Mar 20 07:46:33 2003 +++ work.patched/dovecot-0.99.10/src/auth/passdb.h Tue Sep 30 12:24:00 2003 @@ -58,6 +58,7 @@ extern struct passdb_module passdb_vpopmail; extern struct passdb_module passdb_ldap; extern struct passdb_module passdb_pgsql; +extern struct passdb_module passdb_mysql; void passdb_init(void); void passdb_deinit(void); diff -u -r --new-file work/dovecot-0.99.10/src/auth/userdb-mysql.c work.patched/dovecot-0.99.10/src/auth/userdb-mysql.c --- work/dovecot-0.99.10/src/auth/userdb-mysql.c Wed Dec 31 16:00:00 1969 +++ work.patched/dovecot-0.99.10/src/auth/userdb-mysql.c Tue Sep 30 12:24:00 2003 @@ -0,0 +1,160 @@ +/* Copyright (C) 2003 Alex Howansky, Timo Sirainen */ + +#include "config.h" +#undef HAVE_CONFIG_H + +#ifdef USERDB_MYSQL + +#include "common.h" +#include "str.h" +#include "strescape.h" +#include "var-expand.h" +#include "db-mysql.h" +#include "userdb.h" + +#include <mysql.h> +#include <stdlib.h> +#include <string.h> + +struct userdb_mysql_connection { + struct mysql_connection *conn; +}; + +struct userdb_mysql_request { + struct mysql_request request; + userdb_callback_t *userdb_callback; + + char username[1]; /* variable width */ +}; + +static struct userdb_mysql_connection *userdb_mysql_conn; + +static int is_result_valid(MYSQL_RES *res) +{ + int i, n_fields, found; + MYSQL_FIELD *fields; + + if (res == NULL) { + i_error("MYSQL: Query failed"); + return FALSE; + } + + if (mysql_num_rows(res) == 0) { + if (verbose) + i_error("MYSQL: Authenticated user not found"); + return FALSE; + } + + n_fields = mysql_num_fields(res); + fields = mysql_fetch_fields(res); + + /* Make sure the 'uid' field exists. */ + for (found = 0, i = 0; i < n_fields; i++) + if (strcmp("uid", fields[i].name) == 0) { + found = 1; + break; + } + + if (!found) { + i_error("MYSQL: User query did not return 'uid' field"); + return FALSE; + } + + /* Make sure the 'gid' field exists. */ + for (found = 0, i = 0; i < n_fields; i++) + if (strcmp("gid", fields[i].name) == 0) { + found = 1; + break; + } + + if (!found) { + i_error("MYSQL: User query did not return 'gid' field"); + return FALSE; + } + + return TRUE; +} + +static const char *my_get_str(MYSQL_RES *res, MYSQL_ROW row, const char *field) +{ + int i, n_fields; + unsigned long *lengths; + MYSQL_FIELD *fields; + + n_fields = mysql_num_fields(res); + lengths = mysql_fetch_lengths(res); + fields = mysql_fetch_fields(res); + for (i = 0; i < n_fields; i++) + if (strcmp(field, fields[i].name) == 0) + return (const char *) lengths[i] == 0 ? + NULL : t_strdup(row[i]); + + return NULL; +} + +static void mysql_handle_request(struct mysql_connection *conn __attr_unused__, + struct mysql_request *request, MYSQL_RES *res) +{ + struct userdb_mysql_request *urequest = + (struct userdb_mysql_request *) request; + struct user_data user; + MYSQL_ROW row; + + if (res != NULL && is_result_valid(res) && + (row = mysql_fetch_row(res))) { + memset(&user, 0, sizeof(user)); + user.virtual_user = urequest->username; + user.system_user = my_get_str(res, row, "system_user"); + user.home = my_get_str(res, row, "home"); + user.mail = my_get_str(res, row, "mail"); + user.uid = atoi(my_get_str(res, row, "uid")); /* XXX leak */ + user.gid = atoi(my_get_str(res, row, "gid")); /* XXX leak */ + urequest->userdb_callback(&user, request->context); + } else { + urequest->userdb_callback(NULL, request->context); + } +} + +static void userdb_mysql_lookup(const char *user, userdb_callback_t *callback, + void *context) +{ + struct mysql_connection *conn = userdb_mysql_conn->conn; + struct userdb_mysql_request *request; + const char *query; + string_t *str; + + str = t_str_new(512); + var_expand(str, conn->set.user_query, str_escape(user), NULL); + query = str_c(str); + + request = i_malloc(sizeof(struct userdb_mysql_request) + strlen(user)); + request->request.callback = mysql_handle_request; + request->request.context = context; + request->userdb_callback = callback; + strcpy(request->username, user); + + db_mysql_query(conn, query, &request->request); +} + +static void userdb_mysql_init(const char *args) +{ + struct mysql_connection *conn; + + userdb_mysql_conn = i_new(struct userdb_mysql_connection, 1); + userdb_mysql_conn->conn = conn = db_mysql_init(args); +} + +static void userdb_mysql_deinit(void) +{ + db_mysql_unref(userdb_mysql_conn->conn); + i_free(userdb_mysql_conn); +} + +struct userdb_module userdb_mysql = { + userdb_mysql_init, + userdb_mysql_deinit, + + userdb_mysql_lookup +}; + +#endif diff -u -r --new-file work/dovecot-0.99.10/src/auth/userdb.c work.patched/dovecot-0.99.10/src/auth/userdb.c --- work/dovecot-0.99.10/src/auth/userdb.c Sun May 18 05:26:28 2003 +++ work.patched/dovecot-0.99.10/src/auth/userdb.c Tue Sep 30 12:24:00 2003 @@ -49,6 +49,10 @@ if (strcasecmp(name, "pgsql") == 0) userdb = &userdb_pgsql; #endif +#ifdef USERDB_MYSQL + if (strcasecmp(name, "mysql") == 0) + userdb = &userdb_mysql; +#endif #ifdef HAVE_MODULES userdb_module = userdb != NULL ? NULL : auth_module_open(name); if (userdb_module != NULL) { diff -u -r --new-file work/dovecot-0.99.10/src/auth/userdb.h work.patched/dovecot-0.99.10/src/auth/userdb.h --- work/dovecot-0.99.10/src/auth/userdb.h Sun May 18 05:26:28 2003 +++ work.patched/dovecot-0.99.10/src/auth/userdb.h Tue Sep 30 12:24:00 2003 @@ -29,6 +29,7 @@ extern struct userdb_module userdb_vpopmail; extern struct userdb_module userdb_ldap; extern struct userdb_module userdb_pgsql; +extern struct userdb_module userdb_mysql; void userdb_init(void); void userdb_deinit(void);

2 1

Re: [Dovecot] PATCH: mysql authentication
by Matthew Reimer 03 Oct '03

03 Oct '03

Timo Sirainen wrote: > > On Saturday, Aug 30, 2003, at 02:16 Europe/Helsinki, Matthew Reimer > wrote: > >> Here's a patch that implements mysql authentication. I started with >> the pgsql files and tweaked them to use mysql instead. It works for >> me, but there might be a couple of memory leaks. I'm welcome to >> suggestions on how to clean it up so it can be committed. > > Thank you. I'll look at it more closely later, but it looked fine with > a quick look. > > It would be nice to be able to use asynchronous database lookups. I'm > not sure how easy that is with MySQL, of if it's possible at all. With > PostgreSQL it looked annoyingly difficult so I haven't done it yet. > > Synchronous calls anyway mean that there's only one SQL statement > executing at a time and that may slow down the authentication if > there's a _lot_ of users logging in constantly. If that's a problem, > growing auth_count should help at least some. It specifies the number > of auth processes that respond to the authentication queries. > > And some day I'll probably move the sql stuff into separate lib-sql > and have only a single sql authenticator.. I'm not sure what you mean by asynchronous database lookups. Do you mean you'd like to be able to fire off a db lookup and then come back later to get the results? Like blocking vs non-blocking? I've pasted what may be relevant mysql documentation below in case it might help answer the question. N db handles could be allocated, giving us N simultaneous lookups. Matt --- From http://www.mysql.com/doc/en/C_API_function_overview.html: There are two ways for a client to process result sets. One way is to retrieve the entire result set all at once by calling mysql_store_result(). This function acquires from the server all the rows returned by the query and stores them in the client. The second way is for the client to initiate a row-by-row result set retrieval by calling mysql_use_result(). This function initialises the retrieval, but does not actually get any rows from the server. In both cases, you access rows by calling mysql_fetch_row(). With mysql_store_result(), mysql_fetch_row() accesses rows that have already been fetched from the server. With mysql_use_result(), mysql_fetch_row() actually retrieves the row from the server. Information about the size of the data in each row is available by calling mysql_fetch_lengths(). After you are done with a result set, call mysql_free_result() to free the memory used for it. The two retrieval mechanisms are complementary. Client programs should choose the approach that is most appropriate for their requirements. In practice, clients tend to use mysql_store_result() more commonly. An advantage of mysql_store_result() is that because the rows have all been fetched to the client, you not only can access rows sequentially, you can move back and forth in the result set using mysql_data_seek() or mysql_row_seek() to change the current row position within the result set. You can also find out how many rows there are by calling mysql_num_rows(). On the other hand, the memory requirements for mysql_store_result() may be very high for large result sets and you are more likely to encounter out-of-memory conditions. An advantage of mysql_use_result() is that the client requires less memory for the result set because it maintains only one row at a time (and because there is less allocation overhead, mysql_use_result() can be faster). Disadvantages are that you must process each row quickly to avoid tying up the server, you don't have random access to rows within the result set (you can only access rows sequentially), and you don't know how many rows are in the result set until you have retrieved them all. Furthermore, you must retrieve all the rows even if you determine in mid-retrieval that you've found the information you were looking for. --- end

1 0

[Dovecot] can't read attachments using javamail with dovecot
by Jonas Bosson 03 Oct '03

03 Oct '03

Dear folks, this might be a java-bug, but it seems to occur only when connecting to dovecot-IMAP. UW and Cyrus-ditto works, while when I try to read attachments (base64), I get slapped in the face with this: java.lang.NullPointerException at com.sun.mail.iap.Response.parse(Response.java:99) at com.sun.mail.iap.Response.<init>(Response.java:68) at com.sun.mail.imap.protocol.IMAPResponse.<init>(IMAPResponse.java:31) at com.sun.mail.imap.protocol.IMAPResponse.readResponse(IMAPResponse.java:105) at com.sun.mail.imap.protocol.IMAPProtocol.readResponse(IMAPProtocol.java:153) at com.sun.mail.iap.Protocol.command(Protocol.java:215) at com.sun.mail.imap.protocol.IMAPProtocol.fetch(IMAPProtocol.java:882) at com.sun.mail.imap.protocol.IMAPProtocol.fetch(IMAPProtocol.java:874) at com.sun.mail.imap.protocol.IMAPProtocol.fetchBody(IMAPProtocol.java:677) at com.sun.mail.imap.IMAPInputStream.fill(IMAPInputStream.java:74) at com.sun.mail.imap.IMAPInputStream.read(IMAPInputStream.java:105) at com.sun.mail.util.BASE64DecoderStream.decode(BASE64DecoderStream.java:143) at com.sun.mail.util.BASE64DecoderStream.read(BASE64DecoderStream.java:54) at se.illuminet.httpd.mail.MailXMLService.serviceXml(MailXMLService.java:361) This occurs in booth javamail 1.2 and 1.3(.1) using dovecot. Of course this unfriendly/unhandled response is a problem with javamail while biting the dust. Further analysis points to that the reading works OK up until 2^16 bytes, so it fails either in reading the tail of the attachment or resuming after the first buffered data is consumed. I tried the BODYSTRCUTURE-patch (booth #1 and then #2), but it didn't help. Now I am fresh out of ideas. The java-bug has a three week delay to surface on "bug-parade". But I still have to explain why it works in UW/Cyrus and not with dovecot. Next step would be to add trace-lines in dovecot. Any ideas? /Jonas

2 6

[Dovecot] pop3s in Outlook
by Antonin Karasek 03 Oct '03

03 Oct '03

Hi, I'm using Dovecot for pop3-ssl. Unofortunatelly, most of my users are using MS Outlook. I want them to be able to remove standard mesage: "The certificat is not signed by...", but I don't know how :-( In the dialog isn't a button "Trust this certificate forever"... Is there anybody, who know, how to solve this? Many thanks.

2 1

[Dovecot] Handling of X-Status flags
by Bernard Blackham 29 Sep '03

29 Sep '03

Hi all, I've done a bit of searching and haven't seen anybody else coming across this problem yet: I noticed that Dovecot uses the opposite flags for marking messages as deleted and draft to most other MUAs I've seen or used: With PINE, mutt and uw-imapd at least, messages are marked with X-Status 'D' for Deleted, and 'T' for drafT. Dovecot reverses this behaviour, using 'D' for Draft, and 'T' for Trashed. Was there any reason behind this? Or have I gone loopy? At our site, we have users reading mail with a mix of PINE locally, and through dovecot via WebMail and there seems to arise a bit of confusion between the two flags. Attached is a patch that reverses this behaviour (prepared against 0.99.10 but applies with a little fuzz to cvs). I'd like to hear people's comments on the issue... is it just me? :) Thanks, Bernard. -- Bernard Blackham bernard at blackham dot com dot au

2 2

[Dovecot] UIDPLUS?
by Keith Edmunds 29 Sep '03

29 Sep '03

Any plans to implement UIDPLUS in Dovecot? Keith

2 1

[Dovecot] Odd problem with dovecot segfaulting
by Tim Miller 29 Sep '03

29 Sep '03

Hi All, I installed dovecot on one of my servers the other day, and I want to use it in a vhosting environment. To this end, I have set it up to use password file authentication with a passwd file specified by me. This file will contain both system users and virtual accounts. To test it, I set up two accounts in the dovecot passwd file. One is a system user, I give his home dir in the correct field, along with the MD5 hash of his password in its field, and everything seems to work OK (he can login, read mail out of /var/spool/mail/user etc.). The seconmd account is a vhosted account, and I set the uid and gid to that under which the vhosting account exists. I did not set a home dir, but I set a mail dir in /var/spool/vmail/imap/vhost/user, and made this dir group writeable by dovecot. The user can login, but immediately upon authentication, dovecot segfaults (the log reports an "Internal login failure" and the authentication process is killed with signal 11, i.e. a segfault). Has anyone encountered this before? Is this even the right way to set up vhosting (I don't want to go with LDAP or SQL authentication right at the moment, but I may move to that later on)? Are there any things I should look for (this is probably due to something I've done wrong) or make dovecot be a bit more verbose in reporting errors to its log? Thanks in advance for any help. From what I've seen so far, dovecot looks like an excellent product. Best, Tim Miller

2 1

[Dovecot] pine and mozilla at the same time
by Gasha 26 Sep '03

26 Sep '03

Hi all, what is the best way to read e-mail from server using "pine" ?? I would like to use graphical IMAP client, mozilla for example. And sometimes run pine from shell. mbox or Maildir? Or maybe setup pine to use IMAP server on "localhost" ?? Gasha

2 1

[Dovecot] can't read attachments using javamail with dovecot
by Jonas Bosson 25 Sep '03

25 Sep '03

Dear folks, this might be a javamail-bug, but it seems to occur only when connecting to dovecot-IMAP. UW and Cyrus-ditto works, while when I try to read attachments (base64), I get slapped in the face with this: java.lang.NullPointerException at com.sun.mail.iap.Response.parse(Response.java:99) at com.sun.mail.iap.Response.<init>(Response.java:68) at com.sun.mail.imap.protocol.IMAPResponse.<init>(IMAPResponse.java:31) at com.sun.mail.imap.protocol.IMAPResponse.readResponse(IMAPResponse.java:105) at com.sun.mail.imap.protocol.IMAPProtocol.readResponse(IMAPProtocol.java:153) at com.sun.mail.iap.Protocol.command(Protocol.java:215) at com.sun.mail.imap.protocol.IMAPProtocol.fetch(IMAPProtocol.java:882) at com.sun.mail.imap.protocol.IMAPProtocol.fetch(IMAPProtocol.java:874) at com.sun.mail.imap.protocol.IMAPProtocol.fetchBody(IMAPProtocol.java:677) at com.sun.mail.imap.IMAPInputStream.fill(IMAPInputStream.java:74) at com.sun.mail.imap.IMAPInputStream.read(IMAPInputStream.java:105) at com.sun.mail.util.BASE64DecoderStream.decode(BASE64DecoderStream.java:143) at com.sun.mail.util.BASE64DecoderStream.read(BASE64DecoderStream.java:54) at se.illuminet.httpd.mail.MailXMLService.serviceXml(MailXMLService.java:361) This occurs in booth javamail 1.2 and 1.3(.1) using dovecot. Of course this unfriendly/unhandled response is a problem with javamail while it bites the dust. Further analysis points to that the reading works OK up until 2^16 bytes, so it fails either in reading the tail of the attachment or resuming after the first buffered data is consumed. I tried the BODYSTRCUTURE-patch (booth #1 and then #2), but it didn't help. Now I am fresh out of ideas. The java-bug has a three week delay to surface on "bug-parade". But I still have to explain why it works in UW/Cyrus and not with dovecot. Next step would be to add trace-lines in dovecot. Any ideas? /Jonas

1 0

[Dovecot] Multiple instances of .customflags staying open
by Ron 25 Sep '03

25 Sep '03

# cat /proc/version Linux version 2.4.20-18.9 (bhcompile(a)daffy.perf.redhat.com) (gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)) #1 Thu May 29 07:09:43 EDT 2003 # dovecot --version 0.99.10 I've just recently noticed a serious problem with my system. After about an hour or so I get errors in /var/log/maillog such as this; Sep 21 06:40:16 the-system imap(ray): opendir() failed with file \ \/home/ray/Maildir//new: Too many open files I investigated with 'lsof' and found that many copies of '.customflags' were open for each and every folder. ie; Each folder's '.customflags' file was open 15 times! I suspect that postfix is not able to store newly collected email while this is occuring, therefore I am likely losing messages. I've tried with multiple mail clients (Sylpheed & Evolution) and multiple users, always with the same result. Further investigation indicates that each time the client scans for new mail another instance of each and every '.customflags' is opened. As I have the client set for checking at five minute intervals then it was probably 75 minutes until the client barfed. Less, if I manualy scan for new mail a few times. If I shutdown the client and restart it then everything is fine for about an hour. Running 'lsof /home/ray/Maildir/.customflags' on the server I can see the list of files increasing each time the client checks for new mail. Any help would be appreciated!

4 14

[Dovecot] Re: Bug: Message time gets changed during move/copy
by Timo Sirainen 25 Sep '03

25 Sep '03

On Sat, 2003-09-13 at 13:10, Akhilesh Agarwal wrote: > SERVER > > * Redhat 9.0 stable (with all up2date updates installed) > * Sendmail-8.12.8-6.90 > * Dovecot 0.99.10 release > * On the workstation running Outlook Express, there should be > some existing messages in Local Folders. (example: message > downloaded from a POP3 server) > * Change the time zone of the workstation machine to non-GMT > time zone. In my case GMT +0530 (Indian Standard Time) > * Create a test IMAP account on the server > * Configure Outlook Express to connect to the IMAP account. > * Now select a message in the Local Folders and copy it to a > folder on the IMAP server. > * If you check the message time on the IMAP account, you will > find that +0530 hrs was added to the message time. (+0530 is > apparently the time zone of my workstation as configure above) Sorry for taking this long to reply, it always takes so much effort to turn on my Windows computer :) I cannot reproduce this. I have my server and workstation set to GMT+3 and copying message from Dovecot to OE6 local folder and back keeps the message date the same. Or actually it looks like IMAP -> local folder copies using the message's Date field rather than IMAP's INTERNALDATE which Received-field shows. I'm not sure if this could be Dovecot's or OE6's fault .. Has anyone else seen timestamps going wrong when copying? > Can anyone please confirm this and let me know, as I am not subscribed > to the list. It actually never made it to list because it was decided to be spam (mostly due to being HTML).

1 0

[Dovecot] status of maildir and mbox
by Eric S. Johansson 25 Sep '03

25 Sep '03

what is the status of mixed support of maildir and mbox at the same time? Has any progress been made? --- eric

3 7

Re: [Dovecot] PC-Pine "Junk in end of group" (fwd)
by Paul 25 Sep '03

25 Sep '03

Also, this line is popping up in my syslog. It wasn't there before the recompile: imap(paul): Error indexing mbox file /home/paul/mail/postponed-msgs: LF not found where expected Paul ---------- Forwarded message ---------- Date: Wed, 24 Sep 2003 14:17:20 -0400 (Eastern Daylight Time) From: Paul <lists(a)pote.com> To: dovecot(a)procontrol.fi Subject: Re: [Dovecot] PC-Pine "Junk in end of group" Timo, thanks - I applied the patch and recompiled, but I am still getting the same error, under the same circumstances. Paul

2 1

[Dovecot] PC-Pine "Junk in end of group"
by Paul Adams 25 Sep '03

25 Sep '03

I am running PC-Pine under Windows XP, connecting via SSL to a Dovecot IMAP server (0.99.10-2 under Debian woody). When I open a mail folder (mbox format) in Pine I get the following non-fatal error: [Junk in end of group: pn=undisclosed-recipients al= dn=] A similar error was reported to comp.mail.pine as happening with a Lotus Domino server. Mark Crispin explained it as a server-side bug: http://groups.google.com/groups?hl=en&lr=lang_en&ie=UTF-8&safe=off&threadm=… Is this something that can be easily fixed? Paul

3 3

[Dovecot] debian installation
by Ewald Geschwinde 23 Sep '03

23 Sep '03

apt-get install postfix-tls postfix-pgsql sasl2-bin libsasl2-modules postgresql libpam-pgsql Reading Package Lists... Done Building Dependency Tree... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: Sorry, but the following packages have unmet dependencies: sasl2-bin: Depends: libcomerr1-kerberos4kth (>= 1.2.2-2) but it is not installable E: Sorry, broken packages I think the new users should know this Maybe it takes some time before the sasl2-bin is update Regards Ewald Geschwinde

3 3

[Dovecot] shared folders?
by Samuel Verner 23 Sep '03

23 Sep '03

hello, does dovecot support shared folders (a very nice feature in cyrus-imapd)? sam

2 1

[Dovecot] dovecot IMAP misserving problem?
by Warren Togami 23 Sep '03

23 Sep '03

http://togami.com/~warren/archive/2003/evolution-1.4.4-crash.mbox I suspect that dovecot-0.99.10 is misserving this message in some way that is confusing some IMAP clients. This behavior causes evolution-1.4.4 to segfault, and squirrelmail-1.4.1 to be unable to read the message. The same message served by uw-imapd works works fine in both evolution and squirrelmail. https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=104288 Red Hat Bugzilla dovecot report https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=104289 Red Hat Bugzilla evolution segfault report http://bugzilla.ximian.com/show_bug.cgi?id=48418 Ximian evolution segfault report

2 6

[Dovecot] problem with auth
by Ewald Geschwinde 22 Sep '03

22 Sep '03

I'm new to dovecot (it's a cool piece of software!!!) I'm using Debian woody I'm trying to start the server but then there is this mail Do I have to set an environment variable or waht does this mean. I'm trying to use a pgsql backend for authentification and I have compiled it from source /usr/local/libexec/dovecot/dovecot-auth start dovecot-auth: Fatal: MECHANISMS environment is unset Regards Ewald Geschwinde

2 1

[Dovecot] feature request: maildirquota
by Eero Volotinen 21 Sep '03

21 Sep '03

Hope maildirquota++ is soon supported, without it, dovecot is useless in my use (mail hosting with maildirquotas). Also QUOTA cabability in dovecot is needed to get to use my webmail plugins that use a001 CAPABILITY to get quota support. Courier imapd supports this. --snippet from quota usage plugin to squirrelmail-- function sqimap_get_quota ($imap_stream, $mailbox) { if (check_quota_capability($imap_stream, "QUOTA")) { fputs ($imap_stream, "a001 GETQUOTAROOT \"$mailbox\"\r\n"); $read_ary = sqimap_read_data ($imap_stream, 'a001', true, $result, $message); for ($i = 0; $i < count($read_ary); $i++) { if (ereg("STORAGE", $read_ary[$i])) { $tempusage = ereg_replace("^.*[(]STORAGE +(.*)[)].*$", "\\1", $read_ary[$i]); $usagearray = explode(" ", $tempusage); return $usagearray[0].":".$usagearray[1]; } } } return "NOQUOTA"; } function check_quota_capability($imap_stream, $capability) { global $imap_general_debug; fputs ($imap_stream, "a001 CAPABILITY\r\n"); $read_ary = sqimap_read_data($imap_stream, 'a001', true, $a, $b); for($i = 0; $i < count($read_ary); $i++) { if (ereg("QUOTA", $read_ary[$i])) return TRUE; } return false; } -- end snippet-- -- Eero

3 2

[Dovecot] Secure coding guide
by Timo Sirainen 21 Sep '03

21 Sep '03

I thought I'd write a small guide to what Dovecot's "secure coding techniques" are and how you'd use them: http://dovecot.fi/doc/securecoding.txt

1 0

[Dovecot] convert wu-imap Maildir format to dovecot
by Alin Osan 21 Sep '03

21 Sep '03

Hello, I intend to migrate a mail server with Maildir from wu-imap to dovecot imap. Using horde/IMP, users can not access their imap forders, as wu-imap created Mail directory that holds all created folders. Dovecot could not detect the mail directory so I had to put default_mail_env = ~/Maildir in dovecot.conf. Before I begin to read the source-code of dovecot or try to migrate the the mailboxes using a shell script, is there any way I can make dovecot read the wu-imap folders format? Please suggest any solution that you find viable. Thank you. -- -- We are what we repeatedly do. Excellence, then, is not an act, but a habit. -- Alin Osan

3 7