mailman with fetchmail, ISP smtp, blocked port 80

Dear Folks,
I have just moved to a new ISP which blocks ports 80, 25 incoming.
I have hosted (and hope to continue to host) two mailing lists, which worked fine till the change.
I also have access to a web server pointed to by dns A record nicku.org on which I cannot install mailman, but on which I can install redirects, use mod_rewrite, and configure apache on. Postfix listens on port 25 on www3.nicku.org and can send mail via ISP mail server. An MX record for nicku.org points to mail.nicku.org, which in turn points as an A record to an email hosting service. www3.nicku.org is the new address of this machine hosting mailman.
I would like to ask:
- Any suggestions on a good way to configure mailman in this situation? My current method (dns points to this machine, www3.nicku.org, apache listening on port 8080, redirect from remote nicku.org to www3.nicku.org:8080) seems not right yet; attempts to click on the "Submit All Data" button on the admindb page just return the same page, without any apparent action having taken place.
- I am running fetchmail as root, with a .fetchmailrc as shown below. Does that look correct? Any suggestions?
- the /var/log/mailman/smtp-failure log shows multiple (failed) attempts to send mail to fetchmail-daemon@www3.nicku.org; how do I persuade mailman to send to the correct address?
- Are there any special settings I need for mailman to match this arrangement better? Currently the changes to my mm_cfg.py are: DEFAULT_URL_HOST = 'www3.nicku.org:8080' DEFAULT_EMAIL_HOST = 'nicku.org' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
Note that people access the web pages via http://nicku.org/mailman/listinfo/camwest-discuss and http://nicku.org/mailman/listinfo/camwest-announce.
set daemon 180 set syslog set postmaster nicku set no bouncemail set no spambounce
poll mail.nicku.org proto pop3 user user01 pass passwordxxx is nicku here user user02 pass passwordxxx is auser here user user03 pass passwordxxx is anotheruser here user user04 pass passwordxxx is mailman here user user05 pass passwordxxx is mailman-admin here user user06 pass passwordxxx is camwest-announce here user user07 pass passwordxxx is camwest-discuss here user user08 pass passwordxxx is camwest-announce-admin here user user09 pass passwordxxx is camwest-announce-bounces here user user10 pass passwordxxx is camwest-announce-confirm here user user11 pass passwordxxx is camwest-announce-join here user user12 pass passwordxxx is camwest-announce-leave here user user13 pass passwordxxx is camwest-announce-owner here user user14 pass passwordxxx is camwest-announce-request here user user15 pass passwordxxx is camwest-announce-subscribe here user user16 pass passwordxxx is camwest-announce-unsubscribe here user user17 pass passwordxxx is camwest-discuss-admin here user user18 pass passwordxxx is camwest-discuss-bounces here user user19 pass passwordxxx is camwest-discuss-confirm here user user20 pass passwordxxx is camwest-discuss-join here user user21 pass passwordxxx is camwest-discuss-leave here user user22 pass passwordxxx is camwest-discuss-owner here user user23 pass passwordxxx is camwest-discuss-request here user user24 pass passwordxxx is camwest-discuss-subscribe here user user25 pass passwordxxx is camwest-discuss-unsubscribe here
where userxx is the username configured on the email hosting service, to which dns A record mail.nicku.org points.
I will be grateful for any suggestions.
Nick Urbanik http://nicku.org nicku@nicku.org GPG: 7FFA CDC7 5A77 0558 DC7A 790A 16DF EC5B BB9D 2C24 ID: BB9D2C24

Nick Urbanik wrote:
I have just moved to a new ISP which blocks ports 80, 25 incoming.
I have hosted (and hope to continue to host) two mailing lists, which worked fine till the change.
I also have access to a web server pointed to by dns A record nicku.org on which I cannot install mailman, but on which I can install redirects, use mod_rewrite, and configure apache on. Postfix listens on port 25 on www3.nicku.org and can send mail via ISP mail server. An MX record for nicku.org points to mail.nicku.org, which in turn points as an A record to an email hosting service. www3.nicku.org is the new address of this machine hosting mailman.
My head hurts already.
I would like to ask:
- Any suggestions on a good way to configure mailman in this situation? My current method (dns points to this machine, www3.nicku.org, apache listening on port 8080, redirect from remote nicku.org to www3.nicku.org:8080) seems not right yet; attempts to click on the "Submit All Data" button on the admindb page just return the same page, without any apparent action having taken place.
Redirect is probably throwing away the POST data. See <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.045.htp>.
- I am running fetchmail as root, with a .fetchmailrc as shown below. Does that look correct? Any suggestions?
I don't know fetchmail.
- the /var/log/mailman/smtp-failure log shows multiple (failed) attempts to send mail to fetchmail-daemon@www3.nicku.org; how do I persuade mailman to send to the correct address?
SMTPHOST = (and SMTPPORT = if it's not 25) in mm_cfg.py
- Are there any special settings I need for mailman to match this arrangement better? Currently the changes to my mm_cfg.py are: DEFAULT_URL_HOST = 'www3.nicku.org:8080' DEFAULT_EMAIL_HOST = 'nicku.org' add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
This is not what you want. You want
DEFAULT_URL_HOST = 'www3.nicku.org'
and
DEFAULT_URL_PATTERN = 'http://%s:8080/mailman/'
Then you want to run fix_url to update the list attributes. See <http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.069.htp>.
This will get the POST URL's on web forms going directly to the proper server and you won't lose data in the redirects. It will also put 'www3.nicku.org:8080' in visible URLs. If this is a problem because
Note that people access the web pages via http://nicku.org/mailman/listinfo/camwest-discuss and http://nicku.org/mailman/listinfo/camwest-announce.
I don't know a solution, but I'm guessing it's OK because 'www3.nicku.org:8080' already appears in the browser's address bar after redirect.
-- Mark Sapiro <msapiro@value.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Mark Sapiro
-
Nick Urbanik