an email header field may contain encoded unicode - in commends how ever, if an email header field is used - it has to contain a valid email address - unicode is not allowed to be used in email addresses
valid examples: reply-to: "any encoded unicode" < valid@email.address> reply-to: < valid@email.address> invalid example: reply-to: "any encoded unicode" Thomas Von: "K Post" <nntp.p...@gmail.com> An: "ASSP development mailing list" <assp-test@lists.sourceforge.net> Datum: 31.01.2020 17:30 Betreff: Re: [Assp-test] Missing MX, A, and FROM for specific sender. Unicode problem? I knew that unicode it was common in the subject, but not from/reply-to. Apparently it's legal in for all headers. https://tools.ietf.org/html/rfc1342 And according to the ever questionable wikipedia, https://en.wikipedia.org/wiki/Unicode_and_email : RFC 2047 provides support for encoding non-ASCII values such as real names and subject lines in email header[5] RFC 6532 allows the use of UTF-8 in a mail header section [7] My gut says that FROM/Reply-To (I don't know about the envelope itself) would need to be checked to see if they're unicode and converted prior to having the email address extracted from those lines and run through checks like MX and A, etc. What do we all think? I don't know if ASSP is already handling unicode in FROM and Reply-To and something's wrong with the formatting in my sample header above, or if ASSP doesn't accept UTF-8 encoded FROM/Reply-To. If it's the later, do you think we should ask Thomas to look into it? On Fri, Jan 31, 2020 at 10:51 AM Robert K Coffman Jr. -Info From Data Corp. <bcoff...@infofromdata.com> wrote: Ken, I can confirm I am seeing this also. I haven't had any complaints (I vaguely recollect way way back in ASSP time I might have had an issue with Survey Monkey) so I have taken no action on it. - Bob On 1/31/2020 10:26 AM, K Post wrote: > Interesting idea Doug. Do any of your users happen to get any > SurveyMonkey notifications? These are sent to the owners of surveys. > I'm curious if you're seeing the same malformed info in the headers. > Thanks > ken > > > On Thu, Jan 30, 2020 at 12:56 PM Doug Lytle <supp...@drdos.info > <mailto:supp...@drdos.info>> wrote: > > This is not a necessarily resolution, but possibly a workaround for you. > > In a past life, I've had some mail servers that just caused more > issues then they were worth, so I ended up identifying their mail > server(S) range of IP Addresses and placed those in an alias on the > firewall and did a NAT directly to the mail server instead of ASSP > If they were destined for port 25. > > Doug > > > _______________________________________________ > Assp-test mailing list > Assp-test@lists.sourceforge.net <mailto: Assp-test@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/assp-test > > > > _______________________________________________ > Assp-test mailing list > Assp-test@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/assp-test > _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test DISCLAIMER: ******************************************************* This email and any files transmitted with it may be confidential, legally privileged and protected in law and are intended solely for the use of the individual to whom it is addressed. This email was multiple times scanned for viruses. There should be no known virus in this email! *******************************************************
_______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
