All,
I am unfortunate enough to have to run Trend Mucus here. We have
trend's smtp server running on the mail server listening to port
2525. When you connect to 2525, mucus forks a copy of exim and
proxies the commands.
The transport I use is:
trend_micro:
driver = smtp
hosts_override = true
hosts = 127.0.0.1
port = 2525
headers_remove = X-Trend-Micro-Scanned
headers_add = X-Trend-Micro-Scanned: ${message_id} ${hmac{md5}
{SECRET}{${message_id}}}\n\
X-Trend-Micro-Interscan-Viruswall-Scanned: yes
allow_localhost = true
(the router that routes to this transport uses the headers inserted
here to prevent loops)
Occasionally, trend mucus freaks out and dumps core or whatever it
does (I have no idea, its really quite horrible software)
2005-05-11 14:37:19 1DVjuI-00068T-3r Remote host 127.0.0.1
[127.0.0.1] closed connection in response to HELO xxxxxxxxxxx.net
After this, any further attempts at delivery to trend mucus are
deferred by exim:
2005-05-11 14:37:19 1DVjuJ-000697-4w == xxxx@???
R=trendscan T=trend_micro defer (-53): retry time not reached for any
host
Now, I've set the retry time for 127.0.0.1 to 1m in the retries
section, but that doesn't seem to have any affect. Ideally, I want
exim to just keep trying, because usually these problems with trend
only happen once every couple of hours, and if you try again straight
away its fine.
How can I get exim to be a little more 'aggressive' with localhost?
Regards,
Nathan.
--
Nathan Ollerenshaw / Systems Engineer
Systems Engineering
ValueCommerce Co., Ltd.
Tokyo Bldg 4F 3-32-7 Hongo Bunkyo-ku Tokyo 113-0033 Japan
Tel. +81.3.3817.8995 Fax. +81.3.3812.4051
mailto:nathan@valuecommerce.co.jp
"A man who never made a mistake never made anything."
- David Gemmell
