![](https://secure.gravatar.com/avatar/55dd4b9d4dca2dc661df666477622d76.jpg?s=120&d=mm&r=g)
I am trying to submit an admin request (rejecting an email) but when I click "submit" it times out. I don't see anything in the log file (maybe I need to look somewhere else). Restarting the service does not help nor does rebooting the system. The status appears to me to be correct:
$ sudo service mailman status Redirecting to /bin/systemctl status mailman.service ● mailman.service - GNU Mailing List Manager Loaded: loaded (/usr/lib/systemd/system/mailman.service; enabled; vendor preset: disabled) Active: active (running) since Thu 2024-04-18 12:21:44 EDT; 4 days ago Process: 1143 ExecStart=/usr/lib/mailman/bin/mailmanctl -s start (code=exited, status=0/SUCCESS) Process: 1126 ExecStartPre=/bin/chmod 660 /var/log/mailman/error (code=exited, status=0/SUCCESS) Process: 1123 ExecStartPre=/bin/chown mailman:mailman /var/log/mailman/error (code=exited, status= 0/SUCCESS) Process: 1119 ExecStartPre=/bin/touch /var/log/mailman/error (code=exited, status=0/SUCCESS) Process: 1097 ExecStartPre=/usr/bin/install -m644 -o root -g root /usr/lib/mailman/cron/crontab.in /etc/cron.d/mailman (code=exited, status=0/SUCCESS) Process: 830 ExecStartPre=/usr/lib/mailman/bin/mailman-update-cfg (code=exited, status=0/SUCCESS) Main PID: 1842 (mailmanctl) Tasks: 9 CGroup: /system.slice/mailman.service ├─1842 /usr/bin/python2 /usr/lib/mailman/bin/mailmanctl -s start ├─1892 /usr/bin/python2 /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s ├─1893 /usr/bin/python2 /usr/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s ├─1894 /usr/bin/python2 /usr/lib/mailman/bin/qrunner --runner=CommandRunner:0:1 -s ├─1895 /usr/bin/python2 /usr/lib/mailman/bin/qrunner --runner=IncomingRunner:0:1 -s ├─1896 /usr/bin/python2 /usr/lib/mailman/bin/qrunner --runner=NewsRunner:0:1 -s ├─1897 /usr/bin/python2 /usr/lib/mailman/bin/qrunner --runner=OutgoingRunner:0:1 -s ├─1898 /usr/bin/python2 /usr/lib/mailman/bin/qrunner --runner=VirginRunner:0:1 -s └─1899 /usr/bin/python2 /usr/lib/mailman/bin/qrunner --runner=RetryRunner:0:1 -s
Apr 18 11:21:19 dap002 systemd[1]: Starting GNU Mailing List Manager... Apr 18 12:21:44 dap002 mailmanctl[1143]: Starting Mailman's master qrunner. Apr 18 12:21:44 dap002 systemd[1]: Started GNU Mailing List Manager.
How do I find out what is going on? Any help would be appreciated.
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 4/23/24 06:55, Dennis Putnam wrote:
Look in the logs of your web server.
Look at the source of the admindb page you are trying to submit. In particular you are looking for a FORM tag like
<FORM action="some URL" method="POST" >
Does that URL look correct? If not see lines 67-95 at https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/...
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/55dd4b9d4dca2dc661df666477622d76.jpg?s=120&d=mm&r=g)
On 4/23/2024 2:31 PM, Mark Sapiro wrote:
Hi Mark,
It looks right to me. This is all I see:
192.168.0.196 - - [24/Apr/2024:11:30:03 -0400] "GET /mailman/admindb/cufsalumni HTTP/1.1" 200 2091 192.168.0.196 - - [24/Apr/2024:11:30:03 -0400] "GET /favicon.ico HTTP/1.1" 200 5882 192.168.0.196 - - [24/Apr/2024:11:30:05 -0400] "POST /mailman/admindb/cufsalumni HTTP/1.1" 200 6964
Is it possible the database is not responding? But if that were the case I wouldn't get the administrative request page, right?
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 4/24/24 08:36, Dennis Putnam wrote:
Your POST gets a 200 status. If it doesn't update it's most likely because the URL is http and is being redirected to https and losing the POST data. See https://wiki.list.org/x/4030602 - you need to ensure the scheme in DEFAULT_URL_PATTERN is https, not http.
Although that said, I don't know why that would cause a timeout.
Again, look at the source of the admindb page in your web browser. Look for
<FORM action="http(s)://mailman/admindb/cufsalumni" method="POST" >
If the scheme is http, the above applies and you need to set
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
in mm_cfg.py
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/55dd4b9d4dca2dc661df666477622d76.jpg?s=120&d=mm&r=g)
On 4/24/2024 6:22 PM, Mark Sapiro wrote:
Hi Mark,
I figured out the issue and the URL is basically correct. The bottom line is that an AT&T router is blocking my IP for some reason. How to fix it is another problem as I don't expect AT&T to do anything about it. Not sure when this started.
Anyway, here is the issue. I don't have a static IP address so I am using dyndns-ip.com. Most of the links on the admin page uses just 'dap002' as the URL host which uses only the LAN. However, the submit and a couple of other links use dyndns-ip.com in the URL which sends it out over the WAN. I never had a problem with that until now. It has been eons since I've configured mailman so I've pretty much forgotten what/how I did it. I guess for the admin pages only, I need to make all the links just dap002 since I only access them on the LAN. The public pages still need to use dyndns-ip.com in the URL. Is there a way to do that?
Even if AT&T fixes the problem it would still be better if all the admin stuff is done only on the LAN.
Thanks.
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 4/27/24 11:03, Dennis Putnam wrote:
You could try creating a file containing only the line
web_page_url = 'http://dap002/LISTNAME/'
and then running Mailman's
bin/config_list -i path/to/that/file LISTNAME
This will probably work, but may have undesired effects such as trying to post to that URL from a public page. You just have to try it and see.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 4/23/24 06:55, Dennis Putnam wrote:
Look in the logs of your web server.
Look at the source of the admindb page you are trying to submit. In particular you are looking for a FORM tag like
<FORM action="some URL" method="POST" >
Does that URL look correct? If not see lines 67-95 at https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/Mailman/...
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/55dd4b9d4dca2dc661df666477622d76.jpg?s=120&d=mm&r=g)
On 4/23/2024 2:31 PM, Mark Sapiro wrote:
Hi Mark,
It looks right to me. This is all I see:
192.168.0.196 - - [24/Apr/2024:11:30:03 -0400] "GET /mailman/admindb/cufsalumni HTTP/1.1" 200 2091 192.168.0.196 - - [24/Apr/2024:11:30:03 -0400] "GET /favicon.ico HTTP/1.1" 200 5882 192.168.0.196 - - [24/Apr/2024:11:30:05 -0400] "POST /mailman/admindb/cufsalumni HTTP/1.1" 200 6964
Is it possible the database is not responding? But if that were the case I wouldn't get the administrative request page, right?
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 4/24/24 08:36, Dennis Putnam wrote:
Your POST gets a 200 status. If it doesn't update it's most likely because the URL is http and is being redirected to https and losing the POST data. See https://wiki.list.org/x/4030602 - you need to ensure the scheme in DEFAULT_URL_PATTERN is https, not http.
Although that said, I don't know why that would cause a timeout.
Again, look at the source of the admindb page in your web browser. Look for
<FORM action="http(s)://mailman/admindb/cufsalumni" method="POST" >
If the scheme is http, the above applies and you need to set
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
in mm_cfg.py
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
![](https://secure.gravatar.com/avatar/55dd4b9d4dca2dc661df666477622d76.jpg?s=120&d=mm&r=g)
On 4/24/2024 6:22 PM, Mark Sapiro wrote:
Hi Mark,
I figured out the issue and the URL is basically correct. The bottom line is that an AT&T router is blocking my IP for some reason. How to fix it is another problem as I don't expect AT&T to do anything about it. Not sure when this started.
Anyway, here is the issue. I don't have a static IP address so I am using dyndns-ip.com. Most of the links on the admin page uses just 'dap002' as the URL host which uses only the LAN. However, the submit and a couple of other links use dyndns-ip.com in the URL which sends it out over the WAN. I never had a problem with that until now. It has been eons since I've configured mailman so I've pretty much forgotten what/how I did it. I guess for the admin pages only, I need to make all the links just dap002 since I only access them on the LAN. The public pages still need to use dyndns-ip.com in the URL. Is there a way to do that?
Even if AT&T fixes the problem it would still be better if all the admin stuff is done only on the LAN.
Thanks.
![](https://secure.gravatar.com/avatar/56f108518d7ee2544412cc80978e3182.jpg?s=120&d=mm&r=g)
On 4/27/24 11:03, Dennis Putnam wrote:
You could try creating a file containing only the line
web_page_url = 'http://dap002/LISTNAME/'
and then running Mailman's
bin/config_list -i path/to/that/file LISTNAME
This will probably work, but may have undesired effects such as trying to post to that URL from a public page. You just have to try it and see.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (2)
-
Dennis Putnam
-
Mark Sapiro