- dovecot - dovecot.org

[Dovecot] imap idle and concurrent connections
by Wolfgang Rosenauer 05 Jul '11

05 Jul '11

Hi, in my testing dovecot (1.2 in that case) seems to not notify all idling clients about new "recent" mails but only one of them. The others get usually a message about the new number of mails after some time but never recent ones. Only one client gets notified about a new mail. Is that a known issue or something which might be configuration specific? Wolfgang

3 4

Re: [Dovecot] Exim and Dovecot2 SASL: 435 Unable to authenticate at present
by Sergey Urushkin 04 Jul '11

04 Jul '11

On Mon, 4 Jul 2011 12:38:01 +0200, Andraž 'ruskie' Levstik wrote: > :2011-06-28T21:38:Sergey Urushkin: > >> Hi. I had working Exim 4.71 and Dovecot 1.2.9 SASL configuration on >> Ubuntu >> Lucid, but needed some features from dovecot2, so I installed 2.0.13 >> from >> https://launchpad.net/~carsten-uppenbrink-net/+archive/dovecot2 . >> Now I get >> Subj error while trying to authenticate via dovecot auth-client >> socket. >> However IMAP auth works fine with 2.0.13 and smtp auth worked fine >> until >> upgrade, so I think there is something wrong with dovecot2. >> >> Dovecot logs stay empty even with auth_debug*, just one string >> "auth: Debug: >> Loading modules from bla...". But here is another information that >> may help. >> And if it's needed I can build dovecot myself to ensure that >> ppa-build isn't >> guilty. Or debug some another way. > > If this is still relevant. > > This has been fixed in a later than 4.71 exim - specifically > 4.72(current version is 4.76) so just upgrade and it will work. Thanks, it's working after upgrading. As you adviced, I wanted to check if the latest version works before posting exim bug report. Well, no bug - no report is needed. > > Regards -- Best regards, Sergey Urushkin

1 0

Re: [Dovecot] virtual users
by /dev/rob0 04 Jul '11

04 Jul '11

On Mon, Jul 04, 2011 at 02:58:34PM +0300, Amira Othman wrote: > Iam using dovecot-1.0.7-7.el5 and postfix-2.3.3-2.3.el5_6 on centos > 5.6 I want to configure mail server without system account .I can > send using the virtual account but can't receive and I have this in > log file > > relay=local, delay=0.02, delays=0.02/0/0/0, dsn=5.1.1, > status=bounced (unknown user: "hoda") This is a Postfix problem, not a Dovecot one. It says that the recipient domain is in this list: > mydestination = $myhostname, localhost.$mydomain, localhost, > $mydomain ... but the "hoda" user or alias does not exist in /etc/passwd nor /etc/aliases. See: http://www.postfix.org/VIRTUAL_README.html http://www.postfix.org/ADDRESS_CLASS_README.html The "upgrade" advice is very good. You should not be starting out with something so long past the end of its support. Follow up on Postfix issues on the Postfix list. However, your issue will probably be solved with some time in the documentation. -- Offlist mail to this address is discarded unless "/dev/rob0" or "not-spam" is in Subject: header

1 1

Re: [Dovecot] virtual users
by Charles Marcus 04 Jul '11

04 Jul '11

On 2011-07-04 7:58 AM, Amira Othman wrote: > Iam using dovecot-1.0.7-7.el5 and postfix-2.3.3-2.3.el5_6 Need I say it? Upgrade. Both are now unsupported/EOL for a long time now... -- Best regards, Charles

1 0

Re: [Dovecot] Replication problem I have. And how I think I can get around problem.
by Peter Dolding 04 Jul '11

04 Jul '11

