- dovecot - dovecot.org

[Dovecot] Dovecot-1.0.beta1: New mail sometimes fails to appear
by Tom Alsberg 14 Feb '06

14 Feb '06

Hi there... Having updated to 1.0.beta1, I for a while thought a bad bug with IDLE handling that caused new mail in INBOX not to appear when using Mozilla Thunderbird has been solved. Although I can not reproduce one kind of problem anymore, after a short while it again appears that one does not always see one's new mail with Thunderbird. I can not consistently reproduce the bug, but from some network captures it indeed appears that sometimes Thunderbird has (in one of its connections to the server) INBOX SELECTed and IDLE on it, new mail arrives, but 10 minutes afterwards it was still not sent an EXISTS message. Initially the symptoms appeared to suggest that something really bad happened to the index files, but I tried INDEX=MEMORY and that did not help much. Thunderbird using multiple connections to the server does of course only make debugging more difficult. But it appears that without multiple connections, one has to constantly cycle around SELECTing to get notified on more than one mailbox, so that may justified. I am a bit lost on this now, and would appreciate some ideas. Although there were several related bugs I noticed in Thunderbird 1.0, it appears that they are gone in 1.5, and yet now it really seems Dovecot is doing something wrong here. Attached is the configuration file I use for the testing installation of Dovecot 1.0.beta1 (somebody tell me if you see something wrong there). The mailbox arrangement is as follows, right now (until we have a better way): * INBOX in /var/mail/%u * most mailboxes in ~/imap.maildir/... as maildirs. * mboxes in ~/imap.mbox/... accessible as #imap.mbox/... * the mbox:~/mail/ is for when namespaces are not used - now there are so it should not be relevant Except for myself, and one test account I have, I have two guinea-pigs using it (who are well aware that it is still under development and that it will break once in a while) and reporting problems to me. Vaguely (since I can't figure the exact reasons), the symptom can be described as follows: When using Mozilla Thunderbird to access mail, new mail arrives to INBOX (mbox:/var/mail/%u), but is sometimes not seen for a long while after it arrives. Sometimes the first (or first few) message arriving appears, but then no new messages appear, and sometimes everything works right and immediately new mail is seen. However whenever (according to Thunderbird) something changes in the mailbox, the mailbox is seen up-to-date as it really was at that time. Thanks, any help appreciated, -- Tom -- Tom Alsberg - hacker (being the best description fitting this space) Web page: http://www.cs.huji.ac.il/~alsbergt/ DISCLAIMER: The above message does not even necessarily represent what my fingers have typed on the keyboard, save anything further. # Dovecot IMAP server configuration at CS.HUJI ############################################## # # $Id$ # GENERAL PARAMETERS: ##################### # Base directory where to store runtime data: base_dir = /var/run/dovecot # Protocols we want to be serving: protocols = imap pop3 # IP or host address where to listen in for connections: listen = * ssl_disable = yes # LOGIN PROCESSES: ################## # Directory for authentication sockets: #login_dir = /var/run/dovecot/login # chroot login process to the login_dir: #login_chroot = yes # User to use for the login process: login_user = nobody # Maximum process size in megabytes: #login_process_size = 16 # Have each login be processed in its own process: #login_process_per_connection = yes # Number of login processes to create: #login_processes_count = 3 # Maximum number of extra login processes to create: #login_max_processes_count = 128 # Maximum number of connections allowed in login state: #login_max_logging_users = 256 # Greeting message for clients: login_greeting = Dovecot mail access server at CS.HUJI ready. # MAIL PROCESSES: ################# # Maximum number of running mail processes: #max_mail_processes = 1024 # Show more verbose process title (in ps): verbose_proctitle = yes # Valid UID range for users: first_valid_uid = 10 #last_valid_uid = 0 # Valid GID range for users: #first_valid_gid = 1 #last_valid_gid = 0 # Extra groups for mail processes: #mail_extra_groups = # ':' separated list of directories under which chrooting is allowed: #valid_chroot_dirs = # Default chroot directory for mail processes: #mail_chroot = # Default MAIL environment to use when it's not set: default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # NAMESPACES: ############# namespace private { separator = / prefix = "" location = maildir:~/imap.maildir/ } namespace private { separator = / prefix = "#imap.mbox/" location = mbox:~/imap.mbox/:INBOX=/var/mail/%u inbox = yes } # MAIL STORE: ############# # Space-separated list of fields to initially save into cache file: #mail_cache_fields = # Space-separated list of fields to never save into cache file: #mail_never_cache_fields = # Like mailbox_check_interval, but used for IDLE command: #mailbox_idle_check_interval = 30 # Whether to allow full filesystem access to clients: #mail_full_filesystem_access = no # Maximum allowed length for mail keyword name: #mail_max_keyword_length = 50 # Whether to save mails with CR+LF instead of plain LF: #mail_save_crlf = no # Whether to use mmap to access mail files: #mail_read_mmaped = no # Whether to disable mmap at all: mmap_disable = yes # Whether to disable write to mmap: #mmap_no_write = no # Locking method for index files: lock_method = dotlock # Whether to list only directories in LIST command: maildir_stat_dirs = yes # Whether to copy mail to other folders using hard links: #maildir_copy_with_hardlinks = no # Locking methods to use for locking mbox: mbox_read_locks = dotlock mbox_write_locks = dotlock # Maximum time in seconds to wait for lock (all of them): mbox_lock_timeout = 300 # Timeout to overwrite dotlock files if mailbox isn't modified: mbox_dotlock_change_timeout = 30 # Whether to read only appended data on change (unless corrupt): #mbox_dirty_syncs = yes # Like mbox_dirty_syncs, but no full syncs with SELECT, EXAMINE, # EXPUNGE, or CHECK: #mbox_very_dirty_syncs = no # Whether to delay writing mbox headers until doing a full write sync: #mbox_lazy_writes = yes # umask to use for mail files and directories: umask = 0077 # Whether drop all privileges before exec of mail process: #mail_drop_priv_before_exec = no # Maximum mail process size in megabytes: #mail_process_size = 256 # Log prefix for mail processes: mail_log_prefix = "%Us(%u): " # IMAP SPECIFIC SETTINGS: ######################### protocol imap { # Login executable location: #login_executable = /usr/local/dovecot/libexec/dovecot/imap-login # IMAP executable location: #mail_executable = /usr/local/dovecot/libexec/dovecot/imap # Maximum IMAP command line length in bytes: #imap_max_line_length = 65536 # Suypport for dynamically loadable modules: #mail_use_modules = no #mail_modules = /usr/local/dovecot/lib/dovecot/imap # Whether to send IMAP capabilities in greeting message: login_greeting_capability = yes # Workarounds for various client bugs: imap_client_workarounds = outlook-idle netscape-eoh } # POP3 SPECIFIC SETTINGS: ######################### protocol pop3 { # Login executable location: #login_executable = /usr/local/dovecot/libexec/dovecot/pop3-login # POP3 executable location: #mail_executable = /usr/local/dovecot/libexec/dovecot/pop3 # Whether to not update recent/seen flags in POP3 sessions: #pop3_no_flag_updates = no # Whether to support deprecated LAST command: #pop3_enable_last = no # POP3 UIDL format to use: #pop3_uidl_format = %08Xu%08Xv # Support for dynamically loadable modules #mail_user_modules = no #mail_modules = /usr/local/dovecot/lib/dovecot/pop3 # Workarounds for various client bugs: pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } # AUTHENTICATION PROCESSES: ########################### # Authentication executable location: #auth_executable = /usr/local/dovecot/libexec/dovecot/dovecot-auth # Maximum authentication process size in megabytes: #auth_process_size = 256 # Authentication cache size in kilobytes: #auth_cache_size = 0 # Time to live in seconds for cached data: #auth_cache_ttl = 3600 # Space separated list of realms for SASL authentication mechanisms: #auth_realms = # Default realm/domain to use if none was specified: #auth_default_realm = # List of allowed characters in username: #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ0123456789.-_@ # Username character translation before it's looked up in database: #auth_username_translation = # Whether to disable plaintext authentication disable_plaintext_auth = no # More verbose authentication logging: auth_verbose = yes # Even more verbose authentication logging for debugging purposes: auth_debug = yes auth default { # Space separated list of wanted authentication mechanisms mechanisms = plain # Password database specification: passdb pam { } # User database specification: userdb passwd { } # User to use for the authentication process: user = root # Directory where to chroot the process: #chroot = # Number of authentication processes to create: #count = 1 # Whether to require a valid SSL client certificate for # authentication: #ssl_require_client_cert = no }

5 28

[Dovecot] Mail.app help
by Mike Garfias 14 Feb '06

14 Feb '06

I'm having a problem with Mail.app and imap folders. I've got a new install of dovecot 1.0beta2, and am only experiencing this problem with Mail. Mutt works as expected, as well as thunderbird. When I create a folder using Mail.app, it is written to ~/Maildir/.INBOX.newfolder, which would be fine, if I wasn't telling everything that I wanted no prefixes. If I move that folder to ~/Maildir/.newfolder, Mail.app can no longer see it, but mutt and thunderbird can. Thunderbird _CAN_ see the folders created as .INBOX.Folder, and even shows it as a subfolder of my inbox, but Mutt completely refuses to see it. Any ideas what I'm doing wrong here?

4 4

[Dovecot] Duplicate entry in ./configure --help
by Luigi Rosa 14 Feb '06

14 Feb '06

The help message has a duplicate entry for "--with-gnu-ld" option: --without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no) --with-gnu-ld assume the C compiler uses GNU ld [default=no] --with-pic try to use only PIC/non-PIC objects [default=use both] --with-tags[=TAGS] include additional configurations [automatic] --with-gnu-ld assume the C compiler uses GNU ld default=no --with-libiconv-prefix[=DIR] search for libiconv in DIR/include and DIR/lib Ciao, luigi -- +--[Luigi Rosa]--

2 1

RE: [Dovecot] passwd-file
by cha yang 14 Feb '06

14 Feb '06

http://wiki.dovecot.org/Authentication Look 3/4 down the page. I think this is what you are looking for. Cha Yang

2 1

[Dovecot] passwd-file
by Simon Waters 14 Feb '06

14 Feb '06

Hi, the wiki doesn't explain the file format for passwd-file. I want to do a small set of virtual users using flat files. I have my postfix "vmailbox" generated, and working as expected for delivery. I've configured dovecot, put passwd-file for the auth_passdb, and specified a file name. By "passwd like" what is allowed? Where is it document. How unlike passwd can it be? Must I read the source code? Simon

1 0

[Dovecot] nologin
by Robert A. Thompson 14 Feb '06

14 Feb '06

I need to be able to setup a nologin system for users on my mail server on a per user basis. We are going to do some maintenance on each user (individually) and would like it if they could not login to dovecot while we do this. I was curious if dovecot implemented anything like this. We are currently using standard pam authentication (nothing db related) and I was hoping to be able to touch a "nologin" file on a per user basis in their home directory. I think I could do this with some pam magic, but was curious if dovecot had something in it that would allow for this. Note: I understand I will have to forcibly kill active connections. --Robert

2 1

[Dovecot] Problems with POP3 UIDL when migrating from MBOX to Maildir
by Jonas Olsson 14 Feb '06

14 Feb '06

Hello, I am in the process of migrating a hosting setup from UW-IMAP to Dovecot. The protocols available to mail clients are IMAP and POP3 both before and after migration. I also wanted to change the mail storage format from MBOX to Maildir. However, at this point I hit a major snag with Dovecot and POP3 UIDL (unique identification listing for POP3 mailboxes). Several of the customers connecting to the mailserver in question are using POP3 clients and leave their e-mails on the server. To avoid downloading all messages every time the clients connect they use the UIDL command in the POP3 specification to determine if any new messages have arrived since last time they checked. In order for this to work the unique identifier of each message must be static and can never change. If the identifiers change, every client will download all messages again, mixing old messages with new, in the belief that all messages are new since their identifiers changed. The first step, migrating from UW-IMAP to Dovecot, did not pose any problems in this regard. Connecting to the POP3 service manually to show the UIDL output revealed: With UW-IMAP: uidl +OK Unique-ID listing follows 1 43ef424e00000001 2 43ef424e00000002 With Dovecot: uidl +OK 1 43ef424e00000001 2 43ef424e00000002 However, after performing a migration to Maildir, storing all messages in ~/Maildir for the user in question, I received a different UIDL output: uidl +OK 1 43ef523100000001 2 43ef523100000002 I used the mb2md utility available from http://batleth.sapienti-sat.org/projects/mb2md/ to do the conversion. A diff between the new Maildir messages and the old mailbox reveals no other difference than the leading "From " line of each message missing from the Maildir messages. ----------- snip ------------------------------ --- /var/mail/testuser 2006-02-12 15:13:01.000000000 +0100 +++ maildir-concat.txt 2006-02-12 15:21:54.000000000 +0100 @@ -1,4 +1,3 @@ -From test(a)example.com Sun Feb 12 15:09:49 2006 Return-Path: <test(a)example.com> X-Original-To: testuser Delivered-To: testuser(a)localhost.localdomain @@ -16,7 +15,6 @@ Testing 1 -From test(a)example.com Sun Feb 12 15:10:23 2006 Return-Path: <test(a)example.com> X-Original-To: testuser Delivered-To: testuser(a)localhost.localdomain ----------- snip ------------------------------ When removing the ~/Maildir directory of the user to redo the conversion I discovered that Dovecot returned another set of UIDL output this time around: uidl +OK 1 43ef528300000001 2 43ef528300000002 This output is for the same messages as in the previous example, with preserved message filenames. Doing a diff between the old ~/Maildir and the new reveals the following differences: ----------- snip ------------------------------ $ diff -ur Maildir.example1 Maildir.example2 Binary files Maildir.example1/dovecot.index and Maildir.example2/dovecot.index differ Binary files Maildir.example1/dovecot.index.cache and Maildir.example2/dovecot.index.cache differ Binary files Maildir.example1/dovecot.index.log and Maildir.example2/dovecot.index.log differ diff -ur Maildir.example1/dovecot-uidlist Maildir.example2/dovecot-uidlist --- Maildir.example1/dovecot-uidlist 2006-02-12 16:20:17.000000000 +0100 +++ Maildir.example2/dovecot-uidlist 2006-02-12 16:21:39.000000000 +0100 @@ -1,3 +1,3 @@ -1 1139757617 3 +1 1139757699 3 1 1139757559.000001.mbox:2, 2 1139757559.000000.mbox:2, ----------- snip ------------------------------ Questions: ---------------- How does Dovecot generate the POP3 UIDL? Is there any workaround that I could use to make Dovecot generate a consistent POP3 UIDL output, enabling a migration from MBOX to Maildir, or am I stuck with using MBOX? My environment ----------------------- OS: CentOS 4.2 Dovecot version: 1.0 beta3 (built locally to an RPM package, available on request) I have tested with earlier versions of Dovecot, getting the same behaviour. Relevant entries in /etc/dovecot.conf: ----------- snip ------------------------------ protocols = imap imaps pop3 pop3s listen = * disable_plaintext_auth = no protocol pop3 { pop3_uidl_format = %08Xv%08Xu pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } ----------- snip ------------------------------ -- /Jonas Olsson

4 6

[Dovecot] IMAP timeout
by Eugeny N Dzhurinsky 14 Feb '06

14 Feb '06

Hi there! Is it possible to set timeout for IMAP connection somehow? The problem is when I'm using mutt to access IMAP mailbox, everything works fine, but after some idle time mutt tells mailbox is closed and next connection crashes it. With courier mutt works just fine, so I think may be dovecot have some timeout which need to be adjusted? I checked manuals and configuration, but no luck... In both cases (dovecot/courier) I'm using IMAP over SSL -- Eugene N Dzhurinsky

3 3

Re: [Dovecot] drac.c
by Matthias Andree 14 Feb '06

14 Feb '06

"Takehiko Abe" <keke(a)gol.com> writes: > I am using dovecot [1.0 beta3] as a pop server with drac. It is Drac is an abomination that needs to go away. I am requesting to unsupport it before Dovecot 1.0. Drac is insecure by design, in that it doesn't authenticate the same channel (but POP3/IMAP instead) that is being privileged (SMTP for relay), and without any clue of how long dynamic IP mappings remain stable. Better solutions are available (and have been for years), namely SMTP AUTH, supported by all relevant mail transfer agents(*) and - IMO - all relevant clients. ________ (*) I do not consider qmail relevant any more. <http://home.pages.de/~mandree/qmail-bugs.html> -- Matthias Andree

4 4

Re: [Dovecot] Solaris 10 U1 (x86?) LDAP gotcha
by Alex Moore 14 Feb '06

14 Feb '06

On Tue, 14 Feb 2006 12:25:15 +0900 Peter Evans <peter+dovecot(a)ixp.jp> wrote: > This is not actually a problem with dovecot, but something with the > way the library in /opt/sfw/lib/libldap.* is compiled. If you find > yourself eating cpu, compile your own ldap from openldap, it is NOT > dovecot's fault. > > It looks like pilot error with the sun freeware edition. Or get openldap from www.blastwave.org:> Although I have not tried openldap with dovecot, I do use it for virtual accounts with another mail product and have never seen what you describe. The blastwave package is typically quite up to date with the current stable from openldap.org. Alex -- --

1 0

[Dovecot] imap process spinning (ix86/OpenBSD 3.8, dovecot 1.0b3)
by Joseph Kiniry 13 Feb '06

13 Feb '06

