Summary | DIMP random attachment bug |
Queue | DIMP |
Queue Version | 1.1.2 |
Type | Bug |
State | Not A Bug |
Priority | 1. Low |
Owners | slusarz (at) horde (dot) org |
Requester | *****.** (at) |
Created | 08/17/2009 (5756 days ago) |
Due | |
Updated | 08/21/2009 (5752 days ago) |
Assigned | 08/19/2009 (5754 days ago) |
Resolved | 08/20/2009 (5753 days ago) |
Milestone | |
Patch | No |
New Attachment: dimp-test.jpg
After composing messages and before sending them, I can see 10
attachements in the database => before section in dimp-test.jpg
After sending all messages, I can see 9 attachements in the database
=> after section in dimp-test.jpg
In my inbox, I receive only 1 message with 1 attachemnt. Other
messages are empty ... => inbox section in dimp-test.jpg
New Attachment: dimp-bug[1].jpeg
NFS volumes.
But, since your last message, I actived the VFS option in the IMP
config file :
$conf['compose']['use_vfs'] = true;
After check database, all attachements are stored in the horde_vfs table.
But I have the same issue. I compose 5 messages with 2 attachements at
same time, I receive :
2 messages without attachements
1 message with only one attachement
2 messages with 2 attachements
PS : cf. dimp-bug.jpeg
State ⇒ Not A Bug
Can you tell me how I can change this option ?
is accessible to all backend servers (such as VFS or NFS). This is
not a support forum. Please see: http://www.horde.org/support.php
what happens when a user switches servers in the middle of composing.
You can't use simple file-based attachment storage if using multiple
servers (VFS or NFS is needed).
Can you tell me how I can change this option ?
State ⇒ Feedback
Priority ⇒ 1. Low
what happens when a user switches servers in the middle of composing.
You can't use simple file-based attachment storage if using multiple
servers (VFS or NFS is needed).
Version ⇒ 1.1.2
Summary ⇒ DIMP random attachment bug
State ⇒ Assigned
Patch ⇒ No
State ⇒ Unconfirmed
New Attachment: dimp-bug.jpeg
Milestone ⇒
Queue ⇒ Horde Groupware Webmail Edition
Summary ⇒ Dimp Random Attachement Bug
Type ⇒ Bug
Priority ⇒ 3. High
University and since 2 mounth we are in production (approximately 3000
users per day). Some users reported us an issue with Dimp interface
and attachements. The problem reported is random, sometimes
attachments work, sometimes not.
Every time, the message is send with attachments, but at the
reception, they have disappeared. This bug doesn't exist with Imp
interface.
After trying to reproduct the issue (it's very hard, because it's a
random issue), I have finaly found a method, but I think that this is
not the only one :
1/ open horde-webmail with Dimp interface
2/ compose a new message
3/ add an attachement
On our server, we can see the attachement :
# ls -lgrt impatt*
-rw------- 1 apache 224256 Aug 17 11:34 impattLCCVy8
4/ Wait one minute :
# date
Mon Aug 17 11:34:52 CEST 2009
# date
Mon Aug 17 11:35:55 CEST 2009
5/ open a new compose message box
6/ switch to the first compose message box
7/ add a second attachement
On our server, we can see all attachements :
# ls -lgrt impatt*
-rw------- 1 apache 224256 Aug 17 11:34 impattLCCVy8
-rw------- 1 apache 224768 Aug 17 11:35 impattW8pzfe
8/ send the message
In our inbox, the message is recieve whitout attachements. And on the
server, the impatt* files are not deleted.
Additionnal informations :
horde-webmail version : 1.2.3
dimp version : 1.1.2
Sessions are stocked in a mysql database :
# Sessions
$conf['session']['name'] = 'Horde';
$conf['session']['cache_limiter'] = 'nocache';
$conf['session']['timeout'] = 0;
# Session en base de donnee
$conf['sessionhandler']['type'] = 'mysql';
$conf['sessionhandler']['params']['persistent'] = false;
$conf['sessionhandler']['params']['rowlocking'] = true;
$conf['sessionhandler']['params']['port'] = 3307;
$conf['sessionhandler']['params']['protocol'] = 'tcp';
$conf['sessionhandler']['params']['hostspec'] = '****';
$conf['sessionhandler']['params']['username'] = '****';
$conf['sessionhandler']['params']['password'] = '****';
$conf['sessionhandler']['params']['database'] = '****';
If we share all sessions with an NFS mounting, the issue is the same.
PS : Additionnal informations in the dimp-bug.jpeg