It’s a protocol limit:
https://www.rfc-editor.org/rfc/rfc5322#section-2.1.1
—
Andrew Sullivan
Please excuse my clumbsy thums
> On Aug 6, 2022, at 13:44, post...@ptld.com wrote:
>
> Does postfix through either smtp or submission (or both) force line breaks?
> I am noticing line
gistry operator: you register domains
inside your domain. That's how DNS works.
If you want to assert that you accept such registrations from the public, you
can tell the PSL: https://publicsuffix.org/submit/
I suspect, however, that we're getting a little off-topic for this list.
Be
I'm the CEO of the Internet Society, and PIR is a supporting
organization of the Internet Society. I am not speaking for the Internet Society here and
I'm definitely not speaking for PIR.)
A
--
Andrew Sullivan
a...@anvilwalrusden.com
n fact.
But most of the original TLDs already had all the 2-character combinations sold
by the time the new restriction went into place, so the rules don't hold for
those.
A
--
Andrew Sullivan
a...@anvilwalrusden.com
but it's certainly not perfect and is basically a curated list and not
something that can be properly generated out of the DNS.
A
--
Andrew Sullivan
a...@anvilwalrusden.com
éxample.tld is legal, éxample.TLD is legal, and ÉXAMPLE.TLD is
an error. (I'm aware that's not how you spell example in French, I'm just
using it for illustration.) I don't think that the above considered TLDs or
EAI, so I don't expect it is relevant; I just mention it for comple
like to encourage people to find ways to stanch mail from
bad sources using reputation lists and so on, rather than wholesale
blocking of whole TLDs.
Best regards,
A
(Full disclosure: in my day job I work for the Internet Society, but I
am not speaking for them now.)
--
Andrew Sullivan
a...@anvilwalrusden.com
On Thu, Oct 31, 2019 at 07:52:11PM -0400, Andrew Sullivan wrote:
> Hi,
>
> I _know_ I am overlooking something, and I need a clue-bat.
Thanks to the list for the help. I tracked this down to a mistake in
main.cf with a too-restrictive smtpd_client_restrictions (I seem to
have comm
t have this
problem. But it annoys me that I've messed it up.
Thanks for your help,
A
--
Andrew Sullivan
a...@anvilwalrusden.com
know" and
"trust") over IPsec. I believe that was the use case originally for
the AD bit, which otherwise is more or less useless for all the
reasons you outline.
(Your general point, of course, still stands.)
A
--
Andrew Sullivan
a...@anvilwalrusden.com
in i18n is pretty
normal. But I get it that you won't get some sort of back end
encoding error.
> support any per-lookup flags. So we'd need dict_get_ex() that
> takes a new utf8 flag and supporting changes throughout the
> code. This is a major change.
Sounds like, yes.
A
--
Andrew Sullivan
a...@anvilwalrusden.com
he problem could well be here; I'm insufficiently familiar with its
internals to comment.
Best regards,
A
--
Andrew Sullivan
a...@anvilwalrusden.com
have port numbers in the logs:
Yes, a good idea anyway.
Best regards,
A
--
Andrew Sullivan
a...@anvilwalrusden.com
ose." Didn't seem a lot of point in publishing by then.
Best regards,
A
--
Andrew Sullivan
a...@anvilwalrusden.com
no DNS Police to come and tell
you that you are using names wrong, or revoke your Internet license if
you do so.
Best regards,
A
--
Andrew Sullivan
a...@anvilwalrusden.com
like you're still seeing a SERVFAIL for the MX record, at
least in what you posted. SERVFAIL means something is wrong, possibly
with the resolver (also called "recursive" or "recursive server")
itself. That's not the answer you need.
Best regards,
A
--
Andrew Sullivan
a...@anvilwalrusden.com
lem resulting from that. If the resolver is validating and can't
prove the insecure delegation, it might return SERVFAIL. (But I agree
I can see the records there.) The SERVFAIL could also be a broken
recursive or a cache failure of some kind.
A
--
Andrew Sullivan
a...@anvilwalrusden.com
ork with the .pgpass
file in the home directory of the invoking user. It might be worth
trying. I have used this in cases where the login shell of the user
was /bin/false, so I don't think that at least should be the barrier.
A
--
Andrew Sullivan
a...@anvilwalrusden.com
icode is on the mail
system, but it's talking to an older-Unicode database backend. I
_think_ the mail server could still send code points that cause an
encoding error, even if the mail server did the validation.
Thanks,
A
--
Andrew Sullivan
a...@anvilwalrusden.com
just changing the code to set
the encoding to UTF8 as opposed to LATIN1. Is there anything I could
do to help? It looks to me like a trivial change in the driver code.
Thanks and best regards,
A
--
Andrew Sullivan
a...@anvilwalrusden.com
20 matches
Mail list logo
