On Fri, 30 Nov 2001, Lawrence Greenfield wrote:
> master/service.c doesn't call execv(); it's directly linked into the
> lmtpd executable.
Yeah, I had just noticed I had master/service.c confused with spawn_service
in master.c (don't ask :P) and I was about to reply to myself with a "never
mind",
Date: Fri, 30 Nov 2001 15:52:00 -0200
From: Henrique de Moraes Holschuh <[EMAIL PROTECTED]>
[...]
But then it execv() lmtpd, which will have its own copies of the config_*
variables, and those are never initialized if they need config_init to work.
master/service.c doesn't call execv
On Fri, 30 Nov 2001, Lawrence Greenfield wrote:
>Date: Fri, 30 Nov 2001 09:14:09 -0200
>From: Henrique de Moraes Holschuh <[EMAIL PROTECTED]>
>
>On Thu, 29 Nov 2001, Jeremy Howard wrote:
>> More importantly, we need separate conf entries for 'SIEVE' versus 'MAIL'
>
>As you wi
Date: Fri, 30 Nov 2001 09:14:09 -0200
From: Henrique de Moraes Holschuh <[EMAIL PROTECTED]>
On Thu, 29 Nov 2001, Jeremy Howard wrote:
> More importantly, we need separate conf entries for 'SIEVE' versus 'MAIL'
As you wish. I am working with two options, now: notifysieve, notifymai
On Thu, 29 Nov 2001, Jeremy Howard wrote:
> More importantly, we need separate conf entries for 'SIEVE' versus 'MAIL'
As you wish. I am working with two options, now: notifysieve, notifymail.
I have noticed that lmtp* do not use config_init, as opposed to just about
every other daemon/service un
> Another patch, this one for the notify-unix or notify-zephyr services.
>
<...>
>
> The new configuration directive is named "notify", and takes a boolean
> value. The default is to do notification (as Cyrus would do without the
> patch). Set it to false to disable notification. SNMP statistics
Another patch, this one for the notify-unix or notify-zephyr services.
By default, one has to chose at compile time what kind of notification he
wants in Cyrus. This poses some problems to distribuitons such as Debian.
For the Debian initial packaging, I have used Zephyr support. However, since
