Groups | Search | Server Info | Login | Register
Groups > comp.mail.headers > #39
| From | Anton Shepelev <anton.txt@gmail.moc> |
|---|---|
| Newsgroups | comp.mail.headers |
| Subject | Re: Bcc: according to RFC 5322 |
| Date | 2024-07-26 01:46 +0300 |
| Organization | A noiseless patient Spider |
| Message-ID | <20240726014637.68f24e30f9afd464e02467ab@gmail.moc> (permalink) |
| References | <20240725175947.ec0c6aab9964a00f7301992b@g{oogle}mail.com> <v7ujq2$1qc$1@tncsrv09.home.tnetconsulting.net> |
Grant Taylor: > My long standing understanding based on personal > experience is that BCC is really an MUA construct wherein > the BCC recipient(s) will receive a copy of the message as > they are added as an SMTP envelope recipient while > expressly being excluded from the RFC 5322 (et al.) > headers. I am surprised. What made you think it Bcc: is handled by the MUA intead of the SMTP server? -- () ascii ribbon campaign -- against html e-mail /\ www.asciiribbon.org -- against proprietary attachments
Back to comp.mail.headers | Previous | Next — Previous in thread | Next in thread | Find similar
Bcc: according to RFC 5322 Anton Shepelev <anton.txt@g{oogle}mail.com> - 2024-07-25 17:59 +0300
Re: Bcc: according to RFC 5322 Grant Taylor <gtaylor@tnetconsulting.net> - 2024-07-25 17:32 -0500
Re: Bcc: according to RFC 5322 Anton Shepelev <anton.txt@gmail.moc> - 2024-07-26 01:46 +0300
Re: Bcc: according to RFC 5322 Grant Taylor <gtaylor@tnetconsulting.net> - 2024-07-25 21:03 -0500
Re: Bcc: according to RFC 5322 "Gary R. Schmidt" <grschmidt@acm.org> - 2024-07-26 22:40 +1000
Re: Bcc: according to RFC 5322 Anton Shepelev <anton.txt@gmail.moc> - 2024-07-28 00:35 +0300
Re: Bcc: according to RFC 5322 Sirius <sirius@trudheim.com> - 2024-07-26 16:09 +0200
Re: Bcc: according to RFC 5322 Anton Shepelev <anton.txt@gmail.moc> - 2024-07-28 00:43 +0300
csiph-web