similar to: “doveadm mailbox” command fails with UTF-8 mailboxes

> On Mar 12, 2019, at 3:28 PM, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > >> On 12 March 2019 21:20 Felipe Gasper via dovecot <dovecot at dovecot.org> wrote: >> >> >> Hello, >> >> I?ve got a strange misconfiguration where the following command: >> >> doveadm -f pager mailbox status -u spamutf8 'messages vsize

> On 12 March 2019 21:20 Felipe Gasper via dovecot <dovecot at dovecot.org> wrote: > > > Hello, > > I?ve got a strange misconfiguration where the following command: > > doveadm -f pager mailbox status -u spamutf8 'messages vsize guid' INBOX 'INBOX.*' > > ? fails with error code 68, saying that it can?t find one of the mailboxes. (It lists

On 12 Mar 2019, at 21.20, Felipe Gasper via dovecot <dovecot at dovecot.org> wrote: > > Hello, > > I?ve got a strange misconfiguration where the following command: > > doveadm -f pager mailbox status -u spamutf8 'messages vsize guid' INBOX 'INBOX.*' > > ? fails with error code 68, saying that it can?t find one of the mailboxes. (It lists the

Hi, For CAs that do not include a signed certificate timestamp in their newly-issued certificates, does Dovecot support either OCSP stapling or the Certificate Transparency TLS extension? If the TLS extension is supported, how does the admin configure the timestamp for each certificate? I?m wondering if any MUAs will follow Google?s lead and insist on CT. Thank you! -Felipe Gasper

Hello, We?re rolling out large SNI deployments for our mail servers. Each domain gets an entry like this in the config: local_name mail.foo.com { ssl_cert = </ssl/domain_tls/*.foo.com/combined ssl_key = </ssl/domain_tls/*.foo.com/combined } There are a couple problems we?re finding with this approach: 1) Dovecot wants to load everything at once, which has some machines taking

On 05/01/2018 09:08 AM, Aki Tuomi wrote: > >> On 01 May 2018 at 19:03 Felipe Gasper < felipe at felipegasper.com >> <mailto:felipe at felipegasper.com>> wrote: >> >> >> Hi, >> >> For CAs that do not include a signed certificate timestamp in their >> newly-issued certificates, does Dovecot support either OCSP stapling >> or the

----- cpssltest at cpanelssltest.org [/usr/local/cpanel]# doveadm -v expunge -u cpssltest -- mailbox-guid b8a359119e771b58484a0000a841250d savedbefore 365days; echo $? doveadm(cpssltest): Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied 0 ----- ^^ In the above, shouldn?t the ?doveadm? command have exited nonzero to indicate a failure to connect? Thanks! -Felipe

I have a library I''ve developed that I believe is the most flexible and useful table sorting/striping/row-selecting library around. Big features: Single and multiple-level sort Arbitrary sort criteria (IP address, date, etc.) Works with table headers that are > 1 row or column large Stripe tables and/or enable row selecting Row selecting supports drag-select and SHIFT-click No extra

Is any proven routine to migrate mailboxes from mUTF-7 to UTF-8 encoding? I've try to use doveadm list/mutf7/rename but have been stuck with nested inboxes. Say I have the next structure: INBOX INBOX.??? INBOX.???.??? encoded for FS respectively as .INBOX .INBOX.&BDYESwRA- .INBOX.&BDYESwRA-.&BE8ENARK- ?When I've try to rename ?INBOX.??? with doveadm mailbox rename -u me

Hello, I?m sending doveadm ?kick? commands to doveadm-server via the doveadm protocol. When ?kick? sends back a NOTFOUND error, though, it?s sending back additional output. strace shows: write(3<UNIX:[3158354->3156665]>, "\t\tkick\tmyssltest\n", 17) = 17 ... read(3<UNIX:[3158354->3156665]>, "\n-NOTFOUND\n\n-\n", 8192) = 14 Going by the protocol

Hello, Is there a man page for this command? I don?t see one in the repository. Given its utility in, e.g., syncing mailboxes via SSH, it seems like documentation for this command would be useful? Thank you! -Felipe Gasper

Currently mailbox names are stored in IMAP's modified-UTF-7 format in filesystem. I was wondering about changing this in v2.0. The default would still be to use mUTF-7 in filesystem, but just adding :UTF8 or something to mail_location could enable UTF-8. Any thoughts? Could this be dangerous somehow? UTF-8 enables a lot of weird characters, perhaps no one really wants to see them on

On Wed, Aug 22, 2018 at 09:54:44AM -0400, Felipe Gasper wrote: > If you don?t want to use the HTTP API, you can use the raw doveadm protocol. > > https://wiki.dovecot.org/Design/DoveadmProtocol > > -FG Thanks, I didn't know about that. I suppose testing the HTTP API and then switching to the raw doveadm protocol over TCP if it turns out "crashy" wouldn't mean

> On May 20, 2020, at 10:46 AM, Sami Ketola <sami.ketola at dovecot.fi> wrote: > >> On 16. May 2020, at 3.46, Felipe Gasper <felipe at felipegasper.com> wrote: >> >> Hello, >> >> Some code that I didn?t write but am maintaining passes a local script?s path as dsync?s ?destination? argument, like so: >> >> dsync -D -u john -v backup

Hello, Some code that I didn?t write but am maintaining passes a local script?s path as dsync?s ?destination? argument, like so: dsync -D -u john -v backup -R -1 "/code/dsync_client.pl" 127.0.0.1 john at mydomain.org dsync_client.pl establishes a TCP connection with a remote dsync process then acts as a proxy between the two dsync processes. ?127.0.0.1? and ?john at mydomain.org?

On 23.08.18 15:35, Felipe Gasper wrote: > >> On Aug 23, 2018, at 8:14 AM, James Beck <james.beck at aa.net.uk> wrote: >> >>> On Wed, Aug 22, 2018 at 09:54:44AM -0400, Felipe Gasper wrote: >>> If you don?t want to use the HTTP API, you can use the raw doveadm protocol. >>> >>> https://wiki.dovecot.org/Design/DoveadmProtocol >>>

Hi all, We have Exim using Dovecot for authentication. Dovecot, in turn, consults a custom internal server that answers Dovecot?s userdb queries. When IMAP connections arrive, for some users we want to forward those connections--without authentication--to an external IMAP server. For these users, we return ?proxy_maybe? and ?nopassword? in the authn response from our userdb server. This tells

Hello, How feasible would it be to have a ?pluggable? Dovecot setup that would permit arbitrary logic for fetching TLS/SNI certificates and key, rather than having to hard-code each domain?s resources in a configuration file? A couple scenarios that I envision such a framework being able to accommodate: 1) An internal TLS service that accepts queries via a UNIX socket by domain name and

A small bug in the mail_log plugin: When I copy a mail from the inbox to a mailbox with special characters, the mailbox name is logged in UTF-8: [...] copy from INBOX: box=INBOX.Euro ?, [...] I guess the name should be in mUTF-7, like it is done when I copy the other way round: [...] copy from Euro &IKw-: box=INBOX, [...]

(This is about v1.2 only, v1.1 will stay as it is.) Until today Dovecot didn't care about mailbox names. IMAP RFC requires them to be modified-UTF-7, but Dovecot didn't try to enforce it in any way. Mailbox names in Sieve scripts should be UTF-8, but currently Dovecot doesn't translate them to mUTF-7 as it should. Cyrus also did this until the latest release (v2.3.13). Now that I