Enhancement #2673
Permit special character into pseudonym
Status: | CLOSED | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 100% | |
Category: | nethserver-mail-server | |||
Target version: | ~FUTURE | |||
Resolution: | REJECTED | NEEDINFO: | No |
Description
Use of special character like "&" are prohibited into the field Email address -> "Email address"
It should be allowed as report by wikipedia and RFC 5322:
http://en.wikipedia.org/wiki/E-mail_address#Local_part
Related issues
History
#1 Updated by Davide Principi over 7 years ago
- NEEDINFO changed from No to Yes
Yes, the validator is more restrictive than what is defined a valid local mail address part in RFCs. Is this a big limitation? Why do you think it's important being more compliant with RFC here?
#2 Updated by Alessio Fattorini over 7 years ago
- NEEDINFO changed from Yes to No
#3 Updated by Alessio Fattorini over 7 years ago
It's a request by some people for a greater versatility of this field.
#4 Updated by Giacomo Sanchietti over 7 years ago
- Status changed from NEW to TRIAGED
- % Done changed from 0 to 20
Even if the RFC allows special characters, it is common use to limit them to letters, numbers and a small set of symbols (like, "." or "_").
For example, see Google guidelines:
https://support.google.com/a/answer/33386?hl=en
Use of special characters always lead to problems with systems which doesn't correctly handle it, like forms on registration web pages.
The interface should allow creation of simple pseudonyms, special ones can be obtained with custom template.
I suggest to close the issue as REJECTED.
#5 Updated by Alessio Fattorini over 7 years ago
I think you're losing my point of view, you should think about a bit :-)
If i'm migrating my mailserver from an existing one that permits this type of email addresses (like MS exchange) i can't recreate those addresses.
This limit can block the migration because clearly i can't change addresses already publicly known.
Is it more articulate now?
#6 Updated by Giacomo Sanchietti over 7 years ago
Now it makes sense, but it still remain a corner case: use of special characters is discouraged.
As a workaround , you can create a template custom with the special pseudonym.
Eg:
mkdir /etc/e-smith/templates-custom/etc/postfix/virtual echo 'b&b@nethesis.it giacomo' > /etc/e-smith/templates-custom/etc/postfix/virtual/70custom signal-event pseudonym-modify
Be careful to use single quotes, as & is a reserved character in bash.
This template will deliver to user giacomo all mail sent to _b&b@nethesis.it _ pseudonym.
#7 Updated by Davide Principi over 7 years ago
- Target version set to ~FUTURE
#8 Updated by Davide Principi almost 5 years ago
- Related to Enhancement #3209: email validation function evalEmail() added
#9 Updated by Davide Principi almost 5 years ago
- Status changed from TRIAGED to CLOSED
- % Done changed from 20 to 100
- Resolution set to REJECTED
See also #3209. This has been implemented on ns7.