Hi Paul
---Paul wrote---
> Is it possible for you to create a bug regarding update of the plugin, so
> they will work with the newest version of SquirrelMail SVN, or can I pay you
> for that?
Third party plugins are not obligated to work with 1.5.x so it's not a bug per
se. But yes, it is poss
Hi Paul
Thanks for your answers.
---Paul Wrote---
Are you sure it requires a TLS connection from the outset? Normally port
587 is used with STARTTLS, where the connection is plaintext and then upgraded.
Sometimes you can connect to port 465 with TLS.
---
Now I has communicated with my hosting com
Hi Paul
Thanks for your answers.
---Paul Wrote---
Are you sure it requires a TLS connection from the outset? Normally port
587 is used with STARTTLS, where the connection is plaintext and then upgraded.
Sometimes you can connect to port 465 with TLS.
---
Now I has communicated with my hosting com
Hi Paul
---Paul wrote---
> Is it possible for you to create a bug regarding update of the plugin, so
> they will work with the newest version of SquirrelMail SVN, or can I pay you
> for that?
Third party plugins are not obligated to work with 1.5.x so it's not a bug per
se. But yes, it is poss
> Now I has communicated with my hosting company. They write me that the
> outgoing SMTP-server only can be accessed on port 25 and 587. Therefore I
> will mean that I not can use the TLS-option in SquirrelMail, since my
> hosting company use STARTTLS over port 587.
SquirrelMail supports STARTTLS.
>>> Is it possible for you to create a bug regarding update of the plugin,
>>> so they will work with the newest version of SquirrelMail SVN, or can I
>>> pay you for that?
>>
>> Third party plugins are not obligated to work with 1.5.x so it's not a bug
>> per se. But yes, it is possible for me to