Suddenly cannot send mail on ISP Shaw Cablesystems

[Mel Comisarow]

With my G5 DP 1.8 GHz PowerMac running Mac OS 10.5.8 and Mail 3.6, about
two weeks ago I suddenly could not send email from my home via my local
ISP, Shaw Cable (Vancouver BC) mail servers. Any attempt to send an
email now generates a message

Cannot send message using the server
shawmail.vc.shawcable.net.

shawmail.vc.shawcable.net is the outgoing mail server that always
worked until about two weeks ago. Shaw Cable tech support claims the
problem is with my Mac as they have done nothing to block my
attempt-to-send emails. I made no changes to my Mac that preceded this
inability to send email. Restarting the Mac or reloading Mail has no
effect on the problem. Similarly, fixing permissions or running Disk
Warrior does not fix the problem.

My incoming email is received as before, via the same server,
shawmail.vc.shawcable.net ,
with no problems.

Also, I can still receive, but now cannot post to newsgroups. I'm
posting this message from work.

Any suggestions would be appreciated. Thanks.

Mel Comisarow

[Barry Margolin]

Post by Mel Comisarow
With my G5 DP 1.8 GHz PowerMac running Mac OS 10.5.8 and Mail 3.6, about
two weeks ago I suddenly could not send email from my home via my local
ISP, Shaw Cable (Vancouver BC) mail servers. Any attempt to send an
email now generates a message
Cannot send message using the server
shawmail.vc.shawcable.net.
shawmail.vc.shawcable.net is the outgoing mail server that always
worked until about two weeks ago. Shaw Cable tech support claims the
problem is with my Mac as they have done nothing to block my
attempt-to-send emails. I made no changes to my Mac that preceded this
inability to send email. Restarting the Mac or reloading Mail has no
effect on the problem. Similarly, fixing permissions or running Disk
Warrior does not fix the problem.
My incoming email is received as before, via the same server,
shawmail.vc.shawcable.net ,
with no problems.
Also, I can still receive, but now cannot post to newsgroups. I'm
posting this message from work.
Any suggestions would be appreciated. Thanks.
Mel Comisarow

What does Connection Doctor show when you're trying to send a message?

[Michael Vilain]

Post by Barry Margolin

Post by Mel Comisarow
With my G5 DP 1.8 GHz PowerMac running Mac OS 10.5.8 and Mail 3.6, about
two weeks ago I suddenly could not send email from my home via my local
ISP, Shaw Cable (Vancouver BC) mail servers. Any attempt to send an
email now generates a message
Cannot send message using the server
shawmail.vc.shawcable.net.
shawmail.vc.shawcable.net is the outgoing mail server that always
worked until about two weeks ago. Shaw Cable tech support claims the
problem is with my Mac as they have done nothing to block my
attempt-to-send emails. I made no changes to my Mac that preceded this
inability to send email. Restarting the Mac or reloading Mail has no
effect on the problem. Similarly, fixing permissions or running Disk
Warrior does not fix the problem.
My incoming email is received as before, via the same server,
shawmail.vc.shawcable.net ,
with no problems.
Also, I can still receive, but now cannot post to newsgroups. I'm
posting this message from work.
Any suggestions would be appreciated. Thanks.
Mel Comisarow

What does Connection Doctor show when you're trying to send a message?

If you and Shaw changed nothing 2 weeks ago, then hardware went
kaflooey. They may have change a configuration or the hardware started
having problems. A friend was working just fine on an older system,
bought a new iMac and couldn't connect to the internet reliable any
more. Turned out her Crapcast modem was 'marginal' and it took her a
month plus buying a disposable cell phone to get it all ironed out.

Get Shaw to replace your modem. It couldn't hurt. If they demur, make
the unit 'have an accident' by plugging it into 220V or be stuck in
front of your .50 Dessert Eagle while you're cleaning it.

[Michael Tuthill]

Post by Mel Comisarow
Cannot send message using the server
shawmail.vc.shawcable.net.

Try using "pop.shaw.ca"

Ultimately you're going to have to contact Shaw support if you can't
get it working. I've always found them to be fairly helpful if you're
patient with them and provide them with all the salient details of the
problem.

[JF Mezei]

