Re: ISP has screwed up smtp for me... what to try? New ISP?
On 09/26/2006 11:59:03 AM, Kenward Vaughan wrote:
Hi Kevin,
I'll try this once I have a chance when I get home.
...
-----Original Message-----
From: Kevin Mark [mailto:kevin.mark@verizon.net]
...
On Mon, Sep 25, 2006 at 07:03:21PM -0700, Kenward Vaughan wrote:
Hi folks,
I hate writing this from my school's web access page, but I
suddenly lost the ability to send emails from home. Receiving is
fine. Nothing had changed at my end from the night before, when I
had no problems. My ISP is Earthlink.
...
Hi Kenward,
apt-get install swaks
and show what settings made if work.
cheers,
Kev
I changed Balsa's settings as well (adding the domain to my login name)
with success.
With a bit of reading, the following worked with swaks:
===========================================================
daddy:~# swaks -t kvaughan@bc.cc.ca.us -f kay_jay@earthlink.net -s
smtpauth.earthlink.net -tlso -a -au kay_jay@earthlink.net -ap
abcdefghijklmnop
=== Trying smtpauth.earthlink.net:25...
=== Connected to smtpauth.earthlink.net.
<- 220-elasmtp-junco.atl.sa.earthlink.net ESMTP Exim 4.34 #1 Wed, 27
Sep 2006 01:37:20 -0400
<- 220-NO UCE. EarthLink does not authorize the use of its computers
or network
<- 220 equipment to accept, transmit, or distribute unsolicited e-
mail.
-> EHLO hpotter.vaughan.home
<- 250-elasmtp-junco.atl.sa.earthlink.net Hello hpotter.vaughan.home
[70.92.98.186]
<- 250-SIZE 14680064
<- 250-PIPELINING
<- 250-AUTH PLAIN LOGIN CRAM-MD5
<- 250-STARTTLS
<- 250 HELP
-> STARTTLS
<- 220 TLS go ahead
=== TLS started w/ cipher BDT854-SHA
~> EHLO hpotter.vaughan.home
<~ 250-elasmtp-junco.atl.sa.earthlink.net Hello hpotter.vaughan.home
[70.92.98.186]
<~ 250-SIZE 14680064
<~ 250-PIPELINING
<~ 250-AUTH PLAIN LOGIN CRAM-MD5
<~ 250 HELP
~> AUTH CRAM-MD5
<~ 334
PDIzNDg0LjExNTkzMzUjUbbFZWxhc210cC1qdW5jby5hdGwuc2EuZWFydGhsaW5rLm5ldD4=
~>
a2F5X2pheUBlYXJ0aGxpbmsubmV0IGViNzY3MzVhNWIwZWYyMGRkMjQzNzE2Y2U4OTRmYTc3
<~ 235 Authentication succeeded
~> MAIL FROM:<kay_jay@earthlink.net>
<~ 250 OK
~> RCPT TO:<kvaughan@bc.cc.ca.us>
<~ 250 Accepted
~> DATA
<~ 354 Enter message, ending with "." on a line by itself
~> Date: Tue, 26 Sep 2006 22:37:20 -0700^M
~> To: kvaughan@bc.cc.ca.us^M
~> From: kay_jay@earthlink.net^M
~> Subject: test Tue, 26 Sep 2006 22:37:20 -0700^M
~> X-Mailer: swaks v20060621.0 jetmore.org/john/code/#swaks^M
~>
~> This is a test mailing^M
~>
~> .
<~ 250 OK id=1GSS6j-00066m-FB
~> QUIT
<~ 221 elasmtp-junco.atl.sa.earthlink.net closing connection
=== Connection closed with remote host.
10:37:21^M
daddy:~# exit
Script done on Tue 26 Sep 2006 10:37:24 PM PDT
===========================================================
My question changes to the obvious. Now that it worked so easily with
that small change in Balsa/Kmail, what is wrong with my Exim setup?
Is it some rewriting rule or choice I made in running its configuration
which screwed things up?
The /etc/exim4/passwd.client file:
# password file used when the local exim is authenticating to a remote
# host as a client.
#
# see passwd_client(5) for more documentation
#
# Example:
### target.mail.server.example:login:password
#207.69.189.201:kay_jay:abcdefghijklmnop
#207.69.189.202:kay_jay:abcdefghijklmnop
#207.69.189.203:kay_jay:abcdefghijklmnop
#207.69.189.204:kay_jay:abcdefghijklmnop
#207.69.189.205:kay_jay:abcdefghijklmnop
#207.69.189.206:kay_jay:abcdefghijklmnop
#207.69.189.207:kay_jay:abcdefghijklmnop
#207.69.189.208:kay_jay@earthlink.net:abcdefghijklmnop
#206.89.93.20*:kay_jay:abcdefghijklmnop
#209.86.93.210:kay_jay:abcdefghijklmnop
#209.86.93.211:kay_jay:abcdefghijklmnop
#*:kay_jay@earthlink.net:abcdefghijklmnop
smtpauth.earthlink.net:kay_jay@earthlink.net:abcdefghijklmnop
Many thanks for the information so far!
Kenward
Reply to: