Le 18/06/2020 à 11:15, David Leangen a écrit :
>
> Hi,
>
> Thanks for thinking about this.
>
>>> When writing the docs, I came to understand that what we mean by “Mail
>>> Server” is not very clear to me.
>
>> Somehow. Let me give a try at generifying this:
>>
>> A mail server is a software whose responsibility is storing,
>> transferring or processing emails.
>>
>> SMTP servers, POP3 servers, IMAP servers and JMAP servers fall into this
>> category.
>
> So 3 things?
>
> 1. Storing
> 2. Transferring
> 3. Processing
>
> Let me dig in to all of these.
>
> Storing - My understanding is that this is optional. A server can be
> stateless, depending on the protocol being served, so no storing necessary.
> Is my understanding correct?
That is why I used the term "or" instead of "and".
> Transferring - I can’t think of any counter-argument.
>
> Processing - This is a very generic term. Basically any server can be said to
> “process” something. Maybe we need to be a little more specific. But then
> again, I’m not sure how.
True.
Let's then dig further: what do we call processing?
Mail processing is the action of modifying an email and triggering side
effects for it (mail storing and transfer mentioned above being some
first class citizen side effects).
I nuanced that via the concept of "main responsibility". My website
sending a newsletter can not be considered a mail server because its
main responsibility is to display my blog.
> Cheers,
> =David
>
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
