July 2012 - dovecot - dovecot.org

[Dovecot] Help needed with configuration giving dict error No such file
by Ajax 31 Jul '12

31 Jul '12

Each time a mail message is delivered to a mailbox records like the following appear in /var/log/dovecot.warn: Jul 29 10:02:05 iris dovecot: lmtp(29320, jax(a)XXX.com) Error: file dict commit: file_dotlock_open(/var/vmail/XXX.com/jax/home/maildir/dovecot-quota) failed: No such file or directory Jul 29 10:02:05 iris dovecot: lmtp(29320, jax(a)XXX.com) Error: file dict commit: file_dotlock_open(/var/vmail/XXX.com/jax/home/maildir/dovecot-quota) failed: No such file or directory Jul 29 10:02:05 iris dovecot: lmtp(29320, jax(a)XXX.com) Error: dict quota: Quota update failed, it's now desynced This is with Dovecot 2.1.7 installed by Debian Squeeze binary packages, dovecot-core v 1:2.1.7-2~bpo60+1, and friends. The host is running GNU/Linux 3.2.0-0.bpo.2-amd64 and on a xfs filesystem. Entries in /etc/dovecot/users look like this: jax@XXX.com:{plain}password The output from 'doveconf -n' is in the attachment to this mail message. I'm a beginner without experience with either IMAP servers or clients. Can you give me pointers to see what I'm missing that causes the errors logged as above? The user data base looks like this: userdb { args = uid=5000 gid=5000 home=/var/vmail/%d/%n/home mail=maildir:/var/vmail/%d/%n driver = static } Being a beginner, I wonder if is necessary to manually make home directories for each '/var/vmail/%d/%n/home'? I've tried test accounts with and without empty "home" directories at the indicated locations without seeing any difference in the error indications. Is it necessary to manually populate the "home" directories? Besides having no clue about the errors logged, I don't understand what it takes to make quotas work nor do I understand what options are available or advisable. The distribution wiki/QuotaMaildir.txt seems clear that the Maildif+++ backend is indicated but beyond that I remain in the dark. FWIW, I've yet to try a real IMAP client. Thank you for any pointers you can give me.

2 1

[Dovecot] Problem with running two dovecot instances on the same server
by Alexandr Sabitov 31 Jul '12

31 Jul '12

