Search results for "jmap"

Re: Replication going away?

by Gerald Galster

>> Just to understand that correctly: I could setup a (cron) based process for doveadm sync, but no longer a setup like >> plugin { >> mail_replica = tcp:$IMAP_REPLICA_SERVER:$IMAP_REPLICA_PORT >> } >> where the cron would lead to some delay and would have to check for concurrent jobs? > > You can also have that too. > > doveadm sync -d > > makes it use mail_replica setting. @Aki: Is it possible to monitor actions that would have triggered replication in dovecot < 2.4, e.g. parsing logs or a lua script to imitate the previous behaviour? @Michael Slusarz: While I understand it takes effort to maintain the replication plugin, this is especially problematic for small active/active high-availability deployments. I guess there are lots of servers that use replication for just 50 or 100 mailboxes. Cloudstorage (like S3) would be overkill for these. Do you provide dovecot pro subscriptions for such small deployments? The basic replication functionality with dsync seems to be available in future versions. Would you consider releasing a "dovecot smb" version for small/medium businesses that maintains the replication plugin (without director) for a yearly subscription fee? Otherwise those affected would have to look for alternatives. The recent release of rust-written Stalwart mailserver comes to mind, that bundles a lot of functionality (smtp, pop, imap, jmap, s3, sieve, dkim/arc/spf/dmarc, dane, mta-sas, ...): https://stalw.art/blog/ Best regards, Gerald

1 year, 9 months

v2.2.22 release candidate released

by Timo Sirainen

http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz.sig There are some larger changes here, especially to doveadm to make it support HTTP API. There's still time to do smaller tweaks to the API, so let us know if you have some improvement ideas. Note that the API was designed to look mostly like JMAP, which we're planning to implement also for v2.3. The plan is to fork v2.3 development tree soon. + Added doveadm HTTP API: See http://wiki2.dovecot.org/Design/DoveadmProtocol/HTTP + virtual plugin: Mailbox filtering can now be done based on the mailbox metadata. See http://wiki2.dovecot.org/Plugins/Virtual + stats: Added doveadm stats reset to reset global stats. + stats: Added authentication statistics if auth_stats=yes. + dsync, imapc, pop3c & pop3-migration: Many optimizations, improvements and error handling fixes. + doveadm: Most commands now stop soon after SIGINT/SIGTERM. - auth: Auth caching was done too aggressively when %variables were used in default_fields, override_fields or LDAP pass/user_attrs. userdb result_* were also ignored when user was found from cache. - imap: Fixed various assert-crashes caused v2.2.20+. Some of them caught actual hangs or otherwise unwanted behavior towards IMAP clients. - Expunges were forgotten in some situations, for example when pipelining multiple IMAP MOVE commands. - quota: Per-namespaces quota were broken for dict and count backends in v2.2.20+ - fts-solr: Search queries were using OR instead of AND as the separator for multi-token search queries in v2.2.20+.

9 years, 1 month

[Dovecot-news] v2.2.22 release candidate released

by Timo Sirainen

http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz.sig There are some larger changes here, especially to doveadm to make it support HTTP API. There's still time to do smaller tweaks to the API, so let us know if you have some improvement ideas. Note that the API was designed to look mostly like JMAP, which we're planning to implement also for v2.3. The plan is to fork v2.3 development tree soon. + Added doveadm HTTP API: See http://wiki2.dovecot.org/Design/DoveadmProtocol/HTTP + virtual plugin: Mailbox filtering can now be done based on the mailbox metadata. See http://wiki2.dovecot.org/Plugins/Virtual + stats: Added doveadm stats reset to reset global stats. + stats: Added authentication statistics if auth_stats=yes. + dsync, imapc, pop3c & pop3-migration: Many optimizations, improvements and error handling fixes. + doveadm: Most commands now stop soon after SIGINT/SIGTERM. - auth: Auth caching was done too aggressively when %variables were used in default_fields, override_fields or LDAP pass/user_attrs. userdb result_* were also ignored when user was found from cache. - imap: Fixed various assert-crashes caused v2.2.20+. Some of them caught actual hangs or otherwise unwanted behavior towards IMAP clients. - Expunges were forgotten in some situations, for example when pipelining multiple IMAP MOVE commands. - quota: Per-namespaces quota were broken for dict and count backends in v2.2.20+ - fts-solr: Search queries were using OR instead of AND as the separator for multi-token search queries in v2.2.20+.

