From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: [9fans] upas+scanmail question
Date: Wed, 13 Mar 2002 12:10:31 +0100 [thread overview]
Message-ID: <20020313111043.EAAD219995@mail.cse.psu.edu> (raw)
Hi,
I'm trying to use scanmail to filter spam. If I understand it,
/mail/lib/qmail calls scanmail to filter spam and then runq .
But for incomming mail, smtpd calls upas/send, which uses /mail/lib/rewrite to
see what to do. Now, if my mailhost is plan9.escet.urjc.es, rewrite
translates plan9.escet.urjc.es!nemo to local!nemo, and the entry for
local!nemo tells upas/send to add the mail to /mail/box/nemo/mbox, without
using qmail at all.
So, should I use two different queues to put scanmail in the smtpd
received mail pipeline? (queue local mails using scanmail, the run the
queue to deliver all queued mails)
Or is there any obvious way to make upas/send filter the mail through
scanmail and then add the mails passing the filter to the user mail
box?
thanks in advance
next reply other threads:[~2002-03-13 11:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-13 11:10 Fco.J.Ballesteros [this message]
2002-03-13 15:04 presotto
2002-03-13 15:23 presotto
2002-03-14 8:27 nigel
2002-03-14 13:55 rob pike
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020313111043.EAAD219995@mail.cse.psu.edu \
--to=nemo@plan9.escet.urjc.es \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).