ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm <texml@fiee.net>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: mailing list behaviour (was: Spurious newlines at beginning of startstop pair)
Date: Fri, 29 Nov 2019 12:10:46 +0100	[thread overview]
Message-ID: <3210F86B-1B07-4946-8698-5DD172AD4EC1@fiee.net> (raw)
In-Reply-To: <c0073142-c64c-7625-b6b0-2b176d1e6b46@mailbox.org>


> Am 2019-11-29 um 11:05 schrieb Denis Maier <denis.maier.lists@mailbox.org>:
> 
> Am 29.11.2019 um 10:38 schrieb Hans Hagen:
>> Second: For some reasons I have not received your message. It wasn't in the Spam folder and I usually receive mails from the list. Any ideas? Are there some known problems?
>> 
>> Your mailbox host does some strange address checking (we run a mail server here and then go to the provider and it checks the internal server with a local address) ... there are some more on this list that bounce that way, like gmx, and i';ve given up bothering about it.
>>  hans
> 
> Ok, what do you suggest? Change to a different mailserver for the list? Which hosts aren't prone to this problem? Or is there something I can change on my side?

The problem seems to be that traditional mailing lists like this just don’t work with modern security standards.

I didn’t check how secure NTG’s mail server is configured, but changing subject and sender of every message is regarded harmful.
Not doing that would mean that: 
* I can’t filter mails (visually or rule based) by subject any more.
* A lot of replies would only go to the sender.
* The connection of threads would get lost.
(I see all of these on other lists.)

So, using an address from a more tolerant (and maybe less secure) provider for lists like this would make sense.


Greetlings, Hraban
---
https://www.fiee.net
http://wiki.contextgarden.net
https://www.dreiviertelhaus.de
GPG Key ID 1C9B22FD

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  parent reply	other threads:[~2019-11-29 11:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27 13:17 Spurious newlines at beginning of startstop pair Denis Maier
2019-11-27 16:25 ` Hans Hagen
     [not found] ` <1747191520.26220.1574979930871@office.mailbox.org>
2019-11-28 22:26   ` Fwd: " denis.maier.lists
2019-11-29  9:38     ` Hans Hagen
2019-11-29 10:05       ` Denis Maier
2019-11-29 11:07         ` Hans Hagen
2019-11-29 11:10         ` Henning Hraban Ramm [this message]
2019-11-29 11:31           ` mailing list behaviour (was: Spurious newlines at beginning of startstop pair) Marco Patzer
2019-11-29 12:02             ` mailing list behaviour Henning Hraban Ramm

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3210F86B-1B07-4946-8698-5DD172AD4EC1@fiee.net \
    --to=texml@fiee.net \
    --cc=ntg-context@ntg.nl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).