'Virtualmin Mailman Mailing Lists' module questions

8 posts / 0 new
Last post
#1 Mon, 12/08/2014 - 12:54
ulrith

'Virtualmin Mailman Mailing Lists' module questions

Hi there!

In process of 'Virtualmin Mailman Mailing Lists' module installation and configuration some questions raised so I spent couple of hours when googling and exploring 20+ pages of this forum search.

It looks like there are several problems with this module which never resolved.

1. List ugly url problem.

There are several posts on this forum in which people complain that default urls for list management is inappropriate:

https://www.virtualmin.com/node/12878#comment-55885

https://www.virtualmin.com/node/8819

https://www.virtualmin.com/node/12727#comment-55931

https://www.virtualmin.com/node/12589#comment-55989

https://www.virtualmin.com/node/33683

I agree that it would be much better to have just lists.domain.tld which can be sent to list users without possible https and 10000 port bad issues.

Could anyone please provide some manual how to do that at last?

(I believe it is possible because of post of Joe:

https://www.virtualmin.com/node/8819#comment-36775 )

2. Yahoo! bad guys problem.

https://www.virtualmin.com/node/32999

https://www.virtualmin.com/node/33167

Are there any suggestions for Centos 6.5 systems with Mailman 2.1.12 last available version? Backports? Manual upgrade?

3. Problem with verification email.

This problem is probably unaware cause there are no mention of it in Google.

When invite new users into the list the message are sent without proper substitution of %(listaddr)s and %(listadmin)s variables (others are substituted correctly).

I would like to ask this questions to 'Virtualmin Mailman Mailing Lists' module administrator/creator but was unable to find any information of he/she/them/it.

Thank you for reading this.

Tue, 12/09/2014 - 04:54
tpnsolutions
tpnsolutions's picture

Hi,

Over the past year and a half as a result of one of my largest clients using Mailman extensively within their business (for which I now manage) I've sort of become a bit of an expert on many of the common issues including installation and general maintenance.

Feel free to drop me a line on Skype to discuss.

Best Regards,
Peter Knowles
TPN Solutions

Email: pknowles@tpnsolutions.com
Phone: 604-229-0715 (new)
Skype: tpnsupport
Website: http://www.tpnsolutions.com
Best Regards,
Peter Knowles | TPN Solutions
Email: pknowles@tpnsolutions.com | Skype: tpnassist
Tue, 12/09/2014 - 06:45 (Reply to #2)
ulrith

Thank you Peter!

Would you be so king to paste here some manual/links to address not only me but other forum users?

Tue, 12/09/2014 - 09:15
tpnsolutions
tpnsolutions's picture

Hi,

In general the manuals are all available at http://list.org. I gather however you may require more assistance if those are not good enough for your needs. Because of this potential, it would not be appropriate for me to dedicate the amount of hours required to assist with your particular needs here on the forums as this would be a billable gig given the nature of it.

Best Regards,
Peter Knowles
TPN Solutions

Email: pknowles@tpnsolutions.com
Phone: 604-229-0715 (new)
Skype: tpnsupport
Website: http://www.tpnsolutions.com
Best Regards,
Peter Knowles | TPN Solutions
Email: pknowles@tpnsolutions.com | Skype: tpnassist
Tue, 12/09/2014 - 09:31
ulrith

list.org manuals are not enough indeed just because we are talking about Virtualmin module not just Mailman itself.

Also I don't have any budget to hire you as an expert, sorry. I would like to use this Support forum for free - as I understand a reason it was created for (and, btw, not for advertisement of any 'expert services')...

Sat, 12/13/2014 - 08:54
ulrith

Okay, there are still no response from module developers/maintainers, so I will post to here my solution of problem 1 (which may be inappropriate or not working for you).

My aim was to change :10000 Virtualmin urls to classic lists.domain.tld but https (SSL) urls. Unfortunately I was unable to find a way to do it within 'Virtualmin Mailman Mailing Lists' module. So I configured Mailman software instead. In my case I don't care if https://domain.tld itself will work in the same way as https://lists.domain.tld (I have no secure content on my domain besides Mailman UI) - so I just've added lists.domain.tld as an alias for the domain.tld. If you need them to be separate please go another way.

1. Edit httpd.conf file.

In this section we need to do the following:

- Remove/comment ugly Virtualmin module redirects

- Add right redirects for SSL virtual host of the domain

- Add redirects for non-secure virtual host of the domain

Here is the example of virtual host section of non-secure domain (port 80) which we need to redirect to secure one:


ServerName domain.tld
...
# New redirect to secure domain:
RewriteCond %{HTTPS} off [NC]
RewriteRule ^/mailman(/.*) https://%{HTTP_HOST}/mailman$1 [L,R=permanent]
# Old Virtualmin redirects which we now comment:
#RedirectMatch /cgi-bin/mailman/([^/\.]*)(.cgi)?(.*) https://domain.tld:10000/virtualmin-mailman/unauthenticated/$1.cgi$3
#RedirectMatch /mailman/([^/\.]*)(.cgi)?(.*) https://domain.tld:10000/virtualmin-mailman/unauthenticated/$1.cgi$3
#Alias /pipermail /var/lib/mailman/archives/public

Here is the new redirect strings for Mailman software which seemingly incompatible with the 'Virtualmin Mailman Mailing Lists' module:


ServerName domain.tld
ServerAlias lists.domain.tld # You have to add lists CNAME record in your domain's DNS to make this work
...
# Some configuration for Mailman archive:

Options FollowSymLinks
AllowOverride None

# New redirects for Mailman on the secure domain:
Alias /pipermail/ /var/lib/mailman/archives/public/
Alias /images/mailman/ /usr/share/images/mailman/
ScriptAlias /admin /usr/lib/mailman/cgi-bin/admin
ScriptAlias /admindb /usr/lib/mailman/cgi-bin/admindb
ScriptAlias /confirm /usr/lib/mailman/cgi-bin/confirm
ScriptAlias /create /usr/lib/mailman/cgi-bin/create
ScriptAlias /edithtml /usr/lib/mailman/cgi-bin/edithtml
ScriptAlias /listinfo /usr/lib/mailman/cgi-bin/listinfo
ScriptAlias /options /usr/lib/mailman/cgi-bin/options
ScriptAlias /private /usr/lib/mailman/cgi-bin/private
ScriptAlias /rmlist /usr/lib/mailman/cgi-bin/rmlist
ScriptAlias /roster /usr/lib/mailman/cgi-bin/roster
ScriptAlias /subscribe /usr/lib/mailman/cgi-bin/subscribe
ScriptAlias /mailman/ /usr/lib/mailman/cgi-bin/

2. Set up new values for Mailman inner variables.

Next we need to edit Mailman config file /etc/mailman/mm_cfg.py:

# Old values should be commented
#DEFAULT_URL_HOST = fqdn
#DEFAULT_EMAIL_HOST = fqdn
# New ones are for SSL UI on lists.domain.tld.
DEFAULT_URL_PATTERN = 'https://%s/'
DEFAULT_URL_HOST = "lists.domain.tld"
DEFAULT_EMAIL_HOST = "domain.tld"
VIRTUAL_HOSTS.clear()

And also put this line into the end of mm_cfg.py for correct archive urls:

PUBLIC_ARCHIVE_URL = 'https://%(hostname)s/pipermail/%(listname)s'

And then apply the configuration with this command in the secure shell:

/usr/lib/mailman/bin/withlist -l -a -r fix_url

Here are couple of pages which helped me:

http://www.howtoforge.com/how-to-install-and-configure-mailman-with-post...

http://wiki.list.org/display/DOC/4.27+Securing+Mailman%27s+web+GUI+by+us...

Sun, 02/15/2015 - 13:20
ulrith

Hi there!

The third problem was related to Russian templates only. I have corrected them, you can download fresh complete Russian translation for 2.1.18-1 version from this page: http://smirnov.la/mailman/

Sun, 02/15/2015 - 13:35
ulrith

Hi again!

This is my last comment to this topic.

In regard to the second problem - Yahoo and AOL new mail policy which use DMARC technology forcing bouncing troubles for Mailman lists - yes, one must upgrade to 2.1.18-1 version to avoid them. This version includes rich features to configure lists against DMARC.

Manual upgrade requires using command prompt to configure and set up lists so I do not recommend to keep using Virtualmin Mailman module at all. It's only useful when run default Mailman version like 2.1.12 which is not good because of reasons discussed above.

I hope someone will find all this findings useful. Thanks.