I've been staring at a couple of entries in the exim rejectlog similar to this
one, which is generated by a pop user gatewaying through hippo.ru.ac.za:
------------------------------------------------------------------------------
1997-11-20 16:47:10 0xYXss-0001Do-00 rejected from d5.phys.ru.ac.za [146.231.178.31]: can't verify header sender (try again later): envelope sender is <phrg@???>
To: helliott@???
P Received: from d5.phys.ru.ac.za [146.231.178.31]
by hippo.ru.ac.za with smtp (Exim 1.73 #1)
id 0xYXss-0001Do-00; Thu, 20 Nov 1997 16:47:10 +0200
I Message-ID: <3474DA0A.2EB0@???>
Date: Thu, 20 Nov 1997 16:47:06 -0800
F From: phrg <phrg@???>
Organization: Rhodes University
X-Mailer: Mozilla 2.0 (Win16; I)
MIME-Version: 1.0
T To: helliott@???
Subject: We want to purchase an episode of 'Wonders of Weather'
X-URL: http://www.baber.com/01348l01.htm
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
------------------------------------------------------------------------------
and can't for the life of me work out what's causing the reject. The mailbox
and username phrg do exist on hippo, so the above message should be fine.
The entries in the config file that could affect this behaviour are:
-------------------------------------------------------
relay_domains = "*.ru.ac.za:kj.ecape.school.za:kc.ecape.school.za"
relay_domains_include_local_mx
sender_host_accept_relay = "*.ru.ac.za:kj.ecape.school.za:kc.ecape.school.za"
sender_verify
sender_verify_except_hosts = "*.ru.ac.za:ru.ac.za:rhodes.ac.za"
sender_verify_except_nets = 146.231.0.0/255.255.0.0
sender_verify_fixup
sender_verify_reject
#sender_verify_log_details
local_domains = "rhodes.ac.za:hippo.ru.ac.za:ru.ac.za"
headers_check_syntax
headers_sender_verify
headers_sender_verify_errmsg
local_domains_include_host
qualify_domain = "hippo.ru.ac.za"
-------------------------------------------------------
The problem, presumably is headers_sender_verify, but I'm not too clear what
it's problem is, because some other pop clients happily manage to live with it.
Is it some misconfiguration on the particular client? What needs to be fixed?
The sender_verify_except_hosts was added in desperation to try and bypass this
problem, but seemingly to no avail, and I'd like to take out anything
extraneous.
Any explanations as to how I could get a clue would be very welcome.
Many thanks,
--
F.F. Jacot Guillarmod - Information Technology - Rhodes University - Grahamstown
Internet: Jacot@??? Phone: +27 461 318284 Fax: +27 461 27764
The views expressed above are not necessarily those of Rhodes University
--
*** Exim information can be found at
http://www.exim.org/ ***
