[mail-crypt-plugin] Password Query for Folder Keys questions
In Folder key plugin operation mode, using the following password query: password_query = SELECT \ email as user, password, \ '%w' AS userdb_mail_crypt_private_password \ FROM virtual_users WHERE email='%u'; Say I have two 'email' users...will each 'email' have a 'userdb_mail_crypt_private_password' field with a plaintext password (%w) in it? And is the 'userdb_mail_crypt_private_password' used automatically to decrypt the user private key which is stored in 'mail_attribute_dict' ? Sent with [ProtonMail](https://protonmail.com) Secure Email.
Re: Convert Maildir to Dbox?
On Wed May 29 2019 02:00:24 GMT-0400 (Eastern Standard Time), Aki Tuomi via dovecot wrote: > On 29.5.2019 8.17, @lbutlr via dovecot wrote: >> Are you sure you read >> it? https://wiki2.dovecot.org/MailboxFormat/dbox seems pretty clear. > David, in particular, is there some question you feel that the wiki > fails to answer? I'm not David, but I just read the entire page and one thing that I was specifically interested in has to do with the importance of the index files. I seem to recall reading somewhere that dovecot saves more than one version of the index files to reduce the chance of losing the indexes, but I don't see anything about that. Also - is it possible to configure dovecot to keep multiple copies? I was also planning on putting the indexes on either a ZFS or BTRFS partition to further reduce the chance of data loss (self-healing preventing silent data corruption, and snapshots), but only saw a comment that they can be stored in a different location, but nothing about why you might want to do that - e.g., to use a more resilient filesystem to store these critical files. Another aspect I'd like to see is recommendations for backup strategies, with respect to the fact that the indexes are so critical.
Re: Changes in sieve Dovecot 2.2
In sieve, 'keep' is usually equivalent to 'fileinto "INBOX"'. As such,
you ending up with duplicates in that configuration does not seem
strange as both of those operations will cause a copy of the message to
be filed to your inbox.
Your new configuration is correct.
That said, Dovecot's sieve implementation, Pigeonhole, is versioned
separately from Dovecot itself. Therefore, you should determine which
pigeonhole version you upgraded from (we are currently at 0.5.6), and
possibly peruse the Pigeonhole changelog to find the change:
https://raw.githubusercontent.com/dovecot/pigeonhole/0.5.6/NEWS
Best regards,
Eirik
On 29/05/2019 17:48, Gter Marcelo via dovecot wrote:
Hi People,
I'm use dovecot in my mailbox system, until last month i used the
dovecot version 2.0 and now i use version 2.2, version 2.2 works well
for me, but i have one small problem, in sieve.
In version 2.0 i had rules in sieve similiar to rule bellow:
if allof (true){
keep;
fileinto "INBOX";
redirect "xx"xx.com.br ";
stop;
}
In the new version 2.2 this rules above, i have one problem duplicate
messages in account from my clients, in paste INBOX, therefore, i
changed rule to bellow ( with remove fileinto inbox)
if allof (true){
keep;
redirect "xx"xx.com.br ";
stop;
}
Dovecot really changed your behavor, i did right to fix this ?
Thanks a Lot,
Marcelo
Re: JMAP support in Dovecot
Thanks for chiming in Bron! I'm very interested in JMAP as you can see, but I'm also very curious - do you have any blog pages dedicated to the user experience vs standard IMAP? How it differs - and most importantly if it is truly better, and if so, how and why? I'd also love to read about actual user experiences - how about a collection of comments from your users? Thanks again, Charles p.s. Even though I've always hosted my own, I'm very tempted to sign up for a paid account to see for myself. On Tue May 28 2019 03:49:25 GMT-0400 (Eastern Standard Time), Bron Gondwana via dovecot wrote: > On Wed, May 22, 2019, at 23:43, Tanstaafl via dovecot wrote: >> On Wed May 22 2019 05:44:59 GMT-0400 (Eastern Standard Time), Aki Tuomi >> via dovecot wrote: >> > Unfortunately we have not been able to work on this much, but also the >> > JMAP spec was until very recently still being worked. We have open >> > dialogue with the Thunderbird people, they haven't so far indicated any >> > pressing need for JMAP in Dovecot. >> > >> > This said, JMAP is still very much in our roadmap. Perhaps just not as >> > close as I initially thought. > > Obviously I'd love to help out in any way possible here! We're very > keen to see JMAP support in Dovecot to encourage others to move > towards it as well. > >> Thanks Aki - no pressing need because of the old chicken/egg problem I >> guess... >> >> That said, a few tidbits... >> >> The Thunderbird Devs are using Topicbox for discussing Thunderbird UI >> development, and Topicbox is built directly on top of JMAP for the email >> integration (I'm not sure they even knew this until I told them >> yesterday): >> >> From: https://fastmail.blog/2018/12/27/jmap-is-on-the-home-straight/ >> >> "But enough about the software, how about the experience! When we >> created our brand new Topicbox product, we built directly on top of JMAP >> for the email. We also used JMAP-inspired APIs for the rest of the >> product experience, so Topicbox’s early users have been on JMAP for over >> a year now." >> >> Lastly, Fastmail is now rolling it out - 30% of their userbase is on >> JMAP, and all new users are automatically on it. Cyrus also provides >> experimental JMAP support in their development snapshots. > > Actually, 99% of our user base has been on JMAP for about 4 months > now! The one remaining percent was users with the old version of our > mobile apps, and they're being cut off next month. > > As for JMAP mail and JMAP core - they're currently with the RFC editor > for the final round of edits - they should have assigned RFC numbers > in the next few weeks I would imagine. There will be some minor > editorial polish, but the way it works is entirely stable now, there > won't be more changes. > > https://datatracker.ietf.org/doc/draft-ietf-jmap-core/ > https://datatracker.ietf.org/doc/draft-ietf-jmap-mail/ > > We're planning to have full support for everything in those specs into > Cyrus IMAP version 3.2 as well. Right now there's a couple of gaps > that we either don't use at FastMail or are papering around with our > perl middleware. You can see the remaining tasks here as we progress: > > https://github.com/cyrusimap/cyrus-imapd/labels/3.2 > > Cheers, > > Bron. > > > > -- > Bron Gondwana > br...@fastmail.fm > >
Changes in sieve Dovecot 2.2
Hi People,
I'm use dovecot in my mailbox system, until last month i used the dovecot
version 2.0 and now i use version 2.2, version 2.2 works well for me, but i
have one small problem, in sieve.
In version 2.0 i had rules in sieve similiar to rule bellow:
if allof (true){
keep;
fileinto "INBOX";
redirect "xx"xx.com.br";
stop;
}
In the new version 2.2 this rules above, i have one problem duplicate
messages in account from my clients, in paste INBOX, therefore, i changed
rule to bellow ( with remove fileinto inbox)
if allof (true){
keep;
redirect "xx"xx.com.br";
stop;
}
Dovecot really changed your behavor, i did right to fix this ?
Thanks a Lot,
Marcelo
UNSUBSCRIBE
UNSUBSCRIBE --- Regards Colin Hart On 2019-05-29 05:17, @lbutlr via dovecot wrote: > Are you sure you read it? https://wiki2.dovecot.org/MailboxFormat/dbox seems > pretty clear. > > -- > This is my signature. There are many like it, but this one is mine.
Re: mail_max_userip_connections
> On 29 May 2019, at 4.40, hfh--- via dovecot wrote: > > mail_max_userip_connections > Can I set up an ip whitelist list, and the ip in this whitelist is > unrestricted? thanks!!! mail_max_userip_connections is not enforced for login_trusted_networks Sami
Re: Dict issue with PostgreSQL for last_login plugin (duplicate key)
‐‐‐ Original Message ‐‐‐ On Wednesday, May 29, 2019 8:01 AM, Aki Tuomi wrote: > We'll take this under consideration, but no promises. Thank you very much Aki for consdering this. It would be really fair for all the PostgreSQL users out there.
Re: Dict issue with PostgreSQL for last_login plugin (duplicate key)
> On May 29, 2019, at 2:01 PM, Aki Tuomi via dovecot > wrote: > > We'll take this under consideration, but no promises. Dear Aki, I reported this issue and request before: https://marc.info/?t=15541153161=1=2 Hope we can have this feature soon. :) Thank you very much.
Re: SIGABRT on fetching mail
On 27.5.2019 22.02, Peter Nabbefeld wrote: > > Hello, > > I've never used gdb, so I don't know why I'm running into problems using > "gdb bt". > > Usually, I'm fetching my mail using "sudo -E getmail", but this doesn't > seem to work with backtrace. :-/ > > Output from "dovecot -n" attached. > > Kind regards, > Peter > > > > https://www.dovecot.org/bugreport-mail Maybe this helps? Aki
Re: Dict issue with PostgreSQL for last_login plugin (duplicate key)
On 28.5.2019 22.34, mabi via dovecot wrote: > ‐‐‐ Original Message ‐‐‐ > On Monday, May 20, 2019 12:37 AM, John Fawcett via dovecot > wrote: > >> there's no field name that is obviously the primary key. I've >> reworked the patch to use the postgres default primary key constraint >> name (tablename_pkey). >> >> The attached fix should work in that case, although I feel it's not >> general enough. >> > I saw there has been quite some discussion how to make things more > generic and better for database queries in general in Dovecot around > my issue but I would still be very thankful if your original patch > could be submitted to Dovecot for review and approval. Your patch > solves an immediate problem which is of adding UPSERT functionality to > PostgreSQL Dict queries. > > MySQL Dict queries has its "INSERT ... ON DUPLICATE KEY UPDATE" > implemented in Dovecot so I think it's more than fair that for now > that PostgreSQL support in Dict also gets its equivalent "INSERT ... > ON CONFLICT UPDATE" implemented. > > This is just my opinion as a long-time "user" of Dovecot, I am no dev... We'll take this under consideration, but no promises. Aki
Re: Convert Maildir to Dbox?
On 29.5.2019 8.17, @lbutlr via dovecot wrote: > Are you sure you read > it? https://wiki2.dovecot.org/MailboxFormat/dbox seems pretty clear. > > -- > This is my signature. There are many like it, but this one is mine. David, in particular, is there some question you feel that the wiki fails to answer? Aki