Post by Mel Comisarow
Cannot send message using the server
shawmail.vc.shawcable.net.

If using the apple "Mail.app" , look in "Window" for "Connection
doctor". This should be giving you more details of what it is trying to
do and where/why it fails. You can then report those back here for comments.

[Mel Comisarow]

Post by JF Mezei

Post by Mel Comisarow
Cannot send message using the server
shawmail.vc.shawcable.net.

If using the apple "Mail.app" , look in "Window" for "Connection
doctor". This should be giving you more details of what it is trying to
do and where/why it fails. You can then report those back here for comments.

1) Thank you for your response.
2) Here's what, delimited by asterisks, Connection Doctor has to say:


******************************************************
When I try to send a test message to my office email

address I get the usual error message, my test message

sitting in Mail's Outbox and Connection Doctor responding

"Connection and login to server succeeded", with the

details as follows:



CONNECTED Aug 31 20:37:54.693

[kCFStreamSocketSecurityLevelNegotiatedSSL] --

host:mail.chem.ubc.ca -- port:995 -- socket:0x1953c9c0 --

thread:0x1b05b3c0



CONNECTED Aug 31 20:37:54.784

[kCFStreamSocketSecurityLevelNone] --

host:shawmail.vc.shawcable.net -- port:587 --

socket:0x1b0ea040 -- thread:0x1a7374a0



CONNECTED Aug 31 20:37:54.786

[kCFStreamSocketSecurityLevelNone] --

host:shawmail.vc.shawcable.net -- port:110 --

socket:0x1b0d1330 -- thread:0x1b067ec0



READ Aug 31 20:37:54.814 [kCFStreamSocketSecurityLevelNone]

-- host:shawmail.vc.shawcable.net -- port:587 --

socket:0x1b0ea040 -- thread:0x1a7374a0

220 mail.shaw.ca ESMTP





WROTE Aug 31 20:37:54.852

[kCFStreamSocketSecurityLevelNone] --

host:shawmail.vc.shawcable.net -- port:587 --

socket:0x1b0ea040 -- thread:0x1a7374a0

EHLO [192.168.1.100]





READ Aug 31 20:37:54.860 [kCFStreamSocketSecurityLevelNone]

-- host:shawmail.vc.shawcable.net -- port:110 --

socket:0x1b0d1330 -- thread:0x1b067ec0

+OK pop.shaw.ca





WROTE Aug 31 20:37:54.876

[kCFStreamSocketSecurityLevelNone] --

host:shawmail.vc.shawcable.net -- port:110 --

socket:0x1b0d1330 -- thread:0x1b067ec0

USER melcom





READ Aug 31 20:37:54.888

[kCFStreamSocketSecurityLevelNegotiatedSSL] --

host:mail.chem.ubc.ca -- port:995 -- socket:0x1953c9c0 --

thread:0x1b05b3c0

+OK Dovecot ready.





READ Aug 31 20:37:54.912 [kCFStreamSocketSecurityLevelNone]

-- host:shawmail.vc.shawcable.net -- port:587 --

socket:0x1b0ea040 -- thread:0x1a7374a0

250-mail.shaw.ca



250-8BITMIME



250-SIZE 29360128



250-STARTTLS



250-AUTH PLAIN LOGIN



250 AUTH=PLAIN LOGIN





WROTE Aug 31 20:37:54.924

[kCFStreamSocketSecurityLevelNegotiatedSSL] --

host:mail.chem.ubc.ca -- port:995 -- socket:0x1953c9c0 --

thread:0x1b05b3c0

USER melcom





READ Aug 31 20:37:54.938 [kCFStreamSocketSecurityLevelNone]

-- host:shawmail.vc.shawcable.net -- port:110 --

socket:0x1b0d1330 -- thread:0x1b067ec0

+OK password required for user ***@shaw.ca





WROTE Aug 31 20:37:54.961

[kCFStreamSocketSecurityLevelNone] --

host:shawmail.vc.shawcable.net -- port:587 --

socket:0x1b0ea040 -- thread:0x1a7374a0

QUIT





WROTE Aug 31 20:37:54.978

[kCFStreamSocketSecurityLevelNone] --

host:shawmail.vc.shawcable.net -- port:110 --

