Re: [Mailman-Users] Prevent users from changing email address

2019-04-23 Thread Grant Taylor via Mailman-Users 

On 4/23/19 5:02 AM, Kiffin Gish wrote:
Is it possible to configure mailman so that it is not possible for users 
to change their email address, e.g. disabling the option and including 
the service desk contact information instead?


What will prevent users from unsubscribing with the old address and 
resubscribing with the new address?




--
Grant. . . .
unix || die



smime.p7s
Description: S/MIME Cryptographic Signature
--
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/archive%40jab.org

Re: [Mailman-Users] Prevent users from changing email address

2019-04-23 Thread Mark Sapiro 
On 4/23/19 4:02 AM, Kiffin Gish wrote:
> Is it possible to configure mailman so that it is not possible for users to 
> change their email address, e.g. disabling the option and including the 
> service desk contact information instead?


Had you not just recently posted to this list with a Mailman 3 question,
I would assume this is a Mailman 2.1 question.

Please post Mailman 3 questions to mailman-us...@mailman3.org


Anyway, the answer for either Mailman is "not without modifying the code".

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter 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/archive%40jab.org

Re: [Mailman-Users] Frustrating web page issues

2019-04-23 Thread Mark Sapiro 
On 4/23/19 8:53 AM, Robert Heller wrote:
> At Tue, 23 Apr 2019 09:13:15 -0600 Mark J Bradakis  wrote:
> 
>>
>> Got the new server on line, up and running, the email lists are doing 
>> just fine.  But for some reason there are problems with the web pages, 
>> like http://autox.team.net/mailman/listinfo will not work.  And I don't 
> 
> Define "will not work". Is the page coming up? Giving a 500 or 404 or 403 or
> some other error? Are you just getting a blank screen? Did you have a look at
> Apache's error_log?


The above URL returns:

Service Unavailable

The server is temporarily unable to service your request due to
maintenance downtime or capacity problems. Please try again later.


Have you run Mailman's bin/check_perms? I suspect some kind of
permissions error on the wrappers in /local/mailman/teamnet/cgi-bin/,
but do check Apache's error.log which should have more information.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter 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/archive%40jab.org

Re: [Mailman-Users] REST API user_id and mailman_id are big integers

2019-04-23 Thread Kiffin Gish 

Thanks, using v3.1 instead of v3.0 solved my problems!

You might want to check the docs where 3.0 is still being used.

--
Kiffin Gish
Gouda, The Netherlands

On 4/23/19 6:35 AM, Mark Sapiro wrote:

On 4/22/19 1:18 AM, Kiffin Gish wrote:

I'm implementing a frontend for accessing the mailman-core via the REST
interface.


This list is primarily for support of Mailman 2.1. While some of us who
read this list are also involved with Mailman 3, some Mailman 3
developers do not read this list.

The preferred lists for Mailman 3 are mailman-us...@mailman3.org

and mailman-develop...@python.org
.



Two problems arise, and both are related to the fact that in the json
response the mailman_id and the user_id are big integers.

As the values are greater than the maximum json integer format they
appear as exponential values with the last digits truncated.


I don't see this. Perhaps you can give specific url's that return these
large integers.

I see things like:

curl -urestadmin:restpass http://localhost:9001/3.1/users
{"entries": [{"created_on": "2005-08-01T07:49:23", "http_etag":
"\"2bf857a70410d149964152eb539a9f2e65167589\"", "is_server_owner":
false, "self_link":
"http://localhost:9001/3.1/users/0001";,
"user_id": "0001"}], "http_etag":
"\"8b70aea0b2faf3427ee675a899bbfe01bd35940b\"", "start": 0, "total_size": 1}

and

curl -urestadmin:restpass http://localhost:9001/3.0/users
{"entries": [{"created_on": "2005-08-01T07:49:23", "http_etag":
"\"eb591d9720aa0ac944b49315b6af1c950410b54c\"", "is_server_owner":
false, "self_link": "http://localhost:9001/3.0/users/1";, "user_id": 1}],
"http_etag": "\"cf73b75814e4f44e603170b39d65b5120218e52e\"", "start": 0,
"total_size": 1}

Granted this installation has only one user and on an installation with
many users, I do see things like

{"created_on": "2019-04-23T01:28:24.579274", "is_server_owner": false,
"self_link":
"http://localhost:8001/3.0/users/163692196465132998753332423763098956585";,
"user_id": 163692196465132998753332423763098956585, "password":
"elided", "http_etag": "\"be49870d5d7cb722fc9e6852ed6a62a83efa088d\""}

