Re: [Mailman-Users] pending subscription to list "mailman"

[Jim Popovitch via Mailman-Users]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On Mon, 2018-06-11 at 12:21 -0700, Mark Sapiro wrote:
> On 6/11/18 10:26 AM, Jim Popovitch via Mailman-Users wrote:
> > 
> > For some unknown reason a legitimate human sent a subscribe request
> > to 
> > mailman-subscr...@domain.tld and now I'm receiving pending
> > subscriber
> > notifications for the "mailman" list, which isn't a list with an
> > available web interface.  Is there a cmd line way to discard
> > pending
> > subscribers?
> 
> Why do you think there's no web interface. Have you tried going to
> http(s)://any.of.your.domains/admindb/mailman/ ?

There's no web interface on domain.tld because it's the backend domain
that's hosting virtual lists.

Using one of the virtual domains, as you described, works to show the
pending sub request, but Submit action is based on mlist settings
(domain.tld) so the submit never occurs.

> There are a couple of scripts at ,
> namely 'erase' and 'list_requests' that can do the discard.

Perfect, thanks!

> 
> > Also, should the mailman/data/aliases.db even contain aliases for
> > the
> > mailman list?
> 
> 
> The address mail...@domain.tld is exposed in both the listinfo and
> admin
> overview pages as a place for questions. Also,
> mailman-boun...@domain.tld is the envelope sender of password
> reminders
> and some owner notices and some MTA configurations don't accept
> outging
> mail that isn't from a deliverable address, although I think this is
> mostly an Exim issue and Exim doesn't use aliases.
> 
> Also, if you don't put a MAILTO in Mailman's crontab, any errors from
> Mailman's crons will be sent to mail...@domain.tld.
> 
> For all these reasons, I recommend setting up the 'mailman' list with
> the Mailman site admins as owners and members and setting
> generic_nonmember_action to accept.
> 
> Anyway, the short answer to "should the mailman/data/aliases.db even
> contain aliases for the mailman list?" is Yes, but if it makes sense
> in
> your installation to remove them, you can.

I'm going to leave them but disable (comment out) the
subscribe/join/etc ones.

Thanks for the help!

- -Jim P.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPxwe8uYBnqxkbORSJxVetMRaJwUFAlsezVMACgkQJxVetMRa
JwVhrg/+NT5FhIwJzONvxuERO5KFPGKz4lYm0ofCEbvagu7YXaxMrU8u8obhb0ho
+pNyPpWSOM41Hk4Bkkwna0bSEakhDQV6NZcfwvvVB4lg39bbpEfYrZ/J/4hYhMwg
huTn4zYvH5mojJnRslRGODgTNQFJ6/mnitvuqvsYUVg1BuuAmL6FcExCTjCFUqcQ
a6YnWgKgvD3ij0innOCn/yyrafJ0yEHwjs2h3NWbUGd+wPKNSY6pPv8vt8ltujnw
ZCUj+Jd96+ihBdw9VSH1mUPzi8MHbFcOX3I4ULeldt9WrvQMofI5l6gU1bzp1qFq
3ISjENRfy7uCO6KDeJozxnJfpS90PP8Og1VWFQWH2/39Dw8TxeDCfsiRtf5fVtEL
HcHzxOjn4h73g4kdphaBuDJnlP12sECzViqEXCpzMJuj5kGP+n5iz6NUSTy89ysC
HSGQrY2WpuIan5XEBxVFOMbRNczOaZ4hulNP6/T212XezvAzwRDAkrMiJndhHZ6v
x6KkEkCI7tqjUJSa7KzpaWrjTwWwP/LXBZKuI0Y9cxgvAQMNbqy6grrRzn5VChje
INv+/vHCboMrhKdHoJjPWlNk3uuiRcj/YaUIJc0V+864G9jlJ1dTZNrR6JQIltJ+
SIYpDAKkRrhwRx60YtSBBGGQcVushHCiYjeNgJmNW5BjFFPeKok=
=rp6+
-END PGP 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] pending subscription to list "mailman"

[Mark Sapiro]

On 6/11/18 10:26 AM, Jim Popovitch via Mailman-Users wrote:
> 
> For some unknown reason a legitimate human sent a subscribe request to 
> mailman-subscr...@domain.tld and now I'm receiving pending subscriber
> notifications for the "mailman" list, which isn't a list with an
> available web interface.  Is there a cmd line way to discard pending
> subscribers?