Hi Dovecot-ers, Immediately on accessing our new dovecot 1.0b3 build, we see processes spinning, much like the old dovecot 0.9x builds did for us. Here is a ktrace of the spinning imap process: topos:tmp# kdump 18248 imap EMUL "native" 18248 imap PSIG SIGALRM caught handler=0x1c03ff88 mask=0x0 18248 imap CALL setitimer(0,0xcfbcb3bc,0xcfbcb3ac) 18248 imap RET setitimer 0 18248 imap CALL sigreturn(0xcfbcb3ec) 18248 imap RET sigreturn JUSTRETURN 18248 imap PSIG SIGALRM caught handler=0x1c03ff88 mask=0x0 18248 imap CALL setitimer(0,0xcfbcb3bc,0xcfbcb3ac) 18248 imap RET setitimer 0 18248 imap CALL sigreturn(0xcfbcb3ec) 18248 imap RET sigreturn JUSTRETURN If any additional config information is needed to debug, just ask. I am now subscribed to (the digest version of) this list. Thanks, Joe --- Joseph Kiniry School of Computer Science and Informatics UCD Dublin http://secure.ucd.ie/ http://srg.cs.ucd.ie/

1 0

[Dovecot] locking problems with RHEL 3 and dovecot
by Dan Bongert 13 Feb '06

13 Feb '06

I just migrated from a FreeBSD/Sendmail/UW-IMAP setup to RHEL 3/Postfix/Dovecot (1.0a5 currently). Both systems used Procmail as the final delivery agent (into inboxes or . Since the changeover, things have *mostly* been going ok, but I've been having some problems that I think are locking-related. I'm getting reports from users about IMAP hangs (mostly from Thunderbird). Sometimes I see this in the Dovecot logs: ovecot: Feb 06 11:30:45 Error: imap(dbongert): fcntl() failed with mbox file /home/d/dbongert/mail/worklists/tech-partners: Resource temporarily unavailable Now, I have read that one should have everything that touches a mailbox use the same sort of locking, but that's the thing--these mailboxes are only accessed via dovecot. I'm sure a few users use procmail to filter their mail, but they're in the strict minority here. As as experiment, I changed these lines to flock rather than fcntl: mbox_read_locks = flock mbox_write_locks = dotlock flock But all that seems to have done is removed the fcntl errors from the log file. These errors seem to be Thunderbird only (1.07-1.5, Linux and Windows clients), but I'm not sure what that means. I've enabled the only thunderbird-specific IMAP workaround I know of: tb-extra-mailbox-sep, but I doubt that has anything to do with this problem. -- Dan Bongert dbongert(a)ssc.wisc.edu SSCC Unix System Administrator

2 2

Re: [Dovecot] drac.c
by Udo Rader 13 Feb '06

13 Feb '06

On Mon, 2006-02-13 at 22:02 +0900, Takehiko Abe wrote: > Udo Rader wrote: > > > a question from an uninitated: what is drac after all? > > Dynamic Relay Authorization Control. > <http://mail.cc.umanitoba.ca/drac/> > > [it is simple... and i think it is clean <duck>] Hmm, SMTP-after-POP ... I would not use it these days. Before we switched to SMTP AUTH, we were also using a POP-before-SMTP model, yet we dropped it immediately when one of our customer's network had been compromized by a virus and due to POPb4SMTP the virus distributed itself using our mailserver without limitation. Udo Rader -- BestSolution.at EDV Systemhaus GmbH http://www.bestsolution.at

1 0

Re: [Dovecot] drac.c
by Matthias Andree 13 Feb '06

13 Feb '06

On Mon, 13 Feb 2006, Takehiko Abe wrote: > Matthias Andree wrote: > > > Drac is an abomination that needs to go away. > > I do not share that view. Are there any arguments that might support your view? -- Matthias Andree

1 0

[Dovecot] drac.c
by Takehiko Abe 13 Feb '06

13 Feb '06

Hello, I am using dovecot [1.0 beta3] as a pop server with drac. It is working nicely, but I am getting the following message in a log: dovecot: pop3(keke): file ioloop.c: line 154 (timeout_remove): \ assertion failed: (*timeout != NULL) dovecot: child 15752 (pop3) killed with signal 6 Adding '&' to 'to_drac' in drac_deinit of drac.c stops the message: void drac_deinit(void) { if (to_drac != NULL) timeout_remove(&to_drac); /* was to_drac */ } But I am not sure if the mod is correct. Thanks, T.

1 0

[Dovecot] Maximum Folder Size/Number of Messages
by Ropetin 13 Feb '06

13 Feb '06

I hope I'm asking this question in the right place, I don't want to offend. I've recently put together a proof of concept Dovecot IMAP server, and I'm very happy with its performance up to this point. I'm looking into using it to replace our existing POP3 server, allowing users to store email on the server rather than on their local machine, hopefully avoiding loss of data. The big question I have is, is there a realistic maximum realistic folder size, either in reference to number of messages or total file size with Dovecot? I'm using Maildir and running it on Debian Linux x86. Right now the filesystem is Ext3, although once the system goes live I'd be looking at something a little more fault tolerant and able to handle the large amount of data. Any recommendations you may have on Filesystem choice are appreciated too! Thanks, Ropetin.

2 1

[Dovecot] LDA delivery problem
by Martin Stephan 12 Feb '06

12 Feb '06

Hi I compiled and configured dovecot-lda as explained in the Wiki (current CVS version). Now I get the following error message: Action: failed Status: 5.0.0 Diagnostic-Code: X-Postfix; Command died with status 80: "/usr/local/libexec/dovecot/deliver". Command output: deliver: Fatal: Can't open log file /var/log/dovecot.log: Permission denied Now, do I have to set this socket listen { master { path = /var/run/dovecot-auth-master mode = 0666 user = vmail # User running Dovecot LDA group = vmail # alternatively mode 0660 + LDA user in this group } } to something else? Or chown the log file? I use Postfix and Dovecot on Ubuntu Breezy. Thanks Martin

1 1

[Dovecot] LDAP mailLocation weirdness
by Udo Rader 12 Feb '06

12 Feb '06

Hi, I've reported this some month ago before (without response), but still I have no clue what is going wrong. Our installation is LDAP based (for virtual hosting) and up to I think alpha2 or 3 everything was working as expected. The trouble I have is that dovecot does not correctly use the information it gets about mailLocation. This is what is stored in the MailMessageStore attribute for a user "f.someone": mbox:/virtual/oeush.at/var/mail/f.someone:INBOX=/virtual/oeush.at/var/mail/f.someone now despite of this setting, this user is unable to fetch any mail, because dovecot partially ignores this setting: ---------CUT--------- dovecot: Feb 04 12:20:42 Info: pop3(f.someone.oeush.at): Effective uid=200, gid=4000 dovecot: Feb 04 12:20:42 Info: pop3(f.someone.oeush.at): mbox: data=/virtual/oeush.at/home/f.someone/mail/:INBOX=/var/mail/f.someone.oeush.at dovecot: Feb 04 12:20:42 Info: pop3(f.someone.oeush.at): mbox: root=/virtual/oeush.at/home/f.someone/mail, index=/virtual/oeush.at/home/f.someone/mail, inbox=/var/mail/f.someone.oeush.at ---------CUT--------- As you can see, dovecot uses /virtual/oeush.at/... both for data and index but not for inbox, where it uses /var/mail/... My LDAP configuration for the mailLocation settings looks like this: ---------CUT--------- # User attributes in order: # Virtual user name (user@domain) # Home directory # MAIL environment # System user name (for getting user's groups from /etc/group) # - For virtual users you don't want to use this, so this defaults to none. # System UID # System GID user_attrs = uid,homeDirectory,MailMessageStore,,uidNumber,gidNumber ---------CUT--------- So where am I wrong? Udo Rader -- BestSolution.at EDV Systemhaus GmbH http://www.bestsolution.at

2 2

[Dovecot] startup script
by William Ross 12 Feb '06

12 Feb '06

hello, Lacking any other guidance, I'm using the following minimal sysv script to start and stop dovecot. If anyone would like to comment on or improve it, I'd be most grateful. thanks, will #!/bin/sh # # System V init script for dovecot imap server # bodged together by will 12.2.06 PIDFILE="/var/run/dovecot/master.pid" LONGNAME="dovecot imap server" NAME="dovecot" DOVECOT='/usr/local/sbin/dovecot' case $1 in start) echo -n "Starting $LONGNAME"; dovecot echo "...done"; ;; stop) echo -n "Stopping $LONGNAME" PID=`cat $PIDFILE` kill $PID echo "...done"; ;; *) N=/etc/init.d/$NAME echo "Usage: $N {start|stop}" >&2 exit 1 ;; esac exit 0 # EOF

1 0

[Dovecot] debian testing and dovecot
by vmstech 12 Feb '06

12 Feb '06

Hi all - Does anyone know how far off beta2 is from getting into debian testing? thx Glenn

2 1

[Dovecot] Compiling Dovecot with gssapi
by Luca Bertoncello 12 Feb '06

12 Feb '06

Hi, all! I'm new to Dovecot and I try to compile it to allow GSSAPI authentication. Unfortunately, configure says me always: Install prefix ...................... : /usr/local File offsets ........................ : 64bit I/O loop method ..................... : poll File change notification method ..... : dnotify Building with SSL support ........... : yes (OpenSSL) Building with IPv6 support .......... : yes Building with pop3 server ........... : yes Building with GSSAPI support ........ : no Building with user database modules . : static prefetch passwd passwd-file checkpassword mysql (modules) Building with password lookup modules : passwd passwd-file shadow pam checkpassword mysql (modules) And, of course, I can't use this authentication method... I searched in google and Dovecot docs, but I didn't found anything... Can someone help me? The system is a Linux RedHat 9 Thanks a lot! -- _______________________________ Luca Bertoncello -Programmierung / Mailserver- IMS Internet-Media-Service GmbH Bärensteiner Straße 7 01277 Dresden Fon: +49 351 2112034 Fax: +49 351 2112020 email: bertoncello(a)internet24.de

3 2

[Dovecot] Dovecot pop3s problem : can't see email
by Rory Campbell-Lange 11 Feb '06

11 Feb '06

Hi. I am trying to setup dovecot running a pop3 service for external clients (and intend in future to setup an imap interface on localhost only for squirrelmail.) Exim is delivering ok to local mailboxes, but I can't seem to get dovecot to serve them. Configuration details: ---------------------- All users run as the tst user, and authentication is done through postgresql. ...excerpt... mail_extra_groups = tst default_mail_env = mbox:INDEX=~/home/tst/Mail/:/home/tst/Mail/%u protocol pop3 { pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } ...excerpt... Log details: ------------ The log shows that docecot is looking at /home/tst/Mail/test Feb 11 13:54:55 tst dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservice=POP3^Isecured^Ilip=217.147.82.200^Irip=83.146.33.145^Iresp=AHRlc3QAcXVhdWpv Feb 11 13:54:55 tst dovecot: auth(default): sql(test,83.146.33.145): query: SELECT passwd as password FROM users WHERE userid = 'test' AND active = 'Y' Feb 11 13:54:55 tst dovecot: auth(default): client out: OK^I1^Iuser=test Feb 11 13:54:55 tst dovecot: auth(default): master in: REQUEST^I1^I14586^I1 Feb 11 13:54:55 tst dovecot: auth(default): sql(test,83.146.33.145): SELECT '/home/tst/Mail/' || home AS home, uid, gid FROM users WHERE userid = 'test' AND active = 'Y' Feb 11 13:54:55 tst dovecot: auth(default): master out: USER^I1^Itest^Ihome=/home/tst/Mail/test^Iuid=1001^Igid=1001 Feb 11 13:54:55 tst dovecot: pop3-login: Login: user=<test>, method=PLAIN, rip=83.146.33.145, lip=217.147.82.200, TLS Feb 11 13:54:58 tst dovecot: pop3(test): Logout. top=0/0, retr=0/ del=0/0, size=0 tst:/home/tst/Mail# ls -lt | grep test -rw------- 1 tst tst 1017 Feb 11 13:41 test -- Rory Campbell-Lange <rory(a)campbell-lange.net> <www.campbell-lange.net>

1 0

[Dovecot] Bug in gssapi support
by Mark Davies 10 Feb '06

10 Feb '06

Hi, Was trying to use the gssapi support and the authentication would consistently die for me. The following patch fixes: --- src/auth/mech-gssapi.c.orig 2006-01-10 15:46:10.000000000 +1300 +++ src/auth/mech-gssapi.c @@ -138,7 +138,7 @@ static OM_uint32 obtain_service_credenti return major_status; } - gss_release_name(&minor_status, gss_principal); + gss_release_name(&minor_status, &gss_principal); return major_status; } as gss_release_name takes a pointer to a gss_name_t as second arg. cheers mark

1 0

[Dovecot] Outlook anonymous IMAP login
by Vincent Jaussaud 10 Feb '06

10 Feb '06

Hello guys, I'm trying to setup anonymous IMAP login on a bunch of Outlook clients, but it doesn't seems to work. I'm using dovecot-0.99.14-r1, on a Gentoo Linux OS. Using command line anonymous login, it's working just fine: youri / # telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK dovecot ready. . CAPABILITY * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE STARTTLS AUTH=PLAIN AUTH=ANONYMOUS . OK Capability completed. . AUTHENTICATE ANONYMOUS + . OK Logged in. But with Outlook it's not working at all. I tried using no password, or just some random stream, it makes no difference. The error I got in dovecot's logs are: Feb 07 12:31:16 Info: PAM: pam_authenticate(anonymous) failed: Authentication failure Feb 07 12:31:19 Info: PAM: pam_authenticate(anonymous) failed: Authentication failure Feb 07 12:31:28 Info: PAM: pam_authenticate(anonymous) failed: Authentication failure My assumption is that Outlook doesn't provide anonymous IMAP support. Could someone confirm this ? Do you know if any workaround/anonymous plugin exist ? Thanks ! --- Everything takes longer, costs more, and is less useful. -- Erwin Tomash

3 4

[Dovecot] Simulating UW Snarf...
by Todd Piket 10 Feb '06

10 Feb '06

I already wrote to Timo, but I thought some others on this list may have had a similar situation. So here goes: The scenario at Michigan Technological University stems from long standing traditions and policies that probably won't change. That said, two of the policies are 1.)we don't bounce mail and 2.)we guarantee delivery when we accept a piece of mail. The UW IMAP "snarf" capability was nice because it allowed us to introduce file system, per user quotas w/o worrying about the "INBOX" in an over quota situation. This is because the user could still read mail. The delivered mail would get "snarfed" from /var/mail/user when the user went back under quota. In our test cases with switching to Maildir with Dovecot, we deliver directly to the user's INBOX instead of /var/mail/user so what do we do when the user is over quota because we can't bounce the mail? After many lengthy discussions our thought was this. Could we symbolically link the user's "Maildir/new" to a non-quota file system such that the move from "new" to "cur" would fail if the user is over quota? What will Dovecot do in that failure situation? Do you have other suggestions? I would be more than willing to develop a patch that makes this an option in the config file. Probably similar to allowing the indexes and control files be on a non-quota file system. Again, it would only allow "Maildir/new" to be on a separate file system, not the whole "INBOX". I hope this conveys the idea well enough. Any thoughts or ideas the list provides would be greatly appreciated. -- Regards, ------------------------------------------------------------ | Todd Piket | Email: todd(a)mtu.edu | | Programmer/Analyst | Phone: (906) 487-1720 | | Distributed Computing Services | | | Michigan Technological University | | ------------------------------------------------------------

8 18

[Dovecot] In-memory Index file bug
by Tony Kay 10 Feb '06

10 Feb '06

Hi, I am getting intermittent error messages in the log when my mail client tries to create/open a folder named ".imhoprefs". Some accounts seem to able to do it, but I have at least one that gives the log error: Feb 7 09:29:54 acad-cl1 dovecot: imap(tkay): close() failed with index file (in-memory index): Bad file descriptor I traced through the code, and it seems to be coming from mail_index_close() (line 1527 of mail-index.c), which seems to be attempting to close a file descriptor for an index. The funny thing is that since I am using in-memory indexes, I believe that there shouldn't be any file descriptor to close, which would explain why the close is failing... Environment information: - Dovecot 1.0b2 - mbox - Environment setting: default_mail_env = mbox:%h:INBOX=%h/.mail:INDEX=MEMORY - Attempting to create/use a folder called mail/.imhoprefs At first, I though the folder itself might be corrupted, so I removed it. No dice. I've checked file permissions. No problems. I honestly can't explain why some users are able to use this folder without error, and others are not. -- Anthony Kay University Computing Center (541) 346-1719 GPG Fingerprint: B0DB D46A 60AF FAE7 A94A 5075 0CB4 4D88 9F4F 7F09 Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. Rich Cook

2 1

[Dovecot] RE: epoll error when running as proxy
by Bill Boebel 10 Feb '06

10 Feb '06