> Mon, 04 Jul 2011 10:46:31 Ed W > On 03/07/2011 07:20, Peter Dolding wrote: > > Now what I need to be able to deal with the problem. > > Have you considered a new Dovecot storage backend? I have plotted some > designs on a napkin a few times.. Consider some kind of storage server > with "eventually consistent" replication capabilities. This could be > used for the metadata storage for all the emails (ie FROM, TO, DATE, > SUBJECT and all the other non body parts you might search on) > Remember I am new to the Dovecot source code. How to code a Dovecot Storage backend it where I might have to start. Really I don't care if the servers are ever fully consistent other than the fact they both contain the same emails. Of course read status shared would be nice. If that status information is out so be it. "eventually consistent" is a deadly thing to try to aim for. Its a simple fact of what needs to be backed up. If a user is at one physical location all the time and connecting to the same server all the time they will not ever see that the 2 servers are not 100 percent synced. For my usage cases lot of times 100 percent synced will be more wasted effort. Roughly synced will be more than suitable. Of course what I am talking about can be used as an foundation to get data from point a to point b. > > Your replication engine can now work in conjunction with Dovecot to sync > changes between servers as quickly as possible, eg if desired implement > a two phase commit when the LDA delivers new emails, so that all storage > servers confirm they have received the new email. You could if you wish > implement quorum support (ie some server which was offline for some mail > deliveries proxies requests to another storage block until it's caught > up syncing) > You are missing something here. My sync's due to issues maybe chaos. So both servers may have been running split from each other both received emails the other has not had users accessing them. Both with users in using the web and local email clients. While all that is going on the servers have to sync. This is very much the worst case. I am sane. I am prepared to give up the users ability to change client programs between servers to make it be able to work. So IMAP unique identifies not be replicated ever. Basically any identifier that cannot be based of a server id + a unique number for server be only unique to the server its on. Basically I cannot ensure quickly and most of the time I don't really need that. As long as the email without breakage is not lost in the server for greater than 15 min without reaching person wanting to read it that would be fine for normal operations. This is still faster than exchange working with pop email accounts. Basically Ed W. I am saying this is the worst I can get away with in a working office. I have gone through the protocals I would most likely ever need to use from a business point of view. pop3 I know basically does not really give a stuff if what is hiding behind is multi master or single master. User might receive a few extra emails if they change between servers. Nothing system killing. As long as the user gets the emails in the end that is the important bit if they a copy for each server bad luck at least they got the email. Too many copies is not a issue from business point of view not getting the copy in the first place is an issue. smtp messages directly from multi locations outgoing does not give a stuff. imap4 who ever invented this protocol for what I want todo I fell like strangling. The id system completely sends you to hell. Business point of view this might be a issue if uses change between servers due to having to download everything again. activesync/Z-push Ok nice. ID are 64 char in size with no defined contents. No ascending order no trouble basically. So nothing stopping me doing server_id:then unique number. So that is most mobile devices covered. Message might disappear when moving between not totally synced servers. Message will catch up as syncs do. So from business usage annoying but issue is not long lasting. Ie custom backend on Z-push and mobile devices will work mostly fine with chaos between the storage servers. MAPI is 64 chars to 512 chars. for ID's. Again nothing in protocol stopping server_id:then unique number. Web applications much of a muchness. Since either they will connect to the same server as the http server at each location so be protected or can be hooked onto a new protocol to know they are connecting to a multi server back end and detect if there are issues going on. Mostly as bad as activesync if you change between hosting locations email syncs might not have caught up with you so a message might disappear temp. So only imap4 is requiring syncing so ids are in order. Question does everyone need imap4 server locations to be interchangeable. I know I don't. Since most people out the office either use web mail or activesync. Only in office will be using imap4. Now I cannot see any fast sane way for imap4 for other than make it id only unique to each server and maybe create like imap 5 for multi server with the option to run locally as a imap5 to imap4 converter. Reason you ask server when it synced with X server and you find out that is older than the copies you have you don't replace. So the client is hiding server to server sync issues. Sometimes the best solution is look at everything and see what is limiting you and deprecate it. If we don't need id aligned we don't need real-time connection. We don't need as reliable of an network. So failures are less. I guess everyone who has tried to sync has attempted to battle the imap protocal. I am mostly the first strange person who has said stuff syncing imap and just go straight past its defect and make the storage work. Simple fault in imap design make the complete back end replication a pain in but when it should be so simple. I have decided of someone else wants imap to be synced let that be their problem. Simple each location stores what they receive. and forwards to all other locations as those locations come on line and the other locations do the reverse. I like the idea of natural event syncing. That the items pure naturally sync with each other. No reprocessing to force syncing due to least amount conflicting data created. Possible for pop MAPI and activesync/Z-push todo natural syncing. IMAP the evil thing just does not want to play ball with natural syncing and it wants to set up events of conflicting data. IMAP might force a real-time synced server in some cases. A master server handing out IMAP id numbers for new messages is one possibility so removing the need change id's on the mail after it is stored. If my web interfaces are using something other than IMAP I could possibly say use webmail until fixed. Worst issues I can see is message read status and other times like that. Where user might have marked a message unread at X on one server and at Y time marked it back read on a different server. But these are more niggles. Better to have the users annoyed by minor niggles and working than unable to work because its broken. Dependable replications the more parts you use the more areas you have for failure. So far my research on what is possible seams to be coming out to reasonable. Hopefully once I have this idea fully ironed out I can start getting into code. I rarely code. But this is a true case I have a problem so I have motivation. Peter Dolding

