Ahh, indeed you are correct, at some point, we seem to have decided this
was too often not what people really expected.
To restore the documented behavior, add this setting:
I will update the docs to clarify this.
On 26/11/2019 10:07 AM, John Wilkes wrote:
> On the Friends - Settings page:
> "Friends is applied after your Filters and after your Spam rules. Friends address list is applied after your Filters and before your Spamrules."
> This is not the behavior I see, and that you confirm. Friends is applied BEFORE filters, not after, as implied above.
> Currently running SurgeMail Version 7.3o4-4, so maybe this has been corrected in a more recent release.
> On 11/25/19 12:33 PM, John Wilkes wrote:
>> Thanks for the reply and explanation. The user had sent a message to the address, and it was automatically added to the user's friends list. The the user added a filter to reject messages from that address, but it didn't work. I then tried to globally block the domain, but that didn't work, either. Now I know why. :-)
>> I removed the address from the user's friends list and disabled automatically adding outgoing addresses.
>> On 11/25/19 12:07 PM, Support ChrisP wrote:
>>> Indeed no, the friends list is an over-ride for almost all situations. This is very much intentional.
>>> You can enforce a rule by using mfilter.rul to reject the message.
>>> On Tuesday 26/11/2019 at 5:43 am, John Wilkes wrote:
>>>> I added domain and global filter entries to reject messages from a domain, but incoming email from that domain is still delivered. The log file indicates that the email was accepted because the sender is on the recipient's "friends" list.
>>>> Shouldn't a global or domain setting override an individual user's setting?