- dovecot - dovecot.org

Re: [Dovecot] syslog messages
by Rich West 27 Sep '06

27 Sep '06

After commenting out the "passdb pam" section and uncommenting "passdb ldap", with the "args = /etc/dovecot-ldap.conf", the syslog messages went completely away, and everything continued to work. I just thought I would mention it in the event that anyone else was seeing similar problems in the future. :) -Rich > > (I sent this last night, but to the wrong address.. argh) > > After an upgrade to FC5, and a rebuild and install of dovecot 1.0RC7, > > I've been getting a LOT of syslog messages like the following: > > Sep 26 21:47:55 myhost dovecot-auth: nss_ldap: reconnected to LDAP > > server ldap://ldap.mydomain.com after 1 attempt > > > > Now, everything is working fine as far as I can tell (it's only been a > > rocky day since the upgrade.. and that was littered with other LDAP > > related problems), but I was wondering why it was even using > > nss_ldap... I have dovecot configured to connect to LDAP directly. > > > > My dovecot.conf contains: > > auth default { > > # Space separated list of wanted authentication mechanisms: > > # plain login digest-md5 cram-md5 ntlm rpa apop anonymous gssapi > > mechanisms = plain > > ... > > passdb pam { > > } > > ... > > # LDAP database > > #passdb ldap { > > # Path for LDAP configuration file, see doc/dovecot-ldap.conf for > > example > > #args = > > #} > > ... > > # LDAP database > > userdb ldap { > > # Path for LDAP configuration file, see doc/dovecot-ldap.conf for > > example > > args = /etc/dovecot-ldap.conf > > } > > > > And I am wondering if I missed something obvious here... > > > > I'm going to try commenting out the "passdb pam" section, uncommenting > > the "passdb ldap" section and see if that allows for everything to go > > directly to LDAP (and not rely on nss_ldap or pam_ldap). > > > > -Rich > > >

1 0

Re: [Dovecot] support for UW-style mbox
by Rich West 27 Sep '06

27 Sep '06

> UW-IMAP will automatically append the contents of /var/spool/mail/user to > ~user/mbox (and then clear /var/spool/mail/user) if ~user/mbox exists. > I'd like to mimic that action with Dovecot. (I'm probably going to be unlucky, > as an earlier respondent pointed out). > > Sorry to show my ignorance, but I thought delivery was a function > of the MTA (Exim in my case), which would require a change to my exim > config file, and would probably not then be a per-user thing. > (i.e. with UW-IMAP, if ~user/mbox doesnt exist, mail gets left in > /var/spool/mail/user). > I need to read about dovecot.conf No, you are correct. Delivery is handled by the MTA. Dovecot just needs to know where to access it. By default, for example, with Sendmail, it will place the email in /var/spool/mail (unless you change some back-end code somewhere along the line), and then you can use procmail (with a global procmailrc file in /etc) to place the mail where you want it to go.. I haven't used UW-IMAP in a while now (well over a year and a half). I stopped using it at all of my supported sites because, even though it was simple to manage, it was just way too slow. From what I remember, the UW implementation is such that UW-IMAP will read from the user's mbox file if it exists, and if it doesn't, it will read from <spooldir>/<username> (in this case, /var/spool/mail/user). UW-IMAP (or any IMAP) wouldn't actually do the delivery, so writing to the spool directory temporarily and then moving it to the home directory shouldn't actually happen. However, I don't truly remember how it worked under the hood, but that just doesn't seem right to me (too much chance for conflict). I do remember (back in the day) the headaches we would get when trying to debug a "lost mail" problems (with a centralized /var/spool/mail directory) and it turned out the user in question had created an mbox file which had next to nothing in it. :) -Rich

2 2

[Dovecot] syslog messages
by Rich West 27 Sep '06

27 Sep '06

(I sent this last night, but to the wrong address.. argh) After an upgrade to FC5, and a rebuild and install of dovecot 1.0RC7, I've been getting a LOT of syslog messages like the following: Sep 26 21:47:55 myhost dovecot-auth: nss_ldap: reconnected to LDAP server ldap://ldap.mydomain.com after 1 attempt Now, everything is working fine as far as I can tell (it's only been a rocky day since the upgrade.. and that was littered with other LDAP related problems), but I was wondering why it was even using nss_ldap... I have dovecot configured to connect to LDAP directly. My dovecot.conf contains: auth default { # Space separated list of wanted authentication mechanisms: # plain login digest-md5 cram-md5 ntlm rpa apop anonymous gssapi mechanisms = plain ... passdb pam { } ... # LDAP database #passdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example #args = #} ... # LDAP database userdb ldap { # Path for LDAP configuration file, see doc/dovecot-ldap.conf for example args = /etc/dovecot-ldap.conf } And I am wondering if I missed something obvious here... I'm going to try commenting out the "passdb pam" section, uncommenting the "passdb ldap" section and see if that allows for everything to go directly to LDAP (and not rely on nss_ldap or pam_ldap). -Rich

1 0

Re: [Dovecot] Big sites using Dovecot
by Bill Boebel 27 Sep '06

27 Sep '06

On Thu, September 21, 2006 1:14 pm, Jonathan <dovecot(a)redigloo.org> said: > Are there any big Dovecot sites (say 50,000-100,000) users on this > list? Yes, Webmail.us. Many multiples of that number :) > What sort of hardware do you use. 80 backend IMAP servers. 5 front-end IMAP-proxy servers. All running Dovecot. The boxes are single AMD CPU, 1GB RAM, and 4 SATA drives. DRBD used to replicate data between servers. > What sort of problems do you see? Dovecot doesn't need much CPU, but it needs a lot of disk. So give it lots of spindles, either in one big box or many small boxes like we do. Right now the only problem we have is the Dovecot proxy software sometimes disconnects imap sessions that it should not disconnect. Since Timo is very busy, we are working on a patch for this. http://www.dovecot.org/list/dovecot/2006-August/015401.html Bill

