Hello,
I'm configuring lazy expunge plugin to act as a kind of backup of my
user's emails.
I'm getting a little problem because a lot of my users use move to
trash behaviour in their email client (most of them are using
thunderbird which has no option to hide deleted messages and is a
On Mon, 2012-08-13 at 17:12 +0100, Chris Webb wrote:
Sharing an installed copy of dovecot between several users each running
a daemon within their own account (or using the same binaries for a
system daemon and a user daemon) is difficult because the compile-time
directory PKG_STATEDIR
Self-explanatory, I hope (note the period on the end of the username);
sieve/pigeonhole does not allow you to have senders which end with a
period, which means that any UNIX users with such usernames who send
mail have it rejected by sieve:
# useradd testuser.
# su - testuser.
$ mail
On 22/08/12 18:16, Gábor Lénárt wrote:
I think nowdays it's a bit outdated to have 1:1 mapping between UNIX
users and email addresses anyway. Maybe it's OK, but it's surely
problematic in case of mass hosting with many users with policies like
you mentioned as well. Virtual users (in the
On Wed, Aug 22, 2012 at 06:45:17PM +0300, David Anderson wrote:
There are no incoming mail accounts for those users. The server in
question is a webserver. Every website has a unique UNIX user, for
security when running scripts. You can't virtualise that. If you run
all your scripts under the
Hello.
I read docs, but still do not understand difference between following
configuration options:
namespace inbox {
# Create and subscribe to folder
mailbox Drafts { auto=subscribe }
and `autocreate' plugin
plugin {
autocreate = inbox.Drafts
autosubscribe =
BLF-CRYPT has been part of glibc for a very very long time. it uses
the blowfish crypt version, that have been changed like 4 times now,
do to issues with it.
I'm not sure why CRYPT wouldn't work for you, seems to work fine in my
dovecot installs.
I'm not sure where the dovecot 2.0 can
It hit another dsync snag. We have a script that executes a dsync
backup command to a remote host. No write should be happening on the
remote host (the backup host). The error is:
dsync-local(anonym...@domain.com): Error: remote:
dsync-remote(anonym...@domain.com): Error: Can't delete
