You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Our company has a colon in its name. Sending from HE:tech <tech@example.com> does not create any problems. But when I try to test it with expect(mail).to deliver_from("HE:tech <tech@example.com>") I receive following error:
Failure/Error: it { expect(mail).to deliver_from("HE:tech <tech@example.com>") }
Mail::Field::ParseError:
Mail::AddressListsParser can not parse |HE:tech <tech@example.com>|
Reason was: Expected one of
, (, ,, ; at line 1, column 29 (byte 29) after :tech <tech@example.com>
The text was updated successfully, but these errors were encountered:
@aliismayilov It isn't an issue. I took a look and it's raised by mail gem. Mail gem implementation follows a RFC. So, I put below the reason of not accept colon on any email header body.
2.2. Header Fields
Header fields are lines composed of a field name, followed by a colon
(":"), followed by a field body, and terminated by CRLF. A field
name MUST be composed of printable US-ASCII characters (i.e.,
characters that have values between 33 and 126, inclusive), except
colon. A field body may be composed of any US-ASCII characters,
except for CR and LF. However, a field body may contain CRLF when
used in header "folding" and "unfolding" as described in section
2.2.3. All field bodies MUST conform to the syntax described in
sections 3 and 4 of this standard.
Our company has a colon in its name. Sending from
HE:tech <tech@example.com>
does not create any problems. But when I try to test it withexpect(mail).to deliver_from("HE:tech <tech@example.com>")
I receive following error:The text was updated successfully, but these errors were encountered: