Hi,
I am curious if Dovecot can add an empty file into a Maildir folder as
soon as a mailbox has exceeded 100% capacity, and later when it detects
the quota has fallen below 100% unlink the file. The idea is the Dovecot
LDA would deliver the message and if this caused the mailbox to reach
100
On 22/08/12 19:20, Gábor Lénárt wrote:
I guess what an RFC says about "email address syntax" is valid rule for both
sender _and_ recipient.
Perhaps it would be best if dovecot applied a policy (whatever policy)
consistently. It was a surprise to me to transition from CMU sieve to
Pigeonhole
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 mail
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
If you should need any more info on this, just drop me a line.
I am fully stuck!
I think that my dovecot.conf is not put together well, only i can't find
the problem...
Thanx
Sascha
Am 22.08.2012 01:44, schrieb Sascha Zucca:
Hi list,
i have a strange "ghost" folder in my subscription list and
On 22.8.2012, at 23.01, Igor Zinovik wrote:
> 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 {
>
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 = i
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
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 sense
Hi,
On Wed, Aug 22, 2012 at 09:56:04AM +0300, David Anderson wrote:
> 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
On Tue, 2012-08-21 at 21:51 +0400, Igor Zinovik wrote:
> I read on upgrading page that one can use UTF8 mailbox names for
> plugins. As i understand i do not need to convert UTF8 names to mUTF-7
> and can use raw UTF8 in plugins section, e.g.:
> /etc/dovecot/dovecot.conf
You couldn't need to use
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 da...@e
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 (typ
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 ha
14 matches
Mail list logo