Topic: Are the bug reports still being updated ??? !!! ???

[Tino]

A bug report was entered on 22/06/2004, author TIMJ, regarding a problem with PORT 25 (smtp) when configuring Mitel Server Ver.6 (BETA x) when it is set to operate as SERVER ONLY,and nothing has been done about the reported bug.


I am having the same problem and it has become an absolute nightmare to try and find valid information in fixing the problem.

[raem]

Why are you concerned about bug reports & follow up when you are still using a beta release.

Surely you should update to the final product first (more secure, more stable, improvements here and there etc etc).

[Tino]

Thanks Ray,

agreed, but as most of us know an upgrade path is most definately not the the best option to use on the Mitel Servers - might just be on the BETA releases that it does not work. (I have tried Version upgrades from 5.6 to 6.0 beta 2, as well as Ver6.0 (first release) to beta 3)

Also, I do not see the need to do a complete Version upgrade if the rest of my machine is stable, except for the fact that if a certain option (SERVER ONLY) is used, that smtp does not work. And that does not mean that my entire system is now unstable.

I am looking for solutions that applies to this specifiec problem, or alternatively a work around that will resolve the issue.

I do not believe in doing a complete upgrade of system when I am having problems with one small aspect of a larger system. That is why there are technical forum - like this one - to get people together and solve problems. Why do you think Mitel has gone this route - it has worked for Linus about 13 years ago.

[raem]

Your reasoning is strange. You want bugs fixed for beta versions of software when final releases have already been released. No one is going to be the least bit concerned about fixing bugs on a beta release when it has been superceded by a final release.

My point was to upgrade to the final release and see if you still have the problem. It may well have been fixed already in the final release. By final I mean v6.0 or 6.0.1.

Your upgrade experience is related to problems with beta versions, of course there will be problems with beta versions as they are not yet the final version without bugs.

You should upgrade as no work is being done on any release except v6.0 final from Mitel and v6.0.1 from contribs.org.

[Tino]

Tanks again Ray,

now before this gets into a mudsling contest, I am going to explain my reasoning...

There are always two sides to a coin. I have to determine if the problem exists with me. The chances a greater that I am having an Old Aged moment (better known as a Senoir moment). If the problem is with me I would like to find out what the hell I am missing.

If an upgrade is the solution, then what have I learned - nothing. I will still be no closer in understanding why this has happened.


In my humble opinion - upgrades are there to resolve serious problems and/or to enhance the functionality of a system.

The latest beta release is always based on the previous release, including fixes and enhancements.

Then there is always the posibility that upgrading to the latest version does not mean that it will resolve the problem. How will I know?

Now the last point: If you refer to TIMJ's bug report, you will notice that he was infact using Ver 6.0.1.

TIMJ wrote:  
"Upgraded SME 5.x to 6.0.1 - Use as Gateway Server
After upgrade no workstations on the network could send email through our external ISP SMTP server. Mailwasher could check and bounce emails, but Outlook couldn't find any SMTP server I tried.
After poking around a lot, found that PORT 25 is being blocked. Could not find any setting on ....."


After two days I am still without a solution.....?

[raem]

> If an upgrade is the solution, then what have I
> learned - nothing. I will still be no closer in
> understanding why this has happened.

It only takes 15 minutes to an hour to do an upgrade, probably much less time than troublshooting and fault diagnosis takes.
If a buggy beta version was the problem, what does it matter, the problem is fixed by upgrading (and the problem was a bug in the software, something completely out of your control)


> The latest beta release is always based on the
> previous release, including fixes and enhancements.

Beta releases do get to a stage when they are considered STABLE with no known functional problems and that is when they turn into a final release. Of course bugs can be found after that, but it seems there have been very few with v6.0.
Recommended practice by ALL software developers is to only use beta versions in test situations and only use stable final releases in production environments.
I just cannot see why you would consider it wise to keep using a beta release, especially when you are experiencing problems.


> Then there is always the posibility that upgrading > to the latest version does not mean that it will
> resolve the problem. How will I know?

You will know when you upgrade to the latest STABLE release and the problem goes away, but if you don't upgrade then you will never find out, simple as that. The act of upgrading is in fact a step in the troubleshooting process. You eliminate one of the possibilities by removing a buggy beta software from the equation (by upgrading).
If the problem is then not fixed, then other people will be interested to fix it because it may also affect them.
(No one will be interested to fix an old beta release though, even if you could prove what the exact problem is, they will all say "upgrade first and then report back").


> "Upgraded SME 5.x to 6.0.1 - Use as Gateway Server
> After upgrade no workstations on the network could > send email through our external ISP SMTP server.

And probably that "bug" was in fact a feature of v6.x, where there is a smtp transproxy. The v6.0 release notes mentioned this and the workaround for it.

[NickR]

A bug report was entered on 22/06/2004, author TIMJ, regarding a problem with PORT 25 (smtp) when configuring Mitel Server Ver.6 (BETA x) when it is set to operate as SERVER ONLY,and nothing has been done about the reported bug.


I am having the same problem and it has become an absolute nightmare to try and find valid information in fixing the problem.

I'm guessing you're talking about the smtpfront proxy, which is enabled by default.  To turn it off, try this:

/sbin/e-smith/db configuration setprop smtpfront-qmail Proxy disabled

followed by:

/sbin/e-smith/signal-event email-update