Networking

NAVIGATION
CATEGORIES
REFERRENCE
LINKS
  • qmail-lspawn ignore default delivery

    5 answers - 611 bytes - related search similar search Add To My Delicious Add To My Stumble Upon Add To My Google Mark Add To My Facebook Add To My Digg Add To My Reddit

    Hi,
    I have a really stange behiavor, I can pass anything to qmail-lspawn
    qmail-lspawn | /path/to/inexistant/prog
    and my email are still correctly delivered under Maildir. I want to put
    maildrop to filter my spam under another directory but it seems that this
    program (the arguement of qmail-lspawn) is never called.
    Someone have an idea about that?
    Thank you
    Eric
    Take charge with a pop-up guard built on patented Microsoft SmartScreen
    Technology
    Start enjoying all the benefits of MSN Premium right now and get the
    first two months FREE*.
  • No.1 | | 493 bytes | |

    Tue, Sep 13, 2005 at 08:40:46PM +0000, eric wyzerski wrote:
    Hi,

    I have a really stange behiavor, I can pass anything to qmail-lspawn
    qmail-lspawn | /path/to/inexistant/prog

    and my email are still correctly delivered under Maildir. I want to put
    maildrop to filter my spam under another directory but it seems that this
    program (the arguement of qmail-lspawn) is never called.
    Someone have an idea about that?

    Have you tried setting deliveryMode to nolocal?
  • No.2 | | 368 bytes | |

    I don't understand it. Why does qmail-ldap change the normal .qmail
    behavior? Namely, .qmail files are parsed, the programs specified in
    qmail files are run, but despite the exit code being '99' for those
    programs, an additional delivery is made into the Maildir. This is not
    standard qmail-local behavior. Looks like a bug to me.
  • No.3 | | 870 bytes | |

    Tue, Sep 13, 2005 at 07:31:21PM -0400, Dan Melomedman wrote:
    I don't understand it. Why does qmail-ldap change the normal .qmail
    behavior? Namely, .qmail files are parsed, the programs specified in
    .qmail files are run, but despite the exit code being '99' for those
    programs, an additional delivery is made into the Maildir. This is not
    standard qmail-local behavior. Looks like a bug to me.

    If you have qmailDotMode set to dotonly you get the old behaviour.
    The qmail-ldap way of doing deliveries based on LDAP entries is a bit
    different to stock .qmail handling. The processing is controlled by
    deliveryMode. By default all delivery methods are done (local, forwards
    and program) so you need to use nolocal, noforward or noprogram to disable
    some of the deliveries. This was done because it makes frontends easier.
  • No.4 | | 893 bytes | |

    Claudio Jeker wrote:
    Tue, Sep 13, 2005 at 07:31:21PM -0400, Dan Melomedman wrote:
    I don't understand it. Why does qmail-ldap change the normal .qmail
    behavior? Namely, .qmail files are parsed, the programs specified in
    .qmail files are run, but despite the exit code being '99' for those
    programs, an additional delivery is made into the Maildir. This is not
    standard qmail-local behavior. Looks like a bug to me.

    If you have qmailDotMode set to dotonly you get the old behaviour.
    The qmail-ldap way of doing deliveries based on LDAP entries is a bit
    different to stock .qmail handling. The processing is controlled by
    deliveryMode. By default all delivery methods are done (local, forwards
    and program) so you need to use nolocal, noforward or noprogram to disable
    some of the deliveries. This was done because it makes frontends easier.
  • No.5 | | 958 bytes | |

    Wed, Sep 14, 2005 at 02:43:30PM -0400, Dan Melomedman wrote:
    Claudio Jeker wrote:
    Tue, Sep 13, 2005 at 07:31:21PM -0400, Dan Melomedman wrote:
    I don't understand it. Why does qmail-ldap change the normal .qmail
    behavior? Namely, .qmail files are parsed, the programs specified in
    .qmail files are run, but despite the exit code being '99' for those
    programs, an additional delivery is made into the Maildir. This is not
    standard qmail-local behavior. Looks like a bug to me.

    If you have qmailDotMode set to dotonly you get the old behaviour.
    The qmail-ldap way of doing deliveries based on LDAP entries is a bit
    different to stock .qmail handling. The processing is controlled by
    deliveryMode. By default all delivery methods are done (local, forwards
    and program) so you need to use nolocal, noforward or noprogram to disable
    some of the deliveries. This was done because it makes frontends easier.

Re: qmail-lspawn ignore default delivery


max 4000 letters.
Your nickname that display:
In order to stop the spam: 5 + 4 =
QUESTION ON "Networking"

EMSDN.COM