1 0

[Dovecot] virtual users
by Amira Othman 04 Jul '11

04 Jul '11

Hello All; Iam using dovecot-1.0.7-7.el5 and postfix-2.3.3-2.3.el5_6 on centos 5.6 I want to configure mail server without system account .I can send using the virtual account but can't receive and I have this in log file relay=local, delay=0.02, delays=0.02/0/0/0, dsn=5.1.1, status=bounced (unknown user: "hoda") my main.cf is myhostname = mail.domain.com mydomain = mydomain.com myorigin = $mydomain inet_interfaces = all mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain mynetworks = *.*.*.*/24, 127.0.0.0/8 relay_domains = home_mailbox = Maildir/ #home_mailbox = Mailbox/ alias_maps = hash:/etc/aliases alias_database = hash:/etc/aliases mail_spool_directory = /var/spool/mail #SASL configuration smtpd_sasl_auth_enable = yes broken_sasl_auth_clients = yes smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous #permit SASL suthentication is added smtpd_recipient_restrictions = permit_mynetworks permit_sasl_authenticated reject_unauth_destination smtpd_sender_restrictions = reject_unknown_sender_domain smtpd_sasl_local_domain = smtpd_sasl_authenticated_header = yes smtpd_tls_auth_only = no smtp_use_tls = yes smtpd_use_tls = yes smtp_tls_note_starttls_offer = yes smtpd_tls_key_file = /etc/postfix/ssl/smtpd.key smtpd_tls_cert_file = /etc/postfix/ssl/smtpd.crt smtpd_tls_CAfile = /etc/postfix/ssl/cacert.pem smtpd_tls_loglevel = 1 smtpd_tls_received_header = yes smtpd_tls_session_cache_timeout = 3600s tls_random_source = dev:/dev/urandom mailbox_command = /usr/bin/procmail-wrapper -o -a $DOMAIN -d $LOGNAME #Hide the login banner smtpd_banner = $myhostname ESMTP #Disable verify function and using of TLS transport encryption between server and client disable_vrfy_command = yes virtual_mailbox_base = /home/vmail/ virtual_mailbox_maps = hash:/etc/postfix/virtual virtual_uid_maps = static:511 virtual_gid_maps = static:512 virtual_alias_maps = hash:/etc/postfix/virtual sender_bcc_maps = hash:/etc/postfix/bcc my dovecot.conf if ## Dovecot configuration file protocols = imap imaps pop3 pop3s disable_plaintext_auth = no shutdown_clients = yes ## ## Logging ## log_path = /var/log/dovecot.log ## ## SSL settings ## ## ## Login processes ## mail_location = maildir:~/Maildir ## ## IMAP specific settings ## protocol imap { # list of plugins to load. mail_plugins = quota imap_quota #mail_plugin_dir = /usr/lib/dovecot/imap # The list is space-separated. #imap_client_workarounds = outlook-idle imap_client_workarounds = delay-newmail outlook-idle netscape-eoh } ## ## POP3 specific settings ## protocol pop3 { pop3_uidl_format = %08Xu%08Xv # Required on x86_64 kernels login_process_size = 64 # list of plugins to load. mail_plugins = quota #pop3_client_workarounds = pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } ## ## LDA specific settings ## protocol lda { # Address to use when sending rejection mails. postmaster_address = postmaster(a)example.com } ## ## Authentication processes ## # Executable location #auth_krb5_keytab = auth default { # NOTE: See also disable_plaintext_auth setting. mechanisms = plain login # authentication to actually work. <doc/wiki/PasswordDatabase.PAM.txt> passdb pam { } passdb passwd-file { # Path for passwd-file args = /etc/dovecot/passwd } userdb passwd { } userdb static { args = uid=511 gid=512 home=/home/vmail/%d/%n } user = root socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } dict { #quota = mysql:/etc/dovecot-dict-quota.conf } ## ## Plugin settings ## plugin { } Amira Othman Server Administrator <http://www.cairosource.com/> www.cairosource.com 6 EL Nil EL Abyad, Mohandiseen Cairo, Egypt Direct: +2 02 3303 7175 Mobile: +2 012 220 4165 The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer.

