Koozali.org: home of the SME Server

masq error

dave

masq error
« on: July 20, 2003, 03:26:03 AM »
Hello all...

I recently installed the denyport contrib and as the RPM installation was completing, I got the following error.

Enabling IP masquerading: /etc/init.d/masq: Program: command not found
/etc/init.d/masq: esmith::__TEMPLATE__::1::allow_tcp_in: command not found
done

I did some looking and found the masq file - I took a chance and listed it's contents (I didn't know if it was binary or not) and found the following line:

Program fragment delivered error Undefined subroutine &esmith::__TEMPLATE__::1::allow_tcp_in called at /etc/e-smith/templates//etc/rc.d/init.d/masq/45AllowSMTP line 5.''

I looked in the 45AllowSMTP template fragment and saw nothing immediately wrong - no file corruption or anything.

I tried the expand-template masq routine and it completed showing no errors.  I listed masq contents again and see the same message.

In an apparently related problem, a couple months ago, I found I wasn't able to get any external email and found the port opening contrib to open port 25 - the port 'allow_tcp_in' references.

My guess is, I have installed something that has screwed up this allow_tcp_in function somewhere.  Does anyone have any ideas?

Any help is appreciated,
Dave

dave

Re: masq error
« Reply #1 on: July 22, 2003, 02:08:13 AM »
A quick pass at the developers email list found that this is a known error related to

e-smith-mailfront-0.3.7-01.noarch.rpm

which is apparently an alpha version.  I'm not certain this is one of the modules I've installed but there are code snippets that look like it's the source of the problem.

Charlie Brady

Re: masq error
« Reply #2 on: July 22, 2003, 02:42:07 AM »
dave wrote:

> A quick pass at the developers email list found that this is
> a known error related to
>
> e-smith-mailfront-0.3.7-01.noarch.rpm
>
> which is apparently an alpha version.  I'm not certain this
> is one of the modules I've installed but there are code
> snippets that look like it's the source of the problem.

Upgrading to 5.6 plus updates would be a good idea. Or, if you'd like to help with the development process, install 6.0beta and report any problems you find to smebugs@mitel.com.

Charlie