Re: [Mailman-Users] Mailman on Google App
Unless Google App Engine has changed recently, it cannot receive any mail at all. So you need to move your mailing list software to someplace else, mailman friendly. There is no hope of doing what you want.
Sorry about that, Laura Creighton
Hi,
Thanks for your quick reply; then is it possible to continue run a Mailman server and still have my email move to Google App. Thanks!
On Wed, Feb 4, 2015 at 1:42 PM, Laura Creighton <lac@openend.se> wrote:
Unless Google App Engine has changed recently, it cannot receive any mail at all. So you need to move your mailing list software to someplace else, mailman friendly. There is no hope of doing what you want.
Sorry about that, Laura Creighton
On 02/04/2015 01:50 PM, cha charle wrote:
Thanks for your quick reply; then is it possible to continue run a Mailman server and still have my email move to Google App. Thanks!
As long as the domain in which you have your email lists is distinct from, perhaps a subdomain of, your main domain, e.g. lists.example.com or mm.example.com where the main domain is example.com, it should be no problem to have a separate MX for that domain pointing to the Mailman server.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark,
Thank you so much for the suggestion, and will give it a try; however, my question is: how do I point to the new subdomain though.
Now, my domain is example.com( for mails and Maillman), and will create a subdomain list.example.com, just for mailman; and the example.com will move to Google app. Once the process is done, what do I need to do in Mailman to change all my current lists to the new subdomain, list.example.com though? Once again, thanks for your help.
On Wed, Feb 4, 2015 at 7:36 PM, Mark Sapiro <mark@msapiro.net> wrote:
On 02/04/2015 01:50 PM, cha charle wrote:
Thanks for your quick reply; then is it possible to continue run a
Mailman
server and still have my email move to Google App. Thanks!
As long as the domain in which you have your email lists is distinct from, perhaps a subdomain of, your main domain, e.g. lists.example.com or mm.example.com where the main domain is example.com, it should be no problem to have a separate MX for that domain pointing to the Mailman server.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: https://mail.python.org/mailman/options/mailman-users/subads%40gmail.com
On 02/06/2015 08:27 AM, cha charle wrote:
Now, my domain is example.com <http://example.com>( for mails and Maillman), and will create a subdomain list.example.com <http://list.example.com>, just for mailman; and the example.com <http://example.com> will move to Google app. Once the process is done, what do I need to do in Mailman to change all my current lists to the new subdomain, list.example.com <http://list.example.com> though? Once again, thanks for your help.
At a minimum, you need an A record in DNS for lists.example.com with the server's IP address.
In Mailman, it depends what you have in mm_cfg.py currently. If you have something like
DEFAULT_EMAIL_HOST = 'example.com' DEFAULT_URL_HOST = 'example.com' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
you want to change the first two lines to
DEFAULT_EMAIL_HOST = 'list.example.com' DEFAULT_URL_HOST = 'list.example.com'
If you have nothing in mm_cfg.py, add
DEFAULT_EMAIL_HOST = 'list.example.com' DEFAULT_URL_HOST = 'list.example.com' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
You can also add
VIRTUAL_HOSTS.clear()
ahead of any add_virtualhost line(s) to remove whatever was put there by Defaults.py.
Then you need to run fix_url to fix your lists. See the FAQs at <http://wiki.list.org/x/4030592> and <http://wiki.list.org/x/4030616>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mark,
Thank you very much for all the detailed information.
On Fri, Feb 6, 2015 at 2:39 PM, Mark Sapiro <mark@msapiro.net> wrote:
On 02/06/2015 08:27 AM, cha charle wrote:
Now, my domain is example.com <http://example.com>( for mails and Maillman), and will create a subdomain list.example.com <http://list.example.com>, just for mailman; and the example.com <http://example.com> will move to Google app. Once the process is done, what do I need to do in Mailman to change all my current lists to the new subdomain, list.example.com <http://list.example.com> though? Once again, thanks for your help.
At a minimum, you need an A record in DNS for lists.example.com with the server's IP address.
In Mailman, it depends what you have in mm_cfg.py currently. If you have something like
DEFAULT_EMAIL_HOST = 'example.com' DEFAULT_URL_HOST = 'example.com' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
you want to change the first two lines to
DEFAULT_EMAIL_HOST = 'list.example.com' DEFAULT_URL_HOST = 'list.example.com'
If you have nothing in mm_cfg.py, add
DEFAULT_EMAIL_HOST = 'list.example.com' DEFAULT_URL_HOST = 'list.example.com' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
You can also add
VIRTUAL_HOSTS.clear()
ahead of any add_virtualhost line(s) to remove whatever was put there by Defaults.py.
Then you need to run fix_url to fix your lists. See the FAQs at <http://wiki.list.org/x/4030592> and <http://wiki.list.org/x/4030616>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
cha charle -
Laura Creighton -
Mark Sapiro