1 0

[Dovecot] Exim and Dovecot2 SASL: 435 Unable to authenticate at present
by Sergey Urushkin 04 Jul '11

04 Jul '11

Hi. I had working Exim 4.71 and Dovecot 1.2.9 SASL configuration on Ubuntu Lucid, but needed some features from dovecot2, so I installed 2.0.13 from https://launchpad.net/~carsten-uppenbrink-net/+archive/dovecot2 . Now I get Subj error while trying to authenticate via dovecot auth-client socket. However IMAP auth works fine with 2.0.13 and smtp auth worked fine until upgrade, so I think there is something wrong with dovecot2. Dovecot logs stay empty even with auth_debug*, just one string "auth: Debug: Loading modules from bla...". But here is another information that may help. And if it's needed I can build dovecot myself to ensure that ppa-build isn't guilty. Or debug some another way. Thanks. dovecot -n: # 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-31-server x86_64 Ubuntu 10.04.2 LTS auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login apop auth_verbose = yes disable_plaintext_auth = no first_valid_gid = 8 first_valid_uid = 8 hostname = mail.domain.lan last_valid_gid = 8 last_valid_uid = 8 lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes listen = * mail_gid = mail mail_location = maildir:~/ mail_plugins = " quota trash" mail_privileged_group = mail mail_uid = mail 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 passdb { args = scheme=CRAM-MD5 username_format=%n /etc/dovecot/passwd.d/%d.passwd driver = passwd-file } plugin { autocreate = Trash autocreate2 = Junk autocreate3 = Drafts autocreate4 = Templates autocreate5 = Sent autosubscribe = Trash autosubscribe2 = Junk autosubscribe3 = Drafts autosubscribe4 = Templates autosubscribe5 = Sent quota = maildir:user quota quota_rule = *:storage=200M sieve = ~/dovecot.sieve sieve_dir = ~/sieve trash = /etc/dovecot/dovecot-trash.conf.ext } postmaster_address = postmaster(a)domain.lan protocols = " imap sieve pop3 sieve" service auth { unix_listener auth-client { mode = 0600 user = Debian-exim } unix_listener auth-userdb { mode = 0600 user = mail } } service managesieve-login { inet_listener sieve_deprecated { port = 2000 } } ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = </etc/ssl/private/dovecot.pem userdb { args = username_format=%n /etc/dovecot/passwd.d/%d.passwd driver = passwd-file } protocol lda { mail_plugins = " quota trash sieve" } protocol imap { imap_client_workarounds = delay-newmail tb-extra-mailbox-sep tb-lsub-flags mail_plugins = " quota trash imap_quota" } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } ################## swaks --to test(a)domain.lan --from=test(a)domain.lan --auth --auth-user=test(a)domain.lan --auth-password=111111 --server 127.0.0.1 -tlsc: (the same without tls, apop) === Trying 127.0.0.1:465... === Connected to 127.0.0.1. === TLS started w/ cipher DHE-RSA-AES256-SHA <~ 220 mail.domain.lan, ESMTP ready ~> EHLO mail.domain.lan <~ 250-mail.domain.lan Hello mail.domain.lan [127.0.0.1] <~ 250-SIZE 26214400 <~ 250-PIPELINING <~ 250-AUTH PLAIN LOGIN <~ 250 HELP ~> AUTH LOGIN <~* 435 Unable to authenticate at present ~> AUTH PLAIN AHRlc3RAZG9tYWluLmxhbgAxMTExMTE= <~* 435 Unable to authenticate at present *** No authentication type succeeded ~> QUIT <~ 221 mail.domain.lan closing connection === Connection closed with remote host. ##################### exim -d+auth output: Exim version 4.71 uid=0 gid=0 pid=29270 D=fbb95cfd Berkeley DB: Berkeley DB 4.8.24: (August 14, 2009) Support for: crypteq iconv() IPv6 PAM Perl Expand_dlfunc GnuTLS move_frozen_messages Content_Scanning DKIM Old_Demime Lookups: lsearch wildlsearch nwildlsearch iplsearch cdb dbm dbmnz dnsdb dsearch ldap ldapdn ldapm mysql nis nis0 passwd pgsql sqlite Authenticators: cram_md5 cyrus_sasl dovecot plaintext spa Routers: accept dnslookup ipliteral iplookup manualroute queryprogram redirect Transports: appendfile/maildir/mailstore/mbx autoreply lmtp pipe smtp Fixed never_users: 0 Size of off_t: 8 GnuTLS compile-time version: 2.8.5 GnuTLS runtime version: 2.8.5 changed uid/gid: forcing real = effective uid=0 gid=0 pid=29270 auxiliary group list: <none> seeking password data for user "root": cache not available getpwnam() succeeded uid=0 gid=0 configuration file is /etc/exim4/exim4.conf log selectors = 0000cefe 00233821 cwd=/ 4 args: /usr/sbin/exim4 -bd -q30m -d+auth trusted user admin user seeking password data for user "Debian-exim": cache not available getpwnam() succeeded uid=103 gid=105 seeking password data for user "Debian-exim": using cached result getpwnam() succeeded uid=103 gid=105 seeking password data for user "mail": cache not available getpwnam() succeeded uid=8 gid=8 originator: uid=0 gid=0 login=root name=root 29270 LOG: MAIN 29270 IPv6 socket creation failed: Address family not supported by protocol 29270 LOG: MAIN 29270 Failed to create IPv6 socket for wildcard listening (Address family not supported by protocol): will use IPv4 29270 listening on all interfaces (IPv4) port 25 29270 LOG: MAIN 29270 IPv6 socket creation failed: Address family not supported by protocol 29270 LOG: MAIN 29270 Failed to create IPv6 socket for wildcard listening (Address family not supported by protocol): will use IPv4 29270 listening on all interfaces (IPv4) port 465 29270 pid written to /var/run/exim4/exim.pid 29270 changed uid/gid: running as a daemon 29270 uid=103 gid=105 pid=29270 29270 auxiliary group list: 105 999 29270 LOG: MAIN 29270 exim 4.71 daemon started: pid=29270, -q30m, listening for SMTP on port 25 (IPv4) and for SMTPS on port 465 (IPv4) 29270 set_process_info: 29270 daemon: -q30m, listening for SMTP on port 25 (IPv4) and for SMTPS on port 465 (IPv4) 29270 daemon running with uid=103 gid=105 euid=103 egid=105 29270 SIGALRM received 29270 1 queue-runner process running 29270 Listening... 29271 Starting queue-runner: pid 29271 29271 exec /usr/sbin/exim4 -q 29270 child 29271 ended: status=0x0 29270 0 queue-runner processes now running 29270 Listening... 29270 Connection request from 127.0.0.1 port 58341 29270 search_tidyup called 29270 1 SMTP accept process running 29270 Listening... 29279 sender_fullhost = [127.0.0.1] 29279 sender_rcvhost = [127.0.0.1] 29279 Process 29279 is handling incoming connection from [127.0.0.1] 29279 host in host_lookup? no (option unset) 29279 set_process_info: 29279 handling incoming connection from [127.0.0.1] I=[127.0.0.1]:465 29279 initializing GnuTLS as a server 29279 read D-H parameters from file 29279 initialized D-H parameters 29279 certificate file = /etc/ssl/certs/dovecot.pem 29279 key file = /etc/ssl/private/dovecot.pem 29279 initialized certificate stuff 29279 host in tls_verify_hosts? no (option unset) 29279 host in tls_try_verify_hosts? no (option unset) 29279 initialized GnuTLS session 29279 gnutls_handshake was successful 29279 cipher: TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32 29279 host in host_reject_connection? no (option unset) 29279 duplicate IP address 127.0.0.1 (MX=-1) removed 29279 gethostbyname2 looked up these IP addresses: 29279 name=localhost address=::1 29279 name=localhost address=127.0.0.1 29279 host in sender_unqualified_hosts? yes (matched "localhost") 29279 duplicate IP address 127.0.0.1 (MX=-1) removed 29279 gethostbyname2 looked up these IP addresses: 29279 name=localhost address=::1 29279 name=localhost address=127.0.0.1 29279 host in recipient_unqualified_hosts? yes (matched "localhost") 29279 host in helo_verify_hosts? no (option unset) 29279 host in helo_try_verify_hosts? no (option unset) 29279 host in helo_accept_junk_hosts? no (option unset) 29279 SMTP>> 220 mail.domain.lan, ESMTP ready 29279 tls_do_write(7f10202175a0, 31) 29279 gnutls_record_send(SSL, 7f10202175a0, 31) 29279 outbytes=31 29279 Process 29279 is ready for new message 29279 smtp_setup_msg entered 29279 Calling gnutls_record_recv(7f102023f0c0, 7f1020241e40, 4096) 29279 SMTP<< EHLO mail.domain.lan 29279 mail.domain.lan in helo_lookup_domains? no (end of list) 29279 sender_fullhost = (mail.domain.lan) [127.0.0.1] 29279 sender_rcvhost = [127.0.0.1] (helo=mail.domain.lan) 29279 set_process_info: 29279 handling TLS incoming connection from (mail.domain.lan) [127.0.0.1] I=[127.0.0.1]:465 29279 host in pipelining_advertise_hosts? yes (matched "*") 29279 host in auth_advertise_hosts? yes (matched "*") 29279 tls_do_write(7f10202229c8, 119) 29279 gnutls_record_send(SSL, 7f10202229c8, 119) 29279 outbytes=119 29279 SMTP>> 250-mail.domain.lan Hello mail.domain.lan [127.0.0.1] 29279 250-SIZE 26214400 29279 250-PIPELINING 29279 250-AUTH PLAIN LOGIN 29279 250 HELP 29279 Calling gnutls_record_recv(7f102023f0c0, 7f1020241e40, 4096) 29279 SMTP<< AUTH LOGIN 29279 dovecot authentication 29279 received: VERSION 1 1 29279 received: MECH PLAIN plaintext 29279 received: MECH LOGIN plaintext 29279 received: MECH APOP private dictionary active 29279 received: SPID 29280 29279 received: CUID 1 29279 received: COOKIE cf735efce15b21bbb10568c4a762017c 29279 SMTP>> 435 Unable to authenticate at present 29279 tls_do_write(7f10202175a0, 39) 29279 gnutls_record_send(SSL, 7f10202175a0, 39) 29279 outbytes=39 29279 LOG: MAIN REJECT 29279 auth_login authenticator failed for (mail.domain.lan) [127.0.0.1] I=[127.0.0.1]:465: 435 Unable to authenticate at present: authentication socket protocol error 29279 Calling gnutls_record_recv(7f102023f0c0, 7f1020241e40, 4096) 29279 SMTP<< AUTH PLAIN AHRlc3RAZG9tYWluLmxhbgAxMTExMTE= 29279 host in smtp_accept_max_nonmail_hosts? yes (matched "*") 29279 dovecot authentication 29279 received: VERSION 1 1 29279 received: MECH PLAIN plaintext 29279 received: MECH LOGIN plaintext 29279 received: MECH APOP private dictionary active 29279 received: SPID 29280 29279 received: CUID 2 29279 received: COOKIE 06f8b3d9441b40b4069f53cdd0d128a4 29279 SMTP>> 435 Unable to authenticate at present 29279 tls_do_write(7f10202175a0, 39) 29279 gnutls_record_send(SSL, 7f10202175a0, 39) 29279 outbytes=39 29279 LOG: MAIN REJECT 29279 auth_plain authenticator failed for (mail.domain.lan) [127.0.0.1] I=[127.0.0.1]:465: 435 Unable to authenticate at present: authentication socket protocol error 29279 Calling gnutls_record_recv(7f102023f0c0, 7f1020241e40, 4096) 29279 SMTP<< QUIT 29279 SMTP>> 221 mail.domain.lan closing connection 29279 tls_do_write(7f10202175a0, 37) 29279 gnutls_record_send(SSL, 7f10202175a0, 37) 29279 outbytes=37 29279 tls_close(): shutting down TLS 29279 LOG: smtp_connection MAIN 29279 SMTP connection from (mail.domain.lan) [127.0.0.1] I=[127.0.0.1]:465 closed by QUIT 29279 search_tidyup called 29270 child 29279 ended: status=0x0 29270 0 SMTP accept processes now running 29270 Listening... -- Best regards, Sergey Urushkin

