Page 1 of 2

error message on "reply"

Posted: Fri Jun 25, 2010 10:47 am
by rlaggren
This error on trying to reply to a post. It appears to be the forum software displaying the message.
----------
Could not connect to smtp host : 60 : Connection timed out

DEBUG MODE

Line : 112
File : smtp.php
------------

I can search and siplay messages no problem. This is about 10:45 am Pacific time.

Rufus

Posted: Fri Jun 25, 2010 10:47 am
by rlaggren
Aha! This one went throught I"ll try again on the OT.

Posted: Fri Jun 25, 2010 10:49 am
by rlaggren
Nope. The OT forum won't accept my post.

Posted: Sat Jun 26, 2010 7:46 am
by rlaggren
On checking the topic I found that all four of my attempts to post were uploaded even though each returned an error message. I have deleted the extras.

Posted: Thu Jul 01, 2010 10:14 pm
by asavage
I just saw that msg too. I am looking into it.

Posted: Thu Jul 01, 2010 10:15 pm
by asavage
It's a problem with emailing a "topic reply notification". Someone has configured a topic such that she is sent an email when someone replies to the topic. Email is not working well right now, after the move. I'll look into it.

Posted: Fri Jul 02, 2010 12:28 am
by windsock
Awesome Al, thanks! 8)

Getting similar messages here replying to PMs and posting to the LDsection, but the messages to the LD section went through OK.

*********************
Ran into problems sending Mail. Response: 550 5.7.1 Authentication Required

DEBUG MODE

Line : 143
File : smtp.php

Posted: Fri Jul 02, 2010 1:04 pm
by asavage
It's going to throw an error msg every time it has to send an email (PM notifications, private emails, etc.).

Thanks for posting the error text. I'll have to figure out how to fix that one when I get home.

Posted: Fri Jul 02, 2010 9:54 pm
by asavage
OK, nobody here knows the correct authentication username/password for the existing broadband connection, and the ISP's support is not available outside business hours. I will attempt to chase down the server authentication data, but it's not unlikely that I can't get it until 06Jul2010. Until then, we are going to keep seeing these error messages. Nothing I can do for now . . .

Posted: Tue Jul 06, 2010 11:27 am
by asavage
I think I've got it fixed. Email topic notifications should be working again.

Posted: Fri Aug 13, 2010 2:15 pm
by windsock
Hey Al,

Sorry if this is bad news but I got this error message when replying to a PM...
Ran into problems sending Mail. Response: 535 5.7.8 Authorization failure (Not authorized to login as specified user).

DEBUG MODE

Line : 132
File : smtp.php
and this one when posting a reply to a message...
Ran into problems sending Mail. Response: 535 5.7.8 Authorization failure (Not authorized to login as specified user).

DEBUG MODE

Line : 132
File : smtp.php
Hope this is some help at some stage.

Cheers,

Phil

Posted: Tue Aug 17, 2010 3:28 pm
by plenzen
Got the same message myself today. The reply that I wrote got posted but I dont think that the people already involved in the subject are going to get email notifications that there is a new posting that is all.
I think that Al might be away or busy at his new job as I sent him a PM quite a while ago and it's still in my "out" basket waiting to be delivered.

P

Posted: Thu Aug 19, 2010 6:28 pm
by goglio704
Ran into problems sending Mail. Response: 535 5.7.8 Authorization failure (Not authorized to login as specified user).

DEBUG MODE

Line : 132
File : smtp.php


Me too...

Posted: Thu Aug 26, 2010 1:34 pm
by asavage
I'll try to look into this again. May not be until next week, though.

Posted: Thu Aug 26, 2010 8:40 pm
by asavage
When I moved, back in May, due to geography I had to change from being with Qwest, to Verizon. Well, local Verizon service here got sold to Frontier.

Frontier changed the login credentials for their servers for existing Verizon customers who were migrated to Frontier. No big deal, they gave me plenty of notice.

However, for no good reason, they also changed the name of the SMTP server. Sigh.

Email from the forum (private email, automatic topic change notifications, new user signups) should again be working now.