Lloyd,
THank you for your explanations.
And how did you fix all that?
What do you mean by: "I finally
had to zap that out of the headers to eliminate all of the problems.
(That was in Mailman.)" ?
Any solution?
Thanks.
> There really is no fix. Dynamic IP's are simply not allowed. The only
> way would be to "spoof" your IP and that is against all RFC's and some
> laws.
>
> The theory is that "real" businesses will have "real" servers with
> dedicated IP's. Comcast, AOL, Compuserver, all Mail.com, many
> government agencies and schools (sometimes MSN/Hotmail)- they all
> block dynamic IP's. In addition, spambag.org (among others) lists them
> as dynamic blocks which then hits people that use their blacklists.
>
> I ran into the same type of problem when I was using a server and so
> many messages were seen as coming from my dynamic IP. I finally
> had to zap that out of the headers to eliminate all of the problems.
> (That was in Mailman.)
>
>
>
>
>
> Subject: Re: [Exim] exim - smarthost config problem - dynamic IP
> rejection
> From: java@???
> To: java@???
> Copies to: "Tor Slettnes" <tor@???>, java@???,
> "'Exim' Users" <exim-users@???>
> Date sent: Tue, 11 May 2004 13:29:43 -0400 (EDT)
>
>> It would be nice to know if anyone has had the same kind of problem I
>> have
>> ( dynamic IP originated mail blocked by some ISPs).
>> If yes what are the steps to follow.
>> I will try to use all the hints you guys sent to me.
>> If anyone out there had/has the same problem I have, it would be
>> appreciate for any posts.
>> Thank you.
>>
>> > It's not even using the authenticator defined by me.
>> > It simply dies on ISP mailserver 550 .
>> > All I see in my exim log is the fact that my ISP does not permit relay
>> 550
>> > :(
>> >
>> >>
>> >> On May 11, 2004, at 08:22, java@??? wrote:
>> >>> login:
>> >>> driver = plaintext
>> >>> public_name = LOGIN
>> >>> client_send =
>> >>> "encrypteduser_password_used_to_authenticate_when_telne_to_my_ISP"
>> >>>
>> >>>
>> >>> Now when I try to send emails, I get 550 relay not permitted from my
>> >>> ISP mail server. My understanding was that one smarthost defined the
>> >>> 'login' will kick in and try to authenticate.
>> >>> In my email log I see the 550 relay not permitted message, but don't
>> >>> see the fact that login is called.
>> >>
>> >> See the provided examples. Basically, "client_send" should list
>> three
>> >> fields, separated by colons:
>> >> client_send = "$server : $username : $password"
>> >>
>> >> $server is the server you authenticate against
>> >> $username is your username on that server
>> >> $password is your password on that server
>> >>
>> >>
>> >> -tor
>> >>
>> >>
>> >
>> >
>>
>>
>> --
>>
>> ## List details at http://www.exim.org/mailman/listinfo/exim-users Exim
>> details at http://www.exim.org/ ##
>>
>>
>>
>
>
> Thanks.
>
> Lloyd F. Tennison
> lloyd_tennison@???
>
> No trees were harmed in the transmission of this message.
> However, a rather large number of electrons were temporarily
> inconvenienced.
>
>
