similar to: alias_for

Any guess at what would cause this? Feb 7 21:20:53 server dovecot: imap(user): Panic: file mailbox-list-fs-iter.c: line 447 (fs_list_get_roots): assertion failed: (full_fs_access) (Sorry, no core dump) According to my logs, this user couldn't start an IMAP session for a 2 hour stretch for hundreds of connections. Then the problem seemed to have went away. I logged back as that

I just added a new namespace-alias with alias_for. Apparently this causes all mailbox indexes to be resynced? Is this intentional and/or is there some way to avoid this? My NFS storage pretty much kills its elf when hundreds of thausands of users needs to resync indexes :) Thanks -- Tom

I've read the web/man pages on dsync, but it's not clear to me whether dsync can be used to export (rather than import) a user's mailbox to a remote non-dovecot IMAP account. (The intention is to use it whenever a user leaves and wants to copy their local mail to Google or whatever. I currently use uw-imapd's mailutil -- it works, but it's dreadfully slow.) As a first crack

Thanks Joseph, Aki, but something missing from upgrade document, where does the dh param file go? I located ssl-parameters.dat so I will put it there. Quoting Joseph Tam <jtam.home at gmail.com>: > On Fri, 22 Jun 2018, Joseph Tam wrote: > >> However, recent advances make this condition obsolete [*] and not >> really safer, so a much faster way to generate a DH key is

Thank you for the response. So, both password files (master and regular user credentials) have the same contents in this scenario, correct? -Kishore On Mon, Aug 3, 2020 at 11:42 PM Joseph Tam <jtam.home at gmail.com> wrote: > On Mon, 3 Aug 2020, Kishore Potnuru wrote: > > > =============== > > Jul 28 11:14:23 auth: Fatal: Master passdb can't have pass=yes if there

On Thu, 20 Dec 2018, Joseph Tam wrote: >> At the expense of sounding stupid, could you please expound on the >> sequence? :) If you want the nitty details (Starting at bottom of page 18) https://tools.ietf.org/html/rfc2831 Joseph Tam <jtam.home at gmail.com>

On Fri, 22 Jun 2018, Aki Tuomi wrote: >> Do I need to make a fresh dh.pem? The upgrade doc tells how to convert >> ssl-parameters.dat but how to make a new one? > > ... or you can make a fresh one using openssl > gendh 4096 > dh.pem This also works openssl dhparam -out dh.pem 4096 > Note that this will require quite a lot of entropy, so you should > probably

On Thu, 10 Aug 2017, Larry Rosenman wrote: > Which mail client on iOS? Sorry, maybe not iOS, but definitely MacOSX Mail app. Joseph Tam <jtam.home at gmail.com>

And here is mine. All dates are todays! # doveadm -f tab fetch -u test at example.org "uid date.saved" mailbox Trash uid date.saved 6829 2018-07-18 06:04:50 6830 2018-07-18 11:10:13 6831 2018-07-18 16:16:15 6832 2018-07-18 16:16:15 6833 2018-07-18 08:22:55 6834 2018-07-18 16:16:15 6835 2018-07-18 08:47:10 6836 2018-07-18 09:12:11 6837 2018-07-18 09:53:31 6838 2018-07-18 11:03:31 SNIP a

Kevin writes: > Appreciate if you could help with this. I have been trying to address this > "slow search" issue for a while with very limited success(I was trying to > implement FTS also), so I will appreciate if you could support. When I'm stumped, one of the diagnostic tools I use is process tracing. Connect via IMAP, in another window/session process trace the IMAP

A mail user reported that he filled up his INBOX (despite reminders he was approaching his filesystem quota), and furthermore, he could not fix the situation because he couldn't expunge message he marked for deletion. The dovecot logs revealed the cause dovecot: imap(user): Error: open(/var/mail/user.lock) failed: Disc quota exceeded This created an impasse where a user cannot free

Nice to get to hear this. However, the password is not stored in clear text here. How then does it work? On Fri, Dec 21, 2018, 00:58 Joseph Tam <jtam.home at gmail.com wrote: > On Thu, 20 Dec 2018, Odhiambo Washington wrote: > > > At the expense of sounding stupid, could you please expound on the > > sequence? :) > > In a nutshell, during protocol handshake, the server

<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> <br> </div> <blockquote type="cite"> <div> On 07/08/2019 00:37 Joseph Tam via dovecot < <a href="mailto:dovecot@dovecot.org">dovecot@dovecot.org</a>> wrote: </div>

I'd like to configure my dovecot service to use the IMAP SPECIAL-USE extension, but have a few questions for those who have used them, or are knowledgable about its use. Using this configuration as an example, namespace { ... mailbox xxx { special_use = \Sent } } Q1) Am I correct that mail client that don't understand SPECIAL-USE extentions will behave the same way with

"Scott W. Sander" writes: > I have noticed that the name of my private server running dovecot appears > in email headers rather than the public-friendly name of my server. Which headers are you taking about? If you're talking about Received: headers, that's usually inserted by your MTA, not dovecot. Joseph Tam <jtam.home at gmail.com>

Timo announced: > https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz > https://dovecot.org/releases/2.2/dovecot-2.2.27.tar.gz.sig > > Note that the download URLs are now https with a certificate from Let's Encrypt. wget complained about ERROR: certificate common name `wiki.dovecot.org' doesn't match requested host name `dovecot.org'. and indeed, the

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 shell script, so no python dependencies. >> https://github.com/Neilpang/acme.sh > > Thanks - I might look at that, but as Ralph mentions in his reply - > Let's encrypt certs are only for three months - never ending circus.

Joseph Ward writes: > I'm aware of at least a couple of fallback options: > ??? -have a self-signed cert for replication and use the Let's Encrypt > one for IMAP/POP > ??? - create firewall rules allowing them to connect to each other over > the public internet so that it can validate the proper cert > ? > These are both much less palatable than simply disabling the

> Old server: > * Ubuntu 10.04.4 LTS > * Dovecot 2.1.13 > * Maildir++ > * Local auth via passwd/shadow files > > New server: > * Debian GNU/Linux 8.6 > * Dovecot 2.2.13 > * Maildir++ > * Quotas enabled > * LDAP > > Basically what's happening is that users are seeing large delays when > navigating between different IMAP folders. So, for example, user

After setting imap_hibernate_timeout to 60s, I could not find any hibernated connections after a few hours. I tested hibernation and made an observation: IDLE'd imap sessions only hibernate if they don't have a mailbox SELECT'd, otherwise they never hibernate. Is this the way it's supposed to work? Joseph Tam <jtam.home at gmail.com>