Also, for testing in the error message I patched src/lib/ioloop-epoll.c to show the "ret" and "errno" variables as well as the variable names, which is why there is a bit of extra data in this error message... imap-login: io_loop_handle_add: epoll_ctl(op=3, fd=10, ret=-1, errno=2): No such file or directory Bill On Thursday, February 9, 2006 16:32, Bill Boebel said: > I am running dovecot 1.0 beta3 as a front-end proxy, and getting the > following error when using epoll. The error goes away if I switch to > poll. On the backend IMAP server I see that the login was successful. > The error occurs when I try to retrieve an email or get a folder listing > via IMAP after logging in successfully... > > Feb 9 15:35:57 director4 dovecot: imap-login: proxy(bboebel(a)webmail.us): > started: user=<bboebel(a)webmail.us>, method=plain, rip=204.119.252.7, > lip=192.168.1.68 > Feb 9 15:09:50 director4 dovecot: imap-login: io_loop_handle_add: > epoll_ctl(op=3, fd=10, ret=-1, errno=2): No such file or directory > Feb 9 14:58:23 director4 dovecot: child 9688 (login) returned error 89 > > I can't find anything in the mailing list archives about this error, so > here are some details. I hope somebody can point me in the right > direction to fix this. > > - I am running this on Red Hat ES4 (32-bit x86), compiling with the > following options: > > ./configure \ > --prefix=/usr \ > --sysconfdir=/etc \ > --localstatedir=/var \ > --with-ssldir=/usr/share/ssl \ > --disable-ipv6 \ > --with-file-offset-size=32 \ > --with-mem-align=4 \ > --with-ioloop=epoll \ > --without-passwd \ > --without-passwd-file \ > --without-shadow \ > --without-pam \ > --without-checkpassword \ > --without-bsdauth \ > --without-gssapi \ > --with-ldap \ > --without-vpopmail \ > --with-static-userdb \ > --with-prefetch-userdb \ > --without-pgsql \ > --with-mysql \ > --without-sqlite \ > --without-ssl \ > --with-storages=maildir > > - I have also complied with these options and got the same error: > > ./configure \ > --prefix=/usr \ > --sysconfdir=/etc \ > --localstatedir=/var \ > --with-ioloop=epoll \ > --with-mysql > > > - I have also tried the latest CSV snapshot (dovecot-20060209.tar.gz) and > 1.0 beta2, and I get the same error. > > - If I switch to poll instead of epoll, everything works fine. > > Any ideas? > > Bill >

5 8

[Dovecot] If mbox does not exist dovecot creates directory
by Alexander Shikoff 10 Feb '06

10 Feb '06

Hi, I've searched the archive of mailing list but did not find anything about this issue. dovecot 1.0alpha5, using mbox format and MySQL DB of users When user is trying to login via POP3 and there is no corresponding mailbox for it dovecot creates a directory instead of mbox file. In this time log looks like Feb 10 10:39:36 orion dovecot: auth-worker(default): sql(ivan.sid(a)my.com.ua,192.168.3.9): query: SELECT `password` FROM `users` WHERE login = 'ivan.sid(a)my.com.ua' Feb 10 10:39:36 orion dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=192.168.5.23 rip=192.168.3.9 resp=AGl2YW4uaXZhbm9mZkBmY2JhbmsuY29tLnVhADE= Feb 10 10:39:36 orion dovecot: auth(default): client out: OK 1 user=ivan.sid(a)my.com.ua Feb 10 10:39:36 orion dovecot: auth-worker(default): sql(ivan.sid(a)my.com.ua,192.168.3.9): SELECT "mbox:/var/mail/virtual/my.com.ua/ivan.sid:INBOX=/var/mail/virtual/my.com.ua/ivan.sid:INDEX=MEMORY" AS `mail`, 'mailnull' AS `uid`, 'mail' AS `gid` FROM users WHERE login = 'ivan.sid(a)my.com.ua' Feb 10 10:39:36 orion dovecot: auth(default): master in: REQUEST 101 98738 1 Feb 10 10:39:36 orion dovecot: auth(default): master out: USER 101 ivan.sid(a)my.com.ua mail=mbox:/var/mail/virtual/my.com.ua/ivan.sid:INBOX=/var/mail/virtual/my.com.ua/ivan.sid:INDEX=MEMORY uid=26 gid=6 Feb 10 10:39:36 orion dovecot: pop3(ivan.sid(a)my.com.ua): Effective uid=26, gid=6 Feb 10 10:39:37 orion dovecot: pop3(ivan.sid(a)my.com.ua): mbox: data=/var/mail/virtual/my.com.ua/ivan.sid:INBOX=/var/mail/virtual/my.com.ua/ivan.sid:INDEX=MEMORY Feb 10 10:39:37 orion dovecot: pop3(ivan.sid(a)my.com.ua): mbox: root=/var/mail/virtual/my.com.ua/ivan.sid, index=, inbox=/var/mail/virtual/my.com.ua/ivan.sid Feb 10 10:39:37 orion dovecot: pop3(ivan.sid(a)my.com.ua): open() failed with mbox file /var/mail/virtual/fcbank.com.ua/ivan.sid: Is a directory Feb 10 10:39:37 orion dovecot: pop3(ivan.sid(a)my.com.ua): Mailbox init failed top=0/0, retr=0/ del=0/0, size=0 Feb 10 10:39:37 orion dovecot: pop3-login: Login: user=<ivan.sid(a)my.com.ua>, method=PLAIN, rip=192.168.3.9, lip=192.168.5.23 Please help me with this issue! Thanks in advance, Alexander -- Kind Regards, Alexander Shikoff minotaur(a)crete.org.ua

2 2

[Dovecot] Maildir, imap and newness of messages
by Anand Buddhdev 10 Feb '06

10 Feb '06

