🚀 go-pugleaf

"Thomas J. Vosseler" wrote:

> I have a NW 5 server with SP3 installed running on a 400 MHz Pentium II
> with 256 Megs of RAM and mirrored 18 gig hard drives.
>
> Mercury is taking a very long time to transfer mail.  When trying to
> send mail via POP the SMTP connection is never less than 5 seconds, and
> it's usually more like 7-10.  On the Netware 3.12 server that this new
> server replaced, SMTP connections for small messages didn't even last
> one second.
>
> I have tried unloading every non-critical nlm, I changed the switch
> parameters in the different sections of the config file to 0, 1 and 2
> and commented them out.  It appears to be working properly just not as
> quickly as it should be.
>
> I would appreciate any help any could provide.
>

I do have exactly the same problems. I did post the same question and did
not get any answer. Now I am looking for another mail system running on
Netware.

Juergen

-----
Juergen Rosemeyer
FH Hannover Germany
juergen.rosemeyer@rz.fh-hannover.de

I'm running Mercury 1.43 and I don't see any problems, maybe its only with
1.44?


Juergen Rosemeyer wrote:

> "Thomas J. Vosseler" wrote:
>
> > I have a NW 5 server with SP3 installed running on a 400 MHz Pentium II
> > with 256 Megs of RAM and mirrored 18 gig hard drives.
> >
> > Mercury is taking a very long time to transfer mail.  When trying to
> > send mail via POP the SMTP connection is never less than 5 seconds, and
> > it's usually more like 7-10.  On the Netware 3.12 server that this new
> > server replaced, SMTP connections for small messages didn't even last
> > one second.
> >
> > I have tried unloading every non-critical nlm, I changed the switch
> > parameters in the different sections of the config file to 0, 1 and 2
> > and commented them out.  It appears to be working properly just not as
> > quickly as it should be.
> >
> > I would appreciate any help any could provide.
> >
>
> I do have exactly the same problems. I did post the same question and did
> not get any answer. Now I am looking for another mail system running on
> Netware.
>
> Juergen
>
> -----
> Juergen Rosemeyer
> FH Hannover Germany
> juergen.rosemeyer@rz.fh-hannover.de

Ian Dobson (ian@fastnet.bc.ca) wrote:

: I'm running Mercury 1.43 and I don't see any problems, maybe its only with
: 1.44?

: > > I have a NW 5 server with SP3 installed running on a 400 MHz Pentium II
: > > with 256 Megs of RAM and mirrored 18 gig hard drives.
: > >
: > > Mercury is taking a very long time to transfer mail.  When trying to
: > > send mail via POP the SMTP connection is never less than 5 seconds, and
: > > it's usually more like 7-10.  On the Netware 3.12 server that this new
: > > server replaced, SMTP connections for small messages didn't even last
: > > one second.
: >
: > I do have exactly the same problems. I did post the same question and did
: > not get any answer. Now I am looking for another mail system running on
: > Netware.

I am running 1.44, and have had no problems...when you say "Sending mail
via POP", do you mean setting mercury as your SMTP gateway on the client?
We don't do that, so that might be the difference.

-- 
Please send administrative requests to admin@ASL.CA

   Brian P. Hampson                  ASL Analytical Service Laboratories Ltd
   System Administrator,             Vancouver, BC (604)253-4188
      ----------------- http://www.ASL.CA/ ----------------------------  

I'm not speaking for the company <- They made me say that.

Juergen Rosemeyer <juergen.rosemeyer@rz.fh-hannover.de> wrote in message
news:383D1115.8ED2C364@rz.fh-hannover.de...
> Brian Hampson wrote:
> >
> > Ian Dobson (ian@fastnet.bc.ca) wrote:
> >
> > : I'm running Mercury 1.43 and I don't see any problems, maybe its only
with
> > : 1.44?
> >
> > : > > I have a NW 5 server with SP3 installed running on a 400 MHz
Pentium II
> > : > > with 256 Megs of RAM and mirrored 18 gig hard drives.
> > : > >
> > : > > Mercury is taking a very long time to transfer mail.  When trying
to
> > : > > send mail via POP the SMTP connection is never less than 5
seconds, and
> > : > > it's usually more like 7-10.  On the Netware 3.12 server that this
new
> > : > > server replaced, SMTP connections for small messages didn't even
last
> > : > > one second.
> > : >
> > : > I do have exactly the same problems. I did post the same question
and did
> > : > not get any answer. Now I am looking for another mail system running
on
> > : > Netware.
> >
> > I am running 1.44, and have had no problems...when you say "Sending mail
> > via POP", do you mean setting mercury as your SMTP gateway on the
client?
> > We don't do that, so that might be the difference.
>
> yes, using Mercury as an SMTP server is very slow. In the kernel menu of
> the Monitor console I can see, that Mercn__P and MercuryP are often the
> busiest
> threads and for the same time the utilization of the server is very
> high.

This may be due to the recent updates to DS.NLM, which can cause it to hog
service sockets (or something like that).  Anyway, the latest DS.NLM v6.09
(released after NW4SP7A) apparently fixes this problem, but you might want
to read below for another workaround/fix.

> Changing the switch parameter seems not to change anything.
> I am using the NDS version with ldap_synonyms set to 1. Can that be the
> reason?

Yes!  Especially if you have a large NDS tree and/or lots of synonyms
defined.
I recommend you do the following:

1) Continue to maintain the LDAP synonyms for WinPMail so that WinPMail will
correctly define the outgoing From e-mail address from the LDAP synonym for
each user.
2) Configure Mercury to NOT use LDAP synonyms.  e.g. ldap_synonyms: 0
3) For each LDAP synonym you have defined in NDS, create a corresponding
Mercury alias entry that redirects that synonym to the appropriate user.
Compile the Mercury alias source file into an ALIAS.MER file.

This requires double entry (maintaining both LDAP synonyms and Mercury
aliases), but results in much quicker response time by Mercury since it
doesn't have to search the whole NDS tree looking for a matching synonym for
each e-mail address on each mail message that the Mercury core module
processes.

--

  +--------------------------------------------------+
  | David J. Kocmoud (Official Pegasus Mail and Mercury Tech Support Member)
  | ** I can only return your call collect to toll phone numbers **
  | 2403 Colgate Circle, College Station, Texas  77840-4615  USA
  | Voice: (409) 696-8586 (evenings)
  | E-Mail:  david-kocmoud@bigfoot.com
  | Home Page:  http://sago.tamu.edu/users/davek/
  +--------------------------------------------------+