7 replies to this topic

[hawkings]

Since my upgrade to LiveZilla 4.1.0.3 I have not been able to send emails (e.g. transcripts).
When I test the send function in the admin setup I get "Test email could not be send <...> SMTP Error: Could not authenticate." which is weird since my SMTP does not require authentication, and it worked perfectly before upgrading.

I have tried against two different working smtp servers, but I get the same error, so I fear that the latest version of LiveZilla has introduced an bug.

Best regards,
René Truelsen

[Derek Punzova]

Our old solution was working for most users but it had many drawbacks so we decided to use the wide spread standard solution phpmailer which was integrated in 4.1.

Quote

weird since my SMTP does not require authentication

I think that phpmailer requires your smtp server to require authentication.

[gabu69]

We recently moved to a centos machine and we have everything instelled properly, however we get this error
when we check the ssl encryption

Quote

The test email could not be sent!
Error: SMTP error: Could not connect to SMTP host

If we dont select ssl encryption we get an error saying:

Quote

The test email could not be sent!
Error: Smtp error: could not authenticate <p> smtp server error 5.7.0 Must issue a STARTTLS command first <p/>

how can this be fixed?

[Patrick Keil]

Hi Gabu,

Please make sure you PHP installation has SSL support (look for an "openssl" section in the output from phpinfo()).

LiveZilla uses the stand class PHPMailer for sending emails. I did some research and found many suggestions on how to fix this on these pages:

http://stackoverflow...rough-phpmailer
http://stackoverflow...s-command-first

Hope this helps.

[gabu69]

Yea we do have SSL support
and problem still continues :S
any other way to make it work?

[gabu69]

anny further help in this thread? I mean we have SSL support what else could it be?

[gabu69]

is there any further help or this will be ignored?

[Derek Punzova]

What kind of help do you expect more? Please note that this is a problem with your webserver.

There's a ton of information in the threads posted above, also you can easily track down this problem yourself. Please understand that we cannot do this for you.

Thanks.