I'm using the standard Dovecot 0.99.14 on Fedora Core 4, with a Maildir++ mailbox. I've noticed what I think is an oddity in the way dovecot handles messages: According to the Maildir specification, a message in Maildir/new is a truly new message, which has not yet been touched by any reader. From an IMAP viewpoint, such a message should have the flag RECENT. However, if a message exists in Maildir/cur, then it means that the message is no longer new (because some other reader has opened the Maildir, and moved the message from new to cur). From an IMAP viewpoint, such a message should NOT have the RECENT flag. However, dovecot seems to get this wrong. For example, if I have a message in Maildir/new, and I use mutt (a console-based maildir-aware mail client) to open the Maildir, then mutt moves the messages from Maildir/new to Maildir/cur (note here that I haven't actually read the message yet, just opened the Maildir with mutt). I expect that when I now open this Maildir with dovecot imap, and do a "select inbox", it should report "1 EXISTS" and "0 RECENT". However, dovecot reports this as "1 EXISTS" and "1 RECENT". In my opinion, this is a bug in Dovecot. Would any of the developers like to comment? Anand

3 3

[Dovecot] Dovecot stops logging of imap logins after logrotation
by Gerhard Hofmann 10 Feb '06

10 Feb '06

Hi list, on my Debian box there is a logrotation cron job that will gzip existing /var/log/mail.log file and create a new mail.log. It seems that after running logrotation dovecot stops logging successful POP or IMAP logins to /var/log/mail.log (nevertheless, it still works to login with POP or SMTP). This is bad because pop-before-smtp mechanisms also stop working. I have deactivated logrotation cron job and will monitor mail.log file. Maybe I should just run /etc/init.d/dovecot restart after logrotation script. What do you think? TIA Gerhard

5 4

[Dovecot] Programming Help
by Neal Katz 10 Feb '06

10 Feb '06

Hi, I was hoping you could provide me with some pointers on how to get started adding some features to dovecot. What I am trying to do is add an optional publish mechanism, that would publish a list of events as they occur, so that an external program could read these events and do "something". These events would be "Add", "Delete", "Move" - these would be posted every time a new message is added, deleted or moved. "CreateDir", "DeleteDir" would be published when a user creates a subf-folder or removes one. A simple example would be to configure the system to publish 'Add Message' events, and then an external program would read these, and send a notification event to web based users who are currently logged in. The publish feature would be controlled by the config file, and would be disabled by default The config setting would allow an administrator to specify what events to publish, the mechanism to use, and optional arguments for the mechanism For mechanisms I plan on developing a file based system, one file per event, written into a directory, the subscriber/reader would delete the file Other mechanisms could include TCP/IP based (connect to port XX, and send some data); or even connect to a commercial Message Queue product. Ex. Publish=ADD+DELETE+MOVE:file:/var/spool/imapevents Or Publish=ADD+DELETE+MOVE:tcpip:localhost:9999 It would help me a lot if you could just provide me with a few pointers as to the best place to add my features into the dovecot code, I took a quick look at the code and decided to contact you first before going ahead and putting things in the WRONG place. I did see the code for supporting inotify and similar mechanisms, but I don't see the big picture ? How does dovecot use inotify ?, what features are enabled that you don't get without inotify. If you have a code-roadmap, or architectural diagrams (or doodles) that would be helpful too. In terms of inotify, I don't think this will work for me, since I would like to have the user, Message-Id and Imap UIDL sent in the event message I hope this makes sense, if not just send me an email asking for clarification. All of the changes I make I will submit back to you, and hopefully they will be made part of the base product. Thanks, Neal Katz p.s. I chose Dovecot because I was very impressed with the ease of installation and migration (from courier), my early tests have shown it to be twice as fast when traverse all messages in a large mailbox ( 100K message ).

3 2

[Dovecot] Mixed IMAP/POP3 environment, a success
by Denis Sbragion 10 Feb '06

10 Feb '06

Hello everybody, I just want to inform the Dovecot developers and users that I completely migrated the first mailbox (my own one) from Eudora/UW to SquirrelMail/Dovecot. I'm using it since a couple of days and after a bit of tuning (mostly SquirrelMail related) it works like a charm. I even performed some heavy operations, like moving thousands of messages between different mailboxes or searching within a 1 Gb folder, and performances are indeed great. My sincere greatest compliments to the Dovecot developers and my biggest thanks to the people who helped me. No wonder that Fedora/RedHat has decided to adopt Dovecot as the default IMAP server for future releases. It looks like the perfect balance between security, performances, flexibility, standards conformance and ease of use. Bye, -- Denis Sbragion InfoTecna Tel: +39 0362 805396, Fax: +39 0362 805404 URL: http://www.infotecna.it

1 0

[Dovecot] Dovecot 1.0b2 now in pkgsrc packaging system
by Todd Vierling 10 Feb '06

10 Feb '06

After months of testing in the "work in progress" pkgsrc-wip playground, dovecot-1.0b2 is now in the main pkgsrc mainline and will be tracked up through the 1.0 release and beyond. This means it's now much easier to get Dovecot 1.0 up and running on NetBSD and any other platform supported by pkgsrc (see www.pkgsrc.org) prior to this, 0.99.x was the newest available. Binary packages for NetBSD and some other systems should start appearing within a week or two of this message. As before, dovecot-nightly is still available in the pkgsrc-wip package tree, for those who like to live on the edge. -- -- Todd Vierling <tv(a)duh.org> <tv(a)pobox.com> <todd(a)vierling.name>

2 1

RE: [Dovecot] alternate ports?
by Villalovos, John L 10 Feb '06

10 Feb '06

dovecot-bounces(a)dovecot.org <> wrote: > On Thu, Feb 09, 2006 at 02:40:45PM -0800, Gregory K. Ruiz-Ade wrote: > >> I'm trying to set up 1.0 beta 2 on one of our systems, and would >> like to run it on alternate ports from the standard IMAP and >> IMAP/SSL ports so that we can test it out a couple users at a time. >> How does one tell dovecot to listen on alternate ports? I can't >> find anything in the example config file... > > imap_listen = host:port > pop3_listen = host:port I don't think that works in the 1.0b beta 2 (Note: 1.0 beta 3 just came out): Try something like this: # Listen on localhost for IMAP. Listen on all interfaces for IMAP/SSL protocol imap { listen = 127.0.0.1 ssl_listen = * }

1 0

[Dovecot] alternate ports?
by Gregory K. Ruiz-Ade 10 Feb '06

10 Feb '06

I'm trying to set up 1.0 beta 2 on one of our systems, and would like to run it on alternate ports from the standard IMAP and IMAP/SSL ports so that we can test it out a couple users at a time. How does one tell dovecot to listen on alternate ports? I can't find anything in the example config file... Thanks, Gregory -- Gregory K. Ruiz-Ade Sr. Systems Administrator Computer Science and Engineering University of California, San Diego Office: EBU3b 1216 Phone: (858) 822-2625 E-mail: gkra(a)ucsd.edu

3 2

[Dovecot] Openwebmail with Dovecot
by ftnx＠ksbase.com 10 Feb '06

10 Feb '06

So far I've managed to get Dovecot to work fine for regular POP users and Squirrelmail. Even though it seems dead slow and obsolete, a few users would like to use Openwebmail. All users are virtual, and there are/will be no system accounts. Anyone have a working example for Dovecot/Openwebmail for virtual user setup? Kari Suomela KARICO Business Services Toronto, ON Canada http://www.karico.ca

4 5

[Dovecot] epoll error when running as proxy
by Bill Boebel 09 Feb '06

09 Feb '06

I am running dovecot 1.0 beta3 as a front-end proxy, and getting the following error when using epoll. The error goes away if I switch to poll. On the backend IMAP server I see that the login was successful. The error occurs when I try to retrieve an email or get a folder listing via IMAP after logging in successfully... Feb 9 15:35:57 director4 dovecot: imap-login: proxy(bboebel(a)webmail.us): started: user=<bboebel(a)webmail.us>, method=plain, rip=204.119.252.7, lip=192.168.1.68 Feb 9 15:09:50 director4 dovecot: imap-login: io_loop_handle_add: epoll_ctl(op=3, fd=10, ret=-1, errno=2): No such file or directory Feb 9 14:58:23 director4 dovecot: child 9688 (login) returned error 89 I can't find anything in the mailing list archives about this error, so here are some details. I hope somebody can point me in the right direction to fix this. - I am running this on Red Hat ES4 (32-bit x86), compiling with the following options: ./configure \ --prefix=/usr \ --sysconfdir=/etc \ --localstatedir=/var \ --with-ssldir=/usr/share/ssl \ --disable-ipv6 \ --with-file-offset-size=32 \ --with-mem-align=4 \ --with-ioloop=epoll \ --without-passwd \ --without-passwd-file \ --without-shadow \ --without-pam \ --without-checkpassword \ --without-bsdauth \ --without-gssapi \ --with-ldap \ --without-vpopmail \ --with-static-userdb \ --with-prefetch-userdb \ --without-pgsql \ --with-mysql \ --without-sqlite \ --without-ssl \ --with-storages=maildir - I have also complied with these options and got the same error: ./configure \ --prefix=/usr \ --sysconfdir=/etc \ --localstatedir=/var \ --with-ioloop=epoll \ --with-mysql - I have also tried the latest CSV snapshot (dovecot-20060209.tar.gz) and 1.0 beta2, and I get the same error. - If I switch to poll instead of epoll, everything works fine. Any ideas? Bill

1 0

[Dovecot] trouble compiling today's CVS in Solaris 9
by Glenn Leavell 09 Feb '06

09 Feb '06

I've recently been able to compile the CVS code in Solaris 9, but I'm now getting a few errors. First, I receive this error during the autogen process: src/plugins/Makefile.am:5: required directory src/plugins/convert does not exist configure.in:1717: required file `src/plugins/convert/Makefile.in' not found I can workaround that by removing the reference to src/plugins/convert in configure.in. I then get this error: src/plugins/Makefile.am:5: required directory src/plugins/convert does not exist I can workaround that by removing the reference to the convert plugin from src/plugins/Makefile.am. After that, the autogen process completes and I get the previously discussed shell error when running make: if [ "" != "" ]; then \ for i in ; do \ echo "extern struct sql_db driver_${i}_db;" >>sql-drivers-register.c ; \ done \ fi /bin/bash: -c: line 1: syntax error near unexpected token `;' /bin/bash: -c: line 1: `if [ "" != "" ]; then for i in ; do echo "extern struct sql_db driver_${i}_db;" >>sql-drivers-register.c ; done fi' I can workaround that by simply running make from /bin/sh. I then get this error: Making all in auth make[3]: Entering directory `/home/glenn/dovecot/src/auth' /bin/bash ../../libtool --mode=link --tag=CC gcc -std=gnu99 -g -O2 -Wall ... <snip> userdb-prefetch.o userdb-static.o userdb-vpopmail.o userdb-sql.o -L/usr/local/ssl/lib libpassword.a ../lib-settings/libsettings.a ../lib-ntlm/libntlm.a ../lib-sql/libsql.a ../lib/liblib.a -lcrypt -lpam -lldap -ldl -lsocket -lnsl -lrt -lsendfile Undefined first referenced symbol in file sql_drivers_register_all main.o ld: fatal: Symbol referencing errors. No output written to dovecot-auth collect2: ld returned 1 exit status make[3]: *** [dovecot-auth] Error 1 make[3]: Leaving directory `/home/glenn/dovecot/src/auth' I'm not sure why sql_drivers_register_all is getting referenced. I tried explicitly turning off all sql-related options on the configure command line, and that didn't help. Any help would be appreciated. Thanks! Glenn

2 1

[Dovecot] FreeBSD dovecot port maintainer
by Alexander Shikoff 09 Feb '06

09 Feb '06

Hi, How often does mantainer update dovecot in FreeBSD ports tree? It would be a good thing to get 1.0beta3 in ports... -- Kind Regards, Alexander Shikoff minotaur(a)crete.org.ua

1 0

[Dovecot] Re: Dovecot 1.0beta3 - make fails without sql
by Chris Wakelin 09 Feb '06

09 Feb '06

The problem seems to be in src/lib-sql/Makefile[.in] When there are no sql drivers to build, the shell-script for making sql-drivers-register.c fails. I've managed to get it to build by just having #include "lib.h" #include "sql-api.h" void sql_drivers_register_all(void) { } as sql-drivers-register.c Best Wishes, Chris P.S. I meant to send the message below to the whole list rather than just Timo. Sorry! Chris Wakelin wrote: > I'm getting build errors with 1.0-beta3. It looks like something to with > the dynamic SQL drivers; presumably needs equivalent of "-I../lib-sql" > somewhere! > > Configure line was "./configure --prefix=/opt/RDGdovect > --with-ssl=openssl", Solaris make, gcc 3.3.2 > > Best Wishes, > Chris > > Undefined first referenced > symbol in file > sql_drivers_register_all main.o > ld: fatal: Symbol referencing errors. No output written to dovecot-auth > collect2: ld returned 1 exit status > *** Error code 1 > make: Fatal error: Command failed for target `dovecot-auth' > > Timo Sirainen wrote: >> + Added support for loading SQL drivers dynamically (see INSTALL file >> for how to build them) > > -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

2 2

[Dovecot] configuring lda
by Lenny 09 Feb '06

09 Feb '06

after coping lda stanza into the config file, I get "unknown protocol name" error. adding lda to the list of protocols doesn't seem to do the trick. lda was built during compile and the binary is present, piping into it manually spits error messages about missing config, so how do I go about the problem above ? It is my undertanding that using dovecot-lda would help maintain the indexes in proper state ( as opposed to using procmail and having to rebuild indexes from scratch upon delivery of large amounts of mail ) ? mucho gracias to you all. protocol lda { # If you wish to use plugins you need to specify plugin directory # For example quota enforcing is implemented by plugin #module_dir = /usr/local/lib/dovecot/lda # Address from LDA should send MDNs like out of quota postmaster_address = postmaster(a)your.dom # If there is no user-specific Sieve-script, global Sieve script is # executed if set. #global_script_path = # UNIX socket path to master authentication server to find users. auth_socket_path = /var/run/dovecot-auth-master }

2 5

[Dovecot] Broken NSS Implementation
by Campbell McKilligan 08 Feb '06

08 Feb '06

We're getting this error when IMAP clients attempt to authenticate using their aliases rather than their actual username: Feb ... dovecot: auth(default): BROKEN NSS IMPLEMENTATION: getpwnam() lookup returned different user than was requested (campbellmckilligan != campbell.mckilligan). Feb ... dovecot: imap-login: Internal login failure: user=<campbell.mckilligan>, method=plain, rip=82.148.120.110, lip=172.20.2.2, TLS Feb ... dovecot: child 27345 (auth) returned error 89 For historic reasons, there is no consistency with which username in individuals mail client. NSS correctly returns the name that dovecot should use for the purposes of accessing mailboxes etc. Dovecot-0.99.14 worked fine in this regard - but since upgrading to 1.0beta3 we have this problem. It's running on a Fedora Core 4 server. It compiled fine with selinux enabled. Is there a switch to control the response to this NSS behaviour? Any help appreciated. Campbell

2 2

RE: [Dovecot] How to have a "public" readonly folder?
by Villalovos, John L 08 Feb '06

08 Feb '06

dovecot-bounces(a)dovecot.org <> wrote: > I have my email users who are using dovecot-1.0.beta2. I just upgraded to dovecot-1.0.beta3. No change. > I also have setup a dummy account to get the Linux Kernel Mailing > List (LKML) traffic. > > I would like to have it so that my IMAP users (maybe POP3 but > don't need > that) be able to read the LKML mailing list from that email account. > > I can put the email into an mbox or a maildir for the LKML mail. > > I have played around with the namespace and public option and I can't > get it to work :( > > I tried this: > > namespace public { > separator = / > prefix = Public/ > location = maildir:/home/virtemail/lkml/ > } > > In my email client (Mozilla Thunderbird 1.5), I am unable to view the > Public folder. If I select subscribe, I can see the Public folder > but it is grayed out. If I do a symbolic link it works, in the sense that I can know subscribe to the folder. I created the file 'dovecot-shared' in the shared folder (I also updated the Wiki to make the procedure a little bit clearer). I couldn't seem to figure out a good way to make it read only though. So I still can't seem to get the namespace method working. I also tried pointing the location at an mbox and that did not work. In the client I can see the Public folder listed but it is grayed out and won't let me subscribe. Any thoughts? Thanks, John

1 0

Re: [Dovecot] Mail.app message numbering for deleted messages
by Jesse Chan-Norris 08 Feb '06

08 Feb '06

On Mon, 23 Jan 2006, Jesse Chan-Norris wrote: > On Jan 22, 2006, at 6:44 AM, Timo Sirainen wrote: > > On Mon, 2006-01-16 at 18:29 -0500, jcn-dovecot(a)pith.org > wrote: > I'm having a strange problem that appeared when I > upgraded from� > > .99something to 1.0alpha3 and then disappeared for a while and then� > > re-appeared when I upgraded to 1.0alpha5. > > > I am using mbox and IMAP in Apple's Mail.app to read my mail. When I� > > delete a message in Mail.app, the message gets marked as deleted in the� > > spool and it disappears from the mail listing in Mail. However, the� > > message number does not change until I either manually flush the > > deleted� messages through mail, or I go offline which deletes the > > messages from the� spool. > > > I have mbox_lazy_writes set to 'no' but this didn't seem to have any� > > effect on the behavior. I never saw this type of behavior with UW-IMAP� > > either, which is what I migrated from. > > > What do you mean by "message number doesn't change"? > > To me this sounds like it all works as it should. Deleted messages are > really deleted only until expunge command is given, which is done when > you manually select "purge expunged messages" command or whatever it was > called in Mail. > > Maybe before with UW-IMAP you just had some "automatically expunge > messages" option set? I don't think that UW-IMAP was expunging messages because I could open up the mbox with pine and see all of the messages flagged as "Deleted" but not yet expunged. And when I try a similar test with Fastmail.fm (delete the message in Mail, then check using the web interface) the mail is marked as deleted in the web interface and does not show up in Mail.app but the messages are re-numbered appropriately. Granted, I have no idea how Mail.app does its numbering (especially since Thunderbird doesn't have message numbering), but is it possible that there's more information that the IMAP server should be sending back that Dovecot isn't? I've attached a screenshot from my Mail.app that shows the numbering issue. The gaps in the message sequence are where a deleted (but not expunged) message was. jcn

4 3

[Dovecot] Mac mail copy/delete problems w/1.0b2
by Tony Kay 08 Feb '06

08 Feb '06

Hi, Mac mail (a horribly mis-behaved client, it seems), has a horribly hard time deleting/copying large blocks of messages from one folder to another. The basic symptom is: 1. Select a bunch of messages 2. Click on delete 3. Wait for a _very_ long time. It also seems very slow on copying, so it may be the "trash folder copy on delete" that is really slowing it down. Anybody else seen this? -- Anthony Kay University Computing Center (541) 346-1719 GPG Fingerprint: B0DB D46A 60AF FAE7 A94A 5075 0CB4 4D88 9F4F 7F09 The best way to have a good idea is to have a lot of ideas. Dr. Linus Pauling

4 6

[Dovecot] Dovecot does not access /var/mail when using Maildir
by mirko＠mirkonet.nl 08 Feb '06

08 Feb '06

Hello, I'm running debain on my machine with postfix, squirrelmail and dovecot installed. Everything works fine and I'm able to access my mail via squirrelmail and via Outlook with imap. However I want to create subfolders what is not possible. After reading I discovered that I use mbox and that maildir is needed in order to be able to use subfolders. I have created a Maildir folder with the maildirmake.dovecot command in my /home/mirko directory and corrected the owner. Now dovecot uses the Maildir and I can create subfolers. However my problem is that I don't receive Emails in my Inbox. Incoming mails are delivered to /var/mail/mirko, but when dovecot uses Maildir it doesn't access this. I have played with the default_mail_env settings in dovecot.conf which does influence the use of mbox or Maildir. However the problem remains: As soon as Maildir is used, the Inbox is empty and I don't receive Email. Is there a way when Maildir is used to point dovecot to /var/mail/ for the incoming Email? Or do I something else wrong? Your help is appreciated. Greetings, Mirko

3 3

[Dovecot] Out of memory problem
by Neil Wilson 08 Feb '06

08 Feb '06

Hi guys, Running SuSe 9.3 with dovecot 1.0.alpha3 source installation. One of the users has quite a lot of important email in a folder, but when he trys to view this folder, it either sits and waits, and then times out, or just logs out straight away. Looking in the log(/var/log/mail), I'm getting the following error. Feb 6 09:22:08 mail postfix/qmgr[27221]: 198B96D1CE: removed Feb 6 09:22:08 mail dovecot: imap(ralphs): pool_system_malloc(): Out of memory Feb 6 09:22:08 mail dovecot: child 23018 (imap) returned error 83 (Out of memory) I've searched around on google for this error and haven't found anything useful as of yet. My next step is to upgrade to the latest version of dovecot, but this is quite a large company, and I will need to wait until after hours to do the upgrade. Any help would be greatly appreciated. Thanks! Neil Wilson DcData Powered by Linux, driven by passion! -- This email and all contents are subject to the following disclaimer: http://www.dcdata.co.za/emaildisclaimer.html

3 11

[Dovecot] Latest snapshot: ./configure does not finish normally
by Alexander Shikoff 08 Feb '06

08 Feb '06

Hi, OS: FreeBSD 6.0-RELEASE-p2 latest dovecot snapshot does not configurable. ./configure script fails: # ./configure --prefix=/usr/local/dovecot --with-passwd --with-passwd-file --without-shadow --with-pam --without-bsdauth --without-ldap --without-vpopmail --with-static-userdb --without-pgsql --with-mysql --with-pop3d --disable-ipv6 --with-storages [... skip ...] config.status: creating src/pop3/Makefile config.status: creating src/pop3-login/Makefile config.status: creating src/util/Makefile config.status: creating src/plugins/Makefile config.status: error: cannot find input file: src/plugins/convert/Makefile.in Snapshot dated 20060201 is configurable, but `make' fails: # ./configure --prefix=/usr/local/dovecot --with-passwd --with-passwd-file --without-shadow --with-pam --without-bsdauth --without-ldap --without-vpopmail --with-static-userdb --without-pgsql --with-mysql --with-pop3d --disable-ipv6 --with-storages [... skip ...] # make gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -o imap cmd-append.o cmd-authenticate.o cmd-capability.o cmd-check.o cmd-close.o cmd-copy.o cmd-create.o cmd-delete.o cmd-examine.o cmd-expunge.o cmd-fetch.o cmd-idle.o cmd-list.o cmd-login.o cmd-logout.o cmd-lsub.o cmd-namespace.o cmd-noop.o cmd-rename.o cmd-search.o cmd-select.o cmd-sort.o cmd-status.o cmd-store.o cmd-subscribe.o cmd-thread.o cmd-uid.o cmd-unselect.o cmd-unsubscribe.o client.o commands.o commands-util.o imap-expunge.o imap-fetch.o imap-fetch-body.o imap-messageset.o imap-search.o imap-sort.o imap-sync.o imap-thread.o mail-storage-callbacks.o main.o namespace.o -Wl,--export-dynamic ../lib-storage/register/libstorage-register.a ../lib-storage/index/libstorage_index.a ../lib-index/libindex.a ../lib-storage/libstorage.a ../lib-storage/subscription-file/libstorage_subscription_file.a ../lib-imap/libimap.a ../lib-mail/libmail.a ../lib-dict/libdict.a ../lib-charset/libcharset.a ../lib/liblib.a ../lib-storage/register/libstorage-register.a(mail-storage-register.o)(.text+0x7): In function `mail_storage_register_all': /usr/home/minotaur/Soft/dovecot-1.0.beta2/src/lib-storage/register/mail-storage-register.c:6: undefined reference to `yes_storage' *** Error code 1 Stop in /usr/home/minotaur/Soft/dovecot-1.0.beta2/src/imap. *** Error code 1 Stop in /usr/home/minotaur/Soft/dovecot-1.0.beta2/src. *** Error code 1 Stop in /usr/home/minotaur/Soft/dovecot-1.0.beta2. *** Error code 1 Stop in /usr/home/minotaur/Soft/dovecot-1.0.beta2. -- Kind Regards, Alexander Shikoff minotaur(a)crete.org.ua Mob.: +380 67 946 31 49

2 1

[Dovecot] beta3
by Pavel Volkovitskiy 08 Feb '06

08 Feb '06

Does any schedule exist for beta3? I'm now running stable snapshot from cvs, but i don't think it's a good thing, beta2 has memory leak in mysql code So what should i do? apply patch to beta2 or beta3 will be really soon? -- Pavel

1 0

[Dovecot] How to have a "public" readonly folder?
by Villalovos, John L 08 Feb '06

08 Feb '06

I searched the website and the mailing list and had difficulty finding an answer. I have my email users who are using dovecot-1.0.beta2. I also have setup a dummy account to get the Linux Kernel Mailing List (LKML) traffic. I would like to have it so that my IMAP users (maybe POP3 but don't need that) be able to read the LKML mailing list from that email account. I can put the email into an mbox or a maildir for the LKML mail. I have played around with the namespace and public option and I can't get it to work :( I tried this: namespace public { separator = / prefix = Public/ location = maildir:/home/virtemail/lkml/ } In my email client (Mozilla Thunderbird 1.5), I am unable to view the Public folder. If I select subscribe, I can see the Public folder but it is grayed out. Any ideas? Thanks, John

1 0

[Dovecot] Compilation problems (1.0-beta2)
by Jeff Dubin 07 Feb '06

07 Feb '06

Hi Folks, I'm running a minimal, textmode only install of FC4, and I'm trying to compile and install Dovecot 1.0-beta2. I keep getting the following error which I'm hoping someone here can help me troubleshoot. (...) /bin/sh ../../libtool --tag=CC --mode=link gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -L/usr/local/ssl/lib -o dovecot auth-process.o askpass.o dict-process.o log.o login-process.o mail-process.o main.o master-settings.o syslog-util.o ssl-init.o ssl-init-gnutls.o ssl-init-openssl.o ../lib-settings/libsettings.a ../lib/liblib.a mkdir .libs gcc -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -o dovecot auth-process.o askpass.o dict-process.o log.o login-process.o mail-process.o main.o master-settings.o syslog-util.o ssl-init.o ssl-init-gnutls.o ssl-init-openssl.o -L/usr/local/ssl/lib ../lib-settings/libsettings.a ../lib/liblib.a main.o(.text+0x127a): In function `main': /home/jdubin/apps/dovecot-1.0.beta2/src/master/main.c:778: undefined reference to `ssl_check_parameters_file' collect2: ld returned 1 exit status make[3]: *** [dovecot] Error 1 (...) So, I thought it's ssl related. I've compiled openssl (0.9.8a) from source as well (installed in default /usr/local/ssl), and set LDFLAGS=-L/usr/local/ssl/lib and CPPFLAGS=-I/usr/local/ssl/include, but no help. Here's what I'm doing: ./configure --without-pop3d --without-vpopmail --without-ipv6 --with-ssl=openssl make I've even tried to compile without ssl, but I still get that same error. What am I missing here? Perhaps I'm just making a typo somewhere, but I'm totally stumped. Thanks! Jeff

3 3

[Dovecot] Re: MySQL client out of memory error
by Roger Weeks 07 Feb '06

07 Feb '06

Alexander - We had this exact same issue with MySQL authentication. We resolved it by changing this entry in the auth section of the dovecot.conf: # Number of authentication processes to create #count = 1 We set count=20, and then through testing lowered it to count=10. This starts 10 auth-worker processes and to this point we have not had problems with the out of memory condition. -- Roger J. Weeks Systems & Network Administrator Mendocino Community Network Now offering DSL across California On Feb 7, 2006, at 2:00 AM, dovecot-request(a)dovecot.org wrote: > Message: 6 > Date: Tue, 7 Feb 2006 11:33:23 +0200 > From: Alexander Shikoff <minotaur(a)crete.org.ua> > Subject: [Dovecot] MySQL client out of memory error > To: dovecot(a)dovecot.org > Message-ID: <20060207093323.GA31385(a)crete.org.ua> > Content-Type: text/plain; charset=koi8-u > > Hi, > > I'm using Dovecot 1.0-alpha5 as POP3 server with MySQL DB of users. > Sometimes clients get an authentication errors. In this time dovecot > writes to log file next lines: > Feb 7 11:14:30 orion dovecot: auth-worker(default): sql > (user(a)mydomain.com.ua,192.168.3.36) Password query failed: MySQL > client run out of memory > Feb 7 11:14:30 orion dovecot: auth-worker(default): sql > (user(a)mydomain.com.ua,192.168.3.36) Password query failed: MySQL > client run out of memory > Feb 7 11:14:33 orion dovecot: auth-worker(default): sql > (user(a)mydomain.com.ua,192.168.3.36) Password query failed: MySQL > client run out of memory > Feb 7 11:14:33 orion dovecot: auth-worker(default): sql > (user(a)mydomain.com.ua,192.168.3.36) Password query failed: MySQL > client run out of memory > > Can anybody say is there a bug in dovecot or this this issue is > mysql-specific problem? > > Thanks in advance, Alexander > > -- > Kind Regards, Alexander Shikoff > minotaur(a)crete.org.ua

1 0

[Dovecot] Mixed IMAP/POP3 environment: further informations
by Denis Sbragion 07 Feb '06

07 Feb '06

Hello All, some further information. While waiting for some info I'm rolling back to UW and I discovered that if I delete the user "~/Maildir" automatically created by Dovecot, so including any index, the POP3 server works as expected. So it isn't the "Status" flag stored in the mbox file that prevents the download but some status information stored in the IMAP indexes created by Dovecot. I've retried this a couple of times to be sure. Does this helps? Bye, -- Denis Sbragion InfoTecna Tel: +39 0362 805396, Fax: +39 0362 805404 URL: http://www.infotecna.it

2 4

[Dovecot] Dovecot index issues (Solaris/Thunderbird)
by Mario Nigrovic-rvvk40 07 Feb '06

07 Feb '06

Folks - My setup is that my mail is filed (by procmail) in ~/.mail/Maildir, an NFS filesystem. But I'm running Dovecot (1.0alpha5) on my local machine (as myself on port 2143), just to serve this mail to my browser (Thunderbird 1.0.2). The NFS data is on a netapp which seems to be creating .nfs files LIKE CRAZY. I expect these are the remnants of lock files, so I'm trying to move my indexes onto local disk. To that end, I've created /var/tmp/mario/dovecot and put the following into my dovecot.conf: default_mail_env = maildir:%h/.mail/Maildir:INDEX=/var/tmp/mario/dovecot Dovecot happily makes index files, but then fails to serve some of my subscribed folders! Thunderbird is less than helpful in telling me what's going wrong, but dtmail shows that dovecot is reporting "out of sync" and a couple other errors (UID out of sequence), then closing the connection (for those folders). This may happen only after Thunderbird has tried to open the folder that I see these errors with dtmail: Dovecot ready. [UNSEEN 227] First unseen. [UIDNEXT 341] Predicted next UID IMAP connection broken (server response) No-op dead stream [CLOSED] No-op dead stream I've turned mmap off and set locking to fcntl. As a last resort, I've turned indexes off default_mail_env = maildir:%h/.mail/Maildir:INDEX=MEMORY but this makes thunderbird reload all headers every time I open a folder, which takes a very long time. Any suggestions? How do I debug this further? Mario

2 5

[Dovecot] error: mbox-sync-headers
by Ludwig Meyerhoff 07 Feb '06

07 Feb '06

Hallo! I installed dovecot at a customers and it is not working. Neither the 1.0.alpha4 (Debian testing) nor the 1.0.beta2 (Debian unstable) do. in /var/log/mail.err I get following error message over and over again: Feb 7 07:12:02 harmserv dovecot: imap(duerkop): file mbox-sync-rewrite.c: line 106 (mbox_sync_headers_add_space): assertion failed: (start_pos < data_size) Feb 7 07:12:02 harmserv dovecot: child 21001 (imap) killed with signal 6 Please notice the client reads the index but cannot access the contents themself! What does this errormessage mean, and how can I get rid of her? Saluti! Ludwig -- Open WebMail Project (http://openwebmail.org)

2 1

[Dovecot] passwd-userdb with args
by Thomas Wouters 07 Feb '06

07 Feb '06

I'm not sure why the 'passwd' userdb didn't allow args, but it meant (for instance) that the quota plugins weren't usable. I spent quite a bit of time trying to get my new quota-rquotad plugin to work, only to find out that it was my 'quota=rquotad:<filesystem list>' argument that wasn't being passed to the imap child :) The attached patch implements arguments for the 'passwd' userdb, just like it exists for the 'static' userdb (in fact, mostly copy-pasted from 'static'.) It doesn't try to avoid clashing with the values found in the passwd-struct, but I suspect it ends up overwriting them. That could probably be a feature ;) I don't use the passwd-file userdb, but that one would probably also enjoy being argified. -- Thomas Wouters <thomas(a)xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!

2 1

Re: [Dovecot] MySQL client out of memory error
by Jakob Hirsch 07 Feb '06

07 Feb '06

Alexander Shikoff wrote: >> > Can anybody say is there a bug in dovecot or this this issue is >> > mysql-specific problem? >> There was a memory leak fixed in the mysql driver, so you might want to >> use the CVS current, wait for beta3 (better than use alphax, anyway), or >> fix it yourself (should be not that hard). > Thanks a lot! > /me is going to download one of the latest CVS snapshots. You are welcome. I'd say they are usually quite stable and a good way to check if your problem was fixed, even if you only look into the changelog. PS: Please keep list traffic on the list and honour other people's Reply-To header.

1 0

[Dovecot] auth: out of memory
by Branko F. Gračnar 07 Feb '06

07 Feb '06

Hello :) I just couldn't login to my dovecot imap (1.0-beta2). Dovecot authenticates from mysql database. Feb 6 19:47:33 elfstone dovecot: auth-worker(default_with_listener): sql(damirh(a)noviforum.si): User query failed: MySQL client run out of memory Feb 6 19:47:52 elfstone dovecot: auth-worker(default_with_listener): ^GOut of memory (Needed 8164 bytes) Feb 6 19:47:52 elfstone dovecot: auth-worker(default_with_listener): sql(bfg(a)noviforum.si): User query failed: MySQL client run out of memory Feb 6 19:48:19 elfstone dovecot: auth-worker(default_with_listener): ^GOut of memory (Needed 8164 bytes) Feb 6 19:48:19 elfstone dovecot: auth-worker(default_with_listener): sql(bfg(a)noviforum.si): User query failed: MySQL client run out of memory Feb 6 19:48:19 elfstone dovecot: auth-worker(default_with_listener): ^GOut of memory (Needed 8164 bytes) Restarting dovecot solved the problem. Ofcourse, machine didn't run into memory problems. Slackware 9.1, linux 2.6. Best regards, Brane

