[swift-users] How mailing lists work

[Johan Jensen]

Every mail usually gets a unique Message-ID assigned by either the mail
client or the first mail server. While it often looks like a valid email,
it is only an identifier.
When you reply to an email, the Message-ID of that email gets set as the
In-Reply-To value.
This is the basic of message threading, but most clients have a lot of
extra code to better determine threading.

In the case of mailing lists, you want to send your reply to the email of
the message you’re replying to, as well as the mailing list. You want to
send it to the mailing list, so it can archive your reply on the website as
well as sending copies out to everyone who have subscribed.
Generally this is done by pressing "Reply All" in your mail client, which
sets the mailing list as cc.

I am not aware of a way to reply to archived messages, if you haven't
received the email yourself.

— Johan

On Sun, Jan 24, 2016 at 6:54 PM, David Keck via swift-users <
swift-users at swift.org> wrote:

> I am totally new to this concept of mailing lists. I have heard about them
> in programming books, but it always seemed like they were for phased out or
> only in use for old projects. Anyway, now that I have a taste of them, I
> think they're awesome! I'd like to know more about how they work.
>
> Specifically, how can I reply and quote someone? Do I reply to the Message
> ID? For example: Message-ID: <m2y4bhpj58.fsf at eno.apple.com> Or do I send
> a reply directly to the original email address?
>
> I know I can access an archive at
> https://lists.swift.org/pipermail/swift-users/, but I'm still not sure
> how to reply from there either.
>
> Sorry if this is super obvious stuff, but everyone has to learn sometime!
>
> Thanks!
>
> David Keck
>
> _______________________________________________
> swift-users mailing list
> swift-users at swift.org
> https://lists.swift.org/mailman/listinfo/swift-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-users/attachments/20160124/3d7d67c3/attachment.html>