Le 30 mai 09 à 00:04, I wrote :
[...]
I really believe that it would be worth to engrave that behavior
somewhere in the docs.
This could prove extremely useful to people considering to replace
their existing LDA in their existing setup, by making explicit some
points to take care of.
As a
Le 28 mai 09 à 23:51, Timo Sirainen a écrit :
On Tue, 2009-05-26 at 14:35 +0200, Axel Luttgens wrote:
[...]
That looks like a server configuration mistake.
No, it's just a Postfix system quickly and dirtily brought to life for
the sole purpose of testing deliver from within a MTA. ;-)
O
On Tue, 2009-05-26 at 14:35 +0200, Axel Luttgens wrote:
> postfix/local[8643]: 1AFE4CA5D97: to=,
> relay=local, delay=0.08, delays=0.01/0.01/0/0.06, dsn=5.2.0,
> status=bounced (cannot update mailbox /Library/WebServer/_inbox/
> mailspool for user www. unable to create lock file /Library/
Le 26 mai 09 à 02:08, Timo Sirainen a écrit :
On Sun, 2009-05-24 at 18:35 +0200, Axel Luttgens wrote:
1. Shouldn't deliver honor the first_valid_uid setting?
I'm not sure. Somehow enforcing it there seems like a bad idea to me.
Yes, could well be that I overlooked some possible side-effects
On Sun, 2009-05-24 at 18:35 +0200, Axel Luttgens wrote:
> 1. Shouldn't deliver honor the first_valid_uid setting?
I'm not sure. Somehow enforcing it there seems like a bad idea to me.
> 2. What exactly is the -e option supposed to do?
..
> Note that the question may somehow be re-phrased as: when
While investigating Dovecot's deliver with Postfix, I encountered some
behaviors making me wonder whether I really understand the purpose of
that binary. So, if you allow...
This is from Postfix' main.cf:
mailbox_command = /usr/local/dovecot/libexec/dovecot/deliver -e -n
This is my quic