Why do you think there's no web interface. Have you tried going to
http(s)://any.of.your.domains/admindb/mailman/ ?

There are a couple of scripts at ,
namely 'erase' and 'list_requests' that can do the discard.


> Also, should the mailman/data/aliases.db even contain aliases for the
> mailman list?


The address mail...@domain.tld is exposed in both the listinfo and admin
overview pages as a place for questions. Also,
mailman-boun...@domain.tld is the envelope sender of password reminders
and some owner notices and some MTA configurations don't accept outging
mail that isn't from a deliverable address, although I think this is
mostly an Exim issue and Exim doesn't use aliases.

Also, if you don't put a MAILTO in Mailman's crontab, any errors from
Mailman's crons will be sent to mail...@domain.tld.

For all these reasons, I recommend setting up the 'mailman' list with
the Mailman site admins as owners and members and setting
generic_nonmember_action to accept.

Anyway, the short answer to "should the mailman/data/aliases.db even
contain aliases for the mailman list?" is Yes, but if it makes sense in
your installation to remove them, you can.


-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan



signature.asc
Description: OpenPGP digital 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

[Mailman-Users] pending subscription to list "mailman"

[Jim Popovitch via Mailman-Users]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hello,

For some unknown reason a legitimate human sent a subscribe request to 
mailman-subscr...@domain.tld and now I'm receiving pending subscriber
notifications for the "mailman" list, which isn't a list with an
available web interface.  Is there a cmd line way to discard pending
subscribers?

Also, should the mailman/data/aliases.db even contain aliases for the
mailman list?

tia,

- -Jim P.
-BEGIN PGP SIGNATURE-

iQIzBAEBCgAdFiEEPxwe8uYBnqxkbORSJxVetMRaJwUFAlsesNcACgkQJxVetMRa
JwVVCw//bsx0xZaY/9ypdkkhf/+zNEGB0i4yauLogAsZyeGaWz/CS2oCrlei6Ghm
0f95MdCBAegtbkRizQP0iMmYOsUmyul0K/22Cp8UJiHegqeMvsA99yvMgREiuhck
nMDg1A+7s2yYy7VaZw390OMMWnfB23zjfGUQqvuGhR21mK8HyygxEYtzXK4jj2Sf
n1EiEc9+UxiVIK27ZhiCkSm0jY5OJ5GaQpCV9KJ7x1cEn33suIzUwksiXvWeHJNu
YgQ5tUZcY9f1Vk/iF6h5dcR05N+Dj3afnwp0p8SHesOlep2zwyIeH2UD2EbvuFTv
dOlDpjspnhhbMzm2m1A+bDZaNd2wlBoC7Hzdm7Zru9LjuZtEz90HQvgAcD3rNEUj
AtH1U/CKrmC9quDQFZPGdhzqIo3svFyJgF9havCYdUq3Dyt+FP6nVIR/D+amRWZQ
CMrtAiyMJUPMdtj3UnsuZ3dH8VJSpxIf2nx0ztOhLGhIJcSs4aVe0dJ8iFwOaB/C
3rwtpJ9FDWyr2K2AQ8js7eepHQpp6ccxqkdC/D1E5L7bmPAz+HaBrNBeGACpFUn/
+uy0HlA1r4UC80Jx76Tl1sf1IVmEiI3JdZCjnDkIbhWilfwZ0OHub8YV/MuMyTdI
dlExCvR95DGJMCOMUdVTKQNI3jZPORC3zX04YAvcRVvcWUrwSXM=
=ScFr
-END PGP 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] Migrating Mailman to New Server (Same Domain)

[Mark Sapiro]

On 6/11/18 4:36 AM, Jeffrey Rolland wrote:
> I tried using your script. The tar_list.sh script works fine. But, for the
> untar_list.sh script, I had two fairly big problems.


Where did you find these scripts? They are not distributed by the GNU
mailman project.


> 1) the mailman user account did not have a home director or shell; I fixed
> those problems handily.


If your new server has a Debian/Ubuntu Mailman package, the Mailman user
is 'list', not 'mailman'.


> 2) I got a ton of permission/owner errors trying to untar the archives. The
> private archives on the new server appeared to have been owned by root,
> while the public archives appeared to be owned by www.-data; neither
> untar-ed well with the script being owned by mailman.


