Jump to content
We've recently updated our Privacy Statement, available here ×

dane_xa

Members
  • Posts

    5
  • Joined

  • Last visited

dane_xa's Achievements

Newbie

Newbie (1/14)

  • Week One Done
  • One Month Later
  • One Year In
  • First Post Rare
  • Conversation Starter Rare

Recent Badges

0

Reputation

  1. I think I've found root cause, and it strikes me as a bug. DEFAULT_EMAIL_PATTERN in DefaultReportJobValidator.java wrongly excludes lots of characters that are valid email address characters. public static final String DEFAULT_EMAIL_PATTERN = "^[^\\~\\`\\(\\)\\[\\]\\{\\}\\:\"\\;\'/\\?\\<\\>\\+\\=\\\\|\\!\\@\\#\\$\\%\\^\\&\\*]+@([\\w+\\-]+\\.)+(\\w+)"; Of course, the authority on this matter is likely one or more RFCs, which I must dig up, but here's a summary from Wikipedia: http://en.wikipedia.org/wiki/E-mail_address#Local_part Looks like I need to patch the source and do a custom build. And perhaps file a bug? Dane
  2. I've been digging into the source. "Invalid email address" comes from DefaultReportJobValidator.java, and it looks like DEFAULT_EMAIL_PATTERN is hard-coded here. The source I'm looking at is: http://jasperforge.org/svn/repos/jasperserver/branches/js-4.5.x And the build I'm running in production is: Product Version: 4.5.0 Build: 20120110_1602 Are these the same version? One other detail... I see the following in catalina.out: WARN ValidatorImpl,http-8080-1:518 - Please make sure your web application server is set to URIEncoding=UTF-8. Perhaps this is an encoding issue, not a validation issue. However, I have URIEncoding="UTF-8" set for my connectors in /etc/tomcat6/server.xml: <Connector port="8080" protocol="HTTP/1.1" maxHttpHeaderSize="8192" maxThreads="150" enableLookups="false" redirectPort="8443" acceptCount="100" URIEncoding="UTF-8" connectionTimeout="20000" disableUploadTimeout="true" />
  3. Still no luck changing the email validation rules. It seems there's another validation mechanism, since I've disabled security.validation.input.on. I'd love to learn more about how email validation works in the code. Any kind souls able to point me in the right direction?
  4. Thanks for the suggestion. I created the schedule without the '+', which worked. Then I edited the schedule and changed the email address to yan+7@mydomain.com. But I got the same validation error as before. So no luck with that workaround. Note that I'm running with security validation disabled in esapi/security-config.properties, so there must be something else causing this error. Dane
  5. Hi Fellow Jasperreports Server Users, I'm having problems with email notification for the report scheduler when the To: email address contains the '+' character. For example, when I enter yan+7@mydomain.com and click submit, the following appears in red below the form field: Invalid email address yan+7@mydomain.com (screenshot attached). Also, the same error occurs using the SOAP API. While testing I'm running with validation disabled. From esapi/security-config.properties ... security.validation.input.on=false security.validation.csrf.on=false security.validation.sql.on=false I've also tried changing regexs (e.g. Validator.Email) in esapi/validation.properties as suggested in this thread: http://community.jaspersoft.com/questions/541525/error-when-entering-more-one-email-recipient-schedule Any ideas how I can make these email addresses work? Dane
×
×
  • Create New...