Oh, the shame of it. I work for the ISP and have just discovered that they
haven't set reverse DNS up properly:-)
Thanks for pointing out the cause of the problem. I'll kick some butt and
get things fixed.
Patrick
>> "Patrick" == Patrick Kirk <[EMAIL PROTECTED]> wrote:
Patrick> had to do with headers...people complain of messages like this:
"received
Patrick> at Mon, 19 Jul 1999 21:11:23 +0100 (BST) from
Patrick> [EMAIL PROTECTED] [212.19.67.118] (may be forged)"
Complain to your ISP to fix his DNS.
$
Martin,
Works perfectly for relaying from work machines now. You asked what this
had to do with headers...people complain of messages like this: "received
at Mon, 19 Jul 1999 21:11:23 +0100 (BST) from
[EMAIL PROTECTED] [212.19.67.118] (may be forged)"
If anyone knows how to get rid of the MAY B
>> "Patrick" == Patrick Kirk <[EMAIL PROTECTED]> wrote:
Patrick> I want exim on my home machine to relay mail from the whole
Patrick> 212.19.64.x and 212.19.67.x so my email does not appear to
Patrick> have a spoofed header and go into spam folders on friends
Patrick> machines. [I tend to move d
Hi all,
I want exim on my home machine to relay mail from the whole 212.19.64.x and
212.19.67.x so my email does not appear to have a spoofed header and go into
spam folders on friends machines. [I tend to move desk a bit].
I have amended exim.conf as follows:
from sender_net_accept_relay = 10.
5 matches
Mail list logo