Re: Inconsistent behaviour

Roger Thomas skrev:

> I want Maildrop to create a folder named Spam if no such folder exists (upon receiving a mail that is tagged
as Spam). So I created a maildroprc file like the following:

[...]

>         `test -d $HOME/Maildir/.Spam`
>         if( $RETURNCODE != 0 )
>         {
>           `/usr/local/bin/maildirmake -f Spam $HOME/Maildir`
>           `echo INBOX.Spam >> $DEFAULT/courierimapsubscribed`
>         }
> 
>         to "$HOME/Maildir/.Spam"
> }

[...]

> Problem is, upon receiving a spam mail, maildrop created a file, NOT A FOLDER.

Try something like (works for us):

`test -d $HOME/Maildir/.Spam/`
    if( $RETURNCODE == 1 )
    {
       `/usr/bin/maildirmake $HOME/Maildir/.Spam/`
       #"whatever else"
    }

Re: Inconsistent behaviour

Hi,

* Roger Thomas wrote (2007-01-07 21:42):
>Problem is, upon receiving a spam mail, maildrop created a file, NOT A FOLDER.

I use mbox, but shouldn't Maildir use a tailing slash?

Thorsten
--

-- 
Getting a thrill out of some stupid quote is a sign of idiocy.
    - turmeric

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

_______________________________________________
Courier-maildrop mailing list
Courier-maildrop <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/courier-maildrop

maildrop/postfix argv's

More experimented with procmail, i'm trying setting up a mailserver
with delivering by maildrop.
I've installed and configured fetchmail,postfix,courier-imap,
courier-authdaemon and so, amavis, clamav, spamassassin and bayes,
as virtual.
Seems all runs well except maildrop.
Maybe i looked not far enaough, but can't find any (with examples)
tuto about the maildrop delivering configs.
So how can i configure maildrop like my procmail:
#:0 H
#* ^X-Mailing-List:.*[<].*lists\.debian\.org[>]
#* ^X-Mailing-List:.*[<] *\/[^ ][^ <at> ]*
#$MATCH

:0
#*^TO_debian-user <at> lists.debian.org
*^(From|Cc|To).* <at> lists.debian.org
${MAILDIR}.Debian/

#:0
#*^TO_debian-user-french <at> lists.debian.org
#${MAILDIR}.Debian/

:0
*^To_debian-testing <at> lists.debian.org
${MAILDIR}.Debian-testing/

:0
*^Sender.* <at> freebsd.org
${MAILDIR}.FreeBSD/

Re: maildrop/postfix argv's

Moin,

* mess-mate wrote (2007-01-07 20:30):
>Maybe i looked not far enaough, but can't find any (with examples)
>tuto about the maildrop delivering configs.

man maildropex

>So how can i configure maildrop like my procmail:

In my experience, very easy. It took me only a couple of minutes to
translate my Procmail rules. I never looked back.

>:0
>#*^TO_debian-user <at> lists.debian.org
>*^(From|Cc|To).* <at> lists.debian.org
>${MAILDIR}.Debian/

Generally:
if (/(From|Cc|To).* <at> lists.debian.org/)
{
    to ${MAILDIR}.Debian/
}

>#:0
>#*^TO_debian-user-french <at> lists.debian.org
>#${MAILDIR}.Debian/
>
>:0
>*^To_debian-testing <at> lists.debian.org

Re: Inconsistent behaviour

Quoting Tony Earnshaw <tonni <at> hetnet.nl>:

> Try something like (works for us):
> 
> `test -d $HOME/Maildir/.Spam/`
>     if( $RETURNCODE == 1 )
>     {
>        `/usr/bin/maildirmake $HOME/Maildir/.Spam/`
>        #"whatever else"
>     }
> 

I have tried:
          `/usr/local/bin/maildirmake $HOME/Maildir/.Spam/`
and
          `/usr/local/bin/maildirmake -f Spam $HOME/Maildir`

