Opened 5 years ago

Closed 23 months ago

#2123 closed task (fixed)

Mailman error: You must GET the form before submitting it.

Reported by: neteler Owned by: sac@…
Priority: normal Milestone:
Component: Systems Admin Keywords: mailman
Cc: Jeff McKenna

Description

Some colleagues of mine tried to subscribe to an OSGeo List recently and ran into this error:

grass-user Subscription results
You must GET the form before submitting it.

Problem: no error message provided nor their susbscription actually issued.

The forms (Name, Email, double password) were filled in.

In /var/log/mailman/* I cannot identify a related error.

What might be missing?

Change History (6)

comment:1 by Jeff McKenna, 5 years ago

If the colleagues work under the same roof, I bet they are hitting this issue: https://bugs.launchpad.net/mailman/+bug/1447445 where load balancing causes them to get the subscription page with one IP and then try to submit with another IP. Here is a related discussion, where they found that in the logs: https://mail.python.org/pipermail/mailman-users/2015-April/078966.html

I think we should upgrade Mailman.

Do you agree?

comment:2 by Jeff McKenna, 5 years ago

Cc: Jeff McKenna added

in reply to:  1 comment:3 by neteler, 5 years ago

Replying to Jeff McKenna:

If the colleagues work under the same roof, I bet they are hitting this issue: https://bugs.launchpad.net/mailman/+bug/1447445 where load balancing causes them to get the subscription page with one IP and then try to submit with another IP.

You nailed it!

Here is a related discussion, where they found that in the logs: https://mail.python.org/pipermail/mailman-users/2015-April/078966.html

I think we should upgrade Mailman.

Do you agree?

If that would solve the problem, yes.

comment:4 by Jeff McKenna, 5 years ago

This was fixed in the mailman 2.1.21 release (OSGeo mailman is 2.1.20, released in year 2015).

comment:5 by strk, 2 years ago

Ticket for updating Mailman: #2174

comment:6 by strk, 23 months ago

Resolution: fixed
Status: newclosed

We're now running 2.1.34 so this should be fixed now. Feel free to reopen if you still have problems.

Note: See TracTickets for help on using tickets.