Starting with the first error message (from your other message) :
[EMAIL PROTECTED]
SMTP error from remote mailer after RCPT TO:<[EMAIL PROTECTED]>:
host smtp.mailtag.com [66.84.135.12]: 554 Undeliverable TO address:
<[EMAIL PROTECTED]>
Ok, so exim on your system tried talking to smtp.mailtag.com
(66.84.135.12). Trying that I get this :
$ telnet 66.84.135.12 smtp
220 mailtag.com, Wildcat! ESMTP Server v5.6.450.3 ready
helo foo
250 mailtag.com
mail from:<>
250 <>... Sender ok.
rcpt to:<[EMAIL PROTECTED]>
554 Undeliverable TO address: <[EMAIL PROTECTED]>
The problem appears that the other system not accepting the
recipient's address. Looking at the list of MX records for chpi.org I
see that that machine isn't supposed to be receiving mail for that
address.
On Sun, Dec 15, 2002 at 08:26:36AM -0600, Cheryl Homiak wrote:
| Having checked my exim logs on both my desktop (cable connection charter)
| and laptop (ppp mailtag) computers, I find two different errors.
| On the cable machine, I find in the logs when the receiving host tries to
| take the email from charter: "relay prohibitted. You must authenticate
| first." The email remains in my queue and is retried.
The solution to this is to authenticate :-).
I'm going to take a guess that smtp.mailtag.com is the server your ISP
provides for you to send mail out and you are trying to use it as a
"smarthost". That's great, you just need to configure your side to
authenticate so that the server will accept recipients in different
domains. Look at the last section of your exim.conf file. It should
have a section (commented out) that looks like this :
cram_md5:
driver = cram_md5
public_name = CRAM-MD5
client_name = username
client_secret = password
Uncomment it and change "username" and "password" to the username and
password your ISP gave you.
| I think incoming mail is ok, but am not sure about that.
It probably is. (particularly if you are using fetchmail to pull it
and have exim deliver locally)
| Also noticed that my ip address has changed radically sometime in the last
| few days on my cable connection; this could have something to do with
| things I suppose as I had the same ip address for a long time.
It could have an effect. If your ISP was using IP-based checks to
determine whether or not you could relay, and then your IP changed,
then maybe it fails those tests now.
HTH,
-D
--
Consider what God has done:
Who can straighten what He has made crooked?
Ecclesiastes 7:13
http://dman.ddts.net/~dman/
msg19504/pgp00000.pgp
Description: PGP signature
