And here's the headers:
Return-Path: [EMAIL PROTECTED] Received: from h00009492a802.ne.client2.attbi.com ([24.128.170.237] verified) by stango.info (Stalker SMTP Server 1.8b8) with SMTP id S.0000147858 for <[my usual account]>; Tue, 16 Mar 2004 04:27:54 -0500 Received: from [28.34.114.104] by h00009492a802.ne.client2.attbi.com with ESMTP id BB19C1EEE0C; Tue, 16 Mar 2004 11:28:42 +0200
I am pretty sure (and I am sure others who know better can correct me) that the router can't do what you want.
For inbound mail, the router first looks at the connecting IP (24.128.170.237 in your example) to see if it is blacklisted.
It then looks at the return path ([EMAIL PROTECTED] in your example) to see if it is routed to error and to make sure it is a valid domain (if you have selected that option).
It then checks the envelope addresses ([my usual account] in your example) to see if they are routed to a spamtrap.
If none of these actions discards the mail, it then performs "normal" routing on the envelope addresses.
This means that the router never sees at the reverse lookup of the connecting IP, which is what you are trying to use to route the mail.
-- Neil
Neil Herber Corporate info at http://www.eton.ca/ Eton Systems, 15 Pinepoint Drive, Nepean, ON, Canada K2H 6B1 Tel: (613) 829-4668
############################################################# This message is sent to you because you are subscribed to the mailing list <[EMAIL PROTECTED]>. To unsubscribe, E-mail to: <[EMAIL PROTECTED]> To switch to the DIGEST mode, E-mail to <[EMAIL PROTECTED]> To switch to the INDEX mode, E-mail to <[EMAIL PROTECTED]> Send administrative queries to <[EMAIL PROTECTED]>
