FAQ
All,

I am using mailman as installed and administered by a web host in
vancouver, webserve.ca.

When I set up a mailing list, the general contact address on the
mail.mail.domainname.ca/mailman/listinfo page is listed as
mailman at mail.domainname.ca, rather than mailman at domainname.ca.

When I send a test email to mailman at mail.domainname.ca I get a bounce
back with this message:

This is an automatically generated Delivery Status Notification.

Delivery to the following recipients failed.

mailman at mail.domainname


When I send a test email to mailman at domainname.ca I get a bounce back
with this message:

You are not allowed to post to this mailing list, and your message has
been automatically rejected. If you think that your messages are
being rejected in error, contact the mailing list owner at mailman-owner at ns38.servepower.com.


I presume this is a configuration issue. Unfortunately I do not have
access on the configuration server, and the webserve.ca support people
seem to be at a loss as to what to do.

Judging from the fact that python's own mail list page uses
mailman at python.org, I presume that the issue is faulty configuration of
the general list contact address in the configuration file.

Could someone explain to me how this can be fixed, so that I can pass it on?

Thanks much,

- Henrik

--

Henrik Bechmann
www.osscommons.ca
www.bechmannsoftware.com
Webmaster, www.dufferinpark.ca

Search Discussions

  • Mark Sapiro at Dec 8, 2006 at 10:57 pm

    Henrik wrote:
    When I set up a mailing list, the general contact address on the
    mail.mail.domainname.ca/mailman/listinfo page is listed as
    mailman at mail.domainname.ca, rather than mailman at domainname.ca.

    The domain in this address depends on whether or not
    VIRTUAL_HOST_OVERVIEW is set to Yes or No. The default is Yes. If you
    visit the http://www.example.com/mailman/listinfo overview page and
    you see only lists in the www.example.com domain, then it is set to
    Yes. If you see all the advertised lists on the server, then it is set
    to No (in mm_cfg.py).

    So, if VIRTUAL_HOST_OVERVIEW is set to No, the domain in the site list
    address is the result of looking up DEFAULT_URL_HOST in the
    VIRTUAL_HOSTS dictionary - i.e. it is the second argument from

    add_virtualhost(DEFAULT_URL_HOST, xxx)

    from mm_cfg.py (normally this is DEFAULT_EMAIL_HOST).

    If VIRTUAL_HOST_OVERVIEW is set to Yes, the domain is the result of
    looking up the host domain from the URL used to access the page.

    In your case, assuming no typo above even though it looks strange,
    there is an entry in mm_cfg.py like

    add_virtualhost('mail.mail.domainname.ca', 'mail.domainname.ca')

    that should be

    add_virtualhost('mail.mail.domainname.ca', 'domainname.ca')

    instead.

    There is another possibility. This add_virtualhost entry also affects
    your own lists. Is the domain 'mail.domainname.ca' the correct domain
    for mailing to your lists? If so, you don't want to change the
    add_virtualhost entry; you need to add an alias or whatever to the MTA
    for your domain for the mailman list.

    On the third hand, I visited the listinfo page on the server at
    ns38.servepower.com, and it appears to be a cPanel mailman so I relly
    don't have a clue. See
    <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.011.htp>.

    When I send a test email to mailman at mail.domainname.ca I get a bounce
    back with this message:

    This is an automatically generated Delivery Status Notification.

    Delivery to the following recipients failed.

    mailman at mail.domainname


    When I send a test email to mailman at domainname.ca I get a bounce back
    with this message:

    You are not allowed to post to this mailing list, and your message has
    been automatically rejected. If you think that your messages are
    being rejected in error, contact the mailing list owner at mailman-owner at ns38.servepower.com.


    I presume this is a configuration issue. Unfortunately I do not have
    access on the configuration server, and the webserve.ca support people
    seem to be at a loss as to what to do.

    You get the above message because the installation has only one site
    list (mailman) for all supported domains and it is configured to
    reject posts from non-members

    Yet, since this is presumably a cPanel Mailman, if it is the case that
    the domain for mail to your lists IS mail.domainname.ca, you may be
    able to solve the whole problem by just creating a 'mailman' list in
    your own domain.

    Judging from the fact that python's own mail list page uses
    mailman at python.org, I presume that the issue is faulty configuration of
    the general list contact address in the configuration file.

    Could someone explain to me how this can be fixed, so that I can pass it on?

    If the above doesn't do it, let us know what else you need.

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan
  • Henrik at Dec 9, 2006 at 2:04 am
    Thanks Mark,
    If VIRTUAL_HOST_OVERVIEW is set to Yes, the domain is the result of
    looking up the host domain from the URL used to access the page.

    This appears to be the case:

    In fact if I access the page with mail.domainname.ca/mailman/, the
    contact address is mailman at mail.domainname.ca, whereas if I access the
    page with domainname.ca/mailman/listinfo (ie without the "mail."
    subdomain), the contact address shows as mailman at domainname.ca.

    Reading the domain from the URL is desirable as I have a number of
    domain names associated with the account, and wish to have mailing lists
    set up for all or most of them. But is seems like what should be used is
    something like (in totally pseudo regex, I have no idea what the syntax
    is in python)

    add_virtualhost('/(mail\.)?(*.)/', '$2')

    Is this true? What would the entry look like? (I don't unfortunately
    have access to mm_cfg.py - is it in principle possible to have a
    mm_cfg.py for a user of a linux system -- ie for a web account). I would
    have to pass this on to the web host.

    Then the other problem would appear to be that the default mail address
    (mailman at domainnname.ca) is not set up properly on creation of the mail
    list.

    Does all this seem like a reasonable theory?

    BTW, mail list creation is done through cpanel, so I presume the
    installation was done through cpanel as well. But I don't know for sure.

    Also, yes I did make a typo with mail.mail.domainname.ca. I should have
    typed mail.domainname.ca. Sorry about the confusion.
    Is the domain 'mail.domainname.ca' the correct domain
    for mailing to your lists? If so, you don't want to change the
    add_virtualhost entry; you need to add an alias or whatever to the MTA
    for your domain for the mailman list.


    I have no control over this, and am not sure of the question. The pop3
    (and SMTP) mail server is mail.domainname.ca. Would this interfere?

    Lists are sent to mylist at domainname.ca, ie no "mail" subdomain is used
    for mailing to the lists. Does this answer that question?
    You get the above message because the installation has only one site
    list (mailman) for all supported domains and it is configured to
    reject posts from non-members

    The ideal would be to have mailman at domainname.ca go to the list owner
    associated with the domain name (ie multiple domain names on my web
    account), as opposed to my web account (in effect my web acount, read
    Linux user, is host to multiple domain names, but so, presumably, are
    other users on the same installation).
    Yet, since this is presumably a cPanel Mailman, if it is the case that
    the domain for mail to your lists IS mail.domainname.ca, you may be
    able to solve the whole problem by just creating a 'mailman' list in
    your own domain.


    Sorry, don't quite get that. You mean create a list called
    mailman at domainname.ca, and this would pre-empt the central installation
    routing? And just make the list private, with only the owner as a
    recipient? This is an interesting possibility, though if I understand it
    right, the proper solution would be to have the mail list installation
    process check sendmail for the existence of a default address for the
    domain list administrator (mailman at domainname.ca) and create one if it
    doesn't exist. But I may not be understanding this properly. What about
    creating a sendmail account called mailman at domainname.ca? Would this
    pre-empt the mail from going to the installation-wide address? If this
    were the case, then the remaining problem would be the aforementioned
    assignment by add_virtualhost. True?

    Thanks again,

    All the best,

    - Henrik

    Mark Sapiro wrote:
    Henrik wrote:
    When I set up a mailing list, the general contact address on the
    mail.mail.domainname.ca/mailman/listinfo page is listed as
    mailman at mail.domainname.ca, rather than mailman at domainname.ca.

    The domain in this address depends on whether or not
    VIRTUAL_HOST_OVERVIEW is set to Yes or No. The default is Yes. If you
    visit the http://www.example.com/mailman/listinfo overview page and
    you see only lists in the www.example.com domain, then it is set to
    Yes. If you see all the advertised lists on the server, then it is set
    to No (in mm_cfg.py).

    So, if VIRTUAL_HOST_OVERVIEW is set to No, the domain in the site list
    address is the result of looking up DEFAULT_URL_HOST in the
    VIRTUAL_HOSTS dictionary - i.e. it is the second argument from

    add_virtualhost(DEFAULT_URL_HOST, xxx)

    from mm_cfg.py (normally this is DEFAULT_EMAIL_HOST).

    If VIRTUAL_HOST_OVERVIEW is set to Yes, the domain is the result of
    looking up the host domain from the URL used to access the page.

    In your case, assuming no typo above even though it looks strange,
    there is an entry in mm_cfg.py like

    add_virtualhost('mail.mail.domainname.ca', 'mail.domainname.ca')

    that should be

    add_virtualhost('mail.mail.domainname.ca', 'domainname.ca')

    instead.

    There is another possibility. This add_virtualhost entry also affects
    your own lists. Is the domain 'mail.domainname.ca' the correct domain
    for mailing to your lists? If so, you don't want to change the
    add_virtualhost entry; you need to add an alias or whatever to the MTA
    for your domain for the mailman list.

    On the third hand, I visited the listinfo page on the server at
    ns38.servepower.com, and it appears to be a cPanel mailman so I relly
    don't have a clue. See
    <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.011.htp>.


    When I send a test email to mailman at mail.domainname.ca I get a bounce
    back with this message:

    This is an automatically generated Delivery Status Notification.

    Delivery to the following recipients failed.

    mailman at mail.domainname


    When I send a test email to mailman at domainname.ca I get a bounce back
    with this message:

    You are not allowed to post to this mailing list, and your message has
    been automatically rejected. If you think that your messages are
    being rejected in error, contact the mailing list owner at mailman-owner at ns38.servepower.com.


    I presume this is a configuration issue. Unfortunately I do not have
    access on the configuration server, and the webserve.ca support people
    seem to be at a loss as to what to do.

    You get the above message because the installation has only one site
    list (mailman) for all supported domains and it is configured to
    reject posts from non-members

    Yet, since this is presumably a cPanel Mailman, if it is the case that
    the domain for mail to your lists IS mail.domainname.ca, you may be
    able to solve the whole problem by just creating a 'mailman' list in
    your own domain.


    Judging from the fact that python's own mail list page uses
    mailman at python.org, I presume that the issue is faulty configuration of
    the general list contact address in the configuration file.

    Could someone explain to me how this can be fixed, so that I can pass it on?

    If the above doesn't do it, let us know what else you need.
    --

    Henrik Bechmann
    www.osscommons.ca
    www.bechmannsoftware.com
    Webmaster, www.dufferinpark.ca
  • Mark Sapiro at Dec 9, 2006 at 3:06 am

    Henrik wrote:
    If VIRTUAL_HOST_OVERVIEW is set to Yes, the domain is the result of
    looking up the host domain from the URL used to access the page.

    This appears to be the case:

    In fact if I access the page with mail.domainname.ca/mailman/, the
    contact address is mailman at mail.domainname.ca, whereas if I access the
    page with domainname.ca/mailman/listinfo (ie without the "mail."
    subdomain), the contact address shows as mailman at domainname.ca.

    Actually, my description in that reply was incomplete. I should have
    added to the above

    "and if the host domain is not a key in VIRTUAL_HOSTS, the host domain
    itself is used"

    Reading the domain from the URL is desirable as I have a number of
    domain names associated with the account, and wish to have mailing lists
    set up for all or most of them. But is seems like what should be used is
    something like (in totally pseudo regex, I have no idea what the syntax
    is in python)

    add_virtualhost('/(mail\.)?(*.)/', '$2')

    You need to do one of two things:

    Either have one canonical host name per domain for web access, enforced
    if necessary with rewrite rules in the web server, and then have one

    add_virtualhost('web host name', 'corresponding email domain')

    for each domain.

    Or have two (assuming the email domain should be 'example.com')

    add_virtualhost('example.com', 'example.com')
    add_virtualhost('mail.example.com', 'example.com')

    Note that it is OK to have two entries with the same email host if the
    web hosts are different, but you can't have two entries with the same
    web host as the second just replaces the first.

    Is this true? What would the entry look like? (I don't unfortunately
    have access to mm_cfg.py - is it in principle possible to have a
    mm_cfg.py for a user of a linux system -- ie for a web account). I would
    have to pass this on to the web host.

    There is one mm_cfg.py for the whole mailman installation. The only way
    around this is to run separate instances of Mailman for separate
    domains.

    Then the other problem would appear to be that the default mail address
    (mailman at domainnname.ca) is not set up properly on creation of the mail
    list.

    It is not an attribute of the list at all. The local part is the name
    of the site list and the domain is determined as above. This is all
    determined on the fly when the listinfo page is sent.


    Yet, since this is presumably a cPanel Mailman, if it is the case that
    the domain for mail to your lists IS mail.domainname.ca, you may be
    able to solve the whole problem by just creating a 'mailman' list in
    your own domain.


    Sorry, don't quite get that. You mean create a list called
    mailman at domainname.ca, and this would pre-empt the central installation
    routing? And just make the list private, with only the owner as a
    recipient?

    Well, I didn't have enough information (and I still don't because I'm
    shooting in the dark and don't know how cPanel does this), but I
    thought your lists might be in the mail.domainname.ca domain and not
    the domainname.ca domain. In that case, I was pretty sure you could
    have created a mailman at mail.domainname.ca list. You may still be able
    to create a mailman at domainname.ca list which would override the site
    list for your domain.

    I don't know if it would work or not, but the worst that can happen is
    it won't create the list, or it will but mail will still go to the
    site list.

    This is an interesting possibility, though if I understand it
    right, the proper solution would be to have the mail list installation
    process check sendmail for the existence of a default address for the
    domain list administrator (mailman at domainname.ca) and create one if it
    doesn't exist. But I may not be understanding this properly. What about
    creating a sendmail account called mailman at domainname.ca? Would this
    pre-empt the mail from going to the installation-wide address?

    It might. You could try that.

    If this
    were the case, then the remaining problem would be the aforementioned
    assignment by add_virtualhost. True?

    I think so.

    --
    Mark Sapiro <msapiro at value.net> The highway is for gamblers,
    San Francisco Bay Area, California better use your sense - B. Dylan

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupmailman-users @
categoriespython
postedDec 8, '06 at 8:19p
activeDec 9, '06 at 3:06a
posts4
users2
websitelist.org

2 users in discussion

Henrik: 2 posts Mark Sapiro: 2 posts

People

Translate

site design / logo © 2022 Grokbase