Hi
> i met problem with spf. Client ([EMAIL PROTECTED]) was sending > message to [EMAIL PROTECTED] (alias to local user and remote user - > [EMAIL PROTECTED]) - local users got message but remove user not. > Problem was that spf (set to 3) and message was bounced to domain1.com > server because domain1.com server is not permitted to send domains > from clientdomain.com (domain clientdomain.com has declared using SPF > that it does not send mail through domain1.com). What's now? I turned > of spf (set to 0). Should smtp server on domain1.com remove spf line > from message and sent without it to domain2.com server ? The receiving remote MTA should not check SPF because it will always fail. If this MTA is out of your control what is left is removing SPF from DNS so that the remote MTA thinks there's no SPF and not check domains. You might also make a view on the DNS server to make some remote cliens not ever get the SPF record, but this workaround is not a good way. It is a inherent problem with SPF. There is a workaround to this problem called SRS, but has problems: i think it won't work if the complete SRS line is longer than 64 bytes (RFC limits). This is also one of the reasons i disabled SPF and one that made me change my opinion about SPF. I belive SPF does not give any valuable protection against spam and domain impersonation. The downsides are bigger IMVHO My 0.03$ Best regards, Maciek
