similar to: how to solve : Dovecot version mismatch: Master is v2.1.7, lmtp is v2.2.13

Dear dovecot users. I have an odd issue in that when I connect to my dovecot server from either a local or remote system I can't see my test emails (I have the impression that is is looking at the wrong location on disk). here are some details.... # dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-xen-amd64 x86_64 Debian 6.0.3 auth_debug = yes auth_debug_passwords = yes

Dear dovecot list. I'm setting up my own VPS and working through getting mail to work. Here is my dovecot -n $dovecot -n maildir:%h/%d/%n/mail : layout=fs # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-5-xen-amd64 x86_64 Debian 6.0.3 auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login cram-md5 auth_verbose = yes auth_verbose_passwords = plain

Every time a user logs into Dovcot's IMAP service PAM closes the session immediately after it opens. I would like a user to have a session open long enough to read some emails. dictator at drakeclasher:~$ sudo dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.14-0.bpo.1-amd64 x86_64 Debian 7.8 mail_location = maildir:~/Maildir namespace inbox

Dear all I have a few public folders setup and working fine, and one such public folder is 'Public/General'. I'm trying to sort dsync replication out to another server and notice that the system log is full of error messages similar to: dovecot: doveadm: Error: dsync-remote(username: Error: Can't update subscription Pu blic/General: Invalid mailbox name The replication setup

Hi, I upgraded from Dovecot v2.0.16 to v2.1.7 over night and I noticed this morning that one of my daily reports which lists summarised mailbox sizes per user has started listing nonsense for vsizes. The reporting script at its core calls : doveadm -f flow mailbox status -A -t 'messages vsize' '*' It appears that Dovecot 2.1.7 is not resetting the vsize after collating the sum

http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz.sig * Session ID is now included by default in auth and login process log lines. It can be added to mail processes also by adding %{session} to mail_log_prefix. + Added ssl_require_crl setting, which specifies if CRL check must be successful when verifying client certificates. +

http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.7.tar.gz.sig * Session ID is now included by default in auth and login process log lines. It can be added to mail processes also by adding %{session} to mail_log_prefix. + Added ssl_require_crl setting, which specifies if CRL check must be successful when verifying client certificates. +

I am trying to have a default sieve rule for new mailboxes that can be edited by users using the round cube sieve plugin. It would actually be better executed when a new user is created but my postfixadmin runs on a separate machine so that's a bit tricky. The "sieve-default =" setting won't quite achieve what I want as I want users to be able to edit the default rule (to

Server: Ubuntu 10.04 LTS 32bit There seems to be an incompatibility when compiling Pigeonhole against Dovecot v2.2.13.rc1. # make check with Pigeonhole throws up the following error message: <snip> Test case: ./tests/extensions/editheader/addheader.svtest: 1: Test 'Addheader - first' SUCCEEDED 2: Test 'Addheader - last' SUCCEEDED 3: Test 'Addheader - framed'

Hello Dovecot users, Now that Dovecot v2.2.13 is released, I can release a new Pigeonhole. Due to changes in Dovecot, this Pigeonhole release will not compile cleanly against older Dovecot releases. This release is mainly about bugfixes. One notable addition is that I have updated the "vnd.dovecot.duplicate" extension to the new IETF draft "duplicate" extension. Changelog

Hello Dovecot users, Now that Dovecot v2.2.13 is released, I can release a new Pigeonhole. Due to changes in Dovecot, this Pigeonhole release will not compile cleanly against older Dovecot releases. This release is mainly about bugfixes. One notable addition is that I have updated the "vnd.dovecot.duplicate" extension to the new IETF draft "duplicate" extension. Changelog

Dear all, we have succesfully configured Dovecot v2.2.13 in debian wheezy 7.8 (using backports) using Maildir structure, to use private index files for the \Seen flag on a per user basis. All users access their emails and Public Folders using IMAP protocol. The problem is that when a user moves an email from publicFolderA to publicFolderB under the same namespace the other users see this

http://dovecot.org/releases/2.2/rc/dovecot-2.2.13.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.13.rc1.tar.gz.sig There have been a ton of smaller and some larger changes since v2.2.12, so I thought I'd first make a RC release and the final v2.2.13 tomorrow. Please try it out! BTW. I've read most of the mails again in Dovecot mailing list, but there are still a few reported

http://dovecot.org/releases/2.2/rc/dovecot-2.2.13.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.13.rc1.tar.gz.sig There have been a ton of smaller and some larger changes since v2.2.12, so I thought I'd first make a RC release and the final v2.2.13 tomorrow. Please try it out! BTW. I've read most of the mails again in Dovecot mailing list, but there are still a few reported

http://dovecot.org/releases/2.2/dovecot-2.2.13.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.13.tar.gz.sig A few minor changes since v2.2.13.rc1, mainly making the Pigeonhole tests pass. * Fixed a DoS attack against imap/pop3-login processes. If SSL/TLS handshake was started but wasn't finished, the login process attempted to eventually forcibly disconnect the client, but failed

http://dovecot.org/releases/2.2/dovecot-2.2.13.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.13.tar.gz.sig A few minor changes since v2.2.13.rc1, mainly making the Pigeonhole tests pass. * Fixed a DoS attack against imap/pop3-login processes. If SSL/TLS handshake was started but wasn't finished, the login process attempted to eventually forcibly disconnect the client, but failed

hi list I upgraded to 1.1.3, and have my logs turned off for some time, but turned it back on when someone complained about moving emails. I saw this in the logs. Seems strange. Using gentoo on AMD 64 bit. All is working fine, but is this a cause for alarm. dovecot: Jun 05 17:10:32 Fatal: imap-login: Dovecot version mismatch: Master is v1.1.rc6, login is v1.1.rc8 (if you don't care, set

Getting the followng error when managesieve is enabled. Any other post I've read says this problem is because the service hasn't restarted after upgrade. I've restarted dovecot & postfix many times, reboot machine too. Still get the error. Racking my brains on this!! May 7 13:21:19 drizzle dovecot: dovecot: Created login processes successfully, unstalling May 7 13:21:20 drizzle

I have a postfix mail server with sql authentication and I want to implement sieve on it. Sieve is working relative good, rules who contain 'fileinto' are executed perfectly. The problem is the redirect to other servers. I configured a rule in Sieve to redirect any email containing "redirect" in subject to a specified foreign destination. # So practically a email coming from

Hi Timo & Dovecot users, We have a 2-node director setup which front-ends for 4 nodes which share a clustered filesystem (GFS). All nodes run Dovecot 2.0.18. Approximately 40k users, but typically only a few thousand active at any time. The director nodes run sendmail, which deliver mail "locally" using LMTP to the director, which then feeds to SMTP on the real servers (also