socket:0x1b0d1330 -- thread:0x1b067ec0

PASS ********





READ Aug 31 20:37:54.989

[kCFStreamSocketSecurityLevelNegotiatedSSL] --

host:mail.chem.ubc.ca -- port:995 -- socket:0x1953c9c0 --

thread:0x1b05b3c0

+OK





WROTE Aug 31 20:37:55.004

[kCFStreamSocketSecurityLevelNegotiatedSSL] --

host:mail.chem.ubc.ca -- port:995 -- socket:0x1953c9c0 --

thread:0x1b05b3c0

PASS ********





READ Aug 31 20:37:55.049

[kCFStreamSocketSecurityLevelNegotiatedSSL] --

host:mail.chem.ubc.ca -- port:995 -- socket:0x1953c9c0 --

thread:0x1b05b3c0

+OK Logged in.





WROTE Aug 31 20:37:55.059

[kCFStreamSocketSecurityLevelNegotiatedSSL] --

host:mail.chem.ubc.ca -- port:995 -- socket:0x1953c9c0 --

thread:0x1b05b3c0

QUIT





READ Aug 31 20:37:55.092

[kCFStreamSocketSecurityLevelNegotiatedSSL] --

host:mail.chem.ubc.ca -- port:995 -- socket:0x1953c9c0 --

thread:0x1b05b3c0

+OK Logging out.





READ Aug 31 20:37:55.276 [kCFStreamSocketSecurityLevelNone]

-- host:shawmail.vc.shawcable.net -- port:110 --

socket:0x1b0d1330 -- thread:0x1b067ec0

+OK Maildrop ready





WROTE Aug 31 20:37:55.286

[kCFStreamSocketSecurityLevelNone] --

host:shawmail.vc.shawcable.net -- port:110 --

socket:0x1b0d1330 -- thread:0x1b067ec0

QUIT





READ Aug 31 20:37:55.360 [kCFStreamSocketSecurityLevelNone]

-- host:shawmail.vc.shawcable.net -- port:110 --

socket:0x1b0d1330 -- thread:0x1b067ec0

+OK





CONNECTED Aug 31 20:38:17.797

[kCFStreamSocketSecurityLevelNegotiatedSSL] --

host:mail.chem.ubc.ca -- port:995 -- socket:0x1b0e64f0 --

thread:0x1b05da20



CONNECTED Aug 31 20:38:17.897

[kCFStreamSocketSecurityLevelNone] --

host:shawmail.vc.shawcable.net -- port:587 --

socket:0x1a7c0860 -- thread:0x1a7f03b0



CONNECTED Aug 31 20:38:17.909

[kCFStreamSocketSecurityLevelNone] --

host:shawmail.vc.shawcable.net -- port:110 --

socket:0x1b06fb30 -- thread:0x1a77f3e0



READ Aug 31 20:38:17.925 [kCFStreamSocketSecurityLevelNone]

-- host:shawmail.vc.shawcable.net -- port:587 --

socket:0x1a7c0860 -- thread:0x1a7f03b0

220 mail.shaw.ca ESMTP





READ Aug 31 20:38:17.954 [kCFStreamSocketSecurityLevelNone]

-- host:shawmail.vc.shawcable.net -- port:110 --

socket:0x1b06fb30 -- thread:0x1a77f3e0

+OK pop.shaw.ca





WROTE Aug 31 20:38:17.973

[kCFStreamSocketSecurityLevelNone] --

host:shawmail.vc.shawcable.net -- port:587 --

socket:0x1a7c0860 -- thread:0x1a7f03b0

EHLO [192.168.1.100]





WROTE Aug 31 20:38:18.001

[kCFStreamSocketSecurityLevelNone] --

host:shawmail.vc.shawcable.net -- port:110 --

socket:0x1b06fb30 -- thread:0x1a77f3e0

USER melcom





READ Aug 31 20:38:18.020

[kCFStreamSocketSecurityLevelNegotiatedSSL] --

host:mail.chem.ubc.ca -- port:995 -- socket:0x1b0e64f0 --

thread:0x1b05da20

+OK Dovecot ready.





READ Aug 31 20:38:18.047 [kCFStreamSocketSecurityLevelNone]

