[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: mysterious c0 80
From: |
Ralph Corderoy |
Subject: |
Re: mysterious c0 80 |
Date: |
Fri, 05 Jan 2024 15:52:04 +0000 |
Hi David,
> > > > nmh shouldn't comp(1) a new email today with a NUL in the body,
> > > > but it should be able to read and show(1) one.
> > >
> > > I'm thinking of removing the support in post(8) for sending NULs.
> > > Any disagreement? It's not a lot of code so could be easily
> > > restored in the future if conditions change.
> > >
> > > > Now, how about dist(1) of that old email? I'd have thought it
> > > > should send the old email verbatim, NUL and all. If that causes
> > > > a bounce then the sender can MIME-forward instead with a single
> > > > message/rfc822 part.
> > >
> > > Agreed.
> >
> > But doesn't dist → send → post so if you remove post's support for
> > sending NULs then dist won't be able to send the old email verbatim.
>
> Yes, but isn't that required by RFC 5322?
Yes, RFC 5322 says do not send NULs.
> I don't object to violating it in this case, so I'm fine with whatever
> we can agree on.
I was confused by your ‘Agreed’ above which agreed dist should be able
to send and post NULs.
--
Cheers, Ralph.
- Re: mysterious c0 80, (continued)
- Re: mysterious c0 80, Ken Hornstein, 2024/01/02
- Re: mysterious c0 80, Michael Richardson, 2024/01/02
- Re: mysterious c0 80, Ralph Corderoy, 2024/01/03
- Re: mysterious c0 80, David Levine, 2024/01/03
- Re: mysterious c0 80, Ralph Corderoy, 2024/01/04
- Re: mysterious c0 80, Ken Hornstein, 2024/01/04
- Re: mysterious c0 80, Ralph Corderoy, 2024/01/04
- Re: mysterious c0 80, Ken Hornstein, 2024/01/04
- Re: mysterious c0 80, Michael Richardson, 2024/01/04
- Re: mysterious c0 80, David Levine, 2024/01/04
- Re: mysterious c0 80,
Ralph Corderoy <=
- Re: mysterious c0 80, Michael Richardson, 2024/01/02
- Re: mysterious c0 80, Ralph Corderoy, 2024/01/02
Re: mysterious c0 80, Michael Richardson, 2024/01/01
Re: mysterious c0 80, Michael Richardson, 2024/01/01