Hello list (or in this case the devs :), I see that you can set DoNoSpoofing and then give exceptions, but I was wondering how to do the inverse. As I understand it, if I leave DoNoSpoofing turned on my users cannot use their company email accounts as secondary send addresses from places like yahoo, unless the service in question can authenticate (and I think gmail actually can authenticate). So I'd rather leave DoNoSpoofing off but have exceptions for addresses like our ticketing system, internal distribution group addresses, and etc. that should be protected by DoNoSpoofing.
If there is no way to this now I do have a suggestion for your consideration. Perhaps noSpoofingCheckIP and noSpoofingCheckDomain could accept a format such as "block:1.2.3.4|score:2.2.2.2|monitor:3.3.3.3". These could be processed after DoNoSpoofing and act as exceptions to that rule (in either direction). That way you can have granular exceptions without 3-4 different sets of parameters. Thanks for your time, Mark Casey ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