-- host:shawmail.vc.shawcable.net -- port:587 --

socket:0x1a7c0860 -- thread:0x1a7f03b0

250-mail.shaw.ca



250-8BITMIME



250-SIZE 29360128



250-STARTTLS



250-AUTH PLAIN LOGIN



250 AUTH=PLAIN LOGIN





READ Aug 31 20:38:18.071 [kCFStreamSocketSecurityLevelNone]

-- host:shawmail.vc.shawcable.net -- port:110 --

socket:0x1b06fb30 -- thread:0x1a77f3e0

+OK password required for user ***@shaw.ca





WROTE Aug 31 20:38:18.093

[kCFStreamSocketSecurityLevelNegotiatedSSL] --

host:mail.chem.ubc.ca -- port:995 -- socket:0x1b0e64f0 --

thread:0x1b05da20

USER melcom





WROTE Aug 31 20:38:18.129

[kCFStreamSocketSecurityLevelNone] --

host:shawmail.vc.shawcable.net -- port:587 --

socket:0x1a7c0860 -- thread:0x1a7f03b0

QUIT





WROTE Aug 31 20:38:18.156

[kCFStreamSocketSecurityLevelNone] --

host:shawmail.vc.shawcable.net -- port:110 --

socket:0x1b06fb30 -- thread:0x1a77f3e0

PASS ********





READ Aug 31 20:38:18.175

[kCFStreamSocketSecurityLevelNegotiatedSSL] --

host:mail.chem.ubc.ca -- port:995 -- socket:0x1b0e64f0 --

thread:0x1b05da20

+OK





WROTE Aug 31 20:38:18.199

[kCFStreamSocketSecurityLevelNegotiatedSSL] --

host:mail.chem.ubc.ca -- port:995 -- socket:0x1b0e64f0 --

thread:0x1b05da20

PASS ********





READ Aug 31 20:38:18.251

[kCFStreamSocketSecurityLevelNegotiatedSSL] --

host:mail.chem.ubc.ca -- port:995 -- socket:0x1b0e64f0 --

thread:0x1b05da20

+OK Logged in.





WROTE Aug 31 20:38:18.274

[kCFStreamSocketSecurityLevelNegotiatedSSL] --

host:mail.chem.ubc.ca -- port:995 -- socket:0x1b0e64f0 --

thread:0x1b05da20

QUIT





READ Aug 31 20:38:18.305

[kCFStreamSocketSecurityLevelNegotiatedSSL] --

host:mail.chem.ubc.ca -- port:995 -- socket:0x1b0e64f0 --

thread:0x1b05da20

+OK Logging out.





READ Aug 31 20:38:18.463 [kCFStreamSocketSecurityLevelNone]

-- host:shawmail.vc.shawcable.net -- port:110 --

socket:0x1b06fb30 -- thread:0x1a77f3e0

+OK Maildrop ready





WROTE Aug 31 20:38:18.481

[kCFStreamSocketSecurityLevelNone] --

host:shawmail.vc.shawcable.net -- port:110 --

socket:0x1b06fb30 -- thread:0x1a77f3e0

QUIT





READ Aug 31 20:38:18.546 [kCFStreamSocketSecurityLevelNone]

-- host:shawmail.vc.shawcable.net -- port:110 --

socket:0x1b06fb30 -- thread:0x1a77f3e0

+OK






******************************************************

[JF Mezei]

The text you are interested in is the on to port 587. This is the SMTP
server for you to submit outgoing emails.

You connect to it. It gives its capabilities, and then you issue the
QUIT command to disconnect. ("you" being your mac).


You'd want the connection doctor to capture soemthing wen you actually
send an email to see what happens. You'd want to make sure that the
emails are going trhough the right service since you appear to have a
ubc and a shaw mailbox.

[Michael Vilain]

Post by Mel Comisarow

Post by JF Mezei

Post by Mel Comisarow
Cannot send message using the server
shawmail.vc.shawcable.net.

If using the apple "Mail.app" , look in "Window" for "Connection
doctor". This should be giving you more details of what it is trying to
do and where/why it fails. You can then report those back here for comments.

