In message <601b01c7-1475-32e0-5aba-e595272e9...@tnetconsulting.net>,
Grant Taylor via mailop writes
>My concern is that Yahoo / AOL isn't creating an arbitrary "every domain
>must have an SOA record" and completely loosing sight of the fact that
>SOAs belong to the /zone/ apex and are not
> On 13.07.2023 at 20:52 Robert L Mathews via mailop wrote:
>
> On 7/13/23 11:12 AM, Jarland Donnell via mailop wrote:
>> Perhaps it's going off topic and apologies if so, but this makes me wonder a
>> second thing. Who is, and why are they, adding subdomains to the PSL when
>> subdomains
> On 13.07.2023 at 17:55 Bill Cole via mailop wrote:
>
> It's not at all logically hard to meet that arbitrary requirement, you just
> need a zone cut everywhere you have a MX record. I've run a DNS and mail
> hosting environment that way. Zone files are very small and numerous.
>
On 7/13/23 11:12 AM, Jarland Donnell via mailop wrote:
Perhaps it's going off topic and apologies if so, but this makes me
wonder a second thing. Who is, and why are they, adding subdomains to
the PSL when subdomains above that in hierarchy are in the same zone file?
Some domains that offer
Perhaps it's going off topic and apologies if so, but this makes me
wonder a second thing. Who is, and why are they, adding subdomains to
the PSL when subdomains above that in hierarchy are in the same zone
file?
On 2023-07-13 13:06, Robert L Mathews via mailop wrote:
On 7/13/23 10:44
On 7/13/23 10:44 AM, Jaroslaw Rafa via mailop wrote:
If .tld is on PSL, then example.tld will be the organizational domain. And
it definitely should have its own zone file, so it should have SOA. I can't
imagine a scenario in which it doesn't.
An example is something like
On 2023-07-13 at 12:06:45 UTC-0400 (Thu, 13 Jul 2023 11:06:45 -0500)
Grant Taylor via mailop
is rumored to have said:
On 7/13/23 10:49 AM, Bill Cole via mailop wrote:
It's not at all logically hard to meet that arbitrary requirement,
you just need a zone cut everywhere you have a MX record.
Dnia 13.07.2023 o godz. 10:23:24 Robert L Mathews via mailop pisze:
>
> But anyway, if other people have this trouble, note that it can
> happen whether the MAIL FROM domain name is directly at a PSL
> breakpoint or not. The issue is just that there's no SOA found at
> the MAIL FROM domain name
On 7/12/23 9:42 PM, Felix Fontein via mailop wrote:
right now there is only a SOA record for `us.` itself and for
`ci.westfir.or.us.`, but for nothing inbetween.
Ugh, you're right, the customer has removed the delegation of
westfir.or.us (I was testing on internal servers that still showed
On 7/13/23 10:49 AM, Bill Cole via mailop wrote:
It's not at all logically hard to meet that arbitrary requirement, you
just need a zone cut everywhere you have a MX record. I've run a DNS and
mail hosting environment that way. Zone files are very small and
numerous. *Logistically* changing an
On 2023-07-12 at 18:38:05 UTC-0400 (Wed, 12 Jul 2023 15:38:05 -0700)
Robert L Mathews via mailop
is rumored to have said:
Today I had a customer complain that mail they send to AOL or Yahoo
addresses was being returned with:
451 Message temporarily deferred due to unresolvable RFC.5321 from
On 7/13/23 2:24 AM, Gellner, Oliver via mailop wrote:
The requirement is actually less restrictive as it only requires a
SOA record and not additional A, or MX records in DNS. It is not
necessary that every hostname has a SOA record, that indeed would be
unreasonable. Yahoo only requires
On 13.07.2023 at 00:38 Robert L Mathews via mailop wrote:
> Aside from anything else, it implies that SOA records can be easily added to
> solve this, similar to how you add MX or A records. But that is usually not
> the case: SOA records can exist only at a DNS zone delegation boundary, not
>
Hi,
> > the conclusions at that time were:
> > [...] > - It only affects domains on the Public Suffix List. i.e.
> > the sender domain is in some public namespace where Y! want to see
> > an SOA to show it's actually administered by someone.
> >
> > Is that the case for you?
>
> No. I might
On 7/12/23 4:22 PM, Andy Smith via mailop wrote:
We last had this thread back in may
Yikes; not sure how I missed that. Thanks for the pointer.
the conclusions at that time were:
[...] > - It only affects domains on the Public Suffix List. i.e. the sender
domain is in some public
Hi,
On Wed, Jul 12, 2023 at 03:38:05PM -0700, Robert L Mathews via mailop wrote:
> see https://postmaster.yahooinc.com/error-codes
>
> According to that page,
>
> "- These errors indicate that the domain used to the right of the @ in the
> MAIL FROM does not appear to be a real domain.
> - We
Today I had a customer complain that mail they send to AOL or Yahoo
addresses was being returned with:
451 Message temporarily deferred due to unresolvable RFC.5321 from
domain; see https://postmaster.yahooinc.com/error-codes
According to that page,
"- These errors indicate that the domain
17 matches
Mail list logo