Hello All, Have anyone met the problem I am struggling with at the moment ? The problem is when I run two instances of dovecot 2.1.8 which are one for proxy-director and another one is a regular one on the same server then I have big amount of strange entries in the /var/log/mail.err: Jul 26 11:51:20 dovecot-test-1 dovecot: director: Error: Empty server list Jul 26 11:51:20 dovecot-test-1 dovecot: director: Fatal: Invalid value for director_mail_servers setting Jul 26 11:51:20 dovecot-test-1 dovecot: master: Error: service(director): command startup failed, throttling for 60 secs Jul 26 11:52:20 dovecot-test-1 dovecot: director: Error: Empty server list Jul 26 11:52:20 dovecot-test-1 dovecot: director: Fatal: Invalid value for director_mail_servers setting Jul 26 11:52:20 dovecot-test-1 dovecot: master: Error: service(director): command startup failed, throttling for 60 secs That's for sure set->director_mail_servers variable in main_preinit of ./src/director/main.c But after dumping it it turns out that ppid of the process which failed to use main_preinit function is a "regular" dovecot not the proxy one. When main_preinit is used by dovecot-proxy then set->director_mail_servers = ip address of a mail server and it is all good but if main_preinit is used by dovecot then set->director_mail_servers = empty and I get fatal errors in logs. So here is a question: How come that "non-proxy" dovecot requests director_mail_servers variable and writes fatal error in the logs if it doesn't find it ? Thank you very much for any assistance! Please find my configs: DOVECOT: root@dovecot-test-1:~/software/dovecot/dovecot-2.1.8# /usr/local/dovecot/sbin/dovecot -n # 2.1.8: /usr/local/dovecot/etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.5 auth_mechanisms = plain digest-md5 cram-md5 apop auth_verbose = yes base_dir = /var/run/dovecot/ default_internal_user = webmail disable_plaintext_auth = no doveadm_password = secret listen = 192.168.0.42 mail_fsync = always mail_location = maildir:~/ mail_nfs_index = yes mail_nfs_storage = yes mail_plugins = " quota fts fts_solr" mmap_disable = yes passdb { args = /usr/local/dovecot/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } plugin { fts = solr fts_solr = break-imap-search url=http://localhost:8080/solr/ quota = maildir:User quota } service doveadm { inet_listener { port = 8282 } } service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service imap { executable = imap } service lmtp { inet_listener lmtp { port = 24 } } service pop3-login { inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service pop3 { executable = pop3 } ssl_cert = </usr/local/dovecot/ssl/dovecot.pem ssl_key = </usr/local/dovecot/ssl/dovecot.pem userdb { args = /usr/local/dovecot/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol imap { mail_plugins = " quota fts fts_solr imap_quota" } DOVECOT-PROXY: root@dovecot-test-1:~/software/dovecot/dovecot-2.1.8# /usr/local/dovecot/sbin/dovecot -c /usr/local/dovecot/etc/dovecot/dovecot-proxy.conf -n # 2.1.8: /usr/local/dovecot/etc/dovecot/dovecot-proxy.conf # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.5 auth_verbose = yes base_dir = /var/run/dovecot-proxy default_internal_user = webmail director_mail_servers = 192.168.0.42 director_servers = 192.168.0.41 disable_plaintext_auth = no doveadm_password = secret doveadm_proxy_port = 8282 instance_name = dovecot-proxy listen = 192.168.0.41 login_greeting = Dovecot Proxy ready. mail_location = maildir:~/ passdb { args = proxy=y nopassword=y driver = static } service auth-worker { user = webmail } service auth { client_limit = 2400 } service director { fifo_listener login/proxy-notify { mode = 0666 } inet_listener { port = 8181 } unix_listener director-userdb { mode = 0600 } unix_listener login/director { mode = 0666 } } service doveadm { inet_listener { port = 8282 } } service imap-login { executable = imap-login director inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service imap { service_count = 0 } service lmtp { inet_listener lmtp { port = 24 } } service pop3-login { executable = pop3-login director inet_listener pop3 { port = 110 } inet_listener pop3s { port = 995 ssl = yes } } service pop3 { service_count = 0 } ssl_cert = </usr/local/dovecot/ssl/dovecot.pem ssl_key = </usr/local/dovecot/ssl/dovecot.pem userdb { args = /usr/local/dovecot/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } protocol imap { mail_max_userip_connections = 100 } protocol doveadm { auth_socket_path = director-userdb } -- Regards, Alexandr Sabitov

3 6

[Dovecot] maildir_copy_with_hardlinks on v.2.0.19
by mailing list subscriber 31 Jul '12

31 Jul '12