1) Thank you for your response.
******************************************************
When I try to send a test message to my office email
address I get the usual error message, my test message
sitting in Mail's Outbox and Connection Doctor responding
"Connection and login to server succeeded", with the
CONNECTED Aug 31 20:37:54.693
[kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:mail.chem.ubc.ca -- port:995 -- socket:0x1953c9c0 --
thread:0x1b05b3c0
CONNECTED Aug 31 20:37:54.784
[kCFStreamSocketSecurityLevelNone] --
host:shawmail.vc.shawcable.net -- port:587 --
socket:0x1b0ea040 -- thread:0x1a7374a0
CONNECTED Aug 31 20:37:54.786
[kCFStreamSocketSecurityLevelNone] --
host:shawmail.vc.shawcable.net -- port:110 --
socket:0x1b0d1330 -- thread:0x1b067ec0
READ Aug 31 20:37:54.814 [kCFStreamSocketSecurityLevelNone]
-- host:shawmail.vc.shawcable.net -- port:587 --
socket:0x1b0ea040 -- thread:0x1a7374a0
220 mail.shaw.ca ESMTP
WROTE Aug 31 20:37:54.852
[kCFStreamSocketSecurityLevelNone] --
host:shawmail.vc.shawcable.net -- port:587 --
socket:0x1b0ea040 -- thread:0x1a7374a0
EHLO [192.168.1.100]
READ Aug 31 20:37:54.860 [kCFStreamSocketSecurityLevelNone]
-- host:shawmail.vc.shawcable.net -- port:110 --
socket:0x1b0d1330 -- thread:0x1b067ec0
+OK pop.shaw.ca
WROTE Aug 31 20:37:54.876
[kCFStreamSocketSecurityLevelNone] --
host:shawmail.vc.shawcable.net -- port:110 --
socket:0x1b0d1330 -- thread:0x1b067ec0
USER melcom
READ Aug 31 20:37:54.888
[kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:mail.chem.ubc.ca -- port:995 -- socket:0x1953c9c0 --
thread:0x1b05b3c0
+OK Dovecot ready.
READ Aug 31 20:37:54.912 [kCFStreamSocketSecurityLevelNone]
-- host:shawmail.vc.shawcable.net -- port:587 --
socket:0x1b0ea040 -- thread:0x1a7374a0
250-mail.shaw.ca
250-8BITMIME
250-SIZE 29360128
250-STARTTLS
250-AUTH PLAIN LOGIN
250 AUTH=PLAIN LOGIN
WROTE Aug 31 20:37:54.924
[kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:mail.chem.ubc.ca -- port:995 -- socket:0x1953c9c0 --
thread:0x1b05b3c0
USER melcom
READ Aug 31 20:37:54.938 [kCFStreamSocketSecurityLevelNone]
-- host:shawmail.vc.shawcable.net -- port:110 --
socket:0x1b0d1330 -- thread:0x1b067ec0
WROTE Aug 31 20:37:54.961
[kCFStreamSocketSecurityLevelNone] --
host:shawmail.vc.shawcable.net -- port:587 --
socket:0x1b0ea040 -- thread:0x1a7374a0
QUIT
WROTE Aug 31 20:37:54.978
[kCFStreamSocketSecurityLevelNone] --
host:shawmail.vc.shawcable.net -- port:110 --
socket:0x1b0d1330 -- thread:0x1b067ec0
PASS ********
READ Aug 31 20:37:54.989
[kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:mail.chem.ubc.ca -- port:995 -- socket:0x1953c9c0 --
thread:0x1b05b3c0
+OK
WROTE Aug 31 20:37:55.004
[kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:mail.chem.ubc.ca -- port:995 -- socket:0x1953c9c0 --
thread:0x1b05b3c0
PASS ********
READ Aug 31 20:37:55.049
[kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:mail.chem.ubc.ca -- port:995 -- socket:0x1953c9c0 --
thread:0x1b05b3c0
+OK Logged in.
WROTE Aug 31 20:37:55.059
[kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:mail.chem.ubc.ca -- port:995 -- socket:0x1953c9c0 --
thread:0x1b05b3c0
QUIT
READ Aug 31 20:37:55.092
[kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:mail.chem.ubc.ca -- port:995 -- socket:0x1953c9c0 --
thread:0x1b05b3c0
+OK Logging out.
READ Aug 31 20:37:55.276 [kCFStreamSocketSecurityLevelNone]
-- host:shawmail.vc.shawcable.net -- port:110 --
socket:0x1b0d1330 -- thread:0x1b067ec0
+OK Maildrop ready
WROTE Aug 31 20:37:55.286
[kCFStreamSocketSecurityLevelNone] --
host:shawmail.vc.shawcable.net -- port:110 --
socket:0x1b0d1330 -- thread:0x1b067ec0
QUIT
READ Aug 31 20:37:55.360 [kCFStreamSocketSecurityLevelNone]
-- host:shawmail.vc.shawcable.net -- port:110 --
socket:0x1b0d1330 -- thread:0x1b067ec0
+OK
CONNECTED Aug 31 20:38:17.797
[kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:mail.chem.ubc.ca -- port:995 -- socket:0x1b0e64f0 --
thread:0x1b05da20
CONNECTED Aug 31 20:38:17.897
[kCFStreamSocketSecurityLevelNone] --
host:shawmail.vc.shawcable.net -- port:587 --
socket:0x1a7c0860 -- thread:0x1a7f03b0
CONNECTED Aug 31 20:38:17.909
[kCFStreamSocketSecurityLevelNone] --
host:shawmail.vc.shawcable.net -- port:110 --
socket:0x1b06fb30 -- thread:0x1a77f3e0
READ Aug 31 20:38:17.925 [kCFStreamSocketSecurityLevelNone]
-- host:shawmail.vc.shawcable.net -- port:587 --
socket:0x1a7c0860 -- thread:0x1a7f03b0
220 mail.shaw.ca ESMTP
READ Aug 31 20:38:17.954 [kCFStreamSocketSecurityLevelNone]
-- host:shawmail.vc.shawcable.net -- port:110 --
socket:0x1b06fb30 -- thread:0x1a77f3e0
+OK pop.shaw.ca
WROTE Aug 31 20:38:17.973
[kCFStreamSocketSecurityLevelNone] --
host:shawmail.vc.shawcable.net -- port:587 --
socket:0x1a7c0860 -- thread:0x1a7f03b0
EHLO [192.168.1.100]
WROTE Aug 31 20:38:18.001
[kCFStreamSocketSecurityLevelNone] --
host:shawmail.vc.shawcable.net -- port:110 --
socket:0x1b06fb30 -- thread:0x1a77f3e0
USER melcom
READ Aug 31 20:38:18.020
[kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:mail.chem.ubc.ca -- port:995 -- socket:0x1b0e64f0 --
thread:0x1b05da20
+OK Dovecot ready.
READ Aug 31 20:38:18.047 [kCFStreamSocketSecurityLevelNone]
-- host:shawmail.vc.shawcable.net -- port:587 --
socket:0x1a7c0860 -- thread:0x1a7f03b0
250-mail.shaw.ca
250-8BITMIME
250-SIZE 29360128
250-STARTTLS
250-AUTH PLAIN LOGIN
250 AUTH=PLAIN LOGIN
READ Aug 31 20:38:18.071 [kCFStreamSocketSecurityLevelNone]
-- host:shawmail.vc.shawcable.net -- port:110 --
socket:0x1b06fb30 -- thread:0x1a77f3e0
WROTE Aug 31 20:38:18.093
[kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:mail.chem.ubc.ca -- port:995 -- socket:0x1b0e64f0 --
thread:0x1b05da20
USER melcom
WROTE Aug 31 20:38:18.129
[kCFStreamSocketSecurityLevelNone] --
host:shawmail.vc.shawcable.net -- port:587 --
socket:0x1a7c0860 -- thread:0x1a7f03b0
QUIT
WROTE Aug 31 20:38:18.156
[kCFStreamSocketSecurityLevelNone] --
host:shawmail.vc.shawcable.net -- port:110 --
socket:0x1b06fb30 -- thread:0x1a77f3e0
PASS ********
READ Aug 31 20:38:18.175
[kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:mail.chem.ubc.ca -- port:995 -- socket:0x1b0e64f0 --
thread:0x1b05da20
+OK
WROTE Aug 31 20:38:18.199
[kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:mail.chem.ubc.ca -- port:995 -- socket:0x1b0e64f0 --
thread:0x1b05da20
PASS ********
READ Aug 31 20:38:18.251
[kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:mail.chem.ubc.ca -- port:995 -- socket:0x1b0e64f0 --
thread:0x1b05da20
+OK Logged in.
WROTE Aug 31 20:38:18.274
[kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:mail.chem.ubc.ca -- port:995 -- socket:0x1b0e64f0 --
thread:0x1b05da20
QUIT
READ Aug 31 20:38:18.305
[kCFStreamSocketSecurityLevelNegotiatedSSL] --
host:mail.chem.ubc.ca -- port:995 -- socket:0x1b0e64f0 --
thread:0x1b05da20
+OK Logging out.
READ Aug 31 20:38:18.463 [kCFStreamSocketSecurityLevelNone]
-- host:shawmail.vc.shawcable.net -- port:110 --
socket:0x1b06fb30 -- thread:0x1a77f3e0
+OK Maildrop ready
WROTE Aug 31 20:38:18.481
[kCFStreamSocketSecurityLevelNone] --
host:shawmail.vc.shawcable.net -- port:110 --
socket:0x1b06fb30 -- thread:0x1a77f3e0
QUIT
READ Aug 31 20:38:18.546 [kCFStreamSocketSecurityLevelNone]
-- host:shawmail.vc.shawcable.net -- port:110 --
socket:0x1b06fb30 -- thread:0x1a77f3e0
+OK
******************************************************

This says your authentication and password was OK, so if you're getting
"authorization failed" it's not from the username/password combo unless
it's different in your keychain from what you supplied here. If all is
the same, that points to a severly borked email configuation on Shaw's
system. Good luck getting anyone to look at it, especially if 'it works
for me' is the first response you're getting from others in this group.
Chances are the script support people in Bangmemore have no clue on
what's going on and only the senior mail support person is going to have
enough expertise to figure this out. Good luck getting ahold of them.
You might want to buy a share of SHAW stock, that way you can complain
to INVESTOR SERVICES of issues you as a shareholder are having with the
company's products. This will bypass the usual support queues.

Failing that, try gmail. They're much better.

[Barry Margolin]

Post by Michael Vilain
This says your authentication and password was OK, so if you're getting
"authorization failed" it's not from the username/password combo unless
it's different in your keychain from what you supplied here.

Actually, his log only shows authentication succeeding to the POP
server. It never even tries to authenticate to the SMTP server.

Check your outgoing server settings and make sure you have
authentication enabled there.

[Jolly Roger]

Post by Mel Comisarow
With my G5 DP 1.8 GHz PowerMac running Mac OS 10.5.8 and Mail 3.6, about
two weeks ago I suddenly could not send email from my home via my local
ISP, Shaw Cable (Vancouver BC) mail servers. Any attempt to send an
email now generates a message
Cannot send message using the server
shawmail.vc.shawcable.net.
shawmail.vc.shawcable.net is the outgoing mail server that always
worked until about two weeks ago. Shaw Cable tech support claims the
problem is with my Mac as they have done nothing to block my
attempt-to-send emails. I made no changes to my Mac that preceded this
inability to send email. Restarting the Mac or reloading Mail has no
effect on the problem. Similarly, fixing permissions or running Disk
Warrior does not fix the problem.
My incoming email is received as before, via the same server,
shawmail.vc.shawcable.net ,
with no problems.
Also, I can still receive, but now cannot post to newsgroups. I'm
posting this message from work.
Any suggestions would be appreciated. Thanks.
Mel Comisarow

If I were a betting man, I'd bet that you are connected to a network
*other than* shawcable.net when you try to send the message, and the
Shaw Cable server is refusing to relay messages.

[JF Mezei]

Post by Jolly Roger
If I were a betting man, I'd bet that you are connected to a network
*other than* shawcable.net when you try to send the message, and the
Shaw Cable server is refusing to relay messages.

Shaw may have obtained a new block of IPs and assigned them to your CMTS
but forgot to "authorize" that block in its various servers so they see
you as being from outside their network instead of being inside.

(the CMTS is the glorified router which talks to your cable modem and
you). Your IP is routable from the internet all the way to that CMTS
(you are in a LAN connection with the CMTS).