> On Mar 9, 2016, at 7:11 PM, Indunil Jayasooriya wrote:
>
>
>
>> On Thu, Mar 10, 2016 at 12:57 AM, Tom Johnson wrote:
>> I'm sorry if I wasn't clear - adding to trusted_networks is not an option.
>> Different users have different needs. One person
On Thu, Mar 10, 2016 at 12:57 AM, Tom Johnson wrote:
> I'm sorry if I wasn't clear - adding to trusted_networks is not an
> option. Different users have different needs. One person might want
> x.x.x.x whitelisted, but another may not.
>
Why don't you need to whitelist
Am 09.03.2016 um 20:27 schrieb Tom Johnson:
> I'm sorry if I wasn't clear - adding to trusted_networks is not an
> option. Different users have different needs. One person might want
> x.x.x.x whitelisted, but another may not.
perhaps you like
http://wiki.policyd.org/policies
On 9. mar. 2016 20.15.41 "J. Echter"
wrote:
So foo-user trusted_networks 8.8.8.8 in sql user prefs, untested
Note whitelist_from is a joke
i'd also go for trusted_networks in local.cf of spamassassin.
Is greylisting also a problem?
Yes trusted must be
Am 09.03.2016 um 18:11 schrieb Benny Pedersen:
> So foo-user trusted_networks 8.8.8.8 in sql user prefs, untested
>
> Note whitelist_from is a joke
i'd also go for trusted_networks in local.cf of spamassassin.
Is greylisting also a problem?
So foo-user trusted_networks 8.8.8.8 in sql user prefs, untested
Note whitelist_from is a joke
Am 09.03.2016 um 16:38 schrieb Tom Johnson:
> We have some customers who need to whitelist email for their domain based on
> the sender's IP address.
>
> I don't want to set up custom policy banks for them (we have hundreds of
> domains, which have different needs and requirements), and I
We have some customers who need to whitelist email for their domain based on
the sender's IP address.
I don't want to set up custom policy banks for them (we have hundreds of
domains, which have different needs and requirements), and I can't add it to a
general spamassassin