2 3

[Dovecot] MySQL client out of memory error
by Alexander Shikoff 07 Feb '06

07 Feb '06

Hi, I'm using Dovecot 1.0-alpha5 as POP3 server with MySQL DB of users. Sometimes clients get an authentication errors. In this time dovecot writes to log file next lines: Feb 7 11:14:30 orion dovecot: auth-worker(default): sql(user(a)mydomain.com.ua,192.168.3.36): Password query failed: MySQL client run out of memory Feb 7 11:14:30 orion dovecot: auth-worker(default): sql(user(a)mydomain.com.ua,192.168.3.36): Password query failed: MySQL client run out of memory Feb 7 11:14:33 orion dovecot: auth-worker(default): sql(user(a)mydomain.com.ua,192.168.3.36): Password query failed: MySQL client run out of memory Feb 7 11:14:33 orion dovecot: auth-worker(default): sql(user(a)mydomain.com.ua,192.168.3.36): Password query failed: MySQL client run out of memory Can anybody say is there a bug in dovecot or this this issue is mysql-specific problem? Thanks in advance, Alexander -- Kind Regards, Alexander Shikoff minotaur(a)crete.org.ua

2 1

[Dovecot] dovecot rpms, .subscriptions file, mbox to maildir
by Saurabh Barve 07 Feb '06

07 Feb '06

Hi, I am running dovecot 0.99-14 on a Fedora Core 2 machine. I had a few questions: 1) I wanted to upgrade to the dovecot-1.0 release. However, I am not sure if that's really required. dovecot-0.99-14 has been running very well for me for quite some time. Is there a real advantage to switching to the latest release. The reason I'm asking this is because: i) I don't have too many users to server - around 15 only. ii) My mail server is a pretty fast machine (~1 GHz, 1 GB RAM) machine, so hardware isn't too much of an issue. iii) I like to install software from rpm's. It's not that I can't install from source, but installing from rpm's makes it much easier for me. Just a personal preference. The version of dovecot that I am running was obtained from Dag Wieers web site. I haven't seen a newer version there. I've googled for rpm's for newer versions, and they are available, but I don't want to install it from some third party source that I don't know/trust. iv) I am also planning to support web mail for my users (probably through Squirrelmail). Are there any advantages/disadvantages to upgrading dovecot for that? v) People use Mozilla Mail, Mail.app, Thunderbird, Outlook, and Opera. Does the 1.0 version provide better integration with different mail clients (even though I understand that sometimes it's a problem with the client implementation). So, are there newer version of dovecot (1.0-stable) available in rpm formats which are guaranteed to be safe and un-trojaned? And is there any really good reason why I should upgrade to 1.0-stable? 2) My second question is about creating the .subscriptions (or subscriptions in 1.0) file. When I moved people over from using pine to using a mail client like Evolution/Thunderbird, I had to create .subscriptions/.mailboxlist file for them so that they could see the folders that they had created in pine. However, people still sometimes access e-mail using pine. They then create new folders in pine, which they are unable to see in their mail client. Is there a way around it? This occurs especially when people check their mail at the start of the month, and pine asks about saving/deleting old sent-mail folders, Trash folders. Is there a way to add these folders automagically to the .subscriptions file? 3) Would I be able to support web mail using mailboxes in mbox format, as I have them now? Or do I have to go for Maildir format? Since our university introduced web mail, they have had two sets of folders - one with capitalization (Sent, Deleted Messages, etc.) and one without (sent-mail, etc. - these were from our pine days). Is this due to web mail? Also, if I do need to convert from mbox to Maildir, what is the standard tool for doing that? I saw at least three different tools/scripts for doing that (mbox2maildir,mb2d,mb2md-2,mb2md.pl, .. ). Which tool (and from where) should I use to convert mailboxes without problems? Any help is greatly appreciated. Thanks in advance, Saurabh. ----- sa(a)atmos.colostate.edu

5 12

[Dovecot] Any change of integrating this patch???
by Tony Kay 07 Feb '06

07 Feb '06

There was a patch posted to fix dotfile folder names in this mail: http://www.dovecot.org/list/dovecot/2005-July/008127.html I have a web mail client (which stores preferences in a dot-file/folder through IMAP) and pine users (address book is a dot-folder in IMAP) that this affects. I can certainly hand-apply the patch, but I'd feel a lot more comfortable if this had some future in the real source. -- Anthony Kay University Computing Center (541) 346-1719 GPG Fingerprint: B0DB D46A 60AF FAE7 A94A 5075 0CB4 4D88 9F4F 7F09 I have earned my disillusionment.

1 0

[Dovecot] Newbie question
by Peter Lindgren 07 Feb '06

07 Feb '06