3 2

[Dovecot] Replication problem I have. And how I think I can get around problem.
by Peter Dolding 04 Jul '11

04 Jul '11

I have two servers in two different locations. Neither what you would call 100 percent safe from being turned off. Most staff use web based email. This backs onto imap server. I do know I will have to deal with contact lists and other items. in that client. Worst part is the link between them may get broken so both servers may be receiving email and back active at the same time. I can see 1 very clear way around this problem. If I accept that the imap ids at each of the server will be that server only. Since users are mostly using webbased they are not going to notice. If they do notice because they have connected to a different domain address stiff bad luck. Now what I need to be able to deal with the problem. 1 a unique server id on each message for the server the message was received on. 1 a unique server receive id for each message as imap like id for service recieved messages for message received directly not synced. 1 logs for messages deleted and changes that are not current server server id. This should be pritty simple todo. Basically 1 log per server flushed when synced with the server it owns to. 1 a sync function that deletes and changes messages that have been deleted or changed at other locations and compares other servers current messages against copies retained at the mirroring location. Now with this. Each new message to each store gets the next imap id along with system wide unique combination of sever id and service receive id. No modifications of already recieved messages ids. Since I am not careing if the imap id are matched between servers. Fairly much able to use a custom for of imap syncing working off the server id's and server receive ids. Of course this solution should be fairly fault torrent. Since each server can directly store any message they receive. Also it should be possible to trace back to what server the message came from in case of spam problems or equal. Now my biggest problem can I attach my own custom attributes to incoming mail to the store and access that information effectively. Since with that information I will be able to do a form of live synced storage. Personally I see imap id design as a defect in protocal since it never allowed server id along with it this is why imap 100 percent synced message stores cannot be run on independent servers with unstable network connects well. Nothing comes without a price. This solution does not require clustered file systems or a constant active connection between servers so able to operate in areas of disruption. It does not block the servers from receiving emails at any time either. Problem is of course is if someone connects a client directly from 1 server to another. Mail will have to be re-downloaded. Also I have to check of z-push/ActiveSync depends on the imap ids being dependable across the network if not most hand held devices will not be a problem. If it don't then only imap has a problem. I can live with that. Ie if local email server down use web mail until local mail server is fixed. Old rule of networking 40 to 50 percent functional network staff can normally still get stuff done. 0 percent functional you have downtime. Now if I can get the email storage fault torrent and to remain operational in case of fault I then can focus on getting the web base applications using a equal system for contacts and other things. So each location can remain fairly operational no matter what. This way if a server disappeared for good only thing that would have to be changed is syncing. Wise move is to allow servers to be defined more than 1 server id. Ie a server gone for good remaining server gets told to take over responsibility for the old servers id messages. New replacement server given a new id and everything keeps on going nice. Anyone else with a better idea or advice how to add my own custom ids in a way they cannot be distrupted and are simple to search. If it works push for server id's in imap5? Ie imap5 clients being able to cope with the event that an email store is spreed between multi servers that may not be connected all the time. Peter Dolding

