Configuring the List-Archive and Archived-At headers
With archiving enabled, mail is sent with headers like the following:
Archived-At: https://example.com/hyperkitty/list/foo-users@lists.example.com/message/ABC/ List-Archive: https://example.com/hyperkitty/list/foo-users@lists.example.com/ List-Post: mailto:foo-users@lists.example.com List-Subscribe: mailto:foo-users-join@lists.example.com
The 'mailto:' entries are fine, but I need all 'https:' links to be prefixed with https://lists.example.com instead of https://example.com .
Does Mailman extract CN parts from the SSL certificate to populate the header values (that would explain 'example.com' in my tests), or is this something I can influence using configuration parameters? I searched the docs for Mailman Suite and HyperKitty, but did not find an answer.
-Ralph
On 3/20/19 5:43 PM, Ralph Seichter wrote:
With archiving enabled, mail is sent with headers like the following:
Archived-At: https://example.com/hyperkitty/list/foo-users@lists.example.com/message/ABC/ List-Archive: https://example.com/hyperkitty/list/foo-users@lists.example.com/ List-Post: mailto:foo-users@lists.example.com List-Subscribe: mailto:foo-users-join@lists.example.com
The 'mailto:' entries are fine, but I need all 'https:' links to be prefixed with https://lists.example.com instead of https://example.com .
Does Mailman extract CN parts from the SSL certificate to populate the header values (that would explain 'example.com' in my tests), or is this something I can influence using configuration parameters? I searched the docs for Mailman Suite and HyperKitty, but did not find an answer.
It has nothing to do with the ssl certificate. It comes from _get_url in hyperkitty/views/mailman.py
def _get_url(mlist_fqdn, msg_id=None): # We can't use HttpRequest.build_absolute_uri() because the mailman API may # be accessed via localhost. # https://docs.djangoproject.com/en/dev/ref/request-response/#django.http.Http... # https://docs.djangoproject.com/en/dev/ref/contrib/sites/#getting-the-current... # result = urljoin(public_url, urlunquote( # reverse('hk_list_overview', args=[mlist_fqdn]))) # We use the MailDomain association from django_mailman3 to find out the # proper domain.
What that means is the lists.example.com domain must first be known to Django at <https://lists.example.com/admin/sites/site/
Then at https://lists.example.com/postorius/domains/, the Web Host for the example.com domain needs to be lists.example.com
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On 3/20/19 6:50 PM, Mark Sapiro wrote:
On 3/20/19 5:43 PM, Ralph Seichter wrote:
With archiving enabled, mail is sent with headers like the following:
Archived-At: https://example.com/hyperkitty/list/foo-users@lists.example.com/message/ABC/ List-Archive: https://example.com/hyperkitty/list/foo-users@lists.example.com/ List-Post: mailto:foo-users@lists.example.com List-Subscribe: mailto:foo-users-join@lists.example.com ... What that means is the lists.example.com domain must first be known to Django at <https://lists.example.com/admin/sites/site/
Then at https://lists.example.com/postorius/domains/, the Web Host for the example.com domain needs to be lists.example.com
I didn't look carefully enough at your example. If the mailto: links are @lists.example.com, then that is the Mail Host at https://lists.example.com/postorius/domains/ for which the Web Host needs to be lists.example.com.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
- Mark Sapiro:
It has nothing to do with the ssl certificate.
In retrospect, that possibility seems unlikely indeed. Note to self: Don't write to public mailing lists at 01:43 local time... ;-)
What that means is the lists.example.com domain must first be known to Django at <https://lists.example.com/admin/sites/site/
Ah, that's what I was missing, thank you. The headers in my test installation are now generated with the correct URLs.
Could I suggest extending the documentation regarding web hosts? https://mailman.readthedocs.io/en/latest/src/mailman/model/docs/domains.html briefly mentions "Domains are how Mailman interacts with email host names and web host names", but as far as I can tell that's pretty much it.
-Ralph
On 3/21/19 9:48 AM, Ralph Seichter wrote:
Could I suggest extending the documentation regarding web hosts? https://mailman.readthedocs.io/en/latest/src/mailman/model/docs/domains.html briefly mentions "Domains are how Mailman interacts with email host names and web host names", but as far as I can tell that's pretty much it.
If you post an issue at https://gitlab.com/mailman/mailman/issues, one of our GSOC aspirants may pick it up.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
- Mark Sapiro:
If you post an issue at https://gitlab.com/mailman/mailman/issues, one of our GSOC aspirants may pick it up.
Done, although I wonder if any GSOC participant would want to write documentation instead of code... ;-)
-Ralph
On 3/22/19 8:05 AM, Ralph Seichter wrote:
- Mark Sapiro:
If you post an issue at https://gitlab.com/mailman/mailman/issues, one of our GSOC aspirants may pick it up.
Done, although I wonder if any GSOC participant would want to write documentation instead of code... ;-)
As part of the application process they need to contribute at least one non-trivial Merge Request and have that accepted. This may qualify.
In any case, the need is now documented in a more visible way than just a post on this list.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Ralph Seichter writes:
- Mark Sapiro:
If you post an issue at https://gitlab.com/mailman/mailman/issues, one of our GSOC aspirants may pick it up.
Done, although I wonder if any GSOC participant would want to write documentation instead of code... ;-)
For their actual, Google-supported, project, Google explicitly excludes documentation.
But for our purposes, they do need a qualifying commit to demonstrate they've figured out how to get changes through our process and into merge requests, a purely adminstrative qualification. Doc patches are easy to write and get approved quickly! :-)
Steve
On March 24, 2019 10:51:07 p.m. PDT, "Stephen J. Turnbull" turnbull.stephen.fw@u.tsukuba.ac.jp wrote:
Ralph Seichter writes:
- Mark Sapiro:
If you post an issue at https://gitlab.com/mailman/mailman/issues, one of our GSOC aspirants may pick it up.
Done, although I wonder if any GSOC participant would want to write documentation instead of code... ;-)
For their actual, Google-supported, project, Google explicitly excludes documentation.
They do for Google Summer of **Code** but they've just announced Google Summer of **Docs** which sounds really neat and we might want to participate.
(It's my personal opinion that our docs have really suffered since I finished my PhD and stopped using them as a warmup exercise when I was procrastinating on writing my thesis. *grin*)
On Sun, Mar 24, 2019, at 11:58 PM, Terri Oda wrote:
On March 24, 2019 10:51:07 p.m. PDT, "Stephen J. Turnbull" turnbull.stephen.fw@u.tsukuba.ac.jp wrote:
Ralph Seichter writes:
- Mark Sapiro:
If you post an issue at https://gitlab.com/mailman/mailman/issues, one of our GSOC aspirants may pick it up.
Done, although I wonder if any GSOC participant would want to write documentation instead of code... ;-)
For their actual, Google-supported, project, Google explicitly excludes documentation.
They do for Google Summer of **Code** but they've just announced Google Summer of **Docs** which sounds really neat and we might want to participate.
They are calling it Season of Docs, happening in winter I think Sept-Dec AFAIK.
Yep, we should participate in that, I sent out an email earlier about this too.
(It's my personal opinion that our docs have really suffered since I finished my PhD and stopped using them as a warmup exercise when I was procrastinating on writing my thesis. *grin*)
Mailman-users mailing list -- mailman-users@mailman3.org To unsubscribe send an email to mailman-users-leave@mailman3.org https://lists.mailman3.org/mailman3/lists/mailman-users.mailman3.org/
-- thanks, Abhilash Raj (maxking)
participants (5)
-
Abhilash Raj -
Mark Sapiro -
Ralph Seichter -
Stephen J. Turnbull -
Terri Oda