JotForm allows, but then does not send email to, addresses with special characters

  • Profile Image
    asdf84
    Asked on July 01, 2010 at 01:09 PM
    Hi,When setting up email notifications I noticed that JotForm will allow me to set as recipient an email address containing special characters (e.g. +), but the silently fails to send emails to those addreses.

    From RFC 3696 (http://tools.ietf.org/html/rfc3696), which describes "Restrictions on email addresses":

    Without quotes, local-parts [of email addresses] may consist of any combination of alphabetic characters, digits, or any of the special characters
    ! # $ % & ' * + - / = ? ^ _ ` . { | } ~
    period (".") may also appear, but may not be used to start or end the local part, nor may two or more consecutive periods appear. Stated differently, any ASCII graphic (printing) character other than the at-sign ("@"), backslash, double quote, comma, or square brackets may appear without quoting.

    Gmail (and Google Apps) has a cool feature where all mail addressed to your account followed by a plus sign (+) and any string following will be sent to your account (http://gmailblog.blogspot.com/2008/03/2-hidden-ways-to-get-more-from-your.html). Thus if my Gmail account were example@gmail.com I will also receive mail sent to example+form1@gmail.com, example+form2@gmail.com, etc, allowing me to easily create filters and rules for handling responses for my various forms.

    Unfortunately, although JotForm will allow me to enter emails such as example+form1@gmail.com as an email notification recipients address, it will silently fail to actually send any notifications to addresses containing plus (+) signs.

    Would it be a quick fix to enable notifications to email addresses containing allowed special characters? If not, the user should at least be informed that email addresses with special characters are not currently recognized as valid by JotForm.
  • Profile Image
    aytekin
    Answered on July 05, 2010 at 10:33 AM
    Thanks for letting us know. I added this to our bug list and we will work on it as soon as possible.