3 2

[Dovecot] SSL_accept failed
by Timothy Martin 26 Sep '06

26 Sep '06

Hello, I'm new to dovecot. I just installed it a few days ago on FreeBSD via the ports and got it up and running without too much trouble. Although yesterday I turned on the SSL/TLS features and tried to get secure connections to work. I don't get any error messages when launching dovecot, I saw it successfully create the SSL parameters after first enabling the feature yet I can't seem to get a successful connection. Normal non- ssl connections work fine. What happens: 1) my client claims to be attempting the connection. 2) things go on for some time with nothing happening 3) finally the dovecot log pops up with these messages dovecot: Sep 09 02:25:23 Warning: imap-login: SSL_accept() syscall failed: EOF [x.x.x.x] dovecot: Sep 09 02:25:23 Info: imap-login: Disconnected: rip=x.x.x.x, lip=x.x.x.x, TLS handshake dovecot: Sep 09 02:26:23 Info: imap-login: Disconnected: Inactivity: rip=x.x.x.x, lip=x.x.x.x, TLS handshake FYI: I've regenerated a fresh cert and key, just for dovecot and I'm using Mac OS X's Mail client. Any clues? .tim

6 17

[Dovecot] log tools with html for dovecot
by Robert Schetterer 26 Sep '06

26 Sep '06

Hi @ll, are there any recommandations for logging tools with html display for dovecot thx -- Diese Nachricht wurde auf Viren und andere gefährliche Inhalte untersucht und ist - aktuelle Virenscanner vorausgesetzt - sauber.

2 2

[Dovecot] Error: pipe() failed: Too many open files
by Dirk Essl 26 Sep '06

26 Sep '06

Hi, I am currently migrating a big bunch of mail accounts to a dovecot server running 1.0rc2 on Solaris 10 suddenly all imap processes died and I see this in my dovecot.log: dovecot: Sep 26 14:54:31 Error: pipe() failed: Too many open files dovecot: Sep 26 14:54:31 Fatal: dup2(stderr) failed: Bad file number dovecot: Sep 26 14:54:31 Error: child 29376 (imap) returned error 89 dovecot: Sep 26 15:15:48 Error: pipe() failed: Too many open files dovecot: Sep 26 15:15:48 Fatal: dup2(stderr) failed: Bad file number dovecot: Sep 26 15:15:49 Error: child 1563 (imap) returned error 89 dovecot: Sep 26 15:15:55 Error: pipe() failed: Too many open files dovecot: Sep 26 15:15:55 Fatal: dup2(stderr) failed: Bad file number dovecot: Sep 26 15:15:55 Error: child 1572 (imap) returned error 89 dovecot: Sep 26 15:15:58 Error: pipe() failed: Too many open files dovecot: Sep 26 15:15:58 Fatal: dup2(stderr) failed: Bad file number dovecot: Sep 26 15:15:58 Error: child 1577 (imap) returned error 89 dovecot: Sep 26 15:18:25 Error: pipe() failed: Too many open files dovecot: Sep 26 15:18:25 Fatal: dup2(stderr) failed: Bad file number dovecot: Sep 26 15:18:25 Error: child 1659 (imap) returned error 89 dovecot: Sep 26 15:18:27 Error: pipe() failed: Too many open files dovecot: Sep 26 15:18:27 Fatal: dup2(stderr) failed: Bad file number dovecot: Sep 26 15:18:27 Error: child 1662 (imap) returned error 89 dovecot: Sep 26 15:18:32 Error: socketpair() failed: Too many open files dovecot: Sep 26 15:18:32 Error: Temporary failure in creating login processes, slowing down for now dovecot: Sep 26 15:18:32 Error: pipe() failed: Too many open files what could cause the error? is this from Solaris or from dovecot? TIA dirk

2 1

[Dovecot] Not getting new mail notification
by Robert Creager 26 Sep '06

26 Sep '06

Hey all, I'm having no luck getting new mail notification except in two mail folders (using maildir w/procmail delivery). I'm using three different clients (sylpheed-claws 1.9.14, Thunderbird 1.5.0.5 and a newer version of Horde). None of them are getting new mail in any except these two folders (inbox and 1 other). If I browse to the folders, still nothing. If I browse to the folders with Horde, I see the new mail, but not always in the other clients. It's hit or miss if the other clients get notified of the mail, but the mail is moved from the new folder. I'm subscribed to the folders and have them to be checked for new messages (in Thunderbird). I tried using dnotify, and things got worse (no folders updated). I've over 350 e-mails sitting in new folders right now: [robert@thunder Maildir]$ ls .*/new | wc 397 332 12925 One interesting item I noticed is that if I touch a file in a new directory (or vi it), I immediately get notification of the mail (and it gets moved from new to cur). I'm running dovecot 1.0 RC7 configured as ./configure --sysconfdir=/etc/dovecot --with-pgsql --with-pam --localstatedir=/var with the following changes to the config: base_dir = /var/lib/dovecot/ protocols = imaps ssl_cert_file = /etc/ssl/dovecot/certs/dovecot.pem ssl_key_file = /etc/ssl/dovecot/private/dovecot.pem default_mail_env = maildir:%h/Maildir verbose_proctitle = yes protocol imap { imap_client_workarounds = tb-extra-mailbox-sep } I'm running dovecot through xinetd: service imaps { disable = no socket_type = stream protocol = tcp wait = no user = root server = /usr/local/libexec/dovecot/imap-login flags = IPv4 server_args = --ssl } Linux thunder.logicalchaos.org 2.6.12-12-3 #5 SMP Wed Feb 1 23:59:03 MST 2006 i686 AMD Athlon(tm) MP 2600+ unknown GNU/Linux Help? Thanks, Rob