9 years, 1 month

New feature: HTTP API

by aki.tuomi＠dovecot.fi

Hi all! We are bringing out HTTP API for doveadm-server in master HEAD. This feature is experimental, and can be expected to have bugs in it and might not always work. If you feel like trying it out though, you can enable it in your configuration file: doveadm_api_key = some-string service doveadm { inet_listener http { port = 8080 } } To use the API, you can go to http://host:8080/doveadm. GET request will print out possible commands, along with their parameters. If you have set API KEY, you need to include it in the request as X-API-Key header. This API has been designed to resemble JMAP API since we are planning to implement it in future version. The rule of thumb is that all the commands work as they would on cli, so the parameters are more or less the same. There are few exceptions, like 'field' parameter in some mail/mailbox commands. Commands are executed by POSTin JSON to /doveadm. The JSON format is [ ["command",{"parameter":"value"},"opaque identifier"], ["command",{"parameter":"value"},"opaque identifier"], ["command",{"parameter":"value"},"opaque identifier"], ... ] Be warned though that even if it supports multiple commands, some commands still use i_fatal to terminate the server if they are unhappy. This will mean you will lose the whole result set, and get no output, so at this point it is safest option to run only one command at a time. If you run into problems or discover issues, please report them in the usual manner to us. Kind regards, Aki Tuomi Dovecot Oy

9 years, 1 month

Re: GMail-like user labels in IMAP/dovecot, situation in 2017?

by Timo Sirainen

On 10 Jan 2017, at 21.00, Gioele Barabucci <gioele(a)svario.it> wrote: > > Hello, > > I am in the process of updating my IMAP dovecot installation and I was > wondering what is the current state of the art for GMail-like > user-defined labels. > > Are GMail-like user-defined labels now somehow achievable with dovecot? I think the main difference between folders and labels is that with folders you have separate flags for a mail in each folder, while with labels there's just one global flags/labels status for the mail. Every other operation can be mapped 1:1 pretty nicely. So the big question is how should this be implemented in a way that allows both regular IMAP access and also label-like access. There are two choices: a) Implement a new storage format where all the mails are in a single physical folder. Treat flags as labels. When accessing with IMAP, create virtual folders based on the flags. This is how GMail works. b) Implement a way to export the current folder-based storage using labels. This could be done with a virtual "all mails" folder, which combines both message flags and folder names into labels for the mails. It also likely means that changing a label changes the flag in each physical folder where the mail exists in. This is what we were planning to do for the Dovecot GMail API support. There are some initial patches for b) that would make it efficient to implement, but they don't work right with replication or with obox format, so they didn't get merged. I think I had some thoughts on how to make them work with a different design, which I probably still have somewhere written down. In any case, priority for GMail API support has dropped pretty low. Most people didn't really care about actually having GMail compatible API, but more about having some kind of a HTTP API. So the plan right now is to add support for JMAP, which also requires support for thread IDs like GMail does, but doesn't require support for labels. > If now, what is missing? Standardized metadata formats? Support in clients? > > I searched the web a bit but I could not find any activity in the > relevant IETF working groups. That seems strange to me, because the > user-defined labels looks like a feature many users would like to have. > I suppose I haven't found the relevant discussion group. Is this kind of > enhancement to IMAP being discussed somewhere? I have a feeling you're thinking about something completely different from what I'm thinking though. You know that we have user-defined flags already, right? What exactly do you want to be different?

8 years, 3 months

Re: [CFP] "Modern Email" Developer Room at FOSDEM '24

by Joris Baum

