On Sun, 2008-05-11 at 15:32 -0700, Tech Color printer wrote:
> so how am I supposed to get this vbounce to work on backscatter's ?
http://wiki.apache.org/spamassassin/FrequentlyAskedQuestions
http://wiki.apache.org/spamassassin/VBounceRuleset
Set whitelist_bounce_relays properly. Without knowing
Well I am confused.
# locate vbounce
/usr/share/spamassassin/updates_spamassassin_org/20_vbounce.cf
/usr/share/spamassassin/20_vbounce.cf
/var/lib/spamassassin/3.002000/updates_spamassassin_org/20_vbounce.cf
# locate VBounce
/usr/lib/perl5/vendor_perl/5.8.0/Mail/SpamAssassin/Plugin/VBounce.pm
bo
On Thu, May 08, 2008 at 04:20:42PM +0100, Justin Mason wrote:
>
> > > In case of VBounce, chances of FPs are even less acceptable. You are
> > > supposed to reject or discard backscatter
>
> who says?
>
> It seems perfectly fine to me to tag vbounce-filtered mail. In mail
> filtering, there wil
> > In case of VBounce, chances of FPs are even less acceptable. You are
> > supposed to reject or discard backscatter
who says?
It seems perfectly fine to me to tag vbounce-filtered mail. In mail
filtering, there will always be FPs.
--j.
Henrik K schrieb:
On Thu, May 08, 2008 at 03:11:59PM +0200, Robert Müller wrote:
BTW: Also for me 'null senders' are not common - never had problems with
this, except UBE.
Have you even looked at your traffic archives, if you keep one? How do you
know there isn't any problems if some
On Thu, May 08, 2008 at 03:11:59PM +0200, Robert Müller wrote:
>
> BTW: Also for me 'null senders' are not common - never had problems with
> this, except UBE.
Have you even looked at your traffic archives, if you keep one? How do you
know there isn't any problems if someone doesn't realize to rep
On Thu, 8 May 2008, Justin Mason wrote:
Matt Kettler writes:
.rp wrote:
So, need a rule that would parse the "Message-ID:" in the body (or attachment)
and not
header, and look for the @FQDN
Is this rule already out in the wild?
You'd likely need a meta of some sort.
Theoretically, somethi
Henrik K schrieb:
On Thu, May 08, 2008 at 11:35:30AM +0100, Justin Mason wrote:
Not in my experience!
I haven't seen anything that isn't a bounce message, an out-of-office
notification, auto-replies, or other stuff targeted by the VBounce
ruleset. certainly not transactional mail. as far
On Thu, May 08, 2008 at 11:35:30AM +0100, Justin Mason wrote:
>
> Not in my experience!
>
> I haven't seen anything that isn't a bounce message, an out-of-office
> notification, auto-replies, or other stuff targeted by the VBounce
> ruleset. certainly not transactional mail. as far as I can tel
Henrik K writes:
> On Thu, May 08, 2008 at 10:03:28AM +0100, Justin Mason wrote:
> >
> > Henrik Krohns writes:
> > > On Thu, May 08, 2008 at 09:35:31AM +0100, Justin Mason wrote:
> > > >
> > > > the VBounce plugin is intended to catch backscatter -- bounces in
> > > > response
> > > > to mail yo
On Thu, May 08, 2008 at 10:03:28AM +0100, Justin Mason wrote:
>
> Henrik Krohns writes:
> > On Thu, May 08, 2008 at 09:35:31AM +0100, Justin Mason wrote:
> > >
> > > the VBounce plugin is intended to catch backscatter -- bounces in response
> > > to mail you didn't send -- so it'll ignore bounces
Henrik Krohns writes:
> On Thu, May 08, 2008 at 09:35:31AM +0100, Justin Mason wrote:
> >
> > the VBounce plugin is intended to catch backscatter -- bounces in response
> > to mail you didn't send -- so it'll ignore bounces in response to mail you
> > _did_ send, by parsing the bounced message's R
Matt Kettler writes:
> Justin Mason wrote:
> > Matt Kettler writes:
> >
> >> .rp wrote:
> >>
> >>> One of the users (actually the boss) had the email address harvested and
> >>> we got clobbered
> >>> by backscatter. Looking at the emails of the various 'unable to deliver'
> >>> type me
Justin Mason wrote:
Matt Kettler writes:
.rp wrote:
One of the users (actually the boss) had the email address harvested and we got clobbered
by backscatter. Looking at the emails of the various 'unable to deliver' type messages, I saw
what these could be filtered on, but don't know ho
Matt Kettler writes:
> .rp wrote:
> > One of the users (actually the boss) had the email address harvested and we
> > got clobbered
> > by backscatter. Looking at the emails of the various 'unable to deliver'
> > type messages, I saw
> > what these could be filtered on, but don't know how to w
.rp wrote:
One of the users (actually the boss) had the email address harvested and we got clobbered
by backscatter. Looking at the emails of the various 'unable to deliver' type messages, I saw
what these could be filtered on, but don't know how to write up and implement the rule
outside of pr
One of the users (actually the boss) had the email address harvested and we got
clobbered
by backscatter. Looking at the emails of the various 'unable to deliver' type
messages, I saw
what these could be filtered on, but don't know how to write up and implement
the rule
outside of procmail. I
17 matches
Mail list logo