Hi, Finally I managed to build (as ordinary user in my home dir) 1.0b2. (remember, I had problems with db-ldap.h disappeared after compile) What is the (simplest and) safest way to shut down dovecot on the live server and replace the running 0.99.14? I run OpenBSD 3.7 on Sparc. The last step would be 'make install', of course. To shutdown dovecot the last time I resorted to kill processes but I felt I had missed something... the install page (http://wiki.dovecot.org/BasicInstall) says to kill it, it feels a little crude; no nicer signals to send? Bear with me, please... /Peter -- Peter Lindgren, dataingenjör E-post: peter "at" norrskenkonsult punkt com http://www.norrskenkonsult.com

1 0

[Dovecot] Shared maildirs
by Charles Marcus 06 Feb '06

06 Feb '06

Hi, This is the one thing holding me back from switching to Dovecot... Can anyone give a realistic timeframe for when Shred maildirs will be officially supported? Thanks... other than that missing piece, Dovecot rocks! Charles

6 15

[Dovecot] Panic: key not found from hash
by Hans-Jürgen Mehnert 06 Feb '06

06 Feb '06

Hello, we have about 120 servers doing some million mails per day. Most of them use dovecot for pop and imap. In version 1.0.alpha4 we have dovecot-crashes on one or two of the machines in a week where dovecot log says "Panic: key not found from hash" and dovecot dies. We tried version 1.0.beta2 on some machines but with that we have another problem where log says "Error: auth-worker(default): sql((USER),(IP)): Password query failed: MySQL client run out of memory" and the auth process dies. Couldn't find anything usefull on that on the net so i'll ask the list bevor i'll post a bug report. ==================== /etc/dovecot.conf ==================== # dovecot pop3 + imap config (rpm) # SG PN HJM 2005-09-09 ## Main protocols = imap imaps pop3 pop3s # protocols = pop3 pop3s ssl_disable = no ssl_cert_file = /etc/ssl/cert ssl_key_file = /etc/ssl/key disable_plaintext_auth = no log_path = /var/log/dovecot ## Login processes login_processes_count = 2 login_max_processes_count = 128 login_max_logging_users = 256 # Greeting message for clients. login_greeting = Dovecot ready. ## Mail processes max_mail_processes = 1024 verbose_proctitle = yes verbose_ssl = no first_valid_uid = 500 last_valid_uid = 0 first_valid_gid = 0 last_valid_gid = 0 mail_extra_groups = mail_debug = no #default_mail_env = #mail_save_crlf = no #mmap_disable = no #lock_method = fcntl #maildir_stat_dirs = no #maildir_copy_with_hardlinks = no #mbox_read_locks = fcntl #mbox_write_locks = dotlock fcntl #mbox_lock_timeout = 300 #mbox_dotlock_change_timeout = 30 #mbox_dirty_syncs = yes #mbox_very_dirty_syncs = no #mbox_lazy_writes = yes #umask = 0077 #mail_drop_priv_before_exec = no #mail_process_size = 256 #mail_log_prefix = "%Us(%u): " ## IMAP specific settings protocol imap { imap_max_line_length = 65536 login_greeting_capability = no imap_client_workarounds = outlook-idle mail_use_modules = yes mail_modules = /usr/lib/dovecot/imap } ## POP3 specific settings protocol pop3 { pop3_no_flag_updates = no pop3_enable_last = yes pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = outlook-no-nuls oe-ns-eoh mail_use_modules = yes mail_modules = /usr/lib/dovecot/pop3 } ## Authentication processes auth_verbose = no auth_debug = no auth_worker_max_count = 30 auth default { mechanisms = plain # SQL database - normal passdb sql { args = /etc/dovecot-sql.conf } # SQL database - normal userdb sql { args = /etc/dovecot-sql.conf } user = root count = 1 } ==================== /etc/dovecot-sql.conf ==================== driver = mysql connect = host=/var/lib/mysql/mysql.sock dbname=(DB) user=(DBUSER) password=(DBPWD) default_pass_scheme = CRYPT password_query = SELECT pwhash AS password, user FROM mail_mailboxes WHERE (user = '%n' AND active = 'Y' AND (type != 'smtp') AND (type = 'imap' OR '%s' = 'pop3')) OR (mainuser = '%n' AND user = CONCAT('%n','mail0') AND (type != 'smtp') AND (type = 'imap' OR '%s' = 'pop3')) user_query = SELECT location AS home, uid, gid, user AS system_user FROM mail_mailboxes WHERE (user = '%n') OR (mainuser = '%n' AND user = CONCAT('%n','mail0')) ==================== table structure ==================== CREATE TABLE mail_mailboxes ( mainuser varchar(128) NOT NULL default '', domain varchar(128) NOT NULL default '', user varchar(128) NOT NULL default '', addr varchar(128) NOT NULL default '', type set('pop3','imap','smtp') NOT NULL default 'pop3', active set('Y','N') NOT NULL default 'Y', pwhash varchar(255) NOT NULL default 'unset', quota int(11) NOT NULL default '0', location varchar(255) NOT NULL default 'unset', uid int(11) NOT NULL default '0', gid int(11) NOT NULL default '0', PRIMARY KEY (user) ) TYPE=MyISAM;

2 1

[Dovecot] Mixed IMAP/POP3 environment and message status flags
by Denis Sbragion 06 Feb '06

06 Feb '06

Hello All, I'm trying to migrate from UW Imap to Dovecot (latest 1.0 beta 2). The target is to go from the actual environment (Eudora + POP3) to a web based IMAP environment (IMAP + SquirrelMail). While migrating we will need to keep both environments for some time, with users having both the ability to use Eudora through POP3 while in the office and also the ability to check e-mail using the web based interface from time to time when they are out of office. Everything seems to work pretty well except for one little quirk. Whenever new mail messages are checked on-line through IMAP they are marked with "Status: O" or "Status: RO" in the main INBOX file (which is kept in the old mbox format now, and is one of the many reasons for the Dovecort choice). This is correct following the RFC standards but after that the POP3 server seems to completely ignore any message marked as "O" or "RO", making it impossible to download previously seen/read messages through Eudora. I've checked any available Eudora and Dovecot setting, including the pop3_no_flag_updates flag, but so far nothing worked. Looking at mailing list archives it looks like this behaviour is intentional and has been introduced to work around some problems with Eudora when the "Leave mail on server" option is enabled. Nevertheless it seems there's still something wrong. UW Imap seems to get this right, it lets Eudora download the already read message, which are correctly downloaded already marked as read. I haven't been able to identify the source of the problem, i.e. if it is either an Eudora problem which UW circumvent in some way or a real Dovecot problem. I'd really like to move to Dovecot, which provides many feature which are really useful for our situation, expecially maildir folders, which are fast and much more "differential backup" friendly than single file mailboxes. Unfortunately this IMAP/POP3 interaction problem would be a major showstopper because it will prevent a smooth migration from the old environment to the new one. Any hint about this issue? Anybody faced a similar problem so far? Thanks in advance for any help, and my compliments for the excellent job performed so far. Dovecot seems to be the right tool to fill the gap between the simpler UW and the Cyrus monster. Keep on going! :) Bye, -- Denis Sbragion InfoTecna Tel: +39 0362 805396, Fax: +39 0362 805404 URL: http://www.infotecna.it

1 0

[Dovecot] dovecot-cvs/mysql-5.0.18 OLD/PASSWORD problem
by John Wong 06 Feb '06

06 Feb '06

i use openbsd/i386, dovecot-cvs(today), mysql-5.0.18 today, i change the mysql_dbuser_password form OLD_PASSWORD to PASSWORD then dovecot can't connect to mysql-server shell$> mysql -u root -p mysql$> SET PASSWORD FOR 'db_user'@'localhost' = PASSWORD('db_pw'); now, dovecot CAN NOT connect to mysql-server shell$> mysql -u root -p mysql$> SET PASSWORD FOR 'db_user'@'localhost' = OLD_PASSWORD('db_pw'); now, dovecot CAN connect to mysql-server and everything work fine i patched src/lib-sql/driver-mysql.c to test, use something like: i_error("host(%s), db->user(%s), db->password(%s), db->dbname(%s) ....); before mysql_real_connect(), then see the maillog, the db->user/password/dbname is correct maillog: auth-worker(default): conn->mysql is NOT NULL auth-worker(default): host((null)), db->user(db_user), db->password(db_pw), db->dbname(dbname), db->port(0), unix_socket(/mysql.sock), db->client_flags(0) auth-worker(default): failed: (1) auth-worker(default): mysql: Connect failed to (null) (dbname): Access denied for user 'db_user'@'localhost' (using password: YES) - waiting for 1 seconds before retry i wrote a small c program to test, it can success connect to mysql, use same user/password/dbname, with both OLD_PASSWORD/PASSWORD why dovecot can't to connect to mysql-server with PASSWORD? help please, thank you base_dir = /var/dovecot/ ssl_cert_file = /etc/ssl/certs/mail.crt ssl_key_file = /etc/ssl/private/mail.key disable_plaintext_auth = no login_dir = /var/dovecot/login login_user = _dovecot valid_chroot_dirs = /var/spool/postfix/var default_mail_env = maildir:%h/%u mmap_no_write = yes protocol imap { imap_client_workarounds = delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep } protocol pop3 { pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } auth default { mechanisms = plain passdb sql { args = /etc/dovecot-sql.conf } userdb static { args = uid=32765 gid=32765 home=/var/spool/postfix/var/./mail } user = _dovecot-auth chroot = /var/dovecot/auth socket listen { client { path = /var/spool/postfix/private/dovecot-auth mode = 0600 user = _postfix } } } driver = mysql connect = host=/mysql.sock dbname=dbname user=db_user password=db_pw default_pass_scheme = PLAIN-MD5 password_query = SELECT password FROM users WHERE userid = '%n' AND %Ls = '1' AND active = '1' --- src/lib-sql/driver-mysql.c.orig Mon Feb 6 23:07:42 2006 +++ src/lib-sql/driver-mysql.c Mon Feb 6 23:39:36 2006 @@ -112,11 +112,17 @@ } alarm(MYSQL_CONNECT_FAILURE_TIMEOUT); + i_error("conn->mysql is %s NULL", conn->mysql == NULL ? "" : "NOT"); + i_error("host(%s), db->user(%s), db->password(%s), db->dbname(%s), " + "db->port(%u), unix_socket(%s), db->client_flags(%u)", + host, db->user, db->password, db->dbname, db->port, unix_socket, + db->client_flags); failed = mysql_real_connect(conn->mysql, host, db->user, db->password, db->dbname, db->port, unix_socket, db->client_flags) == NULL; alarm(0); if (failed) { + i_error("failed: (%i)", (int)failed); if (conn->connect_failure_count > 0) { /* increase delay between reconnections to this server */

1 0

[Dovecot] nearly there
by ohp＠pyrenet.fr 05 Feb '06

05 Feb '06

Hi Timo et all. At last I found with unix socket wouldn't connect and it works now. However after auth, imap crashes with signal 6. This happens on 1 machine, the other (unixware too) work fine. The stack trace doesn't make much sense here it is anway... Core image of imap (process p1) created CORE FILE [makedev in cmd-status.c(a)sys/mkdev.h] SIGNALED 8 (fpe code[FPE_INTDIV] address[0x804e38b]) in p1 76: return __makedev(ver, maj, min); debug> Stack Trace for p1, Program imap *[0] makedev(maj=16, min=1, presumed: 0x8094258) [cmd-status.c@sys/mkdev.h@76] [1] cmd_store(cmd=0x0, presumed: 0x1, 0x80947a0) [cmd-store.c@139] [2] _cmd_select_full(cmd=0x8072498, readonly=false) [cmd-select.c@84] [3] cmd_store(cmd=0x10, presumed: 0x807d184, 0x8047cac) [cmd-store.c@74] [4] minor(dev=134511756, presumed: 0x8055266, 0x8047cac) [cmd-subscribe.c@sys/mkdev.h@112] [5] imap_search_args_build(pool=0x8047cac, box=0x8047cb4, args=0x8047ca0, error_r=0x804ebc1) [imap-search.c@416] [6] imap_search_get_uidset_arg(pool=0x1, box=0x8047cac, uidset="\215}\004\b\235}\004\b\245}\004\b\020\220\b\b\313}\004\b\335}\004\b\357}\004\b", arg_r=0x0, error_r=0x0, 0x1) [imap-search.c@447] [7] cmd_append_cancel(ctx=0x8047cb4, nonsync=true, presumed: 0) [cmd-append.c@158] [8] ?() [0] debug> The log says Trying to allocate 0 bytes and imap gets killed. Does it ring any bells? -- Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) 15, Chemin des Monges +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: ohp(a)pyrenet.fr ------------------------------------------------------------------------------ Make your life a dream, make your dream a reality. (St Exupery)

2 2

[Dovecot] vpopmail authentification broken in dovecot 1.0beta
by daniel petre 05 Feb '06

05 Feb '06

hello, i got * net-mail/dovecot Latest version available: 1.0_beta2 Latest version installed: 1.0_beta2 Size of files: 1,309 kB Homepage: http://dovecot.org/ Description: An IMAP and POP3 server written with security primarily in mind License: LGPL-2.1 and since dovecot-0.99.14-r1 authentification doesnt work no more. i posted something similar with dovecot-1.0_alpha5 but all the answers i got were like "it isnt dovecot's fault, its vpopmails". bummer, my vpopmail did not changed , but dovecot versions yes. so i think dovecot is broken with vpopmail auth. i edited dovecot.conf and enabled all the parts related to vpopmail correctly like in old dovecot.conf here's what i receive in the log: dovecot: Jan 31 14:51:28 Info: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=81.18.x.x rip=81.18.x.x resp= dovecot: Jan 31 14:51:28 Info: auth(default): client out: CONT 1 dovecot: Jan 31 14:51:28 Info: auth(default): client in: CONT 1 AGRhbmlAbGlgudXhzb2x1fdGlvbnMucmh8AcG9jcG9j dovecot: Jan 31 14:51:28 Error: auth(default): vmysql: sql error[3]: MySQL server has gone away dovecot: Jan 31 14:51:28 Info: auth(default): vpopmail(dani(a)domain.ro,81.18.x.x): unknown user dovecot: Jan 31 14:51:29 Info: auth(default): client out: FAIL 1 user=dani(a)domain.ro dovecot: Jan 31 14:51:29 Info: auth(default): client in: AUTH 2 PLAIN service=POP3 lip=81.18.x.x rip=81.18.x.x resp=AGRhbmlAbGlgudXhzb2x1fdGlvbnMucmh8AcG9jcG9j dovecot: Jan 31 14:51:29 Error: auth(default): vmysql: sql error[3]: MySQL server has gone away dovecot: Jan 31 14:51:29 Info: auth(default): vpopmail(dani(a)domain.ro,81.18.x.x): unknown user dovecot: Jan 31 14:51:31 Info: auth(default): client out: FAIL 2 user=dani(a)domain.ro i tried compiling dovecot with and without mysql support and the log is the same. vpopmail support is compiled in. so i use only vpopmail auth, no passdb, no mysql, no ssl. anyone can help with this error? coz dovecot seems such a nice imap/pop3 daemon but so much broken since last 0.9 version which is a shame.. thank you. -- Daniel Petre System Administrator Tech Support Coordinator ............................................................................. RCS & RDS Pitesti Tel.: +40348.400.401 Fax: +40348.400.441 http://www.rcs-rds.ro ............................................................................. Privileged/Confidential Information may be contained in this message. If you are not in the addresses indicated in this message (or responsible for delivery of the message to such person), you may not copy or deliver this message to anyone. In such a case, you should destroy this message and kindly notify the sender by reply e-mail.

2 1

[Dovecot] default_mail_env auto-detect woes for maildir users
by David Friedlander 05 Feb '06

05 Feb '06

Hello-- I am a fairly new dovecot user and have run into a problem. I am running dovecot 1.0alpha5 (built from source) on a Fedora Core 1 machine. The system has about 400 users with over 80 IMAP users, and we have just transitioned from UW-IMAP. Thus all users are currently still mbox users. I would like to transition them to maildir users (this was the main point for me switching servers), and I chose dovecot because it could simultaneously support both formats. My dovecot.conf uses auto_detect (no default_mail_env defined, by choice). Auto-detect is working fine for mbox users, as shown by this (edited) log snippet: dovecot: imap(janeuser): maildir: couldn't find root dir dovecot: imap(janeuser): mbox: root exists (/Home/janeuser/mail) dovecot: imap(janeuser): mbox: INBOX exists (/var/mail/janeuser) dovecot: imap(janeuser): mbox: root=/Home/janeuser/mail, index=/Home/janeuser/mail, inbox=/var/mail/janeuser However, for another user who already has ~/Maildir and a proper maildir-format spool location ( /var/mail/joeuser/{cur|new|tmp} ) the log shows: dovecot: imap(joeuser): maildir: root exists (/Home/joeuser/Maildir) dovecot: imap(joeuser): maildir: root=/Home/joeuser/Maildir, index=/Home/joeuser/Maildir, control=, inbox= (Mail clients show no messages, but one can see them from the UNIX shell and with mutt on the server.) If I set default_mail_env = maildir:~/Maildir:INBOX=/var/spool/mail/%u then everything works fine for 'joeuser'. However, I need auto-detect during this transition phase. My questions, please: * How do I get INBOX ("inbox=") to be properly defined/detected? * Must I do this with namespaces, and how does that affect the fact that there will be a transition period where some users use mbox and others use maildir? * Other advice? I have been unable to track this down so far, between reading the Dovecot documentation and Googling the dovecot mailing list archives. Thanks in advance, David

2 2

[Dovecot] Support for Kmail maildir format
by Graham Cobb 04 Feb '06

04 Feb '06

Has anyone looked into providing support in dovecot for Kmail folders? I would like to make my Kmail folders (on my main desktop system) available to my other systems (including over a VPN when I am travelling). Kmail is my main mail program and I have a lot of mail in a lot of folders, so I don't want to set up a separate IMAP service and move all the mail and folders. Kmail's use of maildir seems to folow the basic maildir approach except that sub-folders are handled differently. If you create a folder (say it is called ABC) in Kmail and start putting mail in it, Kmail creates a directory on the disk called ABC (not .ABC) and creates the cur, new and tmp folders within it to contain the email. If you then create a subfolder of ABC (say it is called DEF, contained within the ABC folder), Kmail creates a directory on the disk called .ABC.directory and creates the DEF directory within that. In other words, maildir directories are given the same name as the mail folder (with no leading dot) but sub-folders are contained in disk directories called .<folder-name>.directory. I have taken a quick look at the dovecot code and am fairly sure this could be handled by a variant on the existing maildir code (e.g. by changes to maildir_fill_readdir and other routines). Has anyone tried this? Graham

5 12

[Dovecot] rquotad (NFS) quota plugin
by Thomas Wouters 03 Feb '06

03 Feb '06

The attached patch is an updated version of my quota-rquotad patch for the quota plugin. Like quota-fs, it only does quota reporting, not enforcing or changing. It also only works on FreeBSD, and possibly other *BSD's. It lacks any and all configure-time tests to see if RPC is even supported, and hardcodes the (Free)BSD way of getting at the NFS server of an NFS mount. I'm mostly mailing it around to avoid duplicate work, in case anyone is looking for it. I do intend to generalize the plugin-patch, and add proper configure checks, I just haven't gotten around to testing it on other BSD systems. Linux support would be nice, but getting at the NFS server of an NFS mount is apparently quite a hassle, as it means reading /etc/mtab or /proc/self/mounts. Yuck. -- Thomas Wouters <thomas(a)xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!

1 0

[Dovecot] mbox to maildir conversion on a user-by-user basis!
by Tony Kay 03 Feb '06

03 Feb '06

In the midst of evaluating Dovecot for use in solving some mbox locking issues (while also waiting for our eventual migration to maildir), I had an epiphany. It looks like Dovecot's auto-detection of mail formats would allow us to migrate from mbox to maildir on a user-by-user basis! I was thinking: 1. Let dovecot autodetect mail storage 2. Use some procmail trickery to detect which format to deliver into (I am researching how to do the detection on a user-by-user basis) 3. Manually convert users as you want by: - Temporarily disable mail delivery for that user (at least make it look like the inbox is locked) - Run conversion on mbox files -> maildir format - Put in the procmail hack for them - Re-enable delivery Way cool. I am still working out the details, but I was wondering if anyone sees a problem with this??? -- Anthony Kay University Computing Center (541) 346-1719 GPG Fingerprint: B0DB D46A 60AF FAE7 A94A 5075 0CB4 4D88 9F4F 7F09 Sanity is a cozy lie. Susan Sontag

2 1

[Dovecot] not creating homedirs when using maildir format
by Ben Halicki 03 Feb '06

03 Feb '06

Hi all, I'm in the process of setting up dovecot, but for some reason, it's not creating home directories if they don't already exist. I have the following line in dovecot.conf: default_mail_env = maildir:~/mail:INBOX=/var/mail/%u I have set permissions on /home to allow everyone full access, so creating directories in /home by dovecot non-root processes shouldn't be a problem. If I instruct dovecot to use mbox format, directories are created without a problem. The problem only seems to exist with maildir. Any help would be greatly appreciated! Thanks and regards, Ben Halicki Information Technology Officer Macquarie Textiles Group Limited Phone: +61 2 6043 0235 Fax: +61 2 6041 1321

4 3

[Dovecot] Dovecot(imap) problem
by Clovis Tristao 03 Feb '06

03 Feb '06

Feb 1 20:13:15 myhost imap(someuser): file mbox-rewrite.c: line 429 (mbox_write_header): assertion failed: (hdr_parsed_size.physical_size == hdr_size) I'm using Fedora Core 4, dovecot 0.99.14-4. Any idea? How to fix this problem? Thanks a lot, Clóvis -- Clovis Tristao - UNICAMP/Faculdade de Engenharia Agricola Administrador de Redes - Secao de Informatica (SINFO) E-mail: mailto:clovis@agr.unicamp.br http://www.agr.unicamp.br Fone(0xx19) 37881031-37881038 ou FAX(55xx19) 37881005/37881010

4 3

Re: [Dovecot] not creating homedirs when using maildir format
by Ben Halicki 02 Feb '06

02 Feb '06

"Ben Halicki" <ben.halicki at macquarietextiles.com.au> writes: > Hi all, > > I'm in the process of setting up dovecot, but for some reason, it's not > creating home directories if they don't already exist. > > I have the following line in dovecot.conf: > > default_mail_env = maildir:~/mail:INBOX=/var/mail/%u > > I have set permissions on /home to allow everyone full access, so > creating directories in /home by dovecot non-root processes shouldn't be > a problem. If I instruct dovecot to use mbox format, directories are > created without a problem. The problem only seems to exist with maildir. > > Any help would be greatly appreciated! Never done this, ISTR there is a PAM module that is supposed to do this (create the directory). It would require you to use PAM, obviously. -- Matthias Andree Thanks for the reply Matthias. Only problem with PAM and pam_mkhomedir, is that Dovecot doesn't seem to open a session, so pam isn't called and pam_mkhomedir doesn't get the chanceto create a home directory. I can't understand why this works with mbox, but not withmaildir!Thanks again,Ben HalickiInformation Technology OfficerMacquarie Textiles Group LimitedPhone: +61 2 6043 0235Fax: +61 2 6041 1321

1 0

Re: [Dovecot] Question about Dovecot and NFS
by Tony Kay 02 Feb '06

02 Feb '06

On Thu, 02 Feb 2006 11:48:02 +0200, Timo Sirainen <tss(a)iki.fi> wrote: > -- SNIP -- > As long as both hosts keep using dotlocking, Dovecot should be able to > handle the above without any corruption problems. > > > I did some testing w/dovecot 0.99 earlier in this same config, > > Forget those results and try with 1.0beta instead :) > I ran tests on 1.0b2. I could _not_ make dovecot misbehave on NFS w/two physical servers accessing the same mailbox. All of the "undesirable" things that happened (i.e. really poorly written clients suffering strange views of the mailbox due to their own stupidity) were well within IMAP spec., and are non-destructive/lossy. Kudos Timo! Thanks for writing some really excellent code. -- Anthony Kay University Computing Center (541) 346-1719 GPG Fingerprint: B0DB D46A 60AF FAE7 A94A 5075 0CB4 4D88 9F4F 7F09 The camera makes everyone a tourist in other people's reality, and eventually in one's own. Susan Sontag

1 0

[Dovecot] SRC.RPM for dovecot (cvs-2006-01-30) with lda
by Sergey Ivanov 02 Feb '06

02 Feb '06

Hi, there is dovecot.src.rpm for ALTLinux, (dovecot beta2 with sieve local delivery agent) uploaded to http://ftp.altlinux.org/pub/distributions/ALTLinux/Daedalus/SRPMS.daedalus/… -- Sergey Ivanov

1 0

Re: [Dovecot] Question about Dovecot and NFS
by Tony Kay 02 Feb '06

02 Feb '06

On Wed, 01 Feb 2006 11:45:16 +0200, Timo Sirainen <tss(a)iki.fi> wrote: > On Tue, 2006-01-31 at 22:42 -0800, Tony Kay wrote: > > How does dovecot handle this kind of conflict. I.e. how would one dovecot IMAP on server A detect that dovecot on server B had rewritten something like flags on the mailbox they are both accessing? I'm sure it doesn't leave the dot lock sitting around, since that would block mail delivery. > > It just checks if mbox's mtime has changed. If it has, it checks if > there are new mails or if it needs to do some other synchronization > (mbox_dirty_syncs / mbox_very_dirty_syncs causes it to delay it as long > as possible). > > UW-IMAP also checks if mtime has changed, but instead of trying to > figure out what changed it just disconnects the client with an > "unexpected mbox change" error. UW uses a "kiss of death" signal for collaborative locking...the mtime changes are all assumed to be appends as far as I know. The problem (which I can reproduce) comes with a situation like this: - IMAP host A and B access INBOX for the same user from different physical servers which share the inbox via NFS - Neither sees the other (because UW imap assumes lingering opens come from c-client apps, and it uses signals/flock/tmp to sync them, which are not available when A and B are on separate hosts). - Delete and expunge a message on B - 'A' can still read the expunged message. - Mark two messages for delete on A, including the one previously expunged by B - New message delivered to inbox (possibly by yet another host) - Expunge on A - New message is lost My theory is that the two IMAPs are both holding a fd open, and this causes one of the copies to become stale (in the sense it no longer has a filesystem name). The new mail is delivered to the non-stale box, and then the expunge on 'A' causes the stale open file to be "rewritten" over the top of the non-stale one. Result: mail loss. We also see things like message flags that magically reset themselves, etc. I did some testing w/dovecot 0.99 earlier in this same config, and it seems like it has some issues. For example a delete/expunge on IMAP A was "sort-of" seen by the B (fetch complained that the UIDs had changed, and would not work until a NOOP was done...this is technically OK), but B magically restored the deleted message with a new UID (which is not so good, since a client that caches stuff may now have a strange view of the world...I need to examine the set of "update" notices that went along with these events to better understand the implications). This also worries me because the "magic" reappearance indicates a copy from a stale fd, which could exhibit the same mail loss I produced w/UW IMAP. I am planning on updating to your latest source tree tomorrow (I am out of time today), and see if I can make it "lose" new mail. Opinions??? Thanks! Tony

