Arturo 'Buanzo' Busleiman writes:
Sam Varshavchik wrote:What you should do is set up an SPF record in your DNS, and turn on SPF checking in Courier, so it will simply refuse to receive any mail supposedly from your domain.Sam, would you mind providing a "Sam's SPF Example", along with related courier settings?
Well, mine is: courier-mta.com. 86400 IN TXT "v=spf1 a:mailx.courier-mta.com -all" My SPF setting is the typical average: opt BOFHSPFHELO=pass,unknown,error,none,neutral opt BOFHSPFMAILFROM=pass,unknown,error,none,neutral opt BOFHSPFTRUSTME=1The key setting is BOFHSPFTRUSTME=1; so as long as you send your mail with authenticated SMTP, you do not have to worry about getting your own outgoing mail smarthsoted through the server.
I currently use this: "v=spf1 ip4:216.139.221.215 ip4:216.239.56.0/23 ip4:64.233.160.0/19 ip4:66.249.80.0/20 ip4:72.14.192.0/18 ip4:209.85.128.0/17 ip4:66.102.0.0/20 -all" But the SPF web-tests available don't provide me with satisfactory enough results. That makes me believe I'm clearly mistaken :)
I don't particularly see anything that's immediately wrong here, although it is unlikely that your mail can originate from all of these IP addresses.
pgp6SGTzALV2U.pgp
Description: PGP signature
------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
