Scalix Forums

I am seeing some delays while using our Scalix mail server as the outgoing mail server coming over the Internet (not from the same network as Scalix server) and I am wondering if it is DNS or something.

The client is Outlook 2007 using IMAPS for incoming - not using the Outlook Connector

It seems only with files with attachments that the connection takes a long time to complete.

Here is my /etc/hosts file on the server:

# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
10.49.1.40 mail.xxxxxxx.com mail

Should the second line be using the EXTERNAL IP of the server instead of the INTERNAL?

Could it be that Scalix is scanning our "outgoing" attachments with ClamAV?
Even a 5mb file attachment takes about 6 minutes to complete the connection on a home cable connection. I can transfer the file with winscp in less time - under a minute.

Doesn't anyone have any ideas here? The client is quite perturbed that sending mail can take 5 minutes or longer and they perceive the new mail server to be a problem. They are using Scalix as their outgoing mail server via the Internet because they don't have a VPN connection to it, even at their office.

They are using IMAPS for receiving and they have seen this problem on all clients and operating systems.

I will be having them switch to the ISP for sending mail just to compare.

Here is the smtpd.cfg - any ideas? Do I want to move the SMTPFILTER line elsewhere maybe?

###############################################################################
# SMTP Relay Configuration
# #######################

EXTENSIONS=AUTH,DSN,8BITMIME
GREETING=SMTPd
DEBUG_LOG=FALSE

# NB Authenticated RELAYs are always allowed
SMTPFILTER=TRUE
RELAY accept 127.0.0.1
RELAY accept .maindomain.com
AUTH_SUCCESS Accept ALL
AUTH_MISMATCH Log_Reject ALL
RELAY Log_Reject ALL

# extra rules added to prevent open relay usage
RECIPIENT Log_Reject *@*@*
RECIPIENT Log_Reject *%*
RECIPIENT Log_Reject *!*
RECIPIENT Log_Reject *#*@*
[SUBMIT]
CATCH @maindomain.com catchall@maindomain.com
CATCH @olddomain.com catchall@maindomain.com
#LISTEN=localhost:587
# Reject all anonymous connections
ANONYMOUS Log_Reject ALL

# The following group sets the configuration for the lmtp listener
# This listener is only active if LMTP=ON is above
[LMTP]
LISTEN=localhost:24

*looks around the empty room and hears the lone cricket chirp*

Anyone? Hello?
Anyone home?

Hi

A stab in the dark here but what is you OS
What does "top' report the wa (disk wait) to be.
Check when trying to send mail

Sorry this is only a starting point.

Mike

Hi

Try turning off Clamv for outgoing messages.

Mike

mikevl wrote:Hi

Try turning off Clamv for outgoing messages.

Mike

Hi Mike,

Can you tell me easily how to turn off ClamAV for outgoing mail? I will try to find the answer myself but if you or anyone has the "quick" answer I'd appreciate it.

Thanks!

mikevl wrote:Hi

A stab in the dark here but what is you OS
What does "top' report the wa (disk wait) to be.
Check when trying to send mail

Sorry this is only a starting point.

Mike

OS is RHEL 4 and we are using Scalix 11.2 with imaps, ClamAV, SpamAssassin with Razor2 plugin. I have not been able to catch any disk i/o problems. Anyone know a good disk i/o sar-like thing for RHEL? I suppose I could probably find a sar rpm for RHEL also.

Hi

The sar util is part of the sysstat rpm under RHEL4. Its on the CD or up2date install sysstat or yum install sysstat if you have yum

Can you turn off Clam for outgoing messages just to check out if that may be contributing to the issue?

Normally we use gateway spam and virus checking before the c___p gets to the Scalix server so I am not sure if this may be a contributing issue. I do know that Clam and Spam assassin do take a period of time to do their thing.

Mike

Hi

If you have to turn Clam off altogeter just to prove a point that may be worth it.

Mike