2 1

[Dovecot] Can't send mail through new server
by Anne Wilson 02 Feb '06

02 Feb '06

I thought I had just about got the old server to the point of being switched off. I have been reading from the dovecot server for a couple of days, and this evening I switched the 'sending' to the new server as well - but I couldn't get anything out. I got: Error while uploading message Could not upload the message dated Wed Feb 1 21:2:56 2006 from Anne Wilson <cannewilson(a)tiscali.co.uk> with subject "xxx" on the server. The destination folder was sent-mail, which has the URL . The error message from the server communication is here: APPEND failed: Can't open append mailbox : Read-only file system ---------- I also got messages like: Error while retrieving messages from the server. Unable to open folder sent-mail. The server replied: SELECT failed: Mailbox open failed, aborted: Read-only file system. --------------- I like to save the sent-mail and trash on the server. ~/Maildir has all the folders including sent-mail and trash. I have the same UID on both boxes. What has gone wrong? Anne -- Registered Linux User No.293302 (http://counter.li.org/)

2 2

[Dovecot] Can't send mail from new server
by Anne Wilson 02 Feb '06

02 Feb '06

I thought I had just about got the old server to the point of being switched off. I have been reading from the dovecot server for a couple of days, and this evening I switched the 'sending' to the new server as well - but I couldn't get anything out. I got: Error while uploading message Could not upload the message dated Wed Feb 1 21:2:56 2006 from Anne Wilson <cannewilson(a)tiscali.co.uk> with subject "xxx" on the server. The destination folder was sent-mail, which has the URL . The error message from the server communication is here: APPEND failed: Can't open append mailbox : Read-only file system ---------- I also got messages like: Error while retrieving messages from the server. Unable to open folder sent-mail. The server replied: SELECT failed: Mailbox open failed, aborted: Read-only file system. --------------- I like to save the sent-mail and trash on the server. ~/Maildir has all the folders including sent-mail and trash. I have the same UID on both boxes. What has gone wrong? Anne -- Registered Linux User No.293302 (http://counter.li.org/)

1 0

[Dovecot] Can't send from the new server
by Anne Wilson 02 Feb '06

02 Feb '06

I thought I had just about got the old server to the point of being switched off. I have been reading from the dovecot server for a couple of days, and this evening I switched the 'sending' to the new server as well - but I couldn't get anything out. I got: Error while uploading message Could not upload the message dated Wed Feb 1 21:2:56 2006 from Anne Wilson <cannewilson(a)tiscali.co.uk> with subject "xxx" on the server. The destination folder was sent-mail, which has the URL . The error message from the server communication is here: APPEND failed: Can't open append mailbox : Read-only file system ---------- I also got messages like: Error while retrieving messages from the server. Unable to open folder sent-mail. The server replied: SELECT failed: Mailbox open failed, aborted: Read-only file system. --------------- I like to save the sent-mail and trash on the server. ~/Maildir has all the folders including sent-mail and trash. I have the same UID on both boxes. What has gone wrong? Anne -- Registered Linux User No.293302 (http://counter.li.org/)

1 0

[Dovecot] extremely slow delete/move operations?
by Gregory K. Ruiz-Ade 01 Feb '06

01 Feb '06

I've been working to migrate several hundered users on to our new mail servers, which run dovecot 0.99.11 (RHEL4). The problem I'm seeing is that deleting or moving a message seems to take a very long time. It's not uncommon for Thundirbird (1.0.7) to have delays of 5-10 seconds to delete a single message from my Inbox (<500k) and place it in my Trash folder (~100MB right now). The systems are Dell PowerEdge 1850 (dual 3.6GHz Xeon) with two 300GB SCSI drives in a hardware mirror. Filesystems are ext3 on LVM. Inboxes are on /var/spool/mail (/export/mail, symlinked into /var). User mail folders are in their home directories (/export/homes1/<user>, automounted to /home/<user>; some home directories are NFS automounted from a NetApp). Both the mail spool and home directories are available over NFS for compatibility reasons with the former setup. What's really bugging me is that I've used the same software (RHEL4 and dovecot 0.9x.x) at my last workplace, and the performance was outstanding; it beat UWIMAPd hands-down, especially with large mailboxes. Here, the opposite seems to be true. The primary difference seems to be that we're using NFS here, but I wasn't using NFS at my last job. I'm getting a lot of grief over the delays when users delete mail or move mail from their inbox to one of their mail folders. Enough so that they're now resisting moving to the new server. Where do I look to find out what's causing the slowness? What can I do to make it faster? Mailbox formats are mbox. Using these options in /etc/dovecot.conf: ----- protocols = imaps pop3s imap_listen = [::] pop3_listen = [::] ssl_cert_file = /usr/share/ssl/certs/csefast.ucsd.edu_cert.pem ssl_key_file = /usr/share/ssl/private/csefast.ucsd.edu_key.pem login_dir = /var/run/dovecot-login login = imap login = pop3 verbose_proctitle = yes first_valid_uid = 100 default_mail_env = mbox:~/:INBOX=/var/mail/%u mail_full_filesystem_access = yes mbox_locks = dotlock fcntl auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = pam auth_user = root ----- Thanks in advance, Gregory -- Gregory K. Ruiz-Ade Sr. Systems Administrator Computer Science and Engineering University of California, San Diego Office: EBU3b 1216 Phone: (858) 822-2625 E-mail: gkra(a)ucsd.edu

9 10

Re: [Dovecot] Question about Dovecot and NFS
by Timo Sirainen 01 Feb '06

01 Feb '06

On Tue, 2006-01-31 at 22:42 -0800, Tony Kay wrote: > How does dovecot handle this kind of conflict. I.e. how would one dovecot IMAP on server A detect that dovecot on server B had rewritten something like flags on the mailbox they are both accessing? I'm sure it doesn't leave the dot lock sitting around, since that would block mail delivery. It just checks if mbox's mtime has changed. If it has, it checks if there are new mails or if it needs to do some other synchronization (mbox_dirty_syncs / mbox_very_dirty_syncs causes it to delay it as long as possible). UW-IMAP also checks if mtime has changed, but instead of trying to figure out what changed it just disconnects the client with an "unexpected mbox change" error.

1 0

[Dovecot] Immutable Maildir (or: "I know drag&drop")
by Michael Renner 31 Jan '06

31 Jan '06

Hi, I'm 'constantly' (every odd month) faced with users happily dragging around or (un)subscribing folders in our shared IMAP account. Is there a "clean" way to prevent users from doing that when having a Maildir? Unix permissions probably won't cut the slack since setting any Maildir (sub)directory to readonly (immutable or chmod u-w ) will probably cause dovecot to hit a wall at high speed sooner or later (lock files, rotated cache/log files) Got any other ideas? best regards, Michael Renner

2 1

[Dovecot] Question about Dovecot and NFS
by Tony Kay 31 Jan '06

31 Jan '06

Hi, We are using mbox and UW IMAP, and are having issues because UW IMAP does not support multiple client access when you use NFS for the mail files. I've done some research (see the comments after my 2 questions below), and most of the other major IMAP servers simply don't support it (courier is about the only one that has a positive comment). How much testing have you done w/NFS-mounted mail in mbox format? Have you found a reliable way to handle NFS mbox files? The UW IMAP docs say that multiple client access to mail spools that are NFS mounted is not safe, and the source has comments like this about NFS mail spools: /* Make fcntl() locking of NFS files be a no-op the way it is with flock() * on BSD. This is because the rpc.statd/rpc.lockd daemons don't work very * well and cause cluster-wide hangs if you exercise them at all. The * result of this is that you lose the ability to detect shared mail_open() * on NFS-mounted files. If you are wise, you'll use IMAP instead of NFS * for mail files. * * Sun alleges that it doesn't matter, because they say they have fixed all * the rpc.statd/rpc.lockd bugs. This is absolutely not true; huge amounts * of user and support time have been wasted in cluster-wide hangs. */ Cyrus' FAQ says this about NFS mail spools: (http://asg.web.cmu.edu/cyrus/imapd/install-FAQ.html#nfs) NFS (don't) Q: Weird things are happening. The mailspool is mounted over NFS, and... A: Don't mount the mail spool over NFS. Due to locking problems with NFS, this doesn't work (and for various other reasons, probably isn't worth the bother; IMAP appears to be I/O bound, not CPU bound, and scaling in this way is not a good idea). More specifically, if you use NFS and it looks to work, you may have locking problems in the future which will result in silently lost mail. If you use NFS and things go berzerk, it's because mmap(2) apparently has different semantics on local disk than it has on NFS. You can get the above behavior (silently lost mail) if you work at it. Courier is the only one that seems friendly (excerpt from their web site): Courier-IMAP is popular on Qmail/Exim/Postfix sites that are configured to use maildirs. The primary advantage of maildirs is that multiple applications can access the same Maildir simultaneously without requiring any kind of locking whatsoever. Maildir is a faster and more efficient way to store mail. It works particularly well over NFS, which has a long history of locking-related woes. -- Anthony Kay University Computing Center (541) 346-1719 GPG Fingerprint: B0DB D46A 60AF FAE7 A94A 5075 0CB4 4D88 9F4F 7F09 When they discover the center of the universe, a lot of people will be disappointed to discover they are not it. Bernard Bailey

3 2

[Dovecot] worth a few Euros?
by -- -- 31 Jan '06

31 Jan '06

Yo Timo, did you say that login processes "just don't crash"? Found these while doing load/malformed data tests. Got the kernel patch allow_setid_cores working. Don't have time to check if they're exploitable. Probably time to get a gamma version out for people, eh? Cheers, Jared :) =========================================================================================== Note: Running dovecot-1.0.beta2 with simple (no funniness) config Note: Running on Intel (in VmWare) with RH9. Note: I'm using shadow authentication, but tried with PAM and it still dumped. Note: For this first core, I see the server responding with: "*OK Waiting for authentication process to respond.." Note: Not sure, but I think these problems are timing related. Be sure to check if a pointer is valid and that will get rid of most of these. Note: I have plenty of sample cores if you need one to fix. -Jared DeMott [root@server dovecot]# gdb ./dovecot-auth -c core.22753 GNU gdb Red Hat Linux (5.3post-0.20021129.18rh) Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"... Core was generated by `dovecot-auth'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libcrypt.so.1...done. Loaded symbols for /lib/libcrypt.so.1 Reading symbols from /lib/libpam.so.0...done. Loaded symbols for /lib/libpam.so.0 Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/tls/libc.so.6...done. Loaded symbols for /lib/tls/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 #0 auth_request_unref (_request=0x807b0f0) at auth-request.c:96 96 i_assert(request->refcount > 0); (gdb) bt #0 auth_request_unref (_request=0x807b0f0) at auth-request.c:96 #1 0x080523ee in auth_request_handler_unref (_handler=0x807b0f0) at auth-request-handler.c:66 #2 0x08050217 in auth_client_connection_destroy (_conn=0x807b0f0) at auth-client-connection.c:327 #3 0x0804ffd8 in auth_client_input (context=0x807b0f0) at auth-client-connection.c:227 #4 0x080607d0 in io_loop_handler_run (ioloop=0x8073100) at ioloop-poll.c:189 #5 0x0805fe29 in io_loop_run (ioloop=0x8073100) at ioloop.c:235 #6 0x08055329 in main (argc=1, argv=0xbfffe454) at main.c:309 #7 0x42015574 in __libc_start_main () from /lib/tls/libc.so.6 (gdb) p request $1 = (struct auth_request *) 0x1 (gdb) i r eax 0x807b0f0 134721776 ecx 0x1 1 edx 0x6c 108 ebx 0x8084e78 134762104 esp 0xbfffe2f0 0xbfffe2f0 ebp 0xbfffe2f8 0xbfffe2f8 esi 0x80a43c8 134890440 edi 0xbfffe314 -1073749228 eip 0x80512d1 0x80512d1 eflags 0x286 646 cs 0x23 35 ss 0x2b 43 ds 0x2b 43 es 0x2b 43 fs 0x0 0 gs 0x33 51 (gdb) ==================================================================================== [root@server 1]# gdb ./dovecot-auth -c core.30100 GNU gdb Red Hat Linux (5.3post-0.20021129.18rh) Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"... warning: exec file is newer than core file. Core was generated by `dovecot-auth'. Program terminated with signal 6, Aborted. #0 0xffffe002 in ?? () (gdb) bt #0 0xffffe002 in ?? () #1 0x42028a73 in ?? () #2 0x0805d47c in default_info_handler (format=0x8067d00 "\024P?u\024?u\020?u\f?u\b?\t", args=0xbffff264 "z|\006\b!") at failures.c:162 #3 0x0805d04b in t_buffer_alloc (size=1108544020) at data-stack.c:347 #4 0x0804fa54 in reply_line_hide_pass (line=0x1 <Address 0x1 out of bounds>) at auth-client-connection.c:35 #5 0x0804fa71 in reply_line_hide_pass (line=0x0) at auth-client-connection.c:36 #6 0x080523bb in auth_request_handler_unref (_handler=0x0) at auth-request-handler.c:74 #7 0x08052b65 in auth_request_handler_auth_continue (handler=0x0, args=0x80774e0 "HU\n\b") at auth-request-handler.c:350 #8 0x0805f916 in io_add (fd=2, condition=39, callback=0x80778e8, context=0x0) at ioloop.c:23 #9 0x080602c8 in io_loop_notify_remove (ioloop=0x0, io=0x8075b00) at ioloop-notify-dn.c:138 #10 0x0805f985 in io_add (fd=0, condition=1073792608, callback=0x80678bc <pwrite_full+64>, context=0x0) at ioloop.c:43 #11 0x08054f94 in add_extra_listeners () at main.c:148 #12 0x42015574 in ?? () (gdb) i r eax 0x0 0 ecx 0x6 6 edx 0x42130a14 1108544020 ebx 0x7594 30100 esp 0xbffff0e0 0xbffff0e0 ebp 0xbffff0e8 0xbffff0e8 esi 0x806daa8 134666920 edi 0x80e92e8 135172840 eip 0xffffe002 0xffffe002 eflags 0x246 582 cs 0x23 35 ss 0x2b 43 ds 0x2b 43 es 0x2b 43 fs 0x0 0 gs 0x33 51 (gdb) ======================================================================================== [root@server login]# gdb ./imap-login -c core.25116 GNU gdb Red Hat Linux (5.3post-0.20021129.18rh) Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"... Core was generated by `imap-login'. Program terminated with signal 11, Segmentation fault. Reading symbols from /lib/libssl.so.4...done. Loaded symbols for /lib/libssl.so.4 Reading symbols from /lib/libcrypto.so.4...done. Loaded symbols for /lib/libcrypto.so.4 Reading symbols from /lib/libresolv.so.2...done. Loaded symbols for /lib/libresolv.so.2 Reading symbols from /usr/kerberos/lib/libgssapi_krb5.so.2...done. Loaded symbols for /usr/kerberos/lib/libgssapi_krb5.so.2 Reading symbols from /usr/kerberos/lib/libkrb5.so.3...done. Loaded symbols for /usr/kerberos/lib/libkrb5.so.3 Reading symbols from /usr/kerberos/lib/libk5crypto.so.3...done. Loaded symbols for /usr/kerberos/lib/libk5crypto.so.3 Reading symbols from /usr/kerberos/lib/libcom_err.so.3...done. Loaded symbols for /usr/kerberos/lib/libcom_err.so.3 Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /usr/lib/libz.so.1...done. Loaded symbols for /usr/lib/libz.so.1 Reading symbols from /lib/tls/libc.so.6...done. Loaded symbols for /lib/tls/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 #0 i_stream_read (stream=0x0) at istream.c:48 48 if (stream->closed) (gdb) bt #0 i_stream_read (stream=0x0) at istream.c:48 #1 0x0804ade2 in client_read (client=0x8070410) at client.c:311 #2 0x0804ae3c in client_input (context=0x8070410) at client.c:333 #3 0x08055558 in io_loop_handler_run (ioloop=0x806cc50) at ioloop-poll.c:189 #4 0x08054bb1 in io_loop_run (ioloop=0x806cc50) at ioloop.c:235 #5 0x0804d3ed in main (argc=1, argv=0xbffff504, envp=0xbffff50c) at main.c:341 #6 0x42015574 in __libc_start_main () from /lib/tls/libc.so.6 (gdb) p stream $1 = (struct istream *) 0x0 (gdb) ====================================================================================== [root@server core]# gdb ./imap -c core.15043 GNU gdb Red Hat Linux (5.3post-0.20021129.18rh) Copyright 2003 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux-gnu"... warning: exec file is newer than core file. Core was generated by `imap'. Program terminated with signal 6, Aborted. Reading symbols from /lib/libdl.so.2...done. Loaded symbols for /lib/libdl.so.2 Reading symbols from /lib/tls/libc.so.6...done. Loaded symbols for /lib/tls/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /lib/libnss_files.so.2...done. Loaded symbols for /lib/libnss_files.so.2 #0 0xffffe002 in ?? () (gdb) bt #0 0xffffe002 in ?? () #1 0x42028a73 in abort () from /lib/tls/libc.so.6 #2 0x0809f9fc in i_internal_panic_handler (fmt=0x80ac360 "file %s: line %d (%s): assertion failed: (%s)", args=0xbfffdd94 "\0251\v\b?") at failures.c:375 #3 0x0809f5cb in i_panic (format=0x80ac360 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:173 #4 0x08082277 in mail_cache_transaction_reserve_more (ctx=0x80cb4a0, block_size=332, commit=true) at mail-cache-transaction.c:257 #5 0x0808248a in mail_cache_transaction_get_space (ctx=0x80cb4a0, min_size=332, max_size=332, offset_r=0x0, available_space_r=0x0, commit=true) at mail-cache-transaction.c:347 #6 0x08082b90 in mail_cache_header_add_field (ctx=0x80cb4a0, field=0) at mail-cache-transaction.c:646 #7 0x08082e0e in mail_cache_add (ctx=0x80cb4a0, seq=1, field=9, data=0x0, data_size=0) at mail-cache-transaction.c:693 #8 0x0807b314 in index_mail_cache_add (mail=0x80cfca0, field=9, data=0x0, data_size=0) at index-mail.c:349 #9 0x0807c799 in index_mail_parse_header_finish (mail=0x80cfca0) at index-mail-headers.c:75 #10 0x0807ce0c in index_mail_parse_header (part=0x42130a14, hdr=0x0, mail=0x80cfca0) at index-mail-headers.c:277 #11 0x0809b3d1 in message_parse_part_header (parser_ctx=0x80d7be8) at message-parser.c:253 #12 0x0809bb01 in message_parser_parse_header (ctx=0x80d7be8, hdr_size=0x80cfd74, callback=0, context=0x0) at message-parser.c:608 #13 0x0807cf18 in index_mail_parse_headers (mail=0x80cfca0, headers=0x80d4088) at index-mail-headers.c:361 #14 0x0807d42f in index_mail_get_headers (_mail=0x80cfca0, field=0x80b0ff5 "Date") at index-mail-headers.c:535 #15 0x0807d4d9 in index_mail_get_first_header (mail=0x80cfca0, field=0x80b0ff5 "Date") at index-mail-headers.c:576 #16 0x080933a4 in mail_get_first_header (mail=0x80d4088, field=0x80b0ff5 "Date") at mail.c:82 #17 0x0807b054 in index_mail_get_date (_mail=0x80cfca0, timezone=0x0) at index-mail.c:253 #18 0x08093370 in mail_get_date (mail=0x80d4088, timezone=0x0) at mail.c:61 #19 0x0805fe97 in mail_thread_input (ctx=0x80bd580, mail=0x80cfca0) at imap-thread.c:456 #20 0x0805f933 in imap_thread (cmd=0x80c37f4, charset=0x80c3b00 "US-ASCII", args=0x80cc628, type=MAIL_THREAD_REFERENCES) at imap-thread.c:143 #21 0x08059863 in cmd_thread (cmd=0x80c37f4) at cmd-thread.c:66 #22 0x08059949 in cmd_uid (cmd=0x80c37f4) at cmd-uid.c:19 #23 0x0805a1a7 in client_handle_input (cmd=0x80c37f4) at client.c:355 #24 0x0805a2c6 in _client_input (context=0x80c37b0) at client.c:406 #25 0x080a4ba8 in io_loop_handler_run (ioloop=0x80c1740) at ioloop-poll.c:189 #26 0x080a4201 in io_loop_run (ioloop=0x80c1740) at ioloop.c:235 #27 0x08061053 in main (argc=1, argv=0xbfffe2d4, envp=0xbfffe2dc) at main.c:238 #28 0x42015574 in __libc_start_main () from /lib/tls/libc.so.6 (gdb) i r eax 0x0 0 ecx 0x6 6 edx 0x42130a14 1108544020 ebx 0x3ac3 15043 esp 0xbfffdc10 0xbfffdc10 ebp 0xbfffdc18 0xbfffdc18 esi 0x80c9cb8 135044280 edi 0x14c 332 eip 0xffffe002 0xffffe002 eflags 0x246 582 cs 0x23 35 ss 0x2b 43 ds 0x2b 43 es 0x2b 43 fs 0x0 0 gs 0x33 51 (gdb) ======================================================================================

3 9

[Dovecot] beta2: strange assert
by Jeff A. Earickson 31 Jan '06

31 Jan '06

Hi, My setup: Solaris 9, mbox format, mailboxes NFS mounted from another S9 system, imap. I got the following assert yesterday: Jan 30 19:57:15 emerald dovecot: [ID 107833 mail.error] imap(user): file index-mail-headers.c: line 258 (index_mail_parse_header): assertion failed: (part != NULL) Jan 30 19:57:16 emerald dovecot: [ID 107833 mail.error] imap(user): file index-mail-headers.c: line 258 (index_mail_parse_header): assertion failed: (part != NULL) The gdb work on the core file is attached. This is a mystery because part was NULL in the core file. Weird. Jeff Earickson Colby College

2 1

[Dovecot] adding a select or a poll?
by ohp＠pyrenet.fr 31 Jan '06

31 Jan '06

Since I put my hands on dovecot, I had this recuring problem at startup: Imap-login would'nt connect to the 'default' socket. I've been strugling with the fact that it would eventually connect on a slow or moderely fast machine but not on a really fast machine. According to Unixware doc, the FIRST connect ALWAYS returns -1 and errno=EINPROGRESS AFAICT, imap loop is like this: while (1) connect if no error bu EINPROGRESS send_handshake if successfull break; end while Now, I think the time between connect and send_handshake might be too short for async connect to finish in most case. I recognize is a Unixware probleme but I think this senario can happen on any system that CAN set errno to EINPROGRESS. I think the two possibilities are 1 - remove the setting of NONBLOCK before connecting to unix sock, but that would ruin the way dovecot is written. 2 - add a poll or a select before send_handshake to be sure the socket is writable. The third way would be to tell unixware users to disable async connects methink would be a pitta. What do you think? -- Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) 15, Chemin des Monges +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: ohp(a)pyrenet.fr ------------------------------------------------------------------------------ Make your life a dream, make your dream a reality. (St Exupery)

1 0

[Dovecot] Re: extremely slow delete/move operations?
by Roger Weeks 31 Jan '06

31 Jan '06

On Jan 30, 2006, at 11:12 AM, Gregory K. Ruiz-Ade wrote: > Message: 10 > The thing is, these mail servers _are_ the local storage for the > mail spools > and home directories. There is no network involved when dovecot is > accessing the INBOX or saved mail folders. Yes, they're "NFS" > mounted, but > this is RHEL4 (linux 2.6.x), and when an NFS share is mounted from > the local > host, it's done as a bind mount, which means local disk access. I don't understand this at all. Mounting anything via NFS should only be done from a remote server, where when you type "mount" at a commandline you see something like: 10.10.10.2:/data on /var/mail type nfs (rw,nfsvers=3,addr=10.10.10.2) If your /etc/fstab or your automounts on your RHEL4 box are mouting LOCAL disks as type NFS, you have set up something very very wrong. Local disks should be mounted at boot like so: /dev/sda3 on / type ext3 (rw) Let's be certain we're clear about this. The disks where dovecot reads and writes your mboxes are local to the RHEL4 machine? If so, you're not using NFS at all. Roger Weeks

2 1

[Dovecot] Dovecot-lda/deliver - how to deliver root's mail?
by Shayne Hardesty 30 Jan '06

30 Jan '06

There's a good chance I could be missing something obvious here, as I can't find much documentation on the LDA other than on the wiki, which is sparse. Local mail delivery works for normal users, but when attempting to deliver mail for root I get this error: Jan 30 13:42:50 apollo deliver: Running as root isn't permitted Both sendmail and dovecot run as root on my server - since I don't allow shell accounts and have multiple layers of security around the server I'm okay with that. How can I tell dovecot-lda it's okay to deliver root's mail as root? Thanks, Shayne

2 1

[Dovecot] poprelay, ip v4 vs ip v6 adresses
by Gerhard Hofmann 30 Jan '06

30 Jan '06

Hi list, I would like to use poprelay as described here: http://wiki.dovecot.org/PopRelay Excerpt from my /var/log/mail.log: dovecot: 2006-01-26 11:27:52 Info: imap-login: Login: user=<planat99>, method=plain, rip=192.168.1.202, lip=192.168.1.5 dovecot: 2006-01-26 13:10:10 Info: pop3-login: Login: user=<planat99>, method=PLAIN, rip=192.168.1.202, lip=192.168.1.5 (these are only two lines but wrapped by my news client) As you can see, the logged remote ip address is in normal ip v4 style, no "ffff" stuff here. The WIKI page says that ip addresses should be in v6-mapped style, how can I achieve this? Respectively, how must I change poprelay.conf to work with my current mail.log style? TIA Gerhard

1 0

[Dovecot] Timeouts
by vmstech 30 Jan '06

30 Jan '06

Hi All - I have a dovecot imap server that I've been running merrily for 6 mths now - the 2 clients that are used on it are evolution and outlook 2003 - I daily have timeout "closed connection" issues with either of these. I have the outlook idle workaround enabled, but I dont think thats the issue - can anyone give me a hint how I can start to trouble shoot this? Thanks Glenn

1 0

Re: [Dovecot] Invisible messages
by Anne Wilson 30 Jan '06

30 Jan '06

On Saturday 28 Jan 2006 20:21, Markus Dobel wrote: > Anne Wilson wrote: > >> * ^To:.*design@lydgate.org > >> ${MAILDIR}.Design > > > > That just leaves the question of the procmail recipe. Will the > > messages end up in the right place? > > AFAIK, Maildir-folders have to end with a "/" in procmailrc. The > procmail recipe should read > > * ^To:.*design@lydgate.org > ${MAILDIR}.Design/ > > Regards, Markus Unfortunately it just doesn't work. Anne -- Registered Linux User No.293302 (http://counter.li.org/)

4 6

[Dovecot] Question about $pat in pop-before-smtp.conf
by Gerhard Hofmann 30 Jan '06

30 Jan '06

Hi, I have setup dovecot to log all successful pop3 and imap logins into /var/log/mail.log I want to use pop-before-smtp to process the log file and write a .db file where sendmail can look up ip addresses that are allowd to relay. mail.log entries look like this: dovecot: 2006-01-26 17:22:28 Info: pop3-login: Login: user=<planat25>, method=PLAIN, rip=213.83.32.125, lip=192.168.1.98 So the question is: how should $pat variable look in pop-before-smtp.conf? I tried the patterns suggested in the WIKI and they do not work. I must admit I'm a newbie to this regex stuff. BTW, would it be easier to patch my dovecot daemon to use DRAC instead? TIA Gerhard

2 2

[Dovecot] Problem with folders, dovecot-0.99.13-3.FC3 and Eudora 7.0.1
by Davide Bolcioni 30 Jan '06

30 Jan '06

Greetings, the Eudora client is attempting to create a subfolder of an existing folder, using the "Make it a folder option" which creates a directory under /home/<user>/mail/<a few paths>. Eudora is seemingly stuck in attempting to create the directory, but there is nothing under /var/log which seems useful in diagnosing the problem. Thank you for your consideration, Davide Bolcioni -- There is no place like /home.

1 0

[Dovecot] I gonna understand one day
by ohp＠pyrenet.fr 29 Jan '06

29 Jan '06

Hi, I'm still struggling with dovecot and Unixware: On my main server, I have two problems: 1- imap-login has great difficulties to connect to 'default'. I have traced it to accept in auth_master_listener.c witch fails with errno=71 (EPROTO) weird... 2- It some times works and I can log-in but imap gets killed by signal 6 (abort?) See the logs: Jan 24 12:40:25 dovecot: Dovecot v1.0.beta2 starting up Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:40:26 dovecot: imap-login: Sending log messages too fast, throttling.. Jan 24 12:40:26 dovecot: auth(default): pgsql: Connected to postfix Jan 24 12:41:06 dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=<hidden> Jan 24 12:41:06 dovecot: auth(default): client out: OK 1 user=ohp Jan 24 12:41:06 dovecot: auth(default): master in: REQUEST 1 15482 1 Jan 24 12:41:06 dovecot: auth(default): master out: USER 1 ohp system_user=ohp uid=101 gid=130 home=/home4/ohp Jan 24 12:41:06 dovecot: imap-login: Login: user=<ohp>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jan 24 12:41:06 dovecot: imap(ohp): Trying to allocate 0 bytes Jan 24 12:41:06 dovecot: child 15812 (imap) killed with signal 6 Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:53 dovecot: imap-login: Sending log messages too fast, throttling.. Jan 24 12:44:53 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:54 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:55 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:56 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:56 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:56 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:56 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:56 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:56 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:56 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:56 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 12:44:56 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:44:58 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:44:58 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:45:03 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:45:03 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:45:08 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:45:08 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:45:13 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:45:13 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:45:18 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 12:45:18 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 14:58:22 dovecot: Dovecot v1.0.beta2 starting up Jan 24 14:58:24 dovecot: auth(default): pgsql: Connected to postfix Jan 24 14:59:32 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 14:59:32 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 14:59:47 dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=<hidden> Jan 24 14:59:47 dovecot: auth(default): client out: OK 1 user=ohp Jan 24 14:59:47 dovecot: auth(default): master in: REQUEST 1 16921 1 Jan 24 14:59:47 dovecot: auth(default): master out: USER 1 ohp system_user=ohp uid=101 gid=130 home=/home4/ohp Jan 24 14:59:47 dovecot: imap-login: Login: user=<ohp>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Jan 24 14:59:47 dovecot: imap(ohp): Trying to allocate 0 bytes Jan 24 14:59:47 dovecot: child 17966 (imap) killed with signal 6 Jan 24 15:22:08 dovecot: imap-login: Disconnected: rip=127.0.0.1, lip=127.0.0.1, secured Jan 24 15:29:04 dovecot: SIGHUP received - reloading configuration Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:05 dovecot: imap-login: Sending log messages too fast, throttling.. Jan 24 15:29:05 dovecot: auth(default): pgsql: Connected to postfix Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:06 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:07 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:08 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:09 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:10 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:11 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:15 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:20 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:23 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:23 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:25 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:28 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:28 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:30 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:33 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:33 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:35 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:36 dovecot: Killed with signal 15 Jan 24 15:29:50 dovecot: Dovecot v1.0.beta2 starting up Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:51 dovecot: imap-login: Sending log messages too fast, throttling.. Jan 24 15:29:51 dovecot: auth(default): pgsql: Connected to postfix Jan 24 15:29:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:53 dovecot: imap-login: Error sending handshake to auth server: Transport endpoint is not connected Jan 24 15:29:53 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:29:56 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:01 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:03 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:03 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:06 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:08 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:08 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:11 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:13 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:13 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:16 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:18 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:18 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:21 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:23 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:23 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:26 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:28 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:28 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:31 dovecot: imap-login: Can't connect to auth server at default: Connection refused Jan 24 15:30:32 dovecot: Killed with signal 15 Any help? Timo? Would you like an account on my fast server? TIA and keep the good jobs. Regards, -- Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) 15, Chemin des Monges +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: ohp(a)pyrenet.fr ------------------------------------------------------------------------------ Make your life a dream, make your dream a reality. (St Exupery)

