similar to: Intermittent "certificate cannot be verified" error

Hi, I'm hoping to upgrade to 1.2 in the next couple of days. I remember seeing something mentioning some sort of config change, but unfortunately I don't remember where I saw it nor what the config option was. Are there any gotchas I need to watch out for in the change to 1.2 from 1.1.8? I've included dovecot -n below. Thanks Guy #dovecot -n # 1.1.8: /etc/dovecot/dovecot.conf # OS:

I'm not sure if it's even intended to work in this particular case, but there's a problem when chroot is explicitely defined and rawlogging is used. Rawlog respects chroot point, without being actually chrooted. Consider configurtion as below, with two cases (dovecot.rawlog dir is of course created earlier, with appropriate uid/gid). 1) dovecot.userdb:

Hi, I've just started trying allow_nets on one of my servers. I have auth_debug and auth_verbose both enabled and the output is as follows: Oct 28 13:05:48 mink dovecot: auth-worker(default): auth(user at domain.net,x.x.x.x): allow_nets: Matching for network 127.0.0.1/8 Oct 28 13:05:48 mink dovecot: auth-worker(default): auth(user at domain.net,x.x.x.x): allow_nets: Matching for network

I have begun havening a problem when sending or when Thunderbird tries to write copy to .Draft. Usually only happens when the message is longer. While in the Thunderbird editor will say "Copying message to Draft folder". It will try indefinitely. The copy is successful but it looks like it is believed to have failed so its retried. Same then happens when sending. Send happens but

Hi, I'm getting a lot of the following messages in my mail.err log. Jul 12 11:25:51 mink dovecot: IMAP(user1 at domain1.net): Corrupted transaction log file /virtual/store1/mail/u/user1_domain1.net/Maildir/.Sent/dovecot.index.log: Append with UID 925, but next_uid = 926 Jul 12 12:44:56 mink dovecot: IMAP(user2 at domain1.net): Corrupted transaction log file

Hi, I recently moved from courier-imap to dovecot, to be able to work with managesieve. I use version 1.2.5, on suse 10.3. I used the script to migrate the courier maildir to dovecot format. It seems to work fine except for one problem : I use a number of aliasses and with Thunderbird I can select which alias (e-mail-address) to use as my identity when sending a mail. I sniffed with wireshark,

Thought this was fixed and now it's back. No help from rawlog as the hang appears prior to authentication. Notice there is around a 90 second delay before authentication fires. Let me know how to proceed debugging. Thanks. _____ Here's my config: listen: *:143 ssl_listen: *:993 ssl_cipher_list: ALL:!LOW:!SSLv2 disable_plaintext_auth: no verbose_ssl: yes login_dir:

Hi all We experience some unexpected behavior with dovecot. It happens that emails marked as read get marked as unread (MUA is Thunderbird on port 143). Unfortunately this happens randomly, reproducing this issue is difficult. We could not find any pattern, it happens rarely. We are running dovecot version 2.2.24 on Debian Jessie (backports repository). /root at dovecot01:~# dovecot --version//

Hi Everyone, I wouldlike to set up a postfix-dovecot with HA using HAproxy but im facing issues. I've followed this documentation : http://wiki2.dovecot.org/HAProxy (pour dovecot) http://blog.haproxy.com/2012/06/30/efficient-smtp-relay-infrastructure-with-postfix-and-load-balancers/ (pour postfix) Package's version : dovecot : 2:2.2.19 (>= 2.2.19 pour proxy protocol)

Hi Timo, Was getting the following error repeatedly in my mail client (squirremail) "error: connection dropped by IMAP server" Looked at the logs for this user and found the following: Nov 19 17:11:32 mink dovecot: IMAP(bobuser at maildom.com): broken sync positions in index file /virtual/store2/mail/s/bobuser_maildom.com/Maildir/dovecot.index Nov 19 17:11:32 mink dovecot:

service submission-login { ? inet_listener submissions { ? ? haproxy = no ? ? port = 465 ? ? reuse_port = no ? ? ssl = yes ? } } Shouldn't the port be 587 here? My config file looks like: service submission-login { ? inet_listener submission { ??? #port = 587 ? } } The # comment must also mean something.. On 7/27/19 3:21 PM, Jean-Daniel via dovecot wrote: > > >> Le 27

Greetings, We are performing a meta-analysis of mink pup survival data versus chemical concentration. We have modeled percent survival successfully using nls as shown below and the plot. What we need to do is construct a confidence interval on the concentration at which we get 50% survival (aka the EC50, although we may want other percent survivals in the future). My first question is, what seems

Hello everyone, I've been asked by a colleague to have a look at some extremely weird dovecot SSL issue they are seeing on one of the student mailservers. They are running dovecot 1.1.6 (yes, I know, a bit old ...) on SLES 10.2 x86_64 with imap(+starttls), imaps, pop3(+starttls) and pop3s enabled. Every couple of weeks the pop3s and pop3+starttls part bail out out. Clients can't connect,

Hi there, I'm using the latest Thunderbird & Dovecot. I'm trying to setup either pop3s or imaps. The plain versions of the protocols both work fine for me, even with the TLS option selected in Thunderbird. But when I try to use the ssl versions, my client does not negotiate - it just time's out. I have as much logging enabled as possible and the only thing that shows up

Hello , Went to /etc/dovecot/dovecot.conf, hunted down "ssl_listen =" which I had set it up to "ssl_listen = required" and commented it out. Tried "service dovecot start" and it started. The USD2,000,000 question being : what does this do (I know , I know, I cannot remember, I documented all this for v1.2.14) and will I need it in the future ? THank you people,

Hello List! I?ve following problem after updating dovecot... Error: (Empty password returned without nopassword) Jan 21 15:56:15 test-mi dovecot: auth(default): new auth connection: pid=83362 Jan 21 15:56:15 test-mi dovecot: auth(default): client in: AUTH 7 PLAIN service=imap lip=192.168.0.32 rip=192.168.0.86 lport=143 rport=2905 resp=AHRrdWV2NUBnb25lby5jb98AdGVzdHVzZXI1

not possible make operation with dovecot version 2.x as was possible in version 1.x: requisites description: connect to dovecot service on IP1 - dovecot must serve users that related to domain1 located in database1 connect to dovecot service on IP2 - dovecot must serve users that related to domain2 located in database2 login must be with username that form not as "user at domain" but

Hi. I would appreciate your advice about this PROBLEM: ======================================================= Find the simplest way to configure a Dovecot 2.2.10 IMAP server to access existing email users' (mbox-format) mail folders via a master_user ****in read-only mode.**** (I've got the master_user access working.) Simplest because while I'm proficient at UNIX systems

Hello kind people, Any help on this would be appreciated. Dovecot v1.2.16. Freshly installed today. Comes up with this during service startup (CentOS 5.5 -> "service dovecot start" <ENTER> : --------------------------- Restarting DovecotFatal: ssl_listen: Can't resolve address required: Name or service not known --------------------------- Here's "dovecot

Hi, I have installed dovecot v1.1.beta2 with the sieve plugin v.1.1.2. I have configured the following namespace: namespace: type: private separator: . prefix: INBOX. location: inbox: yes hidden: no list: yes When I create a rule which should move messages into the subfolder "Junk", Dovecot's deliver seems to ignore the namespace and creates a new folder