[Mailman-Users] listhost vs hostname vs host_name

[Will]

Mark Sapiro wrote:
> Will wrote:
>   
>> so we have an automated setup between a CMS forum and mailman to create 
>> lists, having a little confusion about what values to pass config_list
>>
>> trying to understand what these three values govern: listhost vs 
>> hostname vs host_name
>>     
>
>
> See the FAQ at <http://wiki.list.org/x/lYA9>.
>
> I don't know what 'listhost' or 'hostname' are. They are not list
> attributes. If you are referring to something specific in the
> documentation, you'll have to tell me what, and I can then translate
> it for you.
>
>   
sorry I think i mixed myself up and confused listhost for emailhost
> host_name is a list attribute that is described if the above referenced
> FAQ and which is set directly from the -e option to bin/newlist.
>
>   

really? that doesn't seem to be the case. I'm creating a list with 
newlist and passing the subdomain value with -e and it only seems to set 
the emailhost value. which works for setting the domain name properly on 
some portions of the email like to address, but list-bounces@ and tpls 
have the host_name wrong. its not until I set the host_name with 
config_list that the subdomain is properly set everywhere.

I do have things working now. but I got it working by setting both -e 
and host_name in a config file passed to config_list.

thanks for your help!
>> right now we set -e emailhost via newlist, this has resulted in some 
>> incorrect data displaying in emails. this seems to set the listhost 
>> value but not host_name or hostname.
>>     
>
>
> Actually, it sets host_name, and as I said, I don't know what
> 'listhost' and 'hostname' are.
>
>
>   
>> we are attaching all lists to a subdomain. so like somelist at sub.domain.com
>>
>> emails from the lists setup however are coming from 
>> somelist-bounces at domain.com and in the emails the post to email address 
>> is give as somelist at domain.com.
>>     
>
>
> Both those domains come directly from the host_name attribute.
>
>
>   
>> postfix and mailman however are working find at accepting emails to 
>> somelist at sub.domain.com and processing them through the lists.
>>
>> so I thought, hmm... maybe we need to set hostname to 'sub.domain.com'. 
>> but I also see that the templates for emails have 2 different hostname 
>> params: hostname and host_name.
>>     
>
>
> What a template refers to as 'hostname' can be anything. For example,
> the 'hostname' substitution in cronpass.txt (the monthly password
> reminder) is either the list's host_name or it is DEFAULT_EMAIL_HOST
> depending on the setting of VIRTUAL_HOST_OVERVIEW. In most other
> cases, it is the list's host_name.
>
>
>   
>> can someone explain the differences between all there and how to get our 
>> list configurations right using the commandline commands for our 
>> subdomained lists?
>>     
>
>
> First you have to get mm_cfg.py correct. See the initial part of the
> FAQ at <http://wiki.list.org/x/gIA9>. Then you should be able to
> create new lists with bin/newlist without specifying -u or -e, and the
> defaults should be good.
>
>
>   
>> oh PS - is there a command also to patch our existing lists to set the 
>> host name values correctly. thanks
>>     
>
>
>  bin/withlist -l -a -r fix_url
>
> run
>
>  bin/fix_url.py
>
> and/or search the FAQ for fix_url for more information.
>
>