On 06/17/2014 09:13 PM, Axb wrote:
On 06/17/2014 08:40 PM, [email protected] wrote:
On 17.06.2014 14:09, RW wrote:
On Mon, 16 Jun 2014 17:03:31 -0230
[email protected] wrote:
> originating_ip_headers X-WebmailclientIP
Actually, that might meet my needs in a better way, as I could add a
custom header and then set that.
I don't think that's a good idea, originating IP addresses may
legitimately be dynamic, so blocklists that tend to FP on dynamic
addresses aren't applied. This is where having an interface for adding
extra IP addresses to be checked would be useful.
In our case, I would only be using it for when the e-mail contains an
X-PHP-Script header and is outgoing from our server, to prevent outgoing
spam from PHP script, as we have some clients with forms being abused
currently and cannot possibly police all their forms.
Can you show us a sample of such a header?
I'm trying to understand what adds that header if, as you say, have no
control over the abused form code?