2 2

[Dovecot] Openwebmail with Dovecot
by ftnx＠ksbase.com 29 Jan '06

29 Jan '06

KS KARICO Business Services Toronto, ON Canada http://www.karico.ca ... Cursors! Foiled Again!

1 0

Re : [Dovecot] How to make pops
by mickael.choisnard＠free.fr 29 Jan '06

29 Jan '06

Hi, I activate ssl in dovecot.conf and i open 995 in my firewall. But when i launch Eudora, i have an error : Server does not support SSL In Eudora, i choose "Required STARTTLS". Where do I have to declare my ssl certificate ? If you don't like Eudora, you can explain me with evolution. # 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/dovecot.pem ssl_key_file = /etc/ssl/private/dovecot.pem # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. ssl_parameters_file = /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 = 24 # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. disable_plaintext_auth = yes

1 0

[Dovecot] pop3_logout_format equivalent for IMAP
by Chris Wakelin 29 Jan '06

29 Jan '06

Hi, I've been thinking for a while that the enhanced logging available for POP would be very useful for IMAP. In particular I'd like to log mailbox size in bytes (at the moment I have a patch that logs SELECTs and number of messages). Even better (though not in the POP code) would be to get some idea of how well the Dovecot indexes and caching are doing by logging the actual number of bytes read. I could have a go at porting the POP changes over to IMAP (programming by imitation as usual :) ) but has anybody else done this? Best Wishes, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

1 0

[Dovecot] 1.0.beta2 released
by Timo Sirainen 29 Jan '06

29 Jan '06

I had originally thought that I'd do a complete audit of the Dovecot's sources this weekend, but looks like I didn't. Hopefully I've been writing good enough code that the "1000 EUR for security hole" offer lasts for a long time. :) This release should fix the SSL parameter regeneration problem. There were two changes that were needed to fix it, but I had forgotten the other one. v1.0.beta2 2006-01-22 Timo Sirainen <tss(a)iki.fi> + Added SQLite support. Patch by Jakob Hirsch. + Added auth_debug_passwords setting. If it's not enabled, hide all password strings from logs. + Added mail_cache_min_mail_count and mbox_min_index_size settings which can be used to make Dovecot do less disk writes in small mailboxes where they don't benefit that much. + Added --build-ssl-parameters parameter to dovecot binary - SSL parameters were being regenerated every 10 minutes, although not with all systems. - Fixed dovecot-auth crashing at startup. Happened only with some specific compilers. - base_dir was supposed to be set world-readable, not world-writable

10 18