Re: VBounce problems

2009-05-15 Thread Karsten Bräckelmann
On Fri, 2009-05-15 at 23:36 +0200, Karsten Bräckelmann wrote: > On Fri, 2009-05-15 at 17:17 -0400, Bowie Bailey wrote: > > Here is a real sample. The only way I can get this message to pass > > VBounce as legitimate is to add bnifstg2.buc.com to the whitelist. > > However, this is *not* a mails

Re: VBounce problems

2009-05-15 Thread Karsten Bräckelmann
On Fri, 2009-05-15 at 17:17 -0400, Bowie Bailey wrote: > Here is a real sample. The only way I can get this message to pass > VBounce as legitimate is to add bnifstg2.buc.com to the whitelist. > However, this is *not* a mailserver, this is the client. > bnofimage1.buc.com is my mailserver, an

Re: VBounce problems

2009-05-15 Thread Bowie Bailey
Karsten Bräckelmann wrote: On Fri, 2009-05-15 at 17:04 -0400, Bowie Bailey wrote: After doing some more testing, I found that if I put the system that *sends* the email into whitelist_bounce_relays, it will work. Is this right? Should I have to list every machine in my network in order to

Re: VBounce problems

2009-05-15 Thread Karsten Bräckelmann
On Fri, 2009-05-15 at 17:04 -0400, Bowie Bailey wrote: > After doing some more testing, I found that if I put the system that > *sends* the email into whitelist_bounce_relays, it will work. Is this > right? Should I have to list every machine in my network in order to > have vbounce work corre

Re: VBounce problems

2009-05-15 Thread Karsten Bräckelmann
On Fri, 2009-05-15 at 16:40 -0400, Bowie Bailey wrote: > Karsten Bräckelmann wrote: > > The VBounce plugin does *not* check the messages headers. Instead, it > > has a look at the plain text body and any message/* MIME attachments. > > > > If it finds your own, whitelisted SMTP relay in there, it

Re: VBounce problems

2009-05-15 Thread Bowie Bailey
After doing some more testing, I found that if I put the system that *sends* the email into whitelist_bounce_relays, it will work. Is this right? Should I have to list every machine in my network in order to have vbounce work correctly? It looks like the original email has to be received *fr

Re: VBounce problems

2009-05-15 Thread Bowie Bailey
Karsten Bräckelmann wrote: On Thu, 2009-05-14 at 12:42 -0400, Bowie Bailey wrote: I have the whitelist_bounce_relays options set for vbounce and the rules are hitting on bounce messages, but the whitelists don't seem to be working. In my local.cf, I have: whitelist_bounce_relays bnofim

Re: VBounce problems

2009-05-15 Thread Karsten Bräckelmann
On Thu, 2009-05-14 at 12:42 -0400, Bowie Bailey wrote: > I have the whitelist_bounce_relays options set for vbounce and the rules > are hitting on bounce messages, but the whitelists don't seem to be working. > > In my local.cf, I have: > > whitelist_bounce_relays bnofimage1.buc.com > > But

Re: VBounce problems

2009-05-15 Thread Bowie Bailey
Bowie Bailey wrote: John Hardin wrote: On Thu, 14 May 2009, Bowie Bailey wrote: I have the whitelist_bounce_relays options set for vbounce and the rules are hitting on bounce messages, but the whitelists don't seem to be working. In my local.cf, I have: whitelist_bounce_relays bnofimage1

Re: VBounce problems

2009-05-14 Thread Bowie Bailey
John Hardin wrote: On Thu, 14 May 2009, Bowie Bailey wrote: I have the whitelist_bounce_relays options set for vbounce and the rules are hitting on bounce messages, but the whitelists don't seem to be working. In my local.cf, I have: whitelist_bounce_relays bnofimage1.buc.com But, an ema

Re: VBounce problems

2009-05-14 Thread John Hardin
On Thu, 14 May 2009, Bowie Bailey wrote: I have the whitelist_bounce_relays options set for vbounce and the rules are hitting on bounce messages, but the whitelists don't seem to be working. In my local.cf, I have: whitelist_bounce_relays bnofimage1.buc.com But, an email with this header c

VBounce problems

2009-05-14 Thread Bowie Bailey
I have the whitelist_bounce_relays options set for vbounce and the rules are hitting on bounce messages, but the whitelists don't seem to be working. In my local.cf, I have: whitelist_bounce_relays bnofimage1.buc.com But, an email with this header comes through: Received: from bnofimage