Greetings thomas, that conf change corrected the problem.

Hi everyone, i'm a mercury user since several time. I just installed squirrelmail and enable the imap protocol, but the performance in the smtp server is veeeery slow, what can i do to improve it?

Thanks a lot

What do you mean?

MercuryS receiving, or MercuryE/C sending out?

Only reason for them to be slow would be interference from the other end. If you have session logging enabled and your disk is extremely full and fragmented, then - but never else any performance bottlenecks.

I also have a problem with what you mean.  When I send via SquirrelMail v1.5.1 I have no problem either with sending from SquirrelMail to MercuryS or with Mercury/32 sending after it has been received.  Here's my settings in the conf.pl

 
General
-------
1.  Domain                 : tstephenson.com
2.  Invert Time            : false
3.  Sendmail or SMTP       : SMTP

SMTP Settings
-------------
4.   SMTP Server           : localhost
5.   SMTP Port             : 25
6.   POP before SMTP       : false
7.   SMTP Authentication   : cram-md5 (with custom username and password)
8.   Secure SMTP (TLS)     : disabled
9.   Header encryption key :

A.  Update IMAP Settings   : localhost:143 (mercury32)
H.  Hide SMTP Settings

R   Return to Main Menu
C   Turn color on
S   Save data
Q   Quit

Command >>

Hi Peter/Thomas:

I use the MercuryS protocol for the internal network, the users have different mail

connections are between 1 to 10 in the MercuryI. In the MercuryS the recurrent connections are between 1 to 15

Thanks in advance.

Roberto N.

Sorry for my english

Now the performance in MercuryS is extremely slow.... how can improve it? the recurrent connections are between 1 to 10 in the MercuryI. In the MercuryS the recurrent connections are between 1 to 15

I do not know what this "extremely slow" means. Is the initial connection slow?  If the time to complete the sending slow.  What does the session log show.  Are you using GreyWall, Clamwall or anything else between the SMTP client and the server?  SquirrelMail connects to MercuryS for sending and it works like any other mail client.  You need though to make sure that you are not doing thing to slow down the process. 

1.   Session logging must be turned off except when debugging.

2.   Check the mail filtering to ensure that you are not using too much body scanning.

3.   Turn off connection control or at least set a limit on the file size.

Hi thomas

"extremely slow"= 3 minutes to complete sending a 1Mb email (imagine a 20Mb).

Here it's a sample of the logging:
------------------
T 20090319 120750 49c12489 Connection from xxx.xxx.x.xx
T 20090319 120751 49c12489 EHLO [xxx.xxx.x.xxx]
T 20090319 120751 49c12489 MAIL FROM:<sistemas@xxxxx.xxx.xx> SIZE=1026100
T 20090319 120751 49c12489 RCPT TO:<xxx@xxxxx.com>
T 20090319 120751 49c12489 DATA
T 20090319 121048 49c12489 DATA - 14332 lines, 1026016 bytes.
T 20090319 121048 49c12489 QUIT
T 20090319 121048 49c12489 Connection closed with xxx.xxx.x.xx, 178 sec. elapsed.
------------------
GreyWall and clamwall ins't installed. Squirrel connected like any other smtp mail client.

The next options is the same from a couple of years

1.- I have the MercuryS session logging enabled
2.- The mail filtering is: file with executable extensions (12 exceptions), multimedia
  extensions (5 exceptions), larger than 9999999 bytes (10Mb).
3.- Connection control is enabled "Only from local lan an localhost".

"extremely slow"= 3 minutes to complete sending a 1Mb email (imagine a 20Mb).

Depending on the connection and the relay host this can be reasonable.I'd need to see a session log to determine where and what is causing the time delay with a fast link.  Could be taking a long time to connect, the host might be very busy and or there could be some sort of TCP/IP level problem causing a lot of retries.  If there are a ton of session logs then this can also be a problem since they will be reused starting from 1 and writing to huge files can really slow things down. 

The next options is the same from a couple of years

1.- I have the MercuryS session logging enabled

Turn it off.  Session logging can be causing the problem especially when the disk is getting fragmented or the files are getting large.  It is only supposed to be turned on when yuo are debugging.

2.- The mail filtering is: file with executable extensions (12 exceptions), multimedia
  extensions (5 exceptions), larger than 9999999 bytes (10Mb).

That's not the problem since the problem is with the actual sending.  All the other stuff you brought out about SquirrelMail are red herrings.

3.- Connection control is enabled "Only from local lan an localhost". 

Again, not the problem.

[quote user="rno22"]T 20090319 120751 49c12489 DATA
T 20090319 121048 49c12489 DATA - 14332 lines, 1026016 bytes.
[/quote]

If you have squirrelmail and Mercury on the same net, connected via even 2Mbit Tbase2 cards it shouldn't be this slow. Try to wireshark the connection traffic for a single transmission. I suspect you have something odd going on in your webmail or internal network. You've transmitted 1026016 bytes in 177 seconds, that's only 45kilobit per second. You must have some form of out of synch problem in either end - maybe an antiviral package between the web-app and the core tcp stack?

THANKS thomas, disabling session log did the trick.

Another question, i have 2 installed mercury, 1 for the production and 1 for test. The production is an old installation updated with every new version. In the test installation i do a fresh install, here i can manage longname for the user (and the directory name for the mailbox.) But in the production installation this doesn't work, what can change it in the configuration for this to work?

Again thnak you so much.

Thanks peter for your time, all back to normality after disable session log. Just as note the squirrel and mercury is in the same machine, even sending mail from the same machine are slow. But now everythig is ok.

Thanks.

Another question, i have 2 installed mercury, 1 for the production and

1 for test. The production is an old installation updated with every

new version. In the test installation i do a fresh install, here i can

manage longname for the user (and the directory name for the mailbox.)

But in the production installation this doesn't work, what can change

it in the configuration for this to work?