More changes:
- I changed my overpopulated Message-ID for the function used by
smtpd(8) (generate_uid()). Now the Message-ID generated by mail(1)
is identical to the one generated by smtpd(8).
- Added a conditional to skip adding the Message-ID if the machine
doesn't have hostname ye
Added random number to Message-ID to get more unique string.
Index: cmd3.c
===
RCS file: /cvs/src/usr.bin/mail/cmd3.c,v
retrieving revision 1.30
diff -u -p -r1.30 cmd3.c
--- cmd3.c 8 Mar 2023 04:43:11 - 1.30
+++ cmd3.c
Avoid printing some headers to stdout when responding from the interface
(when you type r or R), especially Conten-Transfer-Enconding and
Content-Type since the values showed before sending are not the ones
that will be used after processing the body when sending.
Index: cmd3.c
==
On Sun Oct 1 15:19:12 2023, Walter wrote
> I decided to add another header, "Message-ID". Sending mails from my
> patched mail(1) I realized that it's convenient the MUA itself add the
> Message-ID (the one in this message was generated by my patch), if you
> relegate this to the MTA, your MUA wi
Opening a new clean thread.
First of all, I'm sending this message from my patched mail(1), take a
look at the headers. :-)
I tried what each and everyone suggested to me, the only way to know for
sure what works and what doesn't. If you decide that this modification
is too much for a simple app
