- dovecot - dovecot.org

[Dovecot] Mbox corruption
by Erinn Looney-Triggs 07 Dec '09

07 Dec '09

I am trying to track down an mbox corruption issue that has been happening for one of our users. It appears that the mbox file is getting truncated and the all important From line no longer exists which then leads to the mbox being useless. It also appears, as in most truncations, that parts of the mbox are being lost. I am not sure how to debug this to find out whether this is a client or server issue and any pointers would be appreciated. Here are the facts as I have them: Server: RHEL5 x64/ Dovecot 1.2.8 Client: Win/ Thunderbird 2.0.0.23 This appears to only be happening for one user out of several hundred across 30 or so Dovecot servers, so I am leaning towards this being a client issue, but I don't know a great deal about the low level working of IMAP to debug. For example, I assume that the client issues a request to the server on the order of delete message 34 and the server then overwrites the mbox file (this then would point to it being a server issue)? The corruption occurs in a random assortment of this users files, so sometimes the inbox, others the Trash or one of many other folders this user has. The user also reports that before the corruption occurs duplicates of e-mail will start to appear in folders, even folders that have been unused for a long period of time. Oh I suppose I should also mention that this is about the third or fourth time this has happened to this user and it seems to happen about every 2-3 weeks. Does any of this sound familiar to anyone? Any suggestions as to how to root this out? Thanks, -Erinn

3 5

[Dovecot] Mbox corruption
by Erinn Looney-Triggs 07 Dec '09

07 Dec '09

> On 12/7/2009, Erinn Looney-Triggs (erinn.looneytriggs at gmail.com) wrote: >> Does any of this sound familiar to anyone? Any suggestions as to how >> to root this out? > > dovecot 0.99.x versions were notorious for this, but haven't heard of > anything like this for recent versions. > > So, this farm of 30 dovecot servers - have you tried to nail down > whether it happens to this user only when they are accessing through one > server? And are you certain that all 30 servers are running 1..2.8, and > configured the same? > > -- > > Best regards, > > Charles Sorry should have been more clear, all 30 systems are completely separate instances, a good example of inter-departmental non-cooperation ;). They are all running version 1.2.8 and are all configured identically minus compile differences for RHEL4 or 5 and x86 vs. x86_64. So the user is always accessing the same server. It is extremely odd that this issue is happening only to this one user on this one system which still make me lean toward it being a client issue but I am unsure of how to determine that. -Erinn

1 0

[Dovecot] 1.1 -> 1.2 upgrade?
by Dave McGuire 07 Dec '09

07 Dec '09

Hey folks. I'm currently running Dovecot v1.1.6, and would like to move to 1.2.x soon. I'm using MySQL-backed LDA and fully virtualized mailboxes. Are there any upgrade gotchas I should be aware of? How much config file hacking should I expect? Thanks, -Dave -- Dave McGuire Port Charlotte, FL

3 4

[Dovecot] forbid some users and machines ?
by Frank Bonnet 07 Dec '09

07 Dec '09

Hello 1 - Is there a way to forbid log in of some Dovecot's users ? I use NIS as authentication mechanism. 2 - Is it possible to forbid some machines (IP addresses ) to connect to Dovecot server ? Thank you

3 2

[Dovecot] [Fwd: fordib some users and machines ( solved !)]
by Frank Bonnet 07 Dec '09

07 Dec '09

Ahem ... not solved the passdb mechanism forbid ALL users

1 0

[Dovecot] fordib some users and machines ( solved !)
by Frank Bonnet 07 Dec '09

07 Dec '09

I just found the right page on the wiki ... Sorry for the noise

1 0

[Dovecot] postmaster_address setting not given
by Stephen Davies 07 Dec '09

07 Dec '09