Hi, yes. This dev room is not specific to dovecot. I think it is nevertheless interesting for the Dovecot community. I was also unsure about sending this call for papers to a few mailing lists as they typically contain technical discussions and information. But FOSDEM is considered a non-commercial event, and it has been some years that an Email room has been scheduled at FOSDEM, so I thought it to be relevant information. If content like that is actually not relevant for this mailing list, I am sorry for that. Just to be more transparent about this, I sent a similar mail to the following lists: info(a)cyrus.topicbox.com , dev(a)lists.roundcube.net and implementation(a)jmap.topicbox.com . Regards, Joris On 22.11.23 20:22, Nick Lockheart wrote: > This exact message was sent to the Cyrus list, too. > > On Wed, 2023-11-22 at 14:06 +0100, Joris Baum wrote: >> Hi, >> >> There will be a developer room that I think will be of particular >> interest for subscribers of this mailing list for "Modern Email" >> during >> FOSDEM '24. It will center around the current state of email, >> free/open >> source software projects related to email and current developments. >> >> FOSDEM is and event for free software and open source developers. The >> event encompasses two main streams: talks curated by organizers >> covering >> diverse topics and the developer rooms. Spread across multiple >> buildings >> at the venue, the developer rooms are focusing on specific concepts, >> technologies, and ideas. This is where the fun is. And most of the >> fun >> will obviously happen in the "Modern Email" room. >> >> The submission deadline for proposals is 1st December 2023. You can >> find >> more info on GitHub: https://github.com/modern-email/FOSDEM-24 . >> >> Regards, >> >> Joris Baum >> >> -- >> Joris Baum >> Tel: +49 721 170293 16 >> Fax: +49 721 170293 179 >> >> http://www.audriga.com | http://www.twitter.com/audriga >> >> --------------------------------------------------------------------- >> ----- >> audriga GmbH | Alter Schlachthof 57 | 76137 Karlsruhe >> Sitz der Gesellschaft: Karlsruhe - Amtsgericht Mannheim - HRB 713034 >> Geschäftsführer: Dr. Frank Dengler, Dr. Hans-Jörg Happel >> --------------------------------------------------------------------- >> ----- >> >> _______________________________________________ >> dovecot mailing list -- dovecot(a)dovecot.org >> To unsubscribe send an email to dovecot-leave(a)dovecot.org > > _______________________________________________ > dovecot mailing list -- dovecot(a)dovecot.org > To unsubscribe send an email to dovecot-leave(a)dovecot.org -- Joris Baum Tel: +49 721 170293 16 Fax: +49 721 170293 179 http://www.audriga.com | http://www.twitter.com/audriga -------------------------------------------------------------------------- audriga GmbH | Alter Schlachthof 57 | 76137 Karlsruhe Sitz der Gesellschaft: Karlsruhe - Amtsgericht Mannheim - HRB 713034 Geschäftsführer: Dr. Frank Dengler, Dr. Hans-Jörg Happel --------------------------------------------------------------------------

1 year, 4 months

Re: v2.2.22 release candidate released

by The Doctor

