status=bounced (user unknown. Command output: Invalid user specified. )

Hi the list,

I'm trying to use maildrop to filter spam, putting it in a specific 
"spam" mail folder.
I was fighting a bit to configure postfix for maildrop, but now, 
maildrop isn't happy.

Postfix reports :
postfix/pipe[28775]: 9C4034929C: to=<test_domain.com <at> mx1.myhost.com>, 
relay=maildrop, delay=0.06, delays=0.05/0/0/0.02, dsn=5.1.1, 
status=bounced (user unknown. Command output: Invalid user specified. )

I think it's because the mail should be test <at> domaine.com. How does 
maildrop knows where to deliver the message ? How can I parse the mailto 
to get a real mail (test <at> domain.com) ?

Extract postfix master.cf:

maildrop  unix  -       n       n       -       -       pipe
   flags=ODRhu user=www-data argv=/usr/bin/maildrop -d ${recipient}

Thanks a lot for helping !

Ben

# Global maildrop filter file

# Uncomment this line to make maildrop default to ~/Maildir for
# delivery- this is where courier-imap (amongst others) will look.

Re: status=bounced (user unknown. Command output: Invalid user specified. )

Ben writes:

> Hi the list,
> 
> I'm trying to use maildrop to filter spam, putting it in a specific 
> "spam" mail folder.
> I was fighting a bit to configure postfix for maildrop, but now, 
> maildrop isn't happy.
> 
> Postfix reports :
> postfix/pipe[28775]: 9C4034929C: to=<test_domain.com <at> mx1.myhost.com>, 
> relay=maildrop, delay=0.06, delays=0.05/0/0/0.02, dsn=5.1.1, 
> status=bounced (user unknown. Command output: Invalid user specified. )
> 
> I think it's because the mail should be test <at> domaine.com. How does 
> maildrop knows where to deliver the message ?

It sends the query to courier-authlib, which does whatever you configured 
courier-authlib to do.

>                                               How can I parse the mailto 
> to get a real mail (test <at> domain.com) ?
> 
> Extract postfix master.cf:

This part is postfix-related, so please try the postfix mailing list.

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

Re: status=bounced (user unknown. Command output: Invalid user specified. )

Le 04/12/2010 01:02, Sam Varshavchik a écrit :
> Ben writes:
>
>> Hi the list,
>>
>> I'm trying to use maildrop to filter spam, putting it in a specific
>> "spam" mail folder.
>> I was fighting a bit to configure postfix for maildrop, but now,
>> maildrop isn't happy.
>>
>> Postfix reports :
>> postfix/pipe[28775]: 9C4034929C: to=<test_domain.com <at> mx1.myhost.com>,
>> relay=maildrop, delay=0.06, delays=0.05/0/0/0.02, dsn=5.1.1,
>> status=bounced (user unknown. Command output: Invalid user specified. )
>>
>> I think it's because the mail should be test <at> domaine.com. How does
>> maildrop knows where to deliver the message ?
>
> It sends the query to courier-authlib, which does whatever you
> configured courier-authlib to do.
>
>> How can I parse the mailto to get a real mail (test <at> domain.com) ?
>>
>> Extract postfix master.cf:
>
> This part is postfix-related, so please try the postfix mailing list.
>
Hi Sam, thank you for your answer.
The problem is that I'm struggled with a mass hosting software that set 
up postfix in a way mails comes in that shape.

Re: status=bounced (user unknown. Command output: Invalid user specified. )

Ben writes:

> Le 04/12/2010 01:02, Sam Varshavchik a écrit :
>> Ben writes:
>>
>>> Hi the list,
>>>
>>> I'm trying to use maildrop to filter spam, putting it in a specific
>>> "spam" mail folder.
>>> I was fighting a bit to configure postfix for maildrop, but now,
>>> maildrop isn't happy.
>>>
>>> Postfix reports :
>>> postfix/pipe[28775]: 9C4034929C: to=<test_domain.com <at> mx1.myhost.com>,
>>> relay=maildrop, delay=0.06, delays=0.05/0/0/0.02, dsn=5.1.1,
>>> status=bounced (user unknown. Command output: Invalid user specified. )
>>>
>>> I think it's because the mail should be test <at> domaine.com. How does
>>> maildrop knows where to deliver the message ?
>>
>> It sends the query to courier-authlib, which does whatever you
>> configured courier-authlib to do.
>>
>>> How can I parse the mailto to get a real mail (test <at> domain.com) ?
>>>
>>> Extract postfix master.cf:
>>
>> This part is postfix-related, so please try the postfix mailing list.
>>
> Hi Sam, thank you for your answer.

