Some time in the semi-recent past we started to receive a few reports of users sending attachments in an email message to Person A, then having an empty copy of that attachment get connected to a separate message they are trying to send to Person B. In other words: 1. Compose message to Person A 2. Attach File1 to message for Person A 3. Send message with attachment to Person A 4. Do some stuff 5. Compose message to Person B 6. Notice that File1 is attached to message to Person B with 0 size and usually an error saying File1 can not be stat'ed. (7. Some people don't notice the error (or ignore it) and send anyway, in which case the sent message has a zero size attachment with the file name) This is the error: filesize() [function.filesize]: stat failed for /path/to/squirrelmail_attachments/ShCp9jtLfH6mAd9BPTTuMSVsWRsP9a19 in /path/to/squirrelmail-1.4.8/src/compose.php on line 1225 The good news is that this appears to be more of an annoyance then a problem because in our testing it appears the original attachment always gets sent properly and at worst Person B gets the name of the attached file. We have been able to reproduce the error with some amount of consistency if we use a fully qualified address for the To: (for some reason I've been unable to reproduce it with just a username that ends up getting the domain appended to it by SM) and /only/ if I click the compose link while the send function is still finishing or at the exact instance that the inbox list returns. In other words Step 3-6 from above become: 3. Click send button 4. Quickly click Compose link to start a new message 5. Notice error message Initially we just told users to be patient, but we've had a few reports of people saying it happens occasionally even if they let everything fulling finish loading. We have been unable to reproduce this though. >From what I can gather it seems that the attachment name and location on the file system sets saved to the session cookie or something and doesn't get cleared until the send is fully completed, which makes good sense to me. We do have users using a wide variety of OS's, browsers and maybe most importantly Internet connections. I'm sure something changed since this started, but it is hard to say what because over this time we have upgraded Apache, PHP and Squirrelmail. We are currently using the following software: FreeBSD 4.11 Apache 2.2.3 PHP 5.1.5 SquirrelMail 1.4.8 Out plugins are: $plugins[0] = 'frii_mods'; $plugins[1] = 'squirrelspell'; $plugins[2] = 'auto_prune_sent'; $plugins[3] = 'address_add'; $plugins[4] = 'delete_move_next'; The frii_mods one is a home brew that just adds @frii.com to the end of the authenticating username if a domain is not supplied. The rest are vanilla. As I mentioned this is more of an annoyance than a real problem, but I was wondering if anyone else had seen anything similar and had any suggestions on how to mitigate it. We're considering adding a custom warning message to the compose screen telling users to be patient and not click anything until the inbox refreshes, but we'd like to avoid modifying the SM source to add a message like that if we don't need to. Thanks for you time. Any feedback would be appreciated. Matt Ruzicka - Senior Systems Administrator Front Range Internet, Inc. matt@xxxxxxxx - (970) 212-0728 ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV -- squirrelmail-users mailing list Posting Guidelines: http://www.squirrelmail.org/wiki/MailingListPostingGuidelines List Address: squirrelmail-users@xxxxxxxxxxxxxxxxxxxxx List Archives: http://news.gmane.org/thread.php?group=gmane.mail.squirrelmail.user List Archives: http://sourceforge.net/mailarchive/forum.php?forum_id=2995 List Info: https://lists.sourceforge.net/lists/listinfo/squirrelmail-users