Problems with Mercury NDS and NW 4.1x

Thread View: comp.mail.pegasus-mail.misc

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by F. Ussler Fri, 04 Jul 1997 00:00

#62

Author: F. Ussler
Date: Fri, 04 Jul 1997 00:00

56 lines
1575 bytes

Hello,



we are using Mercury 1.31 under Netware 4.11 in NDS mode and it is

working often ok. 

But we had also often problems (also with Mercury 1.30) in irregular

times.(with interval between days and weeks )



Errors:

- the smtp-Port from Mercury isn't available 

  (--> connection timout ...on unix host)

- sometimes error "user unknown", but the user exist 

- error messages       socket closed unexpectedly

                       socket read timeout or error 



We had already configured BIND IP with GATE-paramter. With same result.

Before we installed this central mail gateway for many domains or OU's

we had no problems when Mercury run locally on different servers.

Did anyone have any problems with NW 4.1x and Mercury 1.3x and can help
me.
Who had some good advices and hints.



Best wishes 



----

Friedhelm Ussler                         

College for Applied Technical, Economic and Social Sciences

Zittau/Goerlitz

Germany

E-Mail: ussler@hrz.htw-zittau.de

Re: Problems with Mercury NDS and NW 4.1x

#63

Author: Tony Locke
Date: Sun, 06 Jul 1997 00:00

33 lines
2050 bytes

"F. Ussler" <ussler@hrz.htw-zittau.de> wrote:
>Hello,
>we are using Mercury 1.31 under Netware 4.11 in NDS mode and it is
>working often ok. 
>But we had also often problems (also with Mercury 1.30) in irregular
>times.(with interval between days and weeks )
>Errors:
>- the smtp-Port from Mercury isn't available 
I've never got these messages. Can you ping your smtp host OK form the
console?

>  (--> connection timout ...on unix host)
>- sometimes error "user unknown", but the user exist 
>- error messages       socket closed unexpectedly socket read timeout or error 
I get socket closed unexpectedly sometimes from  mac clients. From
PC's they seem OK. On the most part it seems to work. I'm getting some
errors delivering mail locally after pegasus has received them from
the world. I'm thinking about putting the bindery version back on it
seems a bit smoother maybe? Connection timeout suggests IP routing
erros according to the mercury FAQ. Stay in touch. Let me know how you
go.

>We had already configured BIND IP with GATE-paramter. With same result.
>Before we installed this central mail gateway for many domains or OU's
>we had no problems when Mercury run locally on different servers.
>Did anyone have any problems with NW 4.1x and Mercury 1.3x and can help
>me.
>Who had some good advices and hints.
>Best wishes 
>Friedhelm Ussler                         
>Germany
>E-Mail: ussler@hrz.htw-zittau.de

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads