Opened 5 years ago

Closed 4 years ago

#1485328 closed Bugs (worksforme)

Unable to forward

Reported by: brucealdridge Owned by:
Priority: 5 Milestone: 0.3-stable
Component: PHP backend Version: 0.2.1
Severity: normal Keywords:
Cc:

Description

Problem with
0.1-rc1
upgraded to 0.1-stable ... then 0.2-alpha

No luck with any.
Everything else seems to work fine. (Send, Reply etc)
Forwarding an email system just hangs.

using firebug ... it seems that a request is posted to /email/ (my roundcube folder) which returns a 404(!!??!)

No applicable errors are shown in either the /logs/ or in /error_log (php logging)

Change History (10)

comment:1 Changed 5 years ago by thomasb

  • Resolution set to worksforme
  • Status changed from new to closed

Works for me. Please test with the latest SVN trunk version.

comment:2 follow-up: Changed 4 years ago by hradek

  • Resolution worksforme deleted
  • Status changed from closed to reopened
  • Version changed from 0.2-alpha to 0.2.1

Same problem on 0.2.1. Nothing shows up in Firebug. It just hangs when trying to send a forward message.

It may be a PHP setting which is wrong that may be causing this which is why it's working for some and not for others. If this is the case, we should find out what setting is causing this to not work on some clients and add it to the list of things the installer checks.

comment:3 in reply to: ↑ 2 Changed 4 years ago by hradek

Replying to hradek:

Same problem on 0.2.1. Nothing shows up in Firebug. It just hangs when trying to send a forward message.

It may be a PHP setting which is wrong that may be causing this which is why it's working for some and not for others. If this is the case, we should find out what setting is causing this to not work on some clients and add it to the list of things the installer checks.

I've been watching my error logs on my server. Here is a line that shows up when I try to forward:

[Mon May 18 15:37:26 2009] [error] [client 63.126.183.110] File does not exist: /home/mydomain/public_html/mail/403.shtml, referer: http://mail.mydomain.org/?_task=mail&_id=15197751694a11b8edd33be&_action=compose

This confirms the original poster's comment about the app generating a 403 which causes it to fail on forwards.

comment:4 Changed 4 years ago by alec

  • Milestone changed from later to 0.3-stable

comment:5 follow-up: Changed 4 years ago by hradek

We've tracked down the issue causing this anomoly. It appears that mod_security was affecting my installation of Roundcube and blocking CC and BCC lines. I had my ISP disable mod_security for the mail/ directory on my account and it seems to have resolved the issue.

This issue was present in 0.2.1 and 0.2.2

comment:6 in reply to: ↑ 5 Changed 4 years ago by hradek

I wanted to note that this should be changed from a Bug to a Feature Request. It's not a problem with Roundcube itself but rather a problem with the environment. I'd check to see if mod_security was enabled, warn the user, and then see about a work around/fix for the issue.

I think it's probably rare that this issue comes up but I think with a lot of hosting companies running the show they likely have mod_security enabled so this needs to be addressed.

comment:7 Changed 4 years ago by thomasb

I assume that you use PHPs mail() function. Configure an SMTP server and make RoundCube send mails directly using that and mod_security should not block outgoing mails. Or did I miss something?

comment:8 Changed 4 years ago by alec

As I understand, it's not related to mail/smtp. It's about sent http request. This is probably by using modsecurity-experimental.conf rule. I'm not sure, not use mod_security. I don't know also if mod_security problem is the same as original requestor problem. Shouldn't mod_security write something to error log?

comment:9 Changed 4 years ago by brucealdridge

apache doesn't report mod_security as being installed on mine, but can that be trusted (also it could have been removed).

from what i've quickly read, it seems like mod_security can be setup to strip anything with 'CC:' or 'BCC:' which could be triggered from the body of email thats being forwarded.

The only obvious workaround for me would be a search and replace 'CC:' with 'CC-' or similar (in html you could just do a'C<b></b>C:' but it seems like a pain to go to this effort for such a small problem.

comment:10 Changed 4 years ago by alec

  • Resolution set to worksforme
  • Status changed from reopened to closed

No feedback, try again with svn-trunk version.

Note: See TracTickets for help on using tickets.