Lack of help in forums - I really need help - nobody home?

[Ruthiness]

Hi

It seems that these issues may be related to the SMTPD issue.

Is it possible to disable (coment out) the Clamv entries for testing?

Then only one of two outcomes. It goes faster or not.

Mike

Hi Mike,

Do you think the "sending authentication info" that takes as long as the initial attachment to upload is related to ClamAV?

[mikevl]

Hi

I am not sure.

I have used Thunderbird before directly connect to the Internet and ovserved the sort of behariour you are talking about. Send Authentication > send address list > send mail includng attachments.

There are other things this could be such as
Disk I/O issues > do top and observer wa and id (disk I/O and CPU idle)
Other DNS issues I am not on your server so I cann not race through and check these things out rapidly to find what the issue may be. So I need to go more slowly.

Mike

[Ruthiness]

I don't believe this has anything to do with DNS at this point.

I took the same size file and sent it several ways.

Whenever I sent it THROUGH the Scalix SMTP server, on both Windows 2003 Server and Vista, it went through a second cycle that takes as long as sending the original file.

It does NOT do this through another SMTP server with the SAME client on either of the operating systems.

It is only through Scalix that I get a second round of sending the attachment. It takes TWICE AS LONG to send a 5mb file BECAUSE of this second round which displays the dialog "sending authentication login information". It should not need to do this.

This is why users are perceiving the new Scalix server to be slow. I would like to see in my Thunderbird client, the SAME behavior that I get with my other SMTP server, which DOES use AUTH because it is NOT my ISP SMTP server.

[Ruthiness]

Nobody has any ideas? We still have this problem...

We want to upgrade to 11.3 but would rather get the config corrected before that.

[kanderson]

This WILL BE a Postgres issue.

The slow speed you are seeing is due to SWA trying to connectot Postgres, and waiting until that times out before dropping back to the older connection style.

As a quick fix, set swa.platform.enabled=false in swa.properties.

That will end the user complaints while you figure out what's up with Postgres.

Kev.