Why do you have that particular IP registered on the box to begin
with?  Seems like if you were to remove it, this problem would go away all
by itself.  TR.WOU.EDU is clearly registered as (we would assume) a
non-dynamic address, 140.211.116.15.  So what purpose is served by having
the machine multihomed with the dynamic 140.211.116.119 IP?  (For that
matter, if you really need that IP on the machine, why can't you get your
DNS folks to rename it so it doesn't have that "dyn-" prefix, which is
probably causing the blacklisting problem to begin with?)

Nathan

At 06:59 PM 8/17/2004 +1000, you wrote:
>I've never had trouble with Optusnet accepting mail from my server before,
>and I'm running off a dynamic IP so it's entirely possible their protection
>scheme is screwed, which wouldn't surprise me at times considering what
>they're like (they used to be my own ISP and I have my own share of
>nightmares that made even AOL look promising). Easiest solution might be to
>mail their admin and try to resolve the issue working with them, best of luck.
>
>At 04:22 AM 17/08/2004, you wrote:
>>On Mon, 16 Aug 2004 10:48:33 -0700, Randy Klumph <[log in to unmask]> wrote:
>>
>> >The following error has been showing up in my LSMTP log.
>>
>>Questions such as this one, exclusively about LSMTP, are better addressed to
>>the LSMTP list: [log in to unmask]
>>
>> >23:40:10 mail.OPTUSNET.COM.AU( 12) <<< RCPT TO:<[log in to unmask]>
>> >23:40:10 mail.OPTUSNET.COM.AU( 12) >>> 554 5.7.1 Rejected
>> >140.211.116.119 is a dynamic IP
>> >
>> >1st - LISTSERV is not configured to use the IP address indicated
>>
>>Is this an IP assigned to the box LSMTP is running on?  Then any of the IPs
>>assigned to the machine may be used when making a connection.
>>
>> >2nd - it is not a dynamic IP, but we do have multiple IPs on a single
>> >box (including this one).
>>
>>Obviously mail.OPTUSNET.COM.AU, in a spam-reduction effort, is using some
>>kind
>>of lookup list of dynamic IPs that it will not accept mail from.  Obviously
>>also their list is incorrect, but there isn't anything you can do about this
>>since you have no idea which Dynamic IP list they are using.
>>
>> >What could be causing this? I'm not sure where to look.
>>
>>It's a recipient-side error.