Hi, I am trying to get dovecot working with postfix, and am coming up against this error message. I have this setting configured in the 'protocol lda' section. I am running v1.1.11 dovecot -n -c /etc/dovecot/dovecot-postfix.conf # 1.1.11: /etc/dovecot/dovecot-postfix.conf # OS: Linux 2.6.31-14-generic x86_64 Ubuntu 9.10 reiserfs log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login login_greeting_capability: yes first_valid_uid: 6060 mail_privileged_group: mail mail_location: maildir:/var/vmail/%d/%n imap_client_workarounds: outlook-idle delay-newmail auth default: mechanisms: plain login debug_passwords: yes passdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf socket: type: listen client: path: /var/spool/postfix/private/dovecot-auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail cat /etc/dovecot/dovecot-postfix.conf protocols = imap log_path = log_timestamp = "%Y-%m-%d %H:%M:%S " disable_plaintext_auth = no syslog_facility = mail ssl_disable = yes mail_location = maildir:/var/vmail/%d/%n mail_privileged_group = mail first_valid_uid = 6060 protocol pop3 { pop3_uidl_format = %08Xu%08Xv mail_max_userip_connections = 3 pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol imap { mail_max_userip_connections = 10 login_greeting_capability = yes imap_client_workarounds = outlook-idle delay-newmail } protocol managesieve { sieve=~/.dovecot.sieve sieve_storage=~/sieve } protocol lda { postmaster_address=postmaster(a)example.com info_log_path = syslog_facility = mail quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r mail_plugins = cmusieve log_path = auth_socket_path = /var/run/dovecot/auth-master sieve_global_path = /var/sieve/global.sieve } auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_debug_passwords = yes auth default { mechanisms = plain login passdb sql { args = /etc/dovecot/dovecot-mysql.conf } userdb sql { args = /etc/dovecot/dovecot-mysql.conf } user = root socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = vmail } client { path = /var/spool/postfix/private/dovecot-auth mode = 0660 user = postfix group = postfix } } } dict { } plugin { } When I run "dovecot -a" I see no mention of the postmaster_address setting. TIA Steve. _________________________________________________________________ View your other email accounts from your Hotmail inbox. Add them now. http://clk.atdmt.com/UKM/go/186394592/direct/01/

3 7

[Dovecot] Mensagem Automatica
by fernando＠dfcom.com.br 07 Dec '09

07 Dec '09

teste

1 0

[Dovecot] virtual domains and SSL certificates
by Dick Middleton 07 Dec '09

07 Dec '09

Hi, This topic has been discussed before e.g: <QUOTE> On 2008-08-07, at 1143, Kacper Wysocki wrote: The problem is that the configuration file specifies only one certificate file for dovecot, which means only one Common Name, which means one cannot provide one server cert that will match mail.foo.com AND mail.bar.com, and either ma...(a)foo.com or bo...(a)bar.com will get a "Security Error: Domain Name Mismatch" in their mail client when connecting through IMAPS. </QUOTE> I bring it up again because I've just been trying the release candidate for Thunderbird 3. This has a config wizard which derives from ones email address the mail server address etc. It doesn't handle SSL virtual mail servers very well because of this problem. I have encountered a web server called Cherokee (http://www.cherokee-project.com) which has virtual server capability that *demands* a different certificate for each virtual server. How can that be I thought? This is what Cherokee documentation says: <QUOTE> SSL Virtual Hosts You might have been told elsewhere that named virtual hosts in SSL cannot be supported without SNI (Server Name Indication) because a web server cannot see the hostname header when the SSL request is being processed. Technically this might have been correct in the past. The first thing that the server has to do is to connect with the other end by using SSL/TLS. The user entered host part of the URI must match the Common Name (CN) provided by the certificate. Since virtual hosts are in use, the CN of the first available certificate may or may not match the one specified in the early stages of TLS negotiation. Cherokee supports the clean and standard method of dealing with this issue called Server Name Indication (SNI) that sends the name of the virtual host during the TLS negotiation. If SNI is supported by your SSL/TLS library, the SSL layer does not need to be restarted. Since the host info can be put in the SSL handshake, things will simply work as long as there is a web browser with SNI support at the other side. Currently every modern web browser supports this, and Cherokee has TLS SNI support for the OpenSSL backends. Note that for SNI to work, client support is required. Web browsers known to support it are Mozilla Firefox 2.0+, Opera 8.0+, Internet Explorer 7 (Vista, not XP) or later and Google Chrome. </QUOTE> If Cherokee can do it why not dovecot? Is this something that is, or could be, being considered? It does assume that TB3 and other mail clients support SNI but whatever, I suspect that once TB3 is released the subject will pop-up more frequently. I'm curious to know the latest thinking. Dick

5 5

[Dovecot] Mensagem Automatica
by fernando＠dfcom.com.br 06 Dec '09

06 Dec '09

teste

1 0