On Fri, Mar 04, 2016 at 03:33:55PM +0200, Timo Sirainen wrote: > http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz > http://dovecot.org/releases/2.2/rc/dovecot-2.2.22.rc1.tar.gz.sig > > There are some larger changes here, especially to doveadm to make it support HTTP API. There's still time to do smaller tweaks to the API, so let us know if you have some improvement ideas. Note that the API was designed to look mostly like JMAP, which we're planning to implement also for v2.3. The plan is to fork v2.3 development tree soon. > > + Added doveadm HTTP API: See > http://wiki2.dovecot.org/Design/DoveadmProtocol/HTTP > + virtual plugin: Mailbox filtering can now be done based on the > mailbox metadata. See http://wiki2.dovecot.org/Plugins/Virtual > + stats: Added doveadm stats reset to reset global stats. > + stats: Added authentication statistics if auth_stats=yes. > + dsync, imapc, pop3c & pop3-migration: Many optimizations, > improvements and error handling fixes. > + doveadm: Most commands now stop soon after SIGINT/SIGTERM. > - auth: Auth caching was done too aggressively when %variables were > used in default_fields, override_fields or LDAP pass/user_attrs. > userdb result_* were also ignored when user was found from cache. > - imap: Fixed various assert-crashes caused v2.2.20+. Some of them > caught actual hangs or otherwise unwanted behavior towards IMAP > clients. > - Expunges were forgotten in some situations, for example when > pipelining multiple IMAP MOVE commands. > - quota: Per-namespaces quota were broken for dict and count backends > in v2.2.20+ > - fts-solr: Search queries were using OR instead of AND as the > separator for multi-token search queries in v2.2.20+. Running into a problem. >From the logs: Main log Mar 05 18:53:13 master: Info: Dovecot v2.2.22.rc1 (fe789d2) starting up for ima p, pop3, lmtp (core dumps disabled) Mar 05 18:53:16 pop3-login: Debug: SSL: where=0x10, ret=1: before/accept initia lization [172.219.116.147] Mar 05 18:53:16 pop3-login: Debug: SSL: where=0x2001, ret=1: before/accept init ialization [172.219.116.147] Mar 05 18:53:16 pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv2/v3 read cli ent hello A [172.219.116.147] Mar 05 18:53:16 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client hello A [172.219.116.147] Mar 05 18:53:16 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server hello A [172.219.116.147] Mar 05 18:53:16 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write certif icate A [172.219.116.147] Mar 05 18:53:17 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write key ex change A [172.219.116.147] Mar 05 18:53:17 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write server done A [172.219.116.147] Mar 05 18:53:17 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 flush data [ 172.219.116.147] Mar 05 18:53:17 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client certificate A [172.219.116.147] Mar 05 18:53:17 pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client key exchange A [172.219.116.147] Mar 05 18:53:17 pop3-login: Debug: SSL: where=0x2002, ret=-1: SSLv3 read client key exchange A [172.219.116.147] Mar 05 18:53:17 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read client key exchange A [172.219.116.147] Mar 05 18:53:17 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read certifi cate verify A [172.219.116.147] Mar 05 18:53:17 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 read finishe d A [172.219.116.147] Mar 05 18:53:17 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write sessio n ticket A [172.219.116.147] Mar 05 18:53:17 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write change cipher spec A [172.219.116.147] Mar 05 18:53:17 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 write finish ed A [172.219.116.147] Mar 05 18:53:17 pop3-login: Debug: SSL: where=0x2001, ret=1: SSLv3 flush data [ 172.219.116.147] Mar 05 18:53:17 pop3-login: Debug: SSL: where=0x20, ret=1: SSL negotiation fini shed successfully [172.219.116.147] Mar 05 18:53:17 pop3-login: Debug: SSL: where=0x2002, ret=1: SSL negotiation fi nished successfully [172.219.116.147] Mar 05 18:53:17 POP3(aboo):Debug: Added userdb setting: plugin/aboo=yes Mar 05 18:53:17 pop3-login: Info: Login: user=<aboo>, method=PLAIN, rip=172.219 .116.147, lip=204.209.81.1, TLS Mar 05 18:53:17 POP3(aboo):Debug: Effective uid=3094, gid=100, home=/usr/home/a boo Mar 05 18:53:17 POP3(aboo):Debug: fs: root=/usr/home/aboo/mail, index=, indexpv t=, control=, inbox=/var/mail/aboo, alt= Mar 05 18:53:17 POP3(aboo):Info: Disconnected: Logged out top=0/0, retr=0/0, de l=0/8, size=210851 Mar 05 18:53:17 pop3-login: Debug: SSL alert: close notify [172.219.116.147] 2nd log Mar 05 18:53:13 config: Error: Couldn't load plugin /usr/dovecot2221/lib/doveco t/settings/libmanagesieve_login_settings.so: Module is for different ABI versio n 2.2.ABIv13(2.2.13) (we have 2.2.ABIv22(2.2.22.rc1)) Mar 05 18:53:13 config: Error: Couldn't load plugin /usr/dovecot2221/lib/doveco t/settings/libmanagesieve_settings.so: Module is for different ABI version 2.2. ABIv13(2.2.13) (we have 2.2.ABIv22(2.2.22.rc1)) Mar 05 18:53:13 auth: Error: passwd-file /etc/passwd: User root has invalid UID '0' Mar 05 18:53:13 auth: Error: passwd-file /etc/passwd: User doctor has invalid G ID '0' Mar 05 18:53:17 auth: Error: recvmsg() failed: Resource temporarily unavailable Mar 05 18:53:17 auth-worker(20615): Error: passwd-file /etc/passwd: User root h as invalid UID '0' Mar 05 18:53:17 auth-worker(20615): Error: passwd-file /etc/passwd: User doctor has invalid GID '0' l/.imap/INBOX/dovecot.index.log: Operation not supported Lifetime of dovecot 2.22.22.rc1 5 seconds up. Lifetime of 2.2.18 endless unless interrupted. Help. -- Member - Liberal International This is doctor@@nl2k.ab.ca Ici doctor@@nl2k.ab.ca God,Queen and country!Never Satan President Republic!Beware AntiChrist rising! http://www.fullyfollow.me/rootnl2k Look at Psalms 14 and 53 on Atheism Manitoba and Saskatchewan! Save your provinces in April! Vote Liberal!!

9 years, 1 month

Search results for query "jmap"