I just downloaded and installed JAMES (2.0a3) this week and I'm also noticing slow retrieval times for messages with large attachments (greater than 1MB). For example, retrieving a message with a 12MB attachment took over 15 minutes on a LAN connection. I tried three different POP3 clients and they all downloaded at about the same rate - which would indicate a server-level problem. (Incidentally, when I send the attachment using the same POP3 clients it goes very quickly but I assume that's because it's a different piece of code - the SMTP engine? - that's doing the work.)
I'm using the default configuration with all file system storage - the only thing I did was add a DNS server to the config file. I'm testing this on a somewhat older machine (WinNT 4, 233Mhz processor, 128MB RAM) but I doubt that has anything to do with it. In the past, this same machine/configuration has hosted a Lotus Domino POP3/SMTP server with download times being essentially the same as upload times. In other words, a message with a 5 MB attachment takes only a few seconds (under 15 seconds) to send and receive. Can anyone confirm that this kind of retrieval time is at least "out of the ordinary"? Are there any JAMES users out there who are able to retrieve large messages (say 5MB) in less than a minute? Thanks! Richard Pajerski "James Gooding" <[EMAIL PROTECTED]> 07/05/2002 08:25 AM Please respond to "James Users List" To [EMAIL PROTECTED] cc bcc Subject Message size greater than 15MB System: Dedicated machine. Win2000 Professional SP2 500Mhz 256MB RAM James 2.0a3 Connecting to MSSQL 2000 SP2 for message storage and users/lists, with the latest SQL JDBC driver from Microsoft. Config: No limit on message size Increased SMTP timeout to 24 minutes Problem: 10MB messages take about 12 minutes to process through the system with 100% CPU, with no other activity/messages to process, which is ok. But, I am having a problem with messages over 15MB. At the start of the processing of the message the James goes to 100% CPU for 10 secs, 30% for 15 secs then 100% again for 100 secs. Then drops back to idle. The message then stays in the spool directory and does not get processed. Restarting James still has no affect. I realise that sending messages of this size in general everyday use is not one of the best ways to work, but every now and again there is a need to send a large file by mail. What is the largest message that anyone has processed through James? Has anyone else come across this, and if so is there something I can to can do? Thank you in advance James Gooding