2 1

[Dovecot] Dovecot error on rhel 6.1 using GFS2(bug)
by Aliet Santiesteban Sifontes 04 Jul '11

04 Jul '11

Hi, just to let you know to all the people testing dovecot in a RHEL 6.1 setup where nodes are Active/Active and sharing a GFS2 filesystem that there is a bug on latest rhel6.1 GFS2 kernel modules, and latest updates in 6.0 wich makes dovecot crash a GFS2 filesystem, with a corruption and other related errors, redhat people have posted a fix for the kernel wich is in QA: https://bugzilla.redhat.com/show_bug.cgi?id=712139 Just hope this helps somebody to don't waste many nights looking for a problem in dovecot config :) as I did... best regards, Aliet

1 0

[Dovecot] Invitation to connect on LinkedIn
by Marcelo Salhab Brogliato via LinkedIn 03 Jul '11

03 Jul '11

LinkedIn ------------ Marcelo Salhab Brogliato requested to add you as a connection on LinkedIn: ------------------------------------------ Michael A., I'd like to add you to my professional network on LinkedIn. - Marcelo Salhab Accept invitation from Marcelo Salhab Brogliato http://www.linkedin.com/e/458g9e-gpoedy6h-6q/V7LnuFRIQXpYNGb2yum6IE4IQU3ZkP… View invitation from Marcelo Salhab Brogliato http://www.linkedin.com/e/458g9e-gpoedy6h-6q/V7LnuFRIQXpYNGb2yum6IE4IQU3ZkP… ------------------------------------------ DID YOU KNOW that LinkedIn can find the answers to your most difficult questions? Post those vexing questions on LinkedIn Answers to tap into the knowledge of the world's foremost business experts: http://www.linkedin.com/e/458g9e-gpoedy6h-6q/ask/inv-23/ -- (c) 2011, LinkedIn Corporation

1 0