‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, August 20, 2020 11:41 AM, antlists <antli...@youngman.org.uk>
wrote:
> Will that python script allow for the situation that the message is
> received, but the message was NOT safely stored for onwards transmission
> before the receiver crashed, and as such the message has not been
> SUCCESSFULLY received?
>
> SMTP has lots of things specifically meant to ensure messages survive
> the internet jungle on their journey ...
thanks for the point. would it suffice if we have
these notifications:
1. receipt by final mail server (mandatory).
2. receipt by end user(s) (optional).
3. opening by end user(s) (optional).
?
----
(1) is required by the server, else mail will be
retransmitted from source relay(s) (or client if
done directly). (2) is optional by final server,
(3) is optional by end user's client.
the job of a relay would be to optionally add some
metadata (e.g. maybe describing sender's role) and
sign the whole thing (e.g. by company's private
key). this way we can have group-level rules.