installling and configuring Courier-maildrop with openldap

------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d

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

Re: installling and configuring Courier-maildrop with openldap

kibirango moses writes:

> « HTML content follows »
> <URL:mailto:courier-maildrop <at> lists.sourceforge.net>Hullo everyone
> I have compiled and installed maildrop (maildrop – 2.5.2) with following 
> options 
> 
> "./configure --prefix=/usr/local/maildrop 
> --exec-prefix=/usr/local/maildrop --enable-maildirquota 
> --enable-maildrop-uid=root --enable-maildrop-gid=mail 
> --enable-restricted-trusted=0 --enable-trusted-users='mail' 
> --enable-maildropldap --with-ldapconfig=/etc/maildrop/maildropldap.config 
> --with-etcdir=/etc/maildrop 

You read this on some ancient web page that hasn't been updated in years, in 
order to come up with this stuff.

Please read the installation instructions in maildrop's INSTALL file, 
instead of some outdated stuff that someone else wrote many years ago, never 
bothered to update, and is now completely wrong.

> make 
> make install-strip 
> make install-man 
> 
> after compiling and installing maildrop it was supposed to create 
> /etc/maildrop folder as well as the "maildropldap.config" but it didnt, so 

That's because it hasn't done so, in years. If you want LDAP, see the 
INSTALL file. You need to install something else, first, with the current 
version of maildrop. Things have gotten a little bit more complicated, over 
the years.

> i have done  compiling and installing maildrop several times but all in 
> vain .
> 
> At some point u have to copy the maildropldap.config  file from the source 
> directory to the /etc but the file does not exist in the source . Which 
> maildrop version should i use?

The current one. And you should use the INSTALL instructions from the 
current version of maildrop, instead of installation instructions for an 
obsolete version, that nobody wants any more.

------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d

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

Filter Spam higher than

I would like to modify the following to DISGARD spam messages higher that a
certain value and sent the rest into the current spam folder. Any help is
appreciated.

exception {
xfilter "/usr/bin/spamassassin -p
/home/cogz/popaccts/cogz.com/spamtest/.spamassassin/user_prefs"
}
if ( /^X-Spam-Status: Yes/:h )
{
to Maildir/.SPAM
}

--

-- 
View this message in context: http://old.nabble.com/Filter-Spam-higher-than-tp30498352p30498352.html
Sent from the courier-maildrop mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d

Re: Filter Spam higher than

On 20 Dec 2010, at 13:44, COGZ wrote:

> 
> I would like to modify the following to DISGARD spam messages higher that a
> certain value and sent the rest into the current spam folder. Any help is
> appreciated.
> 
> exception {
> xfilter "/usr/bin/spamassassin -p
> /home/cogz/popaccts/cogz.com/spamtest/.spamassassin/user_prefs"
> }
> if ( /^X-Spam-Status: Yes/:h )
> {
> to Maildir/.SPAM
> }
> 

Try thinking about it in terms of spam level. There's a good guide at
http://www.nmrfam.wisc.edu/equipment-facilities/access-to-the-nmrfam-network-and-spectrometers/spamassassin-setup/
for example you could use the following:

if( /^X-Spam-Level: \*{7,}/ )
{
to "/dev/null"
}
if( /^X-Spam-Level: \*{5,7}/ )
{
to "Maildir/.Junk"
}

This is pretty similar to what I've got set up. Works well.

Consider using logging to make sure messages are going through as they should.

--Ronald.

R MacDonald : http://www.rmacd.com/
ronald <at> rmacd.com : +44-777-2351655