Trying to figure out forwarding

OS: FreeBSD 4.5-STABLE

Software:
courier-imap-1.3.12 IMAP (and POP3) server that provides access to Maildir
mail
maildrop-1.3.7      Replacement local mail delivery agent, similar to
procmail
postfix-1.1.5,1     An alternative to widely-used Sendmail

Mail from postfix is coming to maildrop through Postfix's pipe to maildrop
like so:
vmail     unix  -       n       n       -       10      pipe
   flags=R user=vmail argv=/usr/local/bin/maildrop -d ${recipient}

I've got a mail system which handles virtual mailboxes for a variety of
domains.  Not EVERYONE with valid addresses in these domains, however, has a
mailbox on this system.  In some cases, the mail needs to go elsewhere.

So, I figured I need to create a /usr/local/etc/maildroprc and forward mail
for these individual users elsewhere.  It looks like my maildroprc needs to
look something like this:
if (hasaddr("user <at> domain")) {
  to "user <at> someotherdomain"
}

But that doesn't seem to be working.  What am I doing wrong?  What's the
correct syntax here? -- And is there an easier way?  Seems like a lot of
lines for really, just an alias.

-Yanek.

RE: Trying to figure out forwarding

> Whatever you see in the mail headers has absolutely nothing 
> to do with the identity of the message's recipient.  Your 
> E-mail address does not appear in any header of this message, 
> for example, so how would you expect hasaddr() to work in this case?
> 
> Mail aliasing/forwarding is handled by the mail server, not the mail 
> delivery agent, like maildrop.  Consult your mail server's 
> documentation for more information.

The problem here is that postfix will deliver via pipe to maildrop on a
per-domain basis, not a per-user basis.  I need mail that's gotten through
postfix to maildrop to again leave the system.  Is this no longer possible,
as envelope information has been lost?

-Yanek.

Configuring postfix / maildrop / userdb / courier-imap

........................................ 
on Mandrake 8.2 
I got postfix configure like this; 

-main.cf :-  
fallback_transport = maildrop 

-master.cf:- 
maildrop     unix   -      n      n      -      -      pipe 
flags=R user=vmail argv=/usr/local/bin/maildrop -d ${recipient} 

vmail is a system user that is member of groups 'mail' and 'vmail'
It's home=/home/vmail ; uid=500 and gid=500 

I configure maildrop like this; 

./configure \ 
--enable-userdb \ 
--enable-maildirquota 
--with-devel \ 
--enable-syslog=1 \ 
--disable-tempdir \ 
--enable-trusted-users='vmail postfix' \ 
--enable-trusted-groups='mail postfix' 

thi command '# maildrop -v' shows:- 
GDBM extensions enabled 
Maildir quota enabled 
Virtual user database enabled 

mail sorting after delivery

Is there a way to sort a specific mail folder after the mail has been
delivered?

Thanks,
Kevin Fonner

RC to reject html email

Hello list, I tried to look through the archives for this question, but they
aren't searchable... at least I couldn't figure it out..

Question: does anyone have a maildrop script to reject email's containing
html.  I'd love for it to do a reply to the sender stating that I do not
accept html email and please re-submit in plain text... bla bla bla.

Anyone got one of these already made?  If not an auto responder, just a
drop/spam would be fine.

thanks!

Chris Bunnell

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth <at> sourceforge.net

Postfix - Maildrop - SpamAssassin

Re: Postfix - Maildrop - SpamAssassin

On Wed, 1 May 2002, Luis Pena wrote:

>             Postfix and Maildrop are working fine together for me as
> long as I have the $HOME/.mailfilter file empty for users.  I’m trying
> to get this mail filtered through spamassassin and have added the line:
>
> xfilter "/usr/share/spamassassin -P"
>
> to the .mailfilter file.  However once I do that, these errors appear in
> my maillog and delivery gets suspended for that user:
> maildrop[19032]: Unable to filter message
> postfix/local[19000]: 3C694233B8: to=<user <at> mydomain.com>, relay=local,
> delay=0, status=deferred (temporary failure. Command output: maildrop:
> error writing to filter. /usr/bin/maildrop: Unable to filter message. )

On my system, /usr/share/spamassassin is a directory.

Do you want /usr/bin/spamassassin?

(If you do more than a few hundred messages a day, using spamc/spamd is
recommended ...)

--

-- 
Charlie Watts
cewatts <at> frontier.net
Frontier Internet, Inc.
http://www.frontier.net/

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth <at> sourceforge.net

pattern match not working as expected using maildrop-1.3.8

I'm using maildrop-1.3.8 on Linux 2.4.8 on x86 hardware.

I have a test message file named 'test-msg.txt' which contains the
following text:
---
Date: Thu, 2 May 2002 18:45:38 -0500
From: dont <at> under.stand
To: get <at> an.swer
Subject: a

This message should be considered spam. What's wrong?
---

I have a filtering instructions file named 'spam-filter' which contains
the following text:
---
if (/^Subject: [^a]+$/)
    echo "ok"
else
    echo "spam"

exit
---

I then invoke maildrop in manual mode using the following command:
---
maildrop spam-filter < test-msg.txt
---

What I don't understand is that it prints "ok", but it _should_ print
"spam". The subject line contains the letter 'a'. The pattern match says
to match a header line that starts with 'Subject: ' and has one or more
characters to the end of the line that are not the letters 'a' or 'A'
(since according to the docs "...the patterns match either uppercase or
lowercase text").

Any ideas?

Thanks.

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth <at> sourceforge.net

maildrop-1.3.8 rpm doesn't build out of the box

Machine info: RPM version 4.0, Mandrake 8.0, Linux 2.4.8, x86 hardware.

I run 'rpm -ta maildrop-1.3.8.tar.gz' as a normal user. After running
for a second or two it exits with the following message:

    configure: error: --enable-userdb requires --with-db
    Bad exit status from /var/tmp/rpm-tmp.79661 (%prep)

The option '--with-db' is missing where configure is invoked in the prep
section of the maildrop.spec file. I added '--with-db=db' and the rpm
builds fine.

But I don't know that this is the best solution as the build won't work
if the build machine does not have the Berkely DB library. Maybe the
problem is that the '--enable-userdb' option thinks it needs the
'--with-db' option when perhaps gdbm or db support is compiled in by
default? I'm just guessing this since there is a '--without-db'
configure option.

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth <at> sourceforge.net

Re: pattern match not working as expected using maildrop-1.3.8

On Thu, 02 May 2002, J. Lewis Muir wrote:

> if (/^Subject: [^a]+$/)
>     echo "ok"
> else
>     echo "spam"
> 
> exit

this will work:

	man maildropfilteir,
	
	[^a]+\$/

Greetings, Mark

_______________________________________________________________

Have big pipes? SourceForge.net is looking for download mirrors. We supply
the hardware. You get the recognition. Email Us: bandwidth <at> sourceforge.net