Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: Phil Marasco on September 20, 2003, 08:16:51 AM

Title: ssmtp/pop3 broken after upgrade
Post by: Phil Marasco on September 20, 2003, 08:16:51 AM
Hello,
After I upgraded to 6.0 beta 3 my remote users have lost the ability to send and recieve email over ssl. I had modified the 5.6 version using the directions located at http://www.pagefault.org/code.shtml. I looked and the new server seems to have all the rpms with newer version numbers but the functionality is gone. Any ideas?
-Phil
Title: Re: ssmtp/pop3 broken after upgrade
Post by: Graeme Fleming on September 20, 2003, 07:22:10 PM
As has been said many times before please report issues with beta version directly to Mitel - if they don't know an issue exists then they can't resolve it!

smebugs@mitel.com (I think)
Title: Re: ssmtp/pop3 broken after upgrade
Post by: Phil Marasco on September 20, 2003, 08:58:43 PM
Although I have done that already, I have found the getting the information to both entities oftens gets different responses. One man's bug is another man's simple problem with a simple solution. But thank you for the immediate slam. Next time I will start the post with "I have already sent this to the bug list but...."

-Phil
Title: Re: ssmtp/pop3 broken after upgrade
Post by: Phil Marasco on September 21, 2003, 02:17:01 AM
AND since the developers said that the features are unsupported I guess I will have to downrev.... oh well. Any ideas? Establishing pptp tunnels to get email is not an option unfortunately.
Title: Re: ssmtp/pop3 broken after upgrade
Post by: Charlie Brady on September 22, 2003, 05:19:43 AM
Graeme Fleming wrote:

> As has been said many times before please report issues with
> beta version directly to Mitel - if they don't know an issue
> exists then they can't resolve it!
>
> smebugs@mitel.com (I think)

In this particular case, no. ssmtp/pop3 is a contrib package, it's not part of the beta. If it doesn't work with the 6.0beta, let the developer of the contrib package know, or, better yet, work out a fix yourself and send it to the developer. Or just remove that package, and continue your testing of the beta.

Regards

Charlie