with a large integer for user_id with API 3.0, but with API 3.1, I get a
string

{"created_on": "2019-04-23T01:28:24.579274", "is_server_owner": false,
"self_link":
"http://localhost:8001/3.1/users/7b25f8647f6343efac82f831674d7329";,
"user_id": "7b25f8647f6343efac82f831674d7329", "password": "elided",
"http_etag": "\"a4c24cd3178e9d9c2361eb011496911f2fd12951\""}



I was just wondering if there is a proper way to handle this and/or it
is possible for the REST API to return these values as strings rather
than numbers.


Are you using API 3.1. If not, try it.


--
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/archive%40jab.org

Re: [Mailman-Users] Frustrating web page issues

2019-04-23 Thread Robert Heller 
At Tue, 23 Apr 2019 09:13:15 -0600 Mark J Bradakis  wrote:

> 
> So a couple of days ago I had a server just up and die.  It was put in 
> place about 12 years ago, if not more.  Luckily I was working on 
> replacing it, so I had  a new box under construction almost ready to 
> take its place.  But the old server dies before I could make a smooth 
> transition and get everything working on the new server.
> 
> Got the new server on line, up and running, the email lists are doing 
> just fine.  But for some reason there are problems with the web pages, 
> like http://autox.team.net/mailman/listinfo will not work.  And I don't 

Define "will not work". Is the page coming up? Giving a 500 or 404 or 403 or
some other error? Are you just getting a blank screen? Did you have a look at
Apache's error_log?

Some posibilities (guesses):

What version of Python is installed?  2 or 3?

What are the mailman settings WRT domain names?  Do they match the new 
server's domain name (eg is the new server's domain the same or different from 
the old server)?

Is selinux installed? Enabled? Permissive?

> know why.  Here's the relevant lines from the httpd config file:
> 
> 
> ScriptAlias /mailman/ "/local/mailman/teamnet/cgi-bin/"
> 
> 
>            Require all granted
>            Options ExecCGI
> 
> 
> 
> This was enough to work on the old server.  New server is Fedora 29, 
> mailman version is mailman-2.1.29, Apache: Server version: Apache/2.4.39 
> (Fedora)  I have gone over the mailman installation instructions, and 
> can't figure out what is going on.  I must be missing something really 
> basic and obvious, but what?  Maybe I am just getting old and senile, I  
> solved problems like this for a quarter of a century as a sys admin at 
> the U of Utah Computer Science department, must be really rusty and out 
> of practice.
> 
> Fun fun fun.
> 
> mjb.
> 
> 
> --
> 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/heller%40deepsoft.com
> 
> 

-- 
Robert Heller -- 978-544-6933
Deepwoods Software-- Custom Software Services
http://www.deepsoft.com/  -- Linux Administration Services
hel...@deepsoft.com   -- Webhosting Services
   
--
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/archive%40jab.org

[Mailman-Users] Frustrating web page issues

2019-04-23 Thread Mark J Bradakis via Mailman-Users 
So a couple of days ago I had a server just up and die.  It was put in 
place about 12 years ago, if not more.  Luckily I was working on 
replacing it, so I had  a new box under construction almost ready to 
take its place.  But the old server dies before I could make a smooth 
transition and get everything working on the new server.


Got the new server on line, up and running, the email lists are doing 
just fine.  But for some reason there are problems with the web pages, 
like http://autox.team.net/mailman/listinfo will not work.  And I don't 
know why.  Here's the relevant lines from the httpd config file:



ScriptAlias /mailman/ "/local/mailman/teamnet/cgi-bin/"


  Require all granted
  Options ExecCGI



This was enough to work on the old server.  New server is Fedora 29, 
mailman version is mailman-2.1.29, Apache: Server version: Apache/2.4.39 
(Fedora)  I have gone over the mailman installation instructions, and 
can't figure out what is going on.  I must be missing something really 
basic and obvious, but what?  Maybe I am just getting old and senile, I  
solved problems like this for a quarter of a century as a sys admin at 
the U of Utah Computer Science department, must be really rusty and out 
of practice.


Fun fun fun.

mjb.


--
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/archive%40jab.org

[Mailman-Users] Prevent users from changing email address

2019-04-23 Thread Kiffin Gish 
Is it possible to configure mailman so that it is not possible for users to 
change their email address, e.g. disabling the option and including the service 
desk contact information instead?
--
Kiffin Gish 
Gouda, The Netherlands
--
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/archive%40jab.org