similar to: No doveadm-save in wiki2?

Displaying 20 results from an estimated 8000 matches similar to: "No doveadm-save in wiki2?"

2017 May 10
2
No doveadm-save in wiki2?
> On May 10, 2017, at 9:50 AM, Sami Ketola <sami.ketola at dovecot.fi> wrote: > > >> On 9 May 2017, at 19.26, KT Walrus <kevin at my.walr.us> wrote: >> >> Is ?doveadm save? an undocumented feature? Or, just well-hidden? >> >> https://wiki2.dovecot.org/Tools/Doveadm <https://wiki2.dovecot.org/Tools/Doveadm> > > That wikipage is
2017 May 10
2
Example for doveadm-save using Doveadm HTTP API
> On May 10, 2017, at 11:06 AM, Sami Ketola <sami.ketola at dovecot.fi> wrote: > > >> On 10 May 2017, at 14.57, KT Walrus <kevin at my.walr.us> wrote: >> >> I could use an example of how to use curl to save a new message to a user?s INBOX using the Doveadm HTTP API. >> > > Here you go: > > doveadm mailbox save > > parameters:
2017 May 10
1
No doveadm-save in wiki2?
> On May 10, 2017, at 10:18 AM, Sami Ketola <sami.ketola at dovecot.fi> wrote: > >> >> On 10 May 2017, at 15.06, KT Walrus <kevin at my.walr.us> wrote: >> >> >>> On May 10, 2017, at 9:50 AM, Sami Ketola <sami.ketola at dovecot.fi> wrote: >>> >>> >>>> On 9 May 2017, at 19.26, KT Walrus <kevin at
2017 May 10
2
Example for doveadm-save using Doveadm HTTP API
I could use an example of how to use curl to save a new message to a user?s INBOX using the Doveadm HTTP API. https://wiki2.dovecot.org/Design/DoveadmProtocol/HTTP <https://wiki2.dovecot.org/Design/DoveadmProtocol/HTTP> Do I really use the -d option and inline the entire new message in the command-line? Or, should I create a temporary .json file with the message wrapped in JSON and pass
2017 May 10
1
Example for doveadm-save using Doveadm HTTP API
> On May 10, 2017, at 5:16 PM, Sami Ketola <sami.ketola at dovecot.fi> wrote: > > >> On 10 May 2017, at 16.26, KT Walrus <kevin at my.walr.us> wrote: >>> >>> # curl -v -X POST -u doveadm:hellodoveadm -H "Content-Type: application/json" -d
2017 May 10
0
No doveadm-save in wiki2?
> On 10 May 2017, at 15.06, KT Walrus <kevin at my.walr.us> wrote: > > >> On May 10, 2017, at 9:50 AM, Sami Ketola <sami.ketola at dovecot.fi> wrote: >> >> >>> On 9 May 2017, at 19.26, KT Walrus <kevin at my.walr.us> wrote: >>> >>> Is ?doveadm save? an undocumented feature? Or, just well-hidden? >>> >>>
2016 Jun 02
2
nginx proxy to dovecot servers
I?m trying to understand how the nginx mail proxy and dovecot work. As a I understand it, nginx can listen on a IP:port for IMAP connections. NGINX then can invoke a PHP script to do authorization and backend server selection. Does NGINX than proxy to the backend dovecot IMAP server all subsequent IMAP commands that the user?s mail client requests? Does the backend dovecot IMAP server do its
2016 Jun 18
2
archive all saved IMAP messages
> On Jun 17, 2016, at 8:01 PM, chaouche yacine <yacinechaouche at yahoo.com> wrote: > > I'm also interested in learning how to do this best. Last time I thought about it is if users have a different e-mail address on the archive server, you can setup a BCC map in postfix that matches the pair of emails (primary email - archive email), this will automatically send all sent
2017 May 10
0
No doveadm-save in wiki2?
> On 9 May 2017, at 19.26, KT Walrus <kevin at my.walr.us> wrote: > > Is ?doveadm save? an undocumented feature? Or, just well-hidden? > > https://wiki2.dovecot.org/Tools/Doveadm <https://wiki2.dovecot.org/Tools/Doveadm> That wikipage is autogenerated from the doveadm manpage? which unfortunately lags behind on the features. We?ll try to update the manpage eventually
2017 Aug 20
3
is a self signed certificate always invalid the first time
> On Aug 20, 2017, at 11:52 AM, Stephan von Krawczynski <skraw at ithnet.com> wrote: > > On Sat, 19 Aug 2017 21:39:18 -0400 > KT Walrus <kevin at my.walr.us> wrote: > >>> On Aug 18, 2017, at 4:05 AM, Stephan von Krawczynski <skraw at ithnet.com> >>> wrote: >>> >>> On Fri, 18 Aug 2017 00:24:39 -0700 (PDT) >>> Joseph
2016 Jun 06
2
Blowfish hashed passwords
>> Maybe, Dovecot could just add support for BLF-CRYPT by using the open source implementation of Blowfish hashing found in https://github.com/php/php-src/tree/master/ext/standard <https://github.com/php/php-src/tree/master/ext/standard>. The implementation looks like a single function to generate the hash. I?m not much of a programmer, but it would seem to me that these .c/.h files
2016 Jun 05
2
Blowfish hashed passwords
> I would love to know why your ubuntu 14.04 system doesn't support sha512-crypt. I just tried SHA512-CRYPT and it is supported on Ubuntu 14.04. I think I was thinking about DBMail instead of Dovecot. I could really use support for BLF-CRYPT since my current password hashes generated by PHP are using Blowfish encryption. Maybe, Dovecot could just add support for BLF-CRYPT by using the
2017 Aug 20
6
is a self signed certificate always invalid the first time
> On Aug 18, 2017, at 4:05 AM, Stephan von Krawczynski <skraw at ithnet.com> wrote: > > On Fri, 18 Aug 2017 00:24:39 -0700 (PDT) > Joseph Tam <jtam.home at gmail.com> wrote: > >> Michael Felt <michael at felt.demon.nl> writes: >> >>>> I use acme.sh for all of my LetsEncrypt certs (web & mail), it is >>>> written in pure
2016 Jun 04
3
Scalability of Dovecot in the Cloud
Does anyone have any idea of how many IMAP connections a single cloud VM (4 vCores at 2.4GHz, 30GB RAM, local SSD storage - non-RAID) can be expected to handle in production. The mailboxes are fairly small (average 5MB total - 50MB max, as I don?t store attachments in Dovecot expect those saved through IMAP in the Sent/Drafts folders) and each user will probably have an average of 2 devices that
2016 Jun 03
3
Blowfish hashed passwords
(I subscribed to a daily digest for this list and can?t figure out how to reply to a reply.) Anyway, Aki Tuomi replied to my feature request saying: > We support in latest 2.2 release > > MD5 MD5-CRYPT SHA SHA1 SHA256 SHA512 SMD5 SSHA SSHA256 SSHA512 PLAIN > CLEAR CLEARTEXT PLAIN-TRUNC CRAM-MD5 SCRAM-SHA-1 HMAC-MD5 DIGEST-MD5 > PLAIN-MD4 PLAIN-MD5 LDAP-MD5 LANMAN NTLM OTP SKEY
2016 Jun 17
2
archive all saved IMAP messages
I need to archive (i.e., send to another mail server) all messages saved on my mail servers. I?ve implemented for SMTP submission, but haven?t figured out how to archive messages saved by IMAP (like to Drafts, Sent, etc.). How would I best implement this? Can I enable Sieve plugin for IMAP? Or, some other method? Like one way backup to archive server? I really only need to archive the messages
2016 Jun 08
2
Advice on once a day message delivery setup
I?m adding once a day mail delivery to my site. Messages are marked by the sender as ?overnight? or ?once a week? delivery. The way I?m planning on implementing this is to queue messages until midnight in a MySQL database. Each mailbox will be kept in two Dovecot mailstores. The first mailstore will give the users IMAP access to their mailbox. A second mailstore will hold the next day?s new
2016 Jul 27
2
any news Enterprise Repository Access?
> That dovecot offers still EE build for free is great, but a road map on > what the future subscription plans are would be nice; e.g low cost fee > for just the repos, higher fees for support etc. That's what I missed. I?d like to see Dovecot distributed in the Docker Store (coming soon) or the Docker Hub. Most enterprises are moving to deploying their apps in containers and these
2017 Feb 22
3
Scaling to 10 Million IMAP sessions on a single server
> On Feb 22, 2017, at 2:44 PM, Timo Sirainen <tss at iki.fi> wrote: > > I guess mainly the message sequence numbers in IMAP protocol makes this more difficult, but it's not an impossible problem to solve. Any thoughts on the wisdom of supporting an external database for session state or even mailbox state (like using Redis or even MySQL)? Also, would it help reliability or
2016 Oct 12
2
Detect IMAP server domain name in Dovecot IMAP proxy
I?m in the process of setting up a Dovecot IMAP proxy to handle a number of IMAP server domains. At the current time, I have my users divided into 70 different groups of users (call them G1 to G70). I want each group to configure their email client to access their mailboxes at a domain name based on the group they belong to (e.g., g1.example.com <http://g1.example.com/>, g2.example.com