uot;ASSP development mailing list" <
> assp-test@lists.sourceforge.net>
> Datum: 05.03.2020 03:05
> Betreff: Re: [Assp-test] Missing MX, A, and FROM for specific
> sender. Unicode problem?
> --
>
>
>
> It's been MUCH better . Survey
No - this looks like a DNS-server timeout while queying the MX for
columbia.edu
Thomas
Von:"K Post"
An: "ASSP development mailing list"
Datum: 05.03.2020 03:05
Betreff: Re: [Assp-test] Missing MX, A, and FROM for specific
sender. Unicode problem?
It
aa.mta2vsmtp.cc.prd.sparkpost (envelope-from <
> *survey-nore...@t.outbound.surveymonkey.com*
> >)
> (ecelerity 4.3.1.69416 r(Core:4.3.1.4)) with ESMTPSA (cipher=AES-256-GCM)
> id 17/C3-02945-4FE1E1E5; Tue, 14 Jan 2020 15:05:08 +
> Message-ID: <17.c3.02945.4fe1e..
t mailing list" <
> assp-test@lists.sourceforge.net>
> Datum: 06.02.2020 02:31
> Betreff: Re: [Assp-test] Missing MX, A, and FROM for specific
> sender. Unicode problem?
> --
>
>
>
> Thanks Thomas,
>
> Here's a sample
OK - I think I got it.
Build 20037 will fix the problem.
Thomas
Von:"K Post"
An: "ASSP development mailing list"
Datum: 06.02.2020 02:31
Betreff: Re: [Assp-test] Missing MX, A, and FROM for specific
sender. Unicode problem?
Thanks Thomas,
Here's
or is that bad
> unicode?
>
> This is no unicode (or better ASCII in UTF-8 - which is the same). This is
> a quoted printable encoded email address, which is (and should not)
> interpreted as such one.
>
> ASSP does not allow (and removes any such EHLO-answer offer) 8-bit M
test@lists.sourceforge.net>
Datum: 02.02.2020 18:49
Betreff: Re: [Assp-test] Missing MX, A, and FROM for specific
sender. Unicode problem?
You're correct in that RFC1342, a proposed standard (from 1992!!) does
say:
...an encoded-word MUST NOT appear in any portion of an "
gt;>> headers.
>>>
>>> ...
>>>
>>> Also note that messages in this format require the use of the
>>> SMTPUTF8 extension [RFC6531 <https://tools.ietf.org/html/rfc6531>] to
>>> be transferred via SMTP.
>>>
>>>
tf.org/html/rfc6531>] to
>> be transferred via SMTP.
>>
>>
>> ...
>>
>> Thomas
>>
>>
>>
>> Von:"K Post"
>> An:"ASSP development mailing list" <
>> assp-test@lists.sourceforge.net>
>>
tain 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 uni
ent mailing list"
Datum: 02.02.2020 18:49
Betreff: Re: [Assp-test] Missing MX, A, and FROM for specific
sender. Unicode problem?
You're correct in that RFC1342, a proposed standard (from 1992!!) does
say:
...an encoded-word MUST NOT appear in any portion of an "address".
Howev
t" <
> 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
eply-to: < valid@email.address>
invalid example:
reply-to: "any encoded unicode"
Thomas
Von:"K Post"
An: "ASSP development mailing list"
Datum: 31.01.2020 17:30
Betreff:Re: [Assp-test] Missing MX, A, and FROM for specific
sender. U
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/rfc1342And according to the ever
questionable wikipedia, https://en.wikipedia.org/wiki/Unicode_and_email :
- RFC 2047
>>> 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.
I'm no longer with that company and do not recall,
Doug
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
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 wrote:
> This is not a necessarily
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
gt;
>> the Reply-To: address is invalid and scored
>>
>> Thomas
>>
>>
>>
>>
>>
>> Von:"K Post"
>> An: "ASSP development mailing list" <
>> assp-test@lis
homas
>
>
>
>
>
> Von:"K Post"
> An:"ASSP development mailing list" <
> assp-test@lists.sourceforge.net>
> Datum:23.01.2020 14:34
> Betreff: Re: [Assp-test] Missing MX, A, and FROM for specific
> sender.
(From-missing) is the feature name
the Reply-To: address is invalid and scored
Thomas
Von:"K Post"
An: "ASSP development mailing list"
Datum: 23.01.2020 14:34
Betreff: Re: [Assp-test] Missing MX, A, and FROM for specific
sender. Unicode problem?
I'
I'm sorry to ask about this again, but the problem persists. Should ASSP
be able to figure out that =?utf-8?q?no-reply=40surveymonkey=2ecom?= is <
no-re...@surveymonkey.com> ? Or - do we know how this malformed address is
getting into the header in the first place - is that ASSP receiving it
We (unfortunately) get a lot of emails from SurveyMonkey.com Most get
through just fine, but certain messages from their website (login
notifications, password resets, etc) give me problems.
The last one scored poorly because of a missing from, missing MX, and
missing a record, *but it actually
23 matches
Mail list logo