9 31

[Dovecot] Preforming an action/trigger after a user successfully authenticates
by Dan Trainor 26 Sep '06

26 Sep '06

Hi - I have searched the docs for v1.0 RC7, but cannot find what I'm looking for. What I'm ultimately wanting to do is have Dovecot preform some action, or a trigger, when the user is successfully authenticated. Even more specifically, I'd like to run another SQL query to record a date/time for last authenticated login. Short from running a script during logrotate, or constantly tailing the log, is there any mechanism in Dovecot that would allow me to do this? Again, all I'm looking to do is to record the last date/time that someone successfully logged in, into a MySQL database. Thanks! -dant

3 7

[Dovecot] Dovecot Usage Poll
by Jackie Hunt 25 Sep '06

25 Sep '06

Hi all, I'm trying to get a feel for how many sites are using Dovecot and the size of the installation. Jonathan's query about big sites spurred my curiousity. I'd like to take an informal poll and will post results to the list. I'm interested in hearing from those of you who are using dovecot in a real-life/production type environment (not just testing). Please email me directly [jackie.hunt(a)colostate.edu] and send the following info: (1) Type of organization: commercial/government/educational/etc. (2) Number of users supported with Dovecot (3) Approx. length of time you've used Dovecot in "production" (4) Whether or not you are using the Dovecot LDA Thanks much, Jackie --- Jackie Hunt ACNS Voice: (970) 663-3789 Colorado State University FAX: (970) 491-1958 Fort Collins, CO 80523 Email: jackie.hunt(a)colostate.edu

7 7

[Dovecot] DSpam mysql-plugin (was DSpam plugin)
by Michael Blinn 25 Sep '06

25 Sep '06

After wrestling with Johannes's original plugin, I had a go at the mysql plugin that Tim wrote, as described here: http://members.plug.org.au/~linuxalien/dokuwiki/projects:dovecot-mysql-dspa… I kept getting "Error: imap dump-capability process killed with signal 11" when attempting to start dovecot with this plugin. I traced the error to line 656 of master-settings.c in the dovecot source, in the 'get_imap_capability' function. In this function, it notes: "Reloading configuration. Don't try to execute the imap process again. Too risky and the wait() call below will break it anyway. Just use the previous capability list we already had generated." I changed the source so that the function always ran " set->imap_generated_capability = p_strdup(settings_pool, generated_capability); return TRUE;" instead of going through the function where it had on the wait described in the comments. Now, voila. Dovecot starts without complaint, the plugin works, the delivery and moving of email works. I'm assuming I've screwed something up by skipping the rest of this get_imap_capability function. My C skills are a few years rusty. What are the ramifications of skipping the remainder of this function? Thanks, Michael

7 8

[Dovecot] Moving to dovecot
by Ian C. Quorn 25 Sep '06

25 Sep '06

