| 1 |
On 8/18/20 4:30 AM, Ashley Dixon wrote: |
| 2 |
> but nothing can replace it in terms of interoperability and |
| 3 |
> convenience. |
| 4 |
|
| 5 |
That is an EXTREMELY important point. |
| 6 |
|
| 7 |
SMTP is a protocol that completely independent implementations can use |
| 8 |
to exchange messages with each other. |
| 9 |
|
| 10 |
You can set up gateways to enable different forms of messages to go to |
| 11 |
and come from SMTP. Things like this allow you to send a fax to an |
| 12 |
email gateway to an MMS gateway to receive a picture on your phone. |
| 13 |
|
| 14 |
There are /SO/ /MANY/ <bla> to / from email gateways (which effectively |
| 15 |
means SMTP) that are used each and every day to run the world. |
| 16 |
|
| 17 |
> Perhaps the younger generation ... would almost-unanimously disagree, |
| 18 |
> but your proposed solution doesn't really provide greater ease for you, |
| 19 |
> or the people e-mailing you! |
| 20 |
|
| 21 |
mail(fire)ball provides something, but I'm quite sure "ease (of use)" is |
| 22 |
decidedly /NOT/ one of the things that it provides. |
| 23 |
|
| 24 |
|
| 25 |
|
| 26 |
-- |
| 27 |
Grant. . . . |
| 28 |
unix || die |
Archives