similar to: v2.2.10 released

Greetings, I'm new to the list. I have encountered what I believe to be a bug in the return of HIGHESTMODSEQ when talking to a IMAP client. HIGHESTMODSEQ does not appear to be incrementing when a new message arrives. The exact steps I took are: 1) Create a new mail account 2) Send a mail to the account, check that you can receive the email. Send a second mail to the account. 3) perform a

123456789012345678901234567890123456789012345678901234567890123456789012 I appear to have taken a mostly-working installation and mucked it up. In my recent messages I mentioned how I was having difficuilty in making my wife's email readable in Squirrelmail; this was solved with directory permissions. However, my usual email client is Thunderbird; I was holding off on using that as there

http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz.sig A few announcements first: I'm now going to start being more strict about not answering Dovecot questions sent to me privately (especially support requests, but also bug reports, feature requests, etc). Often those questions could be answered by other people in the mailing list as

http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.5.tar.gz.sig A few announcements first: I'm now going to start being more strict about not answering Dovecot questions sent to me privately (especially support requests, but also bug reports, feature requests, etc). Often those questions could be answered by other people in the mailing list as

Hi there, Just wondering what is considered current best practice for managing dovecot? The options I see are: Doveadm binary Doveadm protocol via socket Doveadm http protocol I?m currently on v2.2.10 and it appears the doveadm protocol command set is limited to just the ?mailbox? commands and the http protocol hasn?t been implemented. Is the doveadm http protocol still experimental in v2.3.2?

Have you considered any alternatives? I'm thinking of IPSec to create a secured network encapsulation channel(s) "above" the TCP connection(s). This would provide encryption with control over cipher(s), and cert validation on both sides (if you used cert auth, not PSK). -- K On Thu, Apr 18, 2019, at 12:15 PM, TG Servers via dovecot wrote: > Ok then it seems again a MariaDB

Hello, I'd like to follow up on someone else's old thread: http://dovecot.org/list/dovecot/2012-April/082624.html I understand that Dovecot (that 2012 discussion was about version 2.0.18) can return "HIGHESTMODSEQ 1" upon SELECT if persistent modseq tracking was never enabled for a mailbox. I'd like to get a clarification on how to enable proper persistent modseq

The quota plugin in 2.0.beta6 leaks 2KB "quota settings" pools. Here is a patch to plug this leak, assuming you intended the caller of quota_init to retain ownership of the quota_set. If on the other hand you intended for quota_init to assume ownership of the quota_set, then the quota_settings_deinit call belongs in quota_deinit. --- a/src/plugins/quota/quota-storage.c (beta6) +++

Hi all, i've got a strange behaviour with a BlackBerry Classic Phone (BBOS 10.3.2.2876) in combination with Dovecot 2.2.13 while trying to fetch mails. Before burying myself into debugging sessions, i try to get an understanding if the following is a Client- or a Server-specific error in the behaviour: CIGA8 UID FETCH 10009:10035 (UID FLAGS) (CHANGEDSINCE NOMODSEQ) CIGA8 BAD Error

Hello! I'm attempting to get Dovecot working with MySQL user database on another machine. I can connect to the MySQL (5.7.26) instance with SSL enabled: ?mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem --ssl-cert=/etc/dovecot/client-cert.pem --ssl-key=/etc/dovecot/client-key.pem --ssl-cipher=DHE-RSA-AES256-SHA -u vmail -p However if I use the same values in dovecot-sql.conf.ext, I

Hi, I'm trying to use dsync to convert sdbox + sis mailboxes to mbox (mbox is chosen here to "re-attach" the attachments to their original place) # dsync -Dv -u $LOGIN -o "mail_location=sdbox:/zfspool/clone_srv_mail/$LOGIN" -o "mail_attachment_dir=/zfspool/clone_srv_attachments" backup

> On 18 April 2019 11:34 TG Servers via dovecot <dovecot at dovecot.org> wrote: > > > Hi, > > when using ssl_verify_server_cert in mysql connection string, is the cert verified also against SAN (DNS and IP)? > Because this doesn't seem to work. I get a certification verification error in handshake when connecting via IP. > But the cert is good as the

On 18/07/2019 23:24, Reio Remma via dovecot wrote: > Hello! > > I'm attempting to get Dovecot working with MySQL user database on > another machine. I can connect to the MySQL (5.7.26) instance with SSL > enabled: > > ?mysql -h db.mrst.ee --ssl-ca=/etc/dovecot/ca.pem > --ssl-cert=/etc/dovecot/client-cert.pem > --ssl-key=/etc/dovecot/client-key.pem

I wrote a mostly-working CONDSTORE support for Dovecot today. You can try it with: hg clone http://hg.dovecot.org/dovecot-condstore/ There are a few problems left: - STORE FLAGS.SILENT should be sending FETCH MODSEQ updates - When SELECTing a mailbox while CONDSTORE hasn't yet been enabled in the session, Dovecot returns a higher HIGHESTMODSEQ than what's used after CONDSTORE is

Hello, I am trying to set up file-dictionary based quotas while supporting the SETQUOTA IMAP command. I am using the following configuration : ---- plugin { quota = dict:User quota::file:%h/Maildir/dovecot-quota quota_set = dict:file:%h/Maildir/dovecot-quota } ---- which enables correct quota accounting + setting through SETQUOTA. A user's dovecot-quota file ends with the following

http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz.sig This is a pretty important upgrade for v2.2 users, because of the IMAP ENVELOPE reply fix. * LDA/LMTP: If new mail delivery first fails with "temporary failure", tempfail the whole delivery instead of falling back to delivering the mail to INBOX. (Requires new Pigeonhole

http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz.sig This is a pretty important upgrade for v2.2 users, because of the IMAP ENVELOPE reply fix. * LDA/LMTP: If new mail delivery first fails with "temporary failure", tempfail the whole delivery instead of falling back to delivering the mail to INBOX. (Requires new Pigeonhole