We're in the process of moving to Dovecot. We're currently running UW-IMAP live with Dovecot 1.0rc7 on alternate ports for testing. We're set to switch to Dovecot tomorrow morning, and I'm sure I'll have lots of stupid questions once that happens. So I guess you can consider this message an introduction as well as a preemptive apology. Our setup: our mailserver is a SunFire 880 running solaris 8. Inboxes are stored in /var/mail, home directories are in /home. Mailboxes are mbox. Both /home and /var/mail are NFS-mounted from a NetApp filer. Indexes are stored in /dovecot (this is a partition on local disk). We have about 500 users accesing their mail on this server. Supported clients are Outlook, Mac Mail, and Thunderbird (both PC and Mac). Many people access their mail via webmail (IMP Horde) instead of or in addition to using a normal client. We also have a few people who use Pine. Authentication is against the local shadow file. Given this setup, do the following config lines seem sane? login_process_per_connection = no login_max_connections = 256 default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u:INDEX=/dovecot/%u namespace private { separator = / prefix = inbox = yes } # for backwards compatibility: namespace private { separator = / prefix = mail/ hidden = yes } namespace private { separator = / prefix = ~/mail/ hidden = yes } namespace private { separator = / prefix = ~%u/mail/ hidden = yes } mail_read_mmaped = no mmap_disable = no mmap_no_write = no lock_method = fcntl mbox_read_locks = dotlock mbox_write_locks = dotlock imap_client_workarounds = outlook-idle tb-extra-mailbox-sep pop3_uidl_format = %08Xv%08Xu pop3_client_workarounds = outlook-no-nuls oe-ns-eoh The namespace stuff came from http://wiki.dovecot.org/Namespaces - it was listed as a way to allow backwards-compatability with UW-IMAP. So, anything there look like a bad idea? Any other config parameters I might want to tweak, tune, or otherwise take a look at? So far dovecot's been pretty much trouble-free in our testing. But I have noticed some error messages in the logs. Anyone know what these mean? Are they anything I should panic over? dovecot: Sep 25 09:34:19 Error: IMAP(cliftoja): UIDVALIDITY changed (1034876030 -> 1159201281) in mbox file /home/wcts/cliftoja/mail/Common installation codes dovecot: Sep 25 09:50:24 Error: IMAP(cliftoja): UIDVALIDITY changed (1156881790 -> 1159202005) in mbox file /home/wcts/cliftoja/mail/Junk dovecot: Sep 25 10:04:01 Error: imap-login: Master sent reply with unknown tag 180 dovecot: Sep 25 10:04:01 Error: child 1078 (login) returned error 89 dovecot: Sep 25 10:18:58 Error: login: tried to change state 0 -> 44 (if you can't login at all, see src/lib/fdpass.c) Thanks in advance, and here's to (hopefully) a trouble-free Dovecot migration (hey, it can't be worse than UW-IMAP). Ian Quorn System Administrator Whitman College Technology Services

1 0

[Dovecot] support for UW-style mbox
by T. Horsnell 25 Sep '06

25 Sep '06

Hi, The dovecot docs say that support for the automatic appending of /var/spool/mail to a ~user/mbox (as is done by UW-IMAP) may be implemented in the near future. Is this still the case? And if so, is it far off? Cheers, Terry.

4 4

[Dovecot] Auth problem
by Riccardo Bini 25 Sep '06

25 Sep '06

Dovecot 1.07rc1 on ubuntu 6.04 I get the following problem: root 26375 0.0 0.2 5548 2240 ? Ss Sep15 1:39 /usr/sbin/dovecot root 26376 0.0 0.3 7896 3364 ? S Sep15 0:31 \_ dovecot-auth root 26378 0.0 0.3 8304 3824 ? S Sep15 0:34 \_ dovecot-auth root 26379 0.0 0.4 8668 4152 ? S Sep15 0:38 \_ dovecot-auth root 32660 0.0 0.2 7340 2856 ? S Sep15 0:00 | \_ dovecot-auth root 2968 0.0 0.2 7260 2728 ? S Sep15 0:00 | \_ dovecot-auth root 24559 0.0 0.2 7260 2768 ? S Sep16 0:00 | \_ dovecot-auth root 24771 0.0 0.2 7260 2768 ? S Sep16 0:00 | \_ dovecot-auth root 6265 0.0 0.2 7376 2788 ? S Sep18 0:00 | \_ dovecot-auth root 11988 0.0 0.2 7376 2900 ? S Sep18 0:00 | \_ dovecot-auth root 13865 0.0 0.2 7584 3044 ? S Sep18 0:00 | \_ dovecot-auth root 337 0.0 0.3 7704 3148 ? S Sep19 0:00 | \_ dovecot-auth root 407 0.0 0.3 7704 3148 ? S Sep19 0:00 | \_ dovecot-auth root 1321 0.0 0.3 7704 3160 ? S Sep19 0:00 | \_ dovecot-auth root 1361 0.0 0.3 7784 3292 ? S Sep19 0:00 | \_ dovecot-auth root 1645 0.0 0.3 7784 3312 ? S Sep19 0:00 | \_ dovecot-auth root 1673 0.0 0.3 7704 3196 ? S Sep19 0:00 | \_ dovecot-auth root 1867 0.0 0.3 7704 3204 ? S Sep19 0:00 | \_ dovecot-auth root 2033 0.0 0.3 7704 3212 ? S Sep19 0:00 | \_ dovecot-auth root 2067 0.0 0.3 7704 3224 ? S Sep19 0:00 | \_ dovecot-auth root 2148 0.0 0.3 7880 3368 ? S Sep19 0:00 | \_ dovecot-auth root 2308 0.0 0.3 7880 3376 ? S Sep19 0:00 | \_ dovecot-auth root 2420 0.0 0.3 7880 3384 ? S Sep19 0:00 | \_ dovecot-auth root 2571 0.0 0.3 7880 3396 ? S Sep19 0:00 | \_ dovecot-auth root 2779 0.0 0.3 7880 3420 ? S Sep19 0:00 | \_ dovecot-auth root 2888 0.0 0.3 7880 3432 ? S Sep19 0:00 | \_ dovecot-auth root 3049 0.0 0.3 7800 3324 ? S Sep19 0:00 | \_ dovecot-auth root 3298 0.0 0.3 7904 3332 ? S Sep19 0:00 | \_ dovecot-auth root 3514 0.0 0.3 7984 3464 ? S Sep19 0:00 | \_ dovecot-auth root 3710 0.0 0.3 7984 3468 ? S Sep19 0:00 | \_ dovecot-auth root 6463 0.0 0.3 7904 3388 ? S Sep19 0:00 | \_ dovecot-auth root 6464 0.0 0.3 7904 3456 ? S Sep19 0:00 | \_ dovecot-auth root 6465 0.0 0.3 7904 3388 ? S Sep19 0:00 | \_ dovecot-auth root 10289 0.0 0.3 7904 3420 ? S Sep19 0:00 | \_ dovecot-auth root 11144 0.0 0.3 7968 3452 ? S Sep19 0:00 | \_ dovecot-auth root 12018 0.0 0.3 8176 3636 ? S Sep19 0:00 | \_ dovecot-auth root 12561 0.0 0.3 8096 3540 ? S Sep19 0:00 | \_ dovecot-auth root 14090 0.0 0.3 8176 3724 ? S Sep19 0:00 | \_ dovecot-auth root 14728 0.0 0.3 8096 3592 ? S Sep19 0:00 | \_ dovecot-auth root 15442 0.0 0.3 8176 3736 ? S Sep19 0:00 | \_ dovecot-auth root 16329 0.0 0.3 8288 3796 ? S Sep19 0:00 | \_ dovecot-auth root 18818 0.0 0.3 8208 3684 ? S Sep19 0:00 | \_ dovecot-auth root 3228 0.0 0.3 8388 3892 ? S Sep20 0:00 | \_ dovecot-auth root 5596 0.0 0.3 8308 3764 ? S Sep20 0:00 | \_ dovecot-auth root 12477 0.0 0.3 8308 3804 ? S Sep20 0:00 | \_ dovecot-auth root 14008 0.0 0.3 8404 3848 ? S Sep20 0:00 | \_ dovecot-auth root 14742 0.0 0.3 8484 3980 ? S Sep20 0:00 | \_ dovecot-auth root 15133 0.0 0.3 8404 3860 ? S Sep20 0:00 | \_ dovecot-auth root 16170 0.0 0.3 8484 4028 ? S Sep20 0:00 | \_ dovecot-auth root 16327 0.0 0.3 8404 3908 ? S Sep20 0:00 | \_ dovecot-auth root 19848 0.0 0.3 8604 4140 ? S Sep20 0:00 | \_ dovecot-auth root 20278 0.0 0.4 8692 4188 ? S Sep20 0:00 | \_ dovecot-auth root 20746 0.0 0.4 8692 4200 ? S Sep20 0:00 | \_ dovecot-auth root 22057 0.0 0.3 8612 4072 ? S Sep20 0:00 | \_ dovecot-auth root 24303 0.0 0.3 8612 4084 ? S Sep20 0:00 | \_ dovecot-auth root 6514 0.0 0.4 8888 4356 ? S 10:32 0:00 | \_ dovecot-auth root 26380 0.0 0.3 8120 3660 ? S Sep15 0:31 \_ dovecot-auth root 32218 0.0 0.3 7952 3444 ? S Sep15 0:27 \_ dovecot-auth What means? Ciao Rick

2 1

[Dovecot] Errors while doing make on Solaris 9 for dovecot-1.0.rc7
by Agarwal, Lalit 25 Sep '06

25 Sep '06

Hi, I have Solaris 9 and I am getting the following errors for dovecot-1.0.rc7 after running 1.configure - No errors see output as attached 2. /usr/ccs/bin/make -- partial output below, complete attached Thanks, Lalit ..... DEPDIR=.deps depmode=none /bin/bash ../../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../.. -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -c var-expand.c source='write-full.c' object='write-full.o' libtool=no \ DEPDIR=.deps depmode=none /bin/bash ../../depcomp \ gcc -DHAVE_CONFIG_H -I. -I. -I../.. -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -c write-full.c rm -f liblib.a false cru liblib.a base64.o bsearch-insert-pos.o buffer.o close-keep-errno.o compat.o data-stack.o env-util.o failures.o fd-close-on-exec.o fd-set-nonblock.o fdpass.o file-cache.o file-copy.o file-dotlock.o file-lock.o file-set-size.o hash.o hex-binary.o hex-dec.o hmac-md5.o home-expand.o hostpid.o imem.o iostream.o istream.o istream-data.o istream-file.o istream-limit.o istream-mmap.o istream-seekable.o ioloop.o ioloop-iolist.o ioloop-notify-none.o ioloop-notify-dn.o ioloop-notify-inotify.o ioloop-notify-kqueue.o ioloop-poll.o ioloop-select.o ioloop-epoll.o ioloop-kqueue.o lib.o lib-signals.o md4.o md5.o mempool.o mempool-alloconly.o mempool-datastack.o mempool-system.o mempool-unsafe-datastack.o mkdir-parents.o mmap-anon.o mmap-util.o module-dir.o mountpoint.o network.o nfs-workarounds.o ostream.o ostream-file.o ostream-crlf.o primes.o printf-upper-bound.o process-title.o randgen.o read-full.o restrict-access.o restrict-process-size.o safe-memset.o safe-mkdir.o sendfile-util.o seq-range-array.o sha1.o str.o str-sanitize.o strescape.o strfuncs.o unix-socket-create.o unlink-directory.o unlink-lockfiles.o utc-offset.o utc-mktime.o var-expand.o write-full.o *** Error code 255 make: Fatal error: Command failed for target `liblib.a' Current working directory /lhome/lalit/dovecot/dovecot-1.0.rc7/src/lib *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Current working directory /lhome/lalit/dovecot/dovecot-1.0.rc7/src *** Error code 1 make: Fatal error: Command failed for target `all-recursive' Current working directory /lhome/lalit/dovecot/dovecot-1.0.rc7 *** Error code 1 make: Fatal error: Command failed for target `all' <<make.out.zip>> <<configure.out.zip>> > Confidentiality Note: This electronic message transmission is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. If you have received this transmission, but are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of the contents of this information is strictly prohibited. If you have received this e-mail in error, please contact me at 212-615-4204 and delete and destroy the original message and all copies. Thank You. > >

2 1

[Dovecot] sieve problem unresolved
by Amadou Toure 25 Sep '06

25 Sep '06

hello, I follow your suggestions : _cyrus timsieved installed on the two LDA server _the sieve script stored in the /var/home (which is the virtual home directory) and in /var/mail/user/ for testing purposes But nothing happened when the user receive a email. Below the sieve script. Regards #################################################### # This script has been automatically generated by avelsieve # (Sieve Mail Filters Plugin for Squirrelmail) #AVELSIEVE_VERSIONYTo0OntzOjU6Im1ham9yIjtpOjE7czo1OiJtaW5vciI7aTowO3M6NzoicmVsZWFzZSI7aToxO3M6Njoic3RyaW5nIjtzOjU6IjEuMC4xIjt9 #AVELSIEVE_CREATED1157627930 #AVELSIEVE_MODIFIED1157628524 require ["fileinto","reject","vacation","imapflags","relational","comparator-i;ascii-numeric","regex","notify","redirect"]; if header :contains "subject" ["order", "test"] { keep; redirect "amadou.toure(a)sentoo.sn"; } vacation # Reply at most once a day to a same sender :days 0 :subject "Out of office reply" # List of allowed recipient addresses from auto reply should be sent. :addresses ["ctsarr(a)sentoo.sn"] "I'm out of office, please contact Amadou TOURE instead. Best regards CHEIKH SARR"; #################################################### Amadou TOURE Sonatel Multimedia, 136 Sacre Coeur, Pyrotechnie, BP 21100 Dakar Tel +221-8699810. Fax +221-8641094 http://www.sentoo.sn DAKAR - SENEGAL ----- Original Message ----- From: "John Peacock" <jpeacock(a)rowman.com> To: "Amadou Toure" <atoure(a)sentoo.sn> Cc: <dovecot(a)dovecot.org> Sent: Monday, September 11, 2006 2:44 PM Subject: Re: [Dovecot] sieve unresolved problem > Amadou Toure wrote: >> What about the directory sieve script storage ? >> We use avelsieve on the squirrel mail web interface to edit and create >> script and the script are stored on the /var/home/first letter/username/ >> (shared across the NFS) but it seems that at the delivery process the >> LDA doesn't execute the script > > You can't just place the sieve script in some random location and expect > dovecot to magically find it. Right now, the only place that deliver > expects to find the script (and it *must* be named .dovecot.sieve) is in > the [virtual] user's home directory. After 1.0 is golden, I would expect > that Timo might have some time to make that configurable, but I wouldn't > want to hold up dovecot trying to get that working now. > > John > > -- > John Peacock > Director of Information Research and Technology > Rowman & Littlefield Publishing Group > 4501 Forbes Boulevard > Suite H > Lanham, MD 20706 > 301-459-3366 x.5010 > fax 301-429-5748 Amadou TOURE Sonatel Multimedia, 136 Sacre Coeur, Pyrotechnie, BP 21100 Dakar Tel +221-8699810. Fax +221-8641094 http://www.sentoo.sn DAKAR - SENEGAL

2 2

Re: [Dovecot] Dovecot - postfix SASL
by Matt 25 Sep '06

25 Sep '06

Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: connection established Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: master_notify: status 0 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: name_mask: resource Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: name_mask: software Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: xsasl_dovecot_server_create: SASL service=smtp, realm=(null) Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: connect from c-67-183-127-210.hsd1.wa.comcast.net[67.183.127.210] Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_list_match: c-67-183-127-210.hsd1.wa.comcast.net: no match Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_list_match: 67.183.127.210: no match Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_list_match: c-67-183-127-210.hsd1.wa.comcast.net: no match Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_list_match: 67.183.127.210: no match Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_hostname: c-67-183-127-210.hsd1.wa.comcast.net ~? 127.0.0.0/8 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_hostaddr: 67.183.127.210 ~? 127.0.0.0/8 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_hostname: c-67-183-127-210.hsd1.wa.comcast.net ~? 205.252.250.12 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_hostaddr: 67.183.127.210 ~? 205.252.250.12 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_list_match: c-67-183-127-210.hsd1.wa.comcast.net: no match Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_list_match: 67.183.127.210: no match Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: send attr request = connect Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: send attr ident = smtp:67.183.127.210 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: private/anvil: wanted attribute: status Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: input attribute name: status Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: input attribute value: 0 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: private/anvil: wanted attribute: count Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: input attribute name: count Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: input attribute value: 1 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: private/anvil: wanted attribute: rate Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: input attribute name: rate Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: input attribute value: 3 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: private/anvil: wanted attribute: (list terminator) Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: input attribute name: (end) Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: > c-67-183-127-210.hsd1.wa.comcast.net[67.183.127.210]: 220 hostyougood.com ESMTP Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: < c-67-183-127-210.hsd1.wa.comcast.net[67.183.127.210]: HELO office Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: > c-67-183-127-210.hsd1.wa.comcast.net[67.183.127.210]: 250 hostyougood.com Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: < c-67-183-127-210.hsd1.wa.comcast.net[67.183.127.210]: MAIL FROM: <admin(a)hostyougood.com> Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: extract_addr: input: <admin(a)hostyougood.com> Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: smtpd_check_addr: addr=admin(a)hostyougood.com Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: ctable_locate: move existing entry key admin(a)hostyougood.com Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: extract_addr: in: <admin(a)hostyougood.com>, result: admin(a)hostyougood.com Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: fsspace: .: block size 4096, blocks free 2152496 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: smtpd_check_queue: blocks 4096 avail 2152496 min_free 0 msg_size_limit 10240000 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: > c-67-183-127-210.hsd1.wa.comcast.net[67.183.127.210]: 250 2.1.0 Ok Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: < c-67-183-127-210.hsd1.wa.comcast.net[67.183.127.210]: RCPT TO: <elitescripts2000(a)yahoo.com> Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: extract_addr: input: <elitescripts2000(a)yahoo.com> Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: smtpd_check_addr: addr=elitescripts2000(a)yahoo.com Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: ctable_locate: move existing entry key elitescripts2000(a)yahoo.com Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: extract_addr: in: <elitescripts2000(a)yahoo.com>, result: elitescripts2000(a)yahoo.com Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: >>> START Recipient address RESTRICTIONS <<< Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: generic_checks: name=permit_mynetworks Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: permit_mynetworks: c-67-183-127-210.hsd1.wa.comcast.net 67.183.127.210 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_hostname: c-67-183-127-210.hsd1.wa.comcast.net ~? 127.0.0.0/8 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_hostaddr: 67.183.127.210 ~? 127.0.0.0/8 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_hostname: c-67-183-127-210.hsd1.wa.comcast.net ~? 205.252.250.12 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_hostaddr: 67.183.127.210 ~? 205.252.250.12 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_list_match: c-67-183-127-210.hsd1.wa.comcast.net: no match Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_list_match: 67.183.127.210: no match Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: generic_checks: name=permit_mynetworks status=0 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: generic_checks: name=permit_sasl_authenticated Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: generic_checks: name=permit_sasl_authenticated status=0 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: generic_checks: name=reject_unauth_destination Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: reject_unauth_destination: elitescripts2000(a)yahoo.com Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: permit_auth_destination: elitescripts2000(a)yahoo.com Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: ctable_locate: leave existing entry key elitescripts2000(a)yahoo.com Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: NOQUEUE: reject: RCPT from c-67-183-127-210.hsd1.wa.comcast.net[67.183.127.210]: 554 5.7.1 <elitescripts2000(a)yahoo.com>: Relay access denied; from=<admin(a)hostyougood.com> to=<elitescripts2000(a)yahoo.com> proto=SMTP helo=<office> Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: generic_checks: name=reject_unauth_destination status=2 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: > c-67-183-127-210.hsd1.wa.comcast.net[67.183.127.210]: 554 5.7.1 <elitescripts2000(a)yahoo.com>: Relay access denied Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: < c-67-183-127-210.hsd1.wa.comcast.net[67.183.127.210]: QUIT Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: > c-67-183-127-210.hsd1.wa.comcast.net[67.183.127.210]: 221 2.0.0 Bye Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_hostname: c-67-183-127-210.hsd1.wa.comcast.net ~? 127.0.0.0/8 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_hostaddr: 67.183.127.210 ~? 127.0.0.0/8 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_hostname: c-67-183-127-210.hsd1.wa.comcast.net ~? 205.252.250.12 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_hostaddr: 67.183.127.210 ~? 205.252.250.12 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_list_match: c-67-183-127-210.hsd1.wa.comcast.net: no match Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: match_list_match: 67.183.127.210: no match Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: send attr request = disconnect Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: send attr ident = smtp:67.183.127.210 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: private/anvil: wanted attribute: status Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: input attribute name: status Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: input attribute value: 0 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: private/anvil: wanted attribute: (list terminator) Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: input attribute name: (end) Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: disconnect from c-67-183-127-210.hsd1.wa.comcast.net[67.183.127.210] Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: master_notify: status 1 Sep 25 04:53:30 hostyougood postfix/smtpd[17497]: connection closed --- Matt <elitescripts2000(a)yahoo.com> wrote: > Hi, > > I am trying to replace pop-before-smtp ( yes it is crap ) with Dovecot SASL. > > I have everything configured according to: > http://www.postfix.org/SASL_README.html > > But, does not allow me to SEND mail via POP3 using outlook express... > > Below are my config files. > > Postfix version 2.3.3 > Dovecot version 1.0.rc7 > > dovecot.conf > ------------ > auth default { > mechanisms = plain login > > passdb sql { > args = > /home/digipanel/secure/programs/dovecot/config/dovecot-mysql.conf > } > userdb sql { > args = > /home/digipanel/secure/programs/dovecot/config/dovecot-mysql.conf > } > socket listen { > client { > path = /home/digipanel/secure/programs/postfix/queue/private/auth > mode = 0666 > user = postfix > group = postfix > } > } > } > > main.cf > ------- > smtpd_recipient_restrictions = > permit_mynetworks, > permit_sasl_authenticated, > reject_unauth_destination > > smtpd_sasl_auth_enable = yes > broken_sasl_auth_clients = yes > smtpd_sasl_type = dovecot > smtpd_sasl_path = private/auth > smtpd_sasl_authenticated_header = yes > > Now my postconf -a yields: dovecot > > So, I know postfix has compiled in Dovecot support. > > My mail logs say I am not allowd to relay off the mailserver. >

5 5

[Dovecot] Dovecot 1.0.rc7 ioloop-poll.c assertion failed after SIGHUP
by Chris Wakelin 25 Sep '06

25 Sep '06

Anybody else seen this one? We're running Dovecot 1.0.rc7 on a different port on our live server (we're generally live with 1.0.beta5) and after a HUP to reload the user database (in a passwd-file) this morning we got:- > dovecot: Sep 22 07:45:05 Info: IMAP 14482 someuser xxx.xxx.xxx.xxx : Disconnected in IDLE > dovecot: Sep 22 07:45:05 Warning: imap-login: SSL_read() syscall failed: No route to host [xxx.xxx.xxx.xxx] > dovecot: Sep 22 07:45:05 Warning: SIGHUP received - reloading configuration > dovecot: Sep 22 07:45:05 Error: Login process died too early - shutting down > dovecot: Sep 22 07:45:05 Panic: file ioloop-poll.c: line 105 (io_loop_handle_remove): assertion failed: (index >= 0 && (unsigned int) index < ctx->fds_count) and Dovecot had died. "someuser" was me, and I'd left my Thunderbird client logged in (via IMAPS) by mistake when I hibernated my PC last night. I'd seen exactly the same assert on a test box the day before yesterday, (this time without a machine hibernating):- > dovecot: Sep 19 19:00:45 Info: imap-login: Aborted login: user=<testuser>, method=PLAIN, rip=yyy.yyy.yyy.yyy, lip=yyy.yyy.yyy.yyy, secured > dovecot: Sep 19 19:07:42 Warning: SIGHUP received - reloading configuration > dovecot: Sep 19 19:07:42 Error: Login process died too early - shutting down > dovecot: Sep 19 19:07:42 Panic: file ioloop-poll.c: line 105 (io_loop_handle_remove): assertion failed: (index >= 0 && (unsigned int) index < ctx->fds_count) Where yyy.yyy.yyy.yyy is actually the test box (I was logging in from the server itself using "openssl s_client"). The thing is, I was hoping to upgrade everyone (~20,000 users) to 1.0.rc7 next Tuesday, but now I'm not so sure! 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

2 6

[Dovecot] Need to detect event: a user move a message to a “spam folder” (for antispam filter)
by Naefen Raphaël 25 Sep '06

25 Sep '06

I’m writing an immune system based antispam filter. I need to detect when a user move a message to her spam folder (to inform the filter). I I found “cmd_copy” in imap library so I detect the copy event. But at this level I wasn’t able to find info about which mail and which user copy this message. My question is: Were I can find user Info to know how is moving this message in the spam folder. Ideally if I can have information about message (content or id) will be perfect. Thanks

3 2

[Dovecot] RC7: BUG! and patch [Was: Re: rc7 bug? [Was: deliver LDA and INBOX location] (fwd)] (fwd)
by David Lee 25 Sep '06

25 Sep '06

Could someone confirm, please, that this bug report and its proposed fix are being checked? 1. Is my analysis (message below) about right? 2. Is my proposed patch (attached) about right? 3. Is this being addressed for "rc8" (or whatever) and its successors? Many thanks. -- : David Lee I.T. Service : : Senior Systems Programmer Computer Centre : : Durham University : : http://www.dur.ac.uk/t.d.lee/ South Road : : Durham DH1 3LE : : Phone: +44 191 334 2752 U.K. : ---------- Forwarded message ---------- Date: Tue, 5 Sep 2006 16:40:00 +0100 (BST) From: David Lee <t.d.lee(a)durham.ac.uk> To: dovecot(a)dovecot.org Subject: [Dovecot] RC7: BUG! and patch [Was: Re: rc7 bug? [Was: deliver LDA and INBOX location] (fwd)] On Tue, 5 Sep 2006, David Lee wrote: > Anyone had any thoughts on the item below? [see earlier in thread] > > If the problem is with my config, I'd like to be guided towards how I > might resolve it. > > If it is a bug in rc7, it would be good to fix it, and I'd be happy to > beta-test. BUG in rc7 (and probably from much earlier). The LDA 'deliver' fails to honour any uid (%i) setting in dovecot.conf. So delivery and reading happen in different places if 'default_mail_env' uses a '%i' variant. Clearly incorrect behaviour. Attached is a draft of a patch which fixes the problem. Please could the patch be reviewed and, in some form, applied? Thanks. -- : David Lee I.T. Service : : Senior Systems Programmer Computer Centre : : Durham University : : http://www.dur.ac.uk/t.d.lee/ South Road : : Durham DH1 3LE : : Phone: +44 191 334 2752 U.K. :

3 3

[Dovecot] Virtual Folders
by James Turnbull 25 Sep '06

25 Sep '06

Hi Just wondering if Virtual Folder functionality was on the roadmap for Dovecot? Thanks James Turnbull -- James Turnbull <james(a)lovedthanlost.net> --- Author of Pro Nagios 2.0 (http://www.amazon.com/gp/product/1590596099/) Hardening Linux (http://www.amazon.com/gp/product/1590594444/) --- PGP Key (http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x0C42DF40)

3 4

[Dovecot] Upgrading
by Chris Kenward 25 Sep '06

25 Sep '06

Hi Folks OK - I'm ready to upgrade my version .99.11 to the latest release candidate but I haven't a clue how to do that on a live mail server without potential disruption. Can anyone help with advice on the best way to do this? CentOS latest release Running Sendmail/Procmail/Dovecot Thanks Chris

3 2

[Dovecot] Allow login via aliases
by Beber 23 Sep '06

23 Sep '06

Hello, I've created aliases for users on my mail server, and I would like that users can login via any of there aliases. Is it possible ? Thanks -- Beber - E-Mail / Jabber (+GMail) : beber_AT_meleeweb.net http://www.meleeweb.net

2 1

[Dovecot] PAM authentication problem: MD5 vs crypt
by bhayden＠umn.edu 23 Sep '06

23 Sep '06

Here's a strange one. I have Dovecot set up on Solaris 9. The auth portion of the config is straight out of the box. Using PAM. We have most users in a dbm file which is just a series of key/value pairs: key is a username, and value is a string equivalent to a shadow entry. nsswitch.conf entry: passwd files dbm. For historical reasons, some users have a classic 13-character Unix crypt password hash, while others have a 34-character MD5 hash. Here's the situation: User location pw Hash Auth succeeds/fails ---------------------------------------------- files crypt succeeds dbm crypt succeeds files MD5 succeeds dbm MD5 FAILS After two days of research, trussing, and etc, I am stumped. Does anyone have a thought? -Brian

2 2

[Dovecot] Wow! Welcome back Timo!
by Charles Marcus 23 Sep '06

23 Sep '06

You were missed... hope all went well with - whatever you were doing... :)

5 8