Opened 4 years ago
Closed 4 years ago
#1485659 closed Bugs (duplicate)
An internal error occured while sending mails.
| Reported by: | tux1337 | Owned by: | |
|---|---|---|---|
| Priority: | 1 - Highest | Milestone: | 0.2.2 |
| Component: | Core functionality | Version: | git-master |
| Severity: | major | Keywords: | internal, error, sending, mail, compose |
| Cc: |
Description
I got the error
An internal error occured. Please try again.
when I press the "send" button in the compose window.
Roundcube sends mails with smtp but the error also occures when php mail() is used.
I can't reproduce it. Sometimes it works, sometimes not. Most time works the first mail, if I try to compose the second mail, the error occures.
Attachments (1)
Change History (14)
comment:1 Changed 4 years ago by tux1337
comment:2 Changed 4 years ago by robin
Bug confirmed. I have two seperate environments, and one of them does this too. But only when replying to a message that has been double-clicked, not when doing a reply directly from the main window.
comment:3 in reply to: ↑ description Changed 4 years ago by l33tmyst
Same for me. It seems it might only be when Rouncube is open in multiple tabs?
Replying to tux1337:
I got the error
An internal error occured. Please try again.
when I press the "send" button in the compose window.
Roundcube sends mails with smtp but the error also occures when php mail() is used.
I can't reproduce it. Sometimes it works, sometimes not. Most time works the first mail, if I try to compose the second mail, the error occures.
comment:4 Changed 4 years ago by saevar
has the same problem...
main problem with this bug is that i cannot find error in any logfile, even if i have all in debug mode (roundcube,apache,mailserver).
Sometimes get from roundcube onscreen message> "An internal error occured. Please try again." and sometimes operation only timeouts...and as i said nothing in logs...
comment:5 Changed 4 years ago by tux1337
Maybe it is a problem with free memory. But I can't say this seriously.
Since my Server got more "free" memory, sending mails works fine.
@the other users with this issue
How much free memory has your server? Is your server swapping?
comment:6 Changed 4 years ago by saevar
server has 1200M ram free, swap untouched, problem still in progress....
comment:7 Changed 4 years ago by tux1337
- Priority changed from 2 to 1 - Highest
- Version changed from 0.2-stable to 0.2.1
error occures also on new version (0.2.1)....
Could someone please fix this bug? This bug makes roundcube worthless.
comment:8 Changed 4 years ago by robin
It seems that some part of the session is lost in the process of doing a reply. But I cannot reproduce the error anymore (r2371/svn).
comment:9 Changed 4 years ago by saevar
we have this error still actual, but as i've been written before, no errors in any log , although we have in all logs LogLevel? debug.
Can any developer PLEASE fix this bug ? it's making roundcube quite unusable for our clients.
comment:10 Changed 4 years ago by tux1337
- Version changed from 0.2.1 to svn-trunk
@robin
Tested with actual svn-trunk (Revision 2387). Bug is still alive. Reply do not work.
Changed 4 years ago by robin
comment:11 Changed 4 years ago by robin
Please test attached patch (#1485659.20090417.patch),
comment:12 Changed 4 years ago by tux1337
I tested the patch with revision you written for. It do not work for me. I got a white page, (means there are php errors, because I disables show errors in php.ini). I haven't got more time to debug it. I don't know if the error is at my environement or on the code... .
I will test it on another server these days, when I've got more time... Sorry for the moment.
comment:13 Changed 4 years ago by robin
- Resolution set to duplicate
- Status changed from new to closed
This turned out to be a duplicate of #1484678.

Now I tested some szenarios.
If the error occures, in the errors log is this entry:
It occures with the second mail in one session. If I logoff and logon with the same tab the error occures with the first mail. If I close the tab and use an new one, it occures with second mail.
The error occures with Opera and Firefox.