Topic: Spamassassin / ClamAV slow email delivery

[pisaacs]

G'day,

I have installed SpamAssassin and ClamAV onto SME 6.01 from Swerts-Knudsen.dk

Since then, the last email sent to a local user seems to have an extremely long delivery time.

Sending another email to the same local user results in the previous one being delivered, but the new last one does not get delivered.

This is absolutely screwing up our companies mail server operation, and I am not familiar enough to fix it.

I have done everything I have read about, such as ensureing procmail is enabled for each of the users, but thats my limit.

Any suggestions would be greatly appreciated,

regards

Paul

[CharlieBrady]

Since then, the last sent email seems to a local user seems to have an extremely long delivery time.

Can you explain what you mean by "seems to have an extremely long delivery time"? What are you actually seeing?

Sending another email to the same local user results in the previous one being delivered, but the new last one dissapears.

Disappears? From where? What are you actually seeing?

[pisaacs]

Can you explain what you mean by "seems to have an extremely long delivery time"? What are you actually seeing?

Disappears? From where? What are you actually seeing?

Hi Charlie,
Sorry, it was a hurridly constructed email over dial up...

1. I send MESSAGE1 to pisaacs@millison.com.au.
2. MESSAGE1 does not show up immediatly on my IMP Inbox (It may after some long time, but I cant be sure of that).
3. I wait 10 minutes and send MESSAGE2 to pisaacs@millison.com.au.
4. MESSAGE1 will now show up in my IMP inbox, but MESSAGE2 does not.

The sending of MESSAGE2 seems to reliably cause the preceeding MESSAGE1 to be processed and delivered to my Inbox.

A MESSAGE3 would cause the preceeding MESSAGE2 to show etc.etc.

I hope this explains it.

I dont really know if MESSAGE1 would eventually get processed as the email server is busy enough that a subsequent email would turn up in a few hours at most, causing MESSAGE1 to appear in the IMP inbox.

regards

Paul.

p.s. Outlook Clients behave the same as IMP.
It may not be related, but about the same time our Outlook clinets started complaining of IMAP errors with the emails UID.

A typical Outlook error is shown below:

The UID of this message changed unexpectedly. This typically indicates a server bug. Your program may not function properly after this.

MsgSeqNum 7677: Previous UID: 64147, New UID: 64142.
   Account:   192.168.0.1
   Protocol:   IMAP
   Server:   192.168.0.1
   Port:   143

Followed by a 2nd Outlook Error message:

Your server has reported a UID which does not comply with the IMAP standard. This typically indicates a server bug. Your program may not function properly after this.

MsgSeqNum 7676, New UID 64110. Prev UID: 64110, Next UID: 64142.
   Account:   192.168.0.1
   Protocol:   IMAP
   Server:   192.168.0.1
   Port:   143