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