On 9/25/20 4:55 AM, Johannes Rohr wrote:
> Great, and apart from that, is the virtualhost configuration obsolete in
> mailman3? I noticed that when you create a new list, you already have to
> append the domain, so this looks to me as if this is now implicit.
The MM 2.1 virtualhost
On 9/25/20 4:41 AM, Brian Carpenter wrote:
>
> It is possible with the following setting set via settings_local.py:
>
> filter_vhost = true
>
That should be
FILTER_VHOST = True
settings_local.py and settings.py are Python so setting something to
`true` rather than `True` will throw a
Am 25.09.20 um 13:41 schrieb Brian Carpenter:
> On 9/25/20 6:49 AM, Johannes Rohr wrote:
>> I am now playing around with Mailman 3, considering to migrate
>> eventually. Reading the documentation, I haven't understood whether
>> there is still a possibility to configure virtual hosts within
On 9/25/20 6:49 AM, Johannes Rohr wrote:
I am now playing around with Mailman 3, considering to migrate
eventually. Reading the documentation, I haven't understood whether
there is still a possibility to configure virtual hosts within mailman.
My goal is to ensure that visitors
Hello
Sorry, but you are on the wrong mailinglist.
This ione is for Mailman 2 only.
Kind regards,
Christian Mack
Am 25.09.20 um 12:49 schrieb Johannes Rohr:
> Dear all,
>
> I am now playing around with Mailman 3, considering to migrate
> eventually. Reading the documentation, I haven't
Dear all,
I am now playing around with Mailman 3, considering to migrate
eventually. Reading the documentation, I haven't understood whether
there is still a possibility to configure virtual hosts within mailman.
My goal is to ensure that visitors of https://lists.domain1.org only see
the lists
Remote Server returned '550 5.6.0 CAT.InvalidContent.Exception:
ExchangeDataException, Decoding of header Subject failed+ADs- raw value:
+AFs-Ps+AF0-
+AD0-?iso8859-7?b?wer98fnz5yDF8OX05enh6t7yIOXq5N7r+-fPn8iDz9Oft?+AD0-;
cannot handle content of message
It looks like the Subject: header of