Hi, I'm trying to get the so-called "single instance store" (I think cyrus has got the name for the first time) with dovecot --version = 2.0.19 binary package installed from ubuntu 12.04 lts official repo. I have checked that "maildir_copy_with_hardlinks" is enabled ("dovecot -a|grep hard" shows "yes") then I have installed and enabled the lmtp component of dovecot. The configuration "dovecot -n" is pasted here: http://paste.lug.ro/131180 Also in the same paste is a strace against dovecot and childrent showing evidence of the MTA delivering a single copy of the message via LMTP with multiple RCPT TO: headers. However when looking in the Maildir, I see the mail break down into three separate files instead of expected hardlinked files ("stat" and "ls" shows one single link count, inodes are different) Given the above data, what (am I | dovecot is) doing wrong? Please cc me if you need additional input when replying as I'm not subscribed to the list (I'll watch the thread online only) Many thanks in advance.

3 6

Re: [Dovecot] [GoLugTech] thunderbird
by Steve Litt 31 Jul '12

31 Jul '12

On Mon, 30 Jul 2012 23:43:49 -0400, Chris Clifton said: > Hi all, > > Do I read it correctly that thunderbird funding is being cut back by > mozilla? > > I'm not on a linux mail client yet, wondering what others are using in > ubuntu for mail client, I need multiple pop3 profiles, good html > support, fast indexing and searching, solid gpg support and all the > usual bells and whistles. Evolution seems to be in pretty widespread > use. Wondering what others like and use heavily. Hi Chris, I tried Evolution once about 10 years ago, and it was too complex and comprehensive for me to understand. The centerpiece of my emailing activity is a Dovecot IMAP server on my daily driver desktop computer. The way it works is that fetchmail grabs all my email from my various POP accounts, pushes them through procmail, whose filters distribute the emails into the proper Dovecot IMAP directories (and also /dev/null stuff from PITA people). As far as I know, my Dovecot has never malfunctioned. Currently, I access my local IMAP with Claws-Mail. Claws is capable, robust, and does what I need without being an ecological disaster like Kmail or intermittently pig slow like Thunderbird. Claws' configuration is difficult to wrap your head around, and very much in need of better documentation, but so far, thanks to a knowledgeable and helpful user community on the mailing list, I've been able to make almost every config change to speed my interaction with Claws. My one complaint about Claws that can't be cured by documentation is its propensity to do everything with one process and one thread, so while you're sending an email or scanning your IMAP, you cannot look at other emails. I also wanted their powerful search to be able to recurse folders, and when nobody volunteered to do it, I tried to do it myself. Making something recursive sounds like simply a matter of writing a simple loop around the existing functionality, but what I found out is, at least this part of Claws was written in a manner resembling MVC, with process and UI completely commingled. For that reason I was unable to make it recursive. I have Claws on my daily driver and all my laptops. Thanks to Kevin Korb's instructions, on the laptops I was able to tell Claws its IMAP server was at 127.0.0.1. I pinholed my OpenBSD/pf firewall appliance to port forward incoming ssh to my daily driver. Then, on my laptop, if I'm at home and on the LAN, I run the following inhouse.sh sudo ssh -NTL 993:127.0.0.1:993 slitt(a)192.168.1.88 While on the road I run this travelling.sh: sudo ssh -NTL 993:127.0.0.1:993 slitt(a)99.99.99.99 In the preceding, 99.99.99.99 is the IP address my ISP gave me, while 192.168.1.88 is the LAN IP address of my daily driver. This makes 127.0.0.1:993 get pushed through ssh to the ISP supplied internet address or the LAN address. So I can use Claws to interact with my daily driver desktop anywhere I go. I'm extremely pleased with this setup. My IMAP tree is trivial to back up, and gives me the assurance that if Claws-Mail ever commits suicide the way Kmail did when they went to Kmail2, I can simply plug in a different IMAP enabled email client. Meanwhile, Claws gives me an extremely productive and easy to use user interface. With my client/server setup, I no longer need to copy all my email too and from the laptop when travelling. I'm going to present on my remote use of my daily driver desktop Dovecot, using Claws and ssh, at tomorrow night's GoLUG meeting. HTH, SteveT Steve Litt * http://www.troubleshooters.com/ * http://twitter.com/stevelitt Troubleshooting Training * Human Performance

2 1

[Dovecot] openbsd + dovecot not downloading emails
by GVG GVG 31 Jul '12

31 Jul '12

Dear list members, first my doveconf -n output: -------------- # 2.0.17 (684381041dc4+): /etc/dovecot/dovecot.conf # OS: OpenBSD 5.1 i386 ffs mail_location = mbox:/var/mail:INBOX=/var/mail/%u mbox_write_locks = fcntl mmap_disable = yes passdb { driver = bsdauth } ssl_cert = </etc/ssl/dovecotcert.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } --------------- when using evolution from a remote linux machine, and try to download/fetch the e-mails from my e-mail server, I get a pop-up window indicationg that is trying to do so (after I did sign-in with my user-id and password!). The problem is taht this process stays there forever and no messages get downloaded! Thanks for your help Tim

2 2

[Dovecot] Address extensions
by Armistead, Kurt 31 Jul '12

31 Jul '12

Hi guys, I'm trying to set up in-mailbox routing for messages using the + delimiter. The server runs postfix and dovecot 1.2.15. I have re-defined the delivery service in master.cf as "-f ${sender} -d ${user}@${nexthop} -n -m INBOX.${extension}" (server was formerly courier) but the routing only works when the destination folder has no uppercase characters. "Folder1" doesn't deliver correctly while "folder2" does. What am I doing wrong? Kurt

2 1

Re: [Dovecot] expire-tool stops on first box with nothing to expire in it
by Joseph Tam 31 Jul '12

31 Jul '12

Timo Sirainen writes: > > In practice, if this query is done on a periodic interval (e.g. daily), > > the date.saved will be roughly correct, and is usable as an age test > > for expungement. > > > > Is there a way to force this value to be cached when the client actually > > saves or moves a message? > > Done for save: http://hg.dovecot.org/dovecot-2.1/rev/c598f76eeeed > > Fixed copy: http://hg.dovecot.org/dovecot-2.1/rev/b13b8267999d > > It still doesn't add it to cache if it's not already cached in both the > source and destination mailbox, but usually it should be after initial > doveadm run. Thanks, Timo. Joseph Tam <jtam.home(a)gmail.com>

1 0

Re: [Dovecot] Enable ACL for master user
by punit_j 30 Jul '12

30 Jul '12

Hi , No one has a solution to this ? Regards, Punit

1 0

[Dovecot] SSL Warnings in Debug Logs
by Asai 29 Jul '12

29 Jul '12

Greetings, In doing some debugging of authentication issues, I'm wondering if these SSL warnings are anything to be investigating? Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x10, ret=1: before/accept initialization [192.168.70.101] Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: before/accept initialization [192.168.70.101] Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2002, ret=-1: SSLv2/v3 read client hello A [192.168.70.101] Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 read client hello A [192.168.70.101] Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write server hello A [192.168.70.101] Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write certificate A [192.168.70.101] Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write key exchange A [192.168.70.101] Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write server done A [192.168.70.101] Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 flush data [192.168.70.101] Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2002, ret=-1: SSLv3 read client certificate A [192.168.70.101] Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2002, ret=-1: SSLv3 read client certificate A [192.168.70.101] Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 read client key exchange A [192.168.70.101] Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 read finished A [192.168.70.101] Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write change cipher spec A [192.168.70.101] Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 write finished A [192.168.70.101] Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2001, ret=1: SSLv3 flush data [192.168.70.101] Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x20, ret=1: SSL negotiation finished successfully [192.168.70.101] Jul 24 11:23:16 triata dovecot: imap-login: Warning: SSL: where=0x2002, ret=1: SSL negotiation finished successfully [192.168.70.101] [root@triata ~]# doveconf -n # 2.0.14: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-194.32.1.el5xen x86_64 CentOS release 5.5 (Final) ext3 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes auth_verbose_passwords = plain mail_debug = yes mail_home = /vmail/%d/%n/home mail_location = maildir:/vmail/%d/%n managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date namespace { inbox = yes location = prefix = separator = / type = private } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } plugin { mail_log_fields = uid box msgid size from sieve = /vmail/%d/%n/sievescript } protocols = imap pop3 lmtp sieve sieve service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { group = vmail mode = 0660 user = vmail } unix_listener auth-userdb { mode = 0660 user = vmail } user = root } service imap-login { process_min_avail = 3 service_count = 0 vsz_limit = 0 } service managesieve-login { inet_listener sieve { port = 4190 } process_min_avail = 0 service_count = 1 vsz_limit = 64 M } ssl_cert = </etc/pki/dovecot/certs/smtpd.pem ssl_key = </etc/pki/dovecot/private/smtpd.pem userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } verbose_ssl = yes protocol lda { hostname = triata.globalchangemultimedia.net mail_plugin_dir = /usr/lib64/dovecot/ mail_plugins = sieve postmaster_address = postmaster(a)globalchangemultimedia.net } protocol imap { imap_idle_notify_interval = 24 mins mail_max_userip_connections = 20 } protocol sieve { mail_max_userip_connections = 10 managesieve_implementation_string = Dovecot Pigeonhole managesieve_logout_format = bytes=%i/%o managesieve_max_line_length = 65536 } -- Asai

2 2

[Dovecot] mysql auth failover failing
by Paul B. Henson 29 Jul '12

29 Jul '12

We are running dovecot to provide authentication for postfix, using two mysql servers in a multi-master replication set as the password source: ---------------------------------------- # 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.37-gentoo-r4 x86_64 Gentoo Base System release 2.0.2 auth_mechanisms = plain login digest-md5 cram-md5 auth_verbose = yes passdb { args = /etc/dovecot/dovecot-sql.conf driver = sql } protocols = none service auth-worker { unix_listener auth-worker { user = postfix } user = $default_internal_user } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = postfix } ssl = no userdb { driver = passwd } --------------------------------------- With an sql config of: ------------------------- driver = mysql connect = host=mysql-1.unx.csupomona.edu host=mysql-2.unx.csupomona.edu dbname=idmgmt user=postfix password=XXXXXXX default_pass_scheme = PLAIN password_query = XXXXXXXXX ------------------------- According to the sample SQL configuration file "HA / round-robin load-balancing is supported by giving multiple host settings, like: host=sql1.host.org host=sql2.host.org". However, as far as I can tell dovecot only connects to the first listed host, and processes all queries through it, there does not appear to be any load-balancing going on. That's not necessarily a dealbreaker; however, high-availability does not appear to be working either. If I shutdown the first mysql server, dovecot starts to log connection failures: Sep 9 15:47:34 tweak dovecot: auth: Error: mysql(mysql-1.unx.csupomona.edu): Connect failed to database (idmgmt): Can't connect to MySQL server on 'mysql-1.unx.csupomona.edu' (111) - waiting for 1 seconds before retry Sep 9 15:47:39 tweak dovecot: auth: Error: mysql(mysql-1.unx.csupomona.edu): Connect failed to database (idmgmt): Can't connect to MySQL server on 'mysql-1.unx.csupomona.edu' (111) - waiting for 25 seconds before retry And postfix starts to fail authentications: Sep 9 15:47:35 tweak postfix/smtpd[5119]: warning: bender.iitsys.csupomona.edu[134.71.250.134]: SASL DIGEST-MD5 authentication failed: Connection lost to authentication server Now and again the authentication process dies: Sep 9 15:47:39 tweak dovecot: auth: Panic: file auth-request-handler.c: line 697 (auth_request_handler_flush_failures): assertion failed: (auth_request->state == AUTH_REQUEST_STATE_FINISHED) Sep 9 15:47:39 tweak dovecot: auth: Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x3f71a) [0x7f25822ca71a] -> /usr/lib64/dovecot/libdovecot.so.0(+0x3f766) [0x7f25822ca766] -> /usr/lib64/dovecot/libdovecot.so.0(+0x198ca) [0x7f25822a48ca] -> dovecot/auth() [0x4137f4] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handle_timeouts+0xd4) [0x7f25822d5fe4] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_handler_run+0x5b) [0x7f25822d6bcb] -> /usr/lib64/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7f25822d5c48] -> /usr/lib64/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f25822c3de3] -> dovecot/auth(main+0x2be) [0x4179de] -> /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f2581898bbd] -> dovecot/auth() [0x40bdc9] Sep 9 15:47:39 tweak dovecot: master: Error: service(auth): child 4154 killed with signal 6 (core dumps disabled) Requests start to pile up: Sep 9 15:51:46 tweak dovecot: auth: Warning: auth workers: Auth request was queued for 25 seconds, 45 left in queue Lookups time out: Sep 9 15:57:22 tweak dovecot: auth: Error: auth worker: Aborted request: Lookup timed out This occasionally pops up: Sep 9 15:58:38 tweak dovecot: auth: Fatal: net_connect_unix(auth-worker) failed: Resource temporarily unavailable And sometimes the auth process gets temporarily disabled: Sep 9 15:58:57 tweak dovecot: master: Error: service(auth): command startup failed, throttling Resulting in more postfix authentication failures: Sep 9 15:58:57 tweak postfix/smtpd[6531]: warning: bender.iitsys.csupomona.edu[134.71.250.134]: SASL DIGEST-MD5 authentication failed: Sep 9 15:59:08 tweak postfix/smtpd[6551]: fatal: no SASL authentication mechanisms To the point where postfix also temporarily throttles smtpd: Sep 9 15:59:21 tweak postfix/master[6526]: warning: /usr/lib64/postfix/smtpd: bad command startup -- throttling Resulting in a complete unavailability of smtp service, not just unavailability of authenticated services. I don't think all authentications fail during the scenario, but I think the majority do. Based on the network traffic, dovecot is almost continuously trying to connect to the first listed server. It sometimes connects to the second listed server, but when it does, the connection does not persist, it goes away almost immediately. Ideally, I would like no authentications to fail if one of the MySQL servers is unavailable. If a few fail just when the server dies, that would be undesirable but acceptable as long as they do not continuously fail while the server is down. Am I doing something wrong? Does the example sql config have incorrect information? We were previously running dovecot 1.2.11, we just recently upgraded to 2. In the previous version, we actually had two different passdb's configured, each one listing only one of the mysql servers. I seem to recall that was the recommendation at the time for high-availability. When that configuration did not seem to work under version 2, I found an updated recommendation to list both servers in the same passdb, which also does not appear to work correctly. I actually went back and tested the older version, and determined it seemed to work okay in the case where the server was up but the service was down, and connections were refused, but also failed a large number of authentication attempts when the server was completely down and connections were timing out. Thanks much... -- Paul B. Henson | (909) 979-6361 | http://www.csupomona.edu/~henson/ Operating Systems and Network Analyst | henson(a)csupomona.edu California State Polytechnic University | Pomona CA 91768

5 19