On 2/14/20 9:11 AM, Dennis Putnam wrote:
> Hi Mark,
>
> I guess there needs to be a caveat in the documentation indicating
> different distros will need different commands. This project is turning
> into a nightmare since I know nothing about django and they way mailman
> 3 is installed is
Hi Mark,
I guess there needs to be a caveat in the documentation indicating
different distros will need different commands. This project is turning
into a nightmare since I know nothing about django and they way mailman
3 is installed is radically different. Hyperkitty was installed but when
I
On 2/14/20 7:49 AM, Dennis Putnam wrote:
> Hi Mark,
>
> Another issue with these servers. The admin says 'pip3' was used to
> install mailman. I thought 'pip' was a python installer.
Some distros call pip for Python 3 pip3.
> Unfortunately I
> cannot find where it put the stuff. So the
On 2/14/20 7:09 AM, Dennis Putnam wrote:
> Hi Mark,
>
> Just a little confusing with respect to the documentation which says:
>
> python manage.py hyperkitty_import -l foo-l...@example.com
> $var_prefix/archives/private/foo-list.mbox/foo-list.mbo
>
>
> So the documentation should say for some
Hi Mark,
Another issue with these servers. The admin says 'pip3' was used to
install mailman. I thought 'pip' was a python installer. Unfortunately I
cannot find where it put the stuff. So the documentation that specifies
$prefix is of no use since I don't know what that is. This is RHEL so
does
Hi Mark,
Just a little confusing with respect to the documentation which says:
python manage.py hyperkitty_import -l foo-l...@example.com
$var_prefix/archives/private/foo-list.mbox/foo-list.mbo
So the documentation should say for some installations:
django-admin hyperkitty_import -l
On 2/13/20 11:36 AM, Dennis Putnam wrote:
> Hi Mark,
>
> Sorry for being a PITA but I can't find manage.py. Indeed I can't find
> any mailman files other than in /opt/mailman which has no /bin.
> Apparently version 3 uses different directories than what I've been
> using (/usr/lib/Mailman and
Hi Mark,
Sorry for being a PITA but I can't find manage.py. Indeed I can't find
any mailman files other than in /opt/mailman which has no /bin.
Apparently version 3 uses different directories than what I've been
using (/usr/lib/Mailman and /var/lib/mailman).
signature.asc
Description: OpenPGP
Hi Mark,
For some reason the first 'create' didn't work even though it said
successful. The 2nd on did and the import worked.
On 2/13/2020 12:09 PM, Mark Sapiro wrote:
> On 2/13/20 8:40 AM, Dennis Putnam wrote:
>> Hi Mark,
>>
>> I'm stuck on the 2nd step.
>>
>> I did:
>>
>> mailman create
On 2/13/20 8:40 AM, Dennis Putnam wrote:
> Hi Mark,
>
> I'm stuck on the 2nd step.
>
> I did:
>
> mailman create rusht...@csdco.com
>
> Got no errors.
Good.
>
> I'm on the new server, copied the pickle file from the old server to the
> current directory and used the command:
>
> mailman
Hi Mark,
I'm stuck on the 2nd step.
I did:
mailman create rusht...@csdco.com
Got no errors.
I'm on the new server, copied the pickle file from the old server to the
current directory and used the command:
mailman import21 rusht...@csdco.com config.pck
I get: Error: No such list:
On 2/13/20 3:17 AM, Dennis Putnam wrote:
> Hi Mark,
>
> I've been thrown into this so I am unfamiliar with these servers (not my
> own that I usually deal with). Anyway, as I unravel things I'm working
> with, I see that I am really running version 2.1.9. As I understand it,
> the DMARC
Hi Mark,
I've been thrown into this so I am unfamiliar with these servers (not my
own that I usually deal with). Anyway, as I unravel things I'm working
with, I see that I am really running version 2.1.9. As I understand it,
the DMARC mitigation was not added until 2.1.18. So I think using
On 2/12/20 9:06 AM, Dennis Putnam wrote:
> Hi Mark,
>
> We finally got the networking folks to cooperate so DNS is the way we
> will go. I don't know if it makes any difference but the version was a
> typo, we are at 2.0.x.
If you really mean your current Mailman is 2.0.x, trying to import to MM
Hi Mark,
We finally got the networking folks to cooperate so DNS is the way we
will go. I don't know if it makes any difference but the version was a
typo, we are at 2.0.x.
Please see embedded comments.
On 2/12/2020 11:42 AM, Mark Sapiro wrote:
> On 2/12/20 6:06 AM, Dennis Putnam wrote:
>> Hi
On 2/12/2020 6:06 AM, Dennis Putnam wrote:
Since we don't have access to change DNS it seems
the easiest thing to do is change their hostnames and IP addresses. If
there is a better way I am interested.
It's not a better-or-worse choice, it's the _only_ choice. If the users are
sending to the
On 2/12/20 6:06 AM, Dennis Putnam wrote:
> Hi Mark,
>
> Those are the ones I have been reading. I guess what I need to do is a
> little more complicated than I posted. The old server is running v 2.1
> and we are running into DEMARC issues. Since we need to upgrade anyway
> we have upgraded a new
Hi Mark,
Those are the ones I have been reading. I guess what I need to do is a
little more complicated than I posted. The old server is running v 2.1
and we are running into DEMARC issues. Since we need to upgrade anyway
we have upgraded a new server to the latest RHEL version and mailman
3.3.
Hi Robert,
Thanks for the reply. I have no access to DNS which is why the old
server needs to be shutdown and the new server renamed the same as the
old server and the IP address changed to match. I have root access to
the mailman server. I'll reply to Mark's message with more detail.
On
At Tue, 11 Feb 2020 14:42:15 -0500 Dennis Putnam wrote:
>
>
>
> Content-Language: en-US
>
> I've been reading up on migrating to a new server but I'm not sure I am
> reading the right instructions. It seems that copying the lists to the
> new server is one thing but it appears that the end
On 2/11/20 11:42 AM, Dennis Putnam wrote:
> I've been reading up on migrating to a new server but I'm not sure I am
> reading the right instructions. It seems that copying the lists to the
> new server is one thing but it appears that the end result means the
> users will have to use a new list
I've been reading up on migrating to a new server but I'm not sure I am
reading the right instructions. It seems that copying the lists to the
new server is one thing but it appears that the end result means the
users will have to use a new list server. That is, if users were
emailing
On 03/09/2017 08:20 AM, Greg Sims wrote:
>
> I have an issue and have run out of ideas.
>
> [root@ray06 log]# cat /var/log/maillog.processed /var/log/maillog | grep
> 'Mar 9' | grep status=sent | wc
>6176 109377 1554218
>
> The above looks at our maillogs for email that was sent on Mar 9.
I recently migrated from RHEL 6 to CentOS 7. The migration seemed to be
straight-forward by:
- creating three mailman lists
- for each of the list directories
- copy files from the old to new server
- list options and membership seems good
I have an issue and have run out of
On Thu, Jun 14, 2007 at 05:03:29PM -0700, Mark Sapiro wrote:
The directories you need to rsync are Mailman's lists/ and
archives/private/ directories. If you're concerned about held
Ok, good, that's easy enough.
messages, you can also do the data/ directory, but it may be better to
I need to build a new mailman server. What is the best/easiest way to
migrate lists (and their archives) to the new machine? Something that
used rsync would be nice so I could keep things as up to date as possible
and then do a final rsync right before the migration.
This is definitely
Brian Hechinger wrote:
I need to build a new mailman server. What is the best/easiest way to
migrate lists (and their archives) to the new machine? Something that
used rsync would be nice so I could keep things as up to date as possible
and then do a final rsync right before the migration.
Aaron Crosman wrote:
The archives problem persists. You gave me the right place to look here
as well. The archives are all owned by list (group list), but the
private archives have restricted access that blocks other users from
getting in:
ls of /var/lib/mailman/archives:
drwxrws--- 200 list
-Original Message-
From: Mark Sapiro [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 26, 2007 10:31 PM
To: Aaron Crosman; mailman-users@python.org
Subject: Re: [Mailman-Users] Server migration problems
- Original Message ---
Subject: [Mailman-Users] Server
Hi All--
On 4/27/07, Aaron Crosman [EMAIL PROTECTED] wrote:
Apache's error log:
[Fri Apr 27 11:42:14 2007] [error] [client 172.17.201.205] Symbolic link
not allowed or link target not accessible:
/var/lib/mailman/archives/public/itd_test, referer:
http://server.org/mailman/listinfo/itd_test
I know this comes up all the time, but having carefully reviewed the FAQ
and archives, I still haven't been able to solve my problem.
I'm working on migrating my mailman setup from an old SuSE server to a
new Debian (4.0) server. For the most part everything has gone
smoothly, but the
- Original Message ---
Subject: [Mailman-Users] Server migration problems
From: Aaron Crosman [EMAIL PROTECTED]
Date: Thu, 26 Apr 2007 14:22:19 -0400
To: mailman-users@python.org
I know this comes up all the time, but having carefully reviewed the FAQ
and archives, I
--On March 19, 2007 6:19:00 PM -0700 Mark Sapiro [EMAIL PROTECTED] wrote:
Presumably the new installation is a 2.1.x installation, not 2.0.x, so
you can't just move the queue entries because they're not compatible
(in 2.1 there is a single .pck file per msg as opposed to the 2.0 .db
and .msg
33 matches
Mail list logo