The best way to move archives is to just move the
archives/private/.mbox/.mbox file from the old
server to the new and then run Mailman's

bin/arch --wipe 

on the new server. See .

-- 
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] Migrating Mailman to New Server (Same Domain)

[Jeffrey Rolland]

I tried using your script. The tar_list.sh script works fine. But, for the
untar_list.sh script, I had two fairly big problems.

1) the mailman user account did not have a home director or shell; I fixed
those problems handily.

2) I got a ton of permission/owner errors trying to untar the archives. The
private archives on the new server appeared to have been owned by root,
while the public archives appeared to be owned by www.-data; neither
untar-ed well with the script being owned by mailman.

Can you help? I'd really like to migrate my server today, and this is my
last task before switching over the firewall exceptions to the new server's
inside-NAT IP address.

Thanks much in advance.

Sincerely,
-- 
Jeffrey Rolland


"The weed of crime bears bitter fruit; crime does NOT pay! The Shadow
knows!"
 - The Shadow, _The Shadow_ (1994)

 -BEGIN GEEK CODE BLOCK-
Version: 3.1
GM d-- s:+ a+ C++>$ UL+>$
P? L+++>+$ E--- W+++>$ N+++>+++$ o? K--? !w--- !O !M- !V-- PS++
PE- Y? PGP+++ t+++ 5? X+ R+>$ tv++ !b DI+++>+ !D G+ e$ h+ r--
y++
--END GEEK CODE BLOCK--

FWIW, I've done two complete migrations of a number of mailman (v2)
lists as I've changed servers over the past few years. A couple of
scripts I've used have worked perfectly in every case. In every
migration, the basic Mailman installation is set up and running on the
new server. Mailman versions, as long as we're talking about v2.x.x,
are a no-nevermind.

The first, which runs on the old server is called tar_list.sh, is kept
in /usr/local/sbin and is run as root:

#!/bin/sh
if [ "$1" = "" ]; then
echo 'Usage: tar_list.sh '
exit
fi

if [ ! -e /var/lib/mailman/lists/$1 ]; then
echo "$1: No such list!"
exit
fi

mkdir /tmp/$1
cd /var/lib/mailman/lists/

echo Creating $1_list.tar.gz 
tar -czvf $1_list.tar.gz $1
mv $1_list.tar.gz /tmp/$1

cd /var/lib/mailman/archives/private/

echo Creating $1_archive.tar.gz 
tar -czvf $1_archive.tar.gz $1
mv  $1_archive.tar.gz /tmp/$1

echo Creating $1_archive_mbox.tar.gz 
tar -czvf $1_archive_mbox.tar.gz $1.mbox
mv $1_archive_mbox.tar.gz /tmp/$1

if [ -L /var/lib/mailman/archives/public/$1 ]; then
touch /tmp/$1/$1_archive_is_public
fi

The second script, on the new server, lives in ~mailman/bin and is run
as the mailman user (which, on my server, has a real, usable shell):

#!/bin/sh
if [ "$2" = "" ]; then
echo 'Usage: untar_list.sh  '
exit
fi

cd ~/tmp/
echo "Give root password on remote system ..."
scp root@$1:/tmp/$2/* .
cd /var/lib/mailman/lists/

echo ""
echo "Creating list $2 ..."
tar -xzvpf ~/tmp/$2_list.tar.gz

cd /var/lib/mailman/archives/private/

echo ""
echo "Creating archive for $2 ..."
tar --same-owner -xzvpf ~/tmp/$2_archive.tar.gz

echo "Creating archive mbox for $1 ..."
tar --same-owner -xzvpf ~/tmp/$2_archive_mbox.tar.gz

if [ -e ~/tmp/$2_archive_is_public ]; then
ln -s /var/lib/mailman/archives/private/$2
/var/lib/mailman/archives/public/$2
fi

echo""
echo "If no errors, delete files in ~/tmp and delete /tmp/$2
directory on remote system"

This does require (and this may be a show-stopper for some) that the
mailman user on the new system be able to ssh to the old server as
root. I'm sure there's an easy workaround for this, but since I've
always has full root access to my servers and run connections between
servers via encrypted VPNs, it's been simply a matter of modifying the
sshd_config file to allow this
--
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