with both creating Spam as a file :(

> You don't have to import HOME, it's default.

If I do not import HOME, my emails will be lost in space. I do not know why. I am running qmail-ldap with
courier-imap 3.0.8.

Any idea?

--
roger

---------------------------------------------------

Re: Inconsistent behaviour

Roger Thomas writes:

> If I do not import HOME, my emails will be lost in space. I do not know why.

And that's a big, honking clue that maildrop is not integrated properly into 
your system.

> I am running qmail-ldap with courier-imap 3.0.8.
> 
> Any idea?

Neither Courier-IMAP, nor maildrop, would ordinarily have any knowledge of 
what you keep in LDAP, unless explicitly configured accordingly.

Furthermore, that version of Courier-IMAP is over two years old, and is 
prehistoric, in Internet time.  The very next version had a complete 
overhaul of the authentication library; the common authentication library in 
Courier-IMAP, and maildrop, was factored out into a separate package, 
courier-authlib.

The best advice for you is to download and install courier-authlib, and 
configure its LDAP module until it works with your mail account schema, then 
upgrade to the current version of Courier-IMAP and maildrop.  As long as you 
have properly set up courier-authlib and it works with your LDAP schema, the 
current version of Courier-IMAP and maildrop should not have any issues 
reading account data from LDAP.

-------------------------------------------------------------------------

Re: maildrop/postfix argv's

Thorsten Haude <list+maildrop <at> thorstenhau.de> wrote:
| Moin,
| 
| * mess-mate wrote (2007-01-07 20:30):
| >Maybe i looked not far enaough, but can't find any (with examples)
| >tuto about the maildrop delivering configs.
| 
| man maildropex

Ok, didn't know

| 
| 
| >So how can i configure maildrop like my procmail:
| 
| In my experience, very easy. It took me only a couple of minutes to
| translate my Procmail rules. I never looked back.
| 
| 
| >:0
| >#*^TO_debian-user <at> lists.debian.org
| >*^(From|Cc|To).* <at> lists.debian.org
| >${MAILDIR}.Debian/
| 
| Generally:
| if (/(From|Cc|To).* <at> lists.debian.org/)
| {
|     to ${MAILDIR}.Debian/
| }
| 

Re: maildrop/postfix argv's

mess-mate <mess-mate <at> wanadoo.fr> wrote:
| Thorsten Haude <list+maildrop <at> thorstenhau.de> wrote:
| | Moin,
| | 
| | * mess-mate wrote (2007-01-07 20:30):
| | >Maybe i looked not far enaough, but can't find any (with examples)
| | >tuto about the maildrop delivering configs.
| | 
| | man maildropex
| 
| Ok, didn't know
| 
| | 
| | 
| | >So how can i configure maildrop like my procmail:
| | 
| | In my experience, very easy. It took me only a couple of minutes to
| | translate my Procmail rules. I never looked back.
| | 
| | 
| | >:0
| | >#*^TO_debian-user <at> lists.debian.org
| | >*^(From|Cc|To).* <at> lists.debian.org
| | >${MAILDIR}.Debian/
| | 
| | Generally:
| | if (/(From|Cc|To).* <at> lists.debian.org/)
| | {
| |     to ${MAILDIR}.Debian/
| | }

variables passed by maildrop via postfix

anybody could teel me the variables i can pass to maildrop from
postfix ?
Sorry if this is a postfix question.
best regards

mess-mate                               
--

-- 

Your reasoning powers are good, and you are a fairly good planner.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

Re: variables passed by maildrop via postfix

mess-mate wrote:
> anybody could teel me the variables i can pass to maildrop from postfix ?
>   
Yes, postfix can  No really that's not a pointer at the postfix list, 
temporarily change the command postfix uses to call maildrop to be:

set > set.txt

Postfix should then dump out all the variables that are made available 
to the child program (which is normally maildrop)

Jay

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV