List Info

Thread: spf problem
spf problem
country flaguser name
New Zealand		 2007-02-25 19:23:35 
I implemented SPF over the weekend and now Surgemail is
bouncing mail 
from my application server

25 16:58:51.00:-1225446480: spf: Going to block it
ip:64.81.241.226 from:<deb-cjennypruitt.com>
to:<ga-northatlanta-leave360resource.net> 

my spf clears the entire class C

v=spf1 ip4:64.81.241.0/24 -all

any ideas how to fix this?

Thanks,
Wayne


-- 
~~~~~~~~~~~~~~~~~~
Wayne Gregori
wgsfnet.com
www.sfnet.com
Re: spf problem
country flaguser name
New Zealand		 2007-02-25 20:32:43 

  


  

    

Put that server's IP address into g_spf_skip


 


BarryZ


1USA


&nbsp;


----- Original Message ----- 



Sent: Sunday, February 25, 2007 8:23 PM


Subject: [SurgeMail List] spf problem




I implemented SPF over the weekend and now Surgemail is bouncing 
mail 
from my application server

25 16:58:51.00:-1225446480: spf: 
Going to block it ip:64.81.241.226 from:<jennypruitt.com">deb-cjennypruitt.com> to:<360resource.net">ga-northatlanta-leave360resource.net> 


my spf clears the entire class C

v=spf1 ip4:64.81.241.0/24 
-all

any ideas how to fix this?

Thanks,
Wayne


-- 

~~~~~~~~~~~~~~~~~~
Wayne Gregori
sfnet.com">wgsfnet.com
www.sfnet.com




====

Need a Better Internet Service?  Checkout www.1usa.com		
  

  
  
   
     
    

  

    Re:  spf problem
  


  

     country flaguser name
New Zealand		
     2007-02-26 11:09:41
  


  

    
On Sun, 2007-02-25 at 17:23 -0800, Wayne Gregori wrote:
> I implemented SPF over the weekend and now Surgemail is
bouncing mail 
> from my application server
> 
> 25 16:58:51.00:-1225446480: spf: Going to block it
ip:64.81.241.226
> from:<deb-cjennypruitt.com>
> to:<ga-northatlanta-leave360resource.net> 
> 
> my spf clears the entire class C
> 
> v=spf1 ip4:64.81.241.0/24 -all

        $ dig txt sfnet.com
        sfnet.com.   86400   IN  TXT  "v=spf1
ip4:64.81.241.0/24 -all"
        
That's good. So any mail from sfnet.com delivered by
64.81.241.226 will
pass SPF. But that's not the question. Surgemail is looking
up SPF for
jennypruitt.com. There is no SPF entry for that domain.
Surgemail
creates a default SPF entry based on the MX, which is on a
separate
subnet. That is why SPF doesn't pass. You need to add an SPF
for each
domain that you will be sending from, not just the primary
domain of the
server.

Corey










  


  

    
  

  
  
   
     
    

  

    Re:  spf problem
  


  

     country flaguser name
New Zealand		
     2007-02-26 13:21:57
  


  

    

  


  

    

>>Create an SPF record for each domain that you 
host.



 


Good catch Corey.&nbsp; 


 


BarryZ


 


----- Original Message ----- 



Sent: Monday, February 26, 2007 12:09 PM


Subject: Re: [SurgeMail List] spf problem




On Sun, 2007-02-25 at 17:23 -0800, Wayne Gregori wrote:
>; I 
implemented SPF over the weekend and now Surgemail is bouncing mail 
> 
from my application server
>; 
> 25 16:58:51.00:-1225446480: spf: 
Going to block it ip:64.81.241.226
> from:<jennypruitt.com">deb-cjennypruitt.com>
> 
to:<360resource.net">ga-northatlanta-leave360resource.net> 

> 
> my spf clears the entire class C
> 
> v=spf1 
ip4:64.81.241.0/24 -all

&nbsp; &nbsp; &nbsp; &nbsp; $ dig 
txt sfnet.com
  ; &nbsp; &nbsp;  
sfnet.com. &nbsp; 86400 ;  IN  TXT  "v=spf1 
ip4:64.81.241.0/24 -all"
&nbsp; &nbsp; &nbsp; &nbsp; 

That's good. So any mail from sfnet.com delivered by 64.81.241.226 
will
pass SPF. But that's not the question. Surgemail is looking up SPF 
for
jennypruitt.com. There is no SPF entry for that domain. 
Surgemail
creates a default SPF entry based on the MX, which is on a 
separate
subnet. That is why SPF doesn't pass. You need to add an SPF for 
each
domain that you will be sending from, not just the primary domain of 
the
server.

Corey









====

Need a Better Internet Service?  Checkout www.1usa.com		
  

  
  
   
     
    

  

    Re:  spf problem
  


  

     country flaguser name
New Zealand		
     2007-02-26 13:38:33
  


  

    

  


  

    
thanks for the explanation Corey.



You see my application server is creating the email from
jennypruitt.com and sending to Surgemail Dlist as a "remove" command.




So I guess the best way to get around this is by doing what I did...
and placing that IP in the 



Skip spf checks for these ip addresses, e.g. other mx hosts




area.




Thanks,

Wayne



Corey Edwards wrote:

pheasant" type="cite">
  
On Sun, 2007-02-25 at 17:23 -0800, Wayne Gregori wrote:
  

  

    
I implemented SPF over the weekend and now Surgemail is bouncing mail 
from my application server

25 16:58:51.00:-1225446480: spf: Going to block it ip:64.81.241.226
from:jennypruitt.com"><deb-cjennypruitt.com>

to:360resource.net"><ga-northatlanta-leave360resource.net> 

my spf clears the entire class C

v=spf1 ip4:64.81.241.0/24 -all
    

  

  

        $ dig txt sfnet.com

        sfnet.com.   86400   IN  TXT  "v=spf1 ip4:64.81.241.0/24 -all"
        
That's good. So any mail from sfnet.com delivered by 64.81.241.226 will
pass SPF. But that's not the question. Surgemail is looking up SPF for
jennypruitt.com. There is no SPF entry for that domain. Surgemail

creates a default SPF entry based on the MX, which is on a separate
subnet. That is why SPF doesn't pass. You need to add an SPF for each
domain that you will be sending from, not just the primary domain of the
server.

Corey








.

  






-- 
~~~~~~~~~~~~~~~~~~

Wayne Gregori
sfnet.com">wgsfnet.com
www.sfnet.com


  

  
  
   
     
    






 [1-5]











   
 





about | contact  Other archives ( Real Estate discussion Medical topics )