On 24.10.24 22:09, Mark Sapiro wrote:
On 10/23/24 23:36, v...@spamcop.net wrote:
The only difference the last times is that with curl, the server side
sends the ACK for the request and milliseconds later a PSH,ACK with
the response headers. When it comes internally from mailman it sends
the AC
On 10/24/24 11:01, dgoldsmith--- via Mailman-users wrote:
We finally migrated from Mailman 2.x to a Mailman 3.x several months ago. We
have had some issues with people who are active list members not being able to
login with their user creds and when trying to use the 'Forgot Password' link
t
On 10/23/24 23:36, v...@spamcop.net wrote:
I have tried anything I could think of but I cannot reproduce the issue using
curl as user mailman (or any other for that matter)
Going directly for localhost:8000, using some or all of the headers I can
capture with tcpdump:
```
$ curl -v -H 'Accep
We finally migrated from Mailman 2.x to a Mailman 3.x several months ago. We
have had some issues with people who are active list members not being able to
login with their user creds and when trying to use the 'Forgot Password' link
to reset, being told their user account does not exist. They
Mark Sapiro wrote:
> On 10/23/24 13:23, Gerald Vogt wrote:
> > I don't quite understand the relevance of the user accessing the
> > localhost tcp port. Any local user can do that.
> I am trying to duplicate what Mailman does in an attempt to find the issue.
> > I can access the template content wit
