SUCCESS!!
I changed the archive option to monthly
edited the vorpal-users.mbox file to include the messages desired in
the archive
mv archive/private/vorpal-users to archive/proviate/vorpal-users.save
bin/arch vorpal-users
This created the entire new pipermail archive.
Anne M. Hammond - Sy
Anne Hammond wrote:
>
>I will change the archiving option to Montly for the new archive,
>and then sort through what you have suggested.
If you change to 'monthly' and then rebuild with bin/arch --wipe with a
complete listname.mbox file, the archive will be completely rebuilt
with monthly indexin
Anne Hammond wrote:
>/var/lib/mailman/archives/private/{list}.mbox/{list}.mbox
>
>contains all email messages since inception of the mailing list.
>
>So it should create a new archive containing all of the
>email messages since inception.
I'm not sure what you are saying above, but I think it is
/var/lib/mailman/archives/private/{list}.mbox/{list}.mbox
contains all email messages since inception of the mailing list.
So it should create a new archive containing all of the
email messages since inception.
Anne M. Hammond - Systems / Network Administration - Tech-X Corp
h
Since
/var/lib/mailman/archives/private/vorpal-users.mbox/vorpal-users.mbox
(thanks for the correction)
contains only the 11 messages from the 2006-December archive, what
will happen to all these dirs from
/var/lib/mailman/archives/private/vorpal-users:
drwxrwsr-x2 mailman mailman4096 S
I will implement your latest suggestion.
Here is what I found out. The new email list was implemented
with Quarterly archiving. The old email list had Monthly
archiving.
So when you looked at the web page for the current month,
the messages from today were in "Fourth quarter 2006 Archives
by thr
Anne Hammond wrote:
>The two messages are in
>/var/lib/mailman/archives/private/vorpal-users.mbox.
/var/lib/mailman/archives/private/vorpal-users.mbox or
/var/lib/mailman/archives/private/vorpal-users.mbox/vorpal-users.mbox?
/var/lib/mailman/archives/private/vorpal-users.mbox should be a
direc
The two messages are in
/var/lib/mailman/archives/private/vorpal-users.mbox.
Now here is the problem. I thought this list was created today, but
it turns out that it was created 9.May.2006. There are 9 messages
in vorpal-users.mbox that were there before, with the 2 from today
at the end.
The
Anne Hammond wrote:
>>
>var/log/mailman/error:
>Dec 17 09:33:24 2006 (19861) admin.py access for non-existent list:
>rm05submit
>Dec 17 17:13:52 2006 (22929) No such list "mapa-users":
>Dec 17 18:39:15 2006 (23426) No such list "farsight-users":
>Dec 17 23:11:00 2006 (25598) No such list "mapa-use
Anne Hammond wrote:
>The one thing I didn't do was restart mailman.
>
>The top level directory is owned by apache.mailman--Do I need
>to restart apache??
Apache has nothing to do with archiving. The lists/listname directory
is owned by apache because the list was created via the web interface.
Only 2 posts.
I looked through the headers, and there are not options
not to archive.
Anne M. Hammond - Systems / Network Administration - Tech-X Corp
hammond_at_txcorp.com 720-974-1840
On Fri, 22 Dec 2006, Mark Sapiro wrote:
> Mark Sapiro wrote:
>>
>> It seems like a permis
The one thing I didn't do was restart mailman.
The top level directory is owned by apache.mailman--Do I need
to restart apache??
Thanks for your message.
See other answers inline below.
The list that has been migrated is vorpal-users.
NOT WORKING:
[EMAIL PROTECTED] vorpal-users]# ls -la
total
Mark Sapiro wrote:
>
>It seems like a permissions issue, but that should normally result in
>error log entries and shunted messages.
Have there been many posts to the list or only a few? Is it possible
they all had X-No-Archive: or X-Archive: no headers?
--
Mark Sapiro <[EMAIL PROTECTED]>
Anne Hammond wrote:
>>
>There are no messages in archive/ or shunt/
>
>Other lists are definitely archiving right away.
OK. Archiving in general works and ArchRunner is running (processing
the archive/ queue). No messages are shunted for archiving exceptions.
>There is nothing in /var/log/mailm
Thanks for the message and hints. The archives go back to 2003.
On Fri, 22 Dec 2006, Mark Sapiro wrote:
> Anne Hammond wrote:
>>
>> How can I troubleshoot? I've read the FAQ but didn't find a
>> recipe for migrating to another host (perhaps I should write it :)
>
>
> Are there entries in any of
Anne Hammond wrote:
>
>How can I troubleshoot? I've read the FAQ but didn't find a
>recipe for migrating to another host (perhaps I should write it :)
Are there entries in any of Mailman's qfiles directories - particularly
archive/ and shunt/? Are other lists on this this installation
archiving?
I moved a mailing list from another host.
First on the target host, created a similar list, then used
add_members -f {from list_members on old host} list name.
Then I tarred the archives from the old host,
mv'd /var/lib/mailman/archives/private/list to list.save
untarred the archi
OK. I'm an absolute idiot! I'm very sorry for wasting
your time. You've been absolutely right the whole time
(we both just didn't know it).
So. It never reached the archive runner so it was
never archived. It was successfully sent, but never
through the actual list. I was just using mailman@ as
a
stupidmail4me wrote:
>Yes, the qrunner log shows the shutdown and startup
>from mailmanctl. I've also checked and ToArchive is in
>the pipeline (it's not commented out or changed in any
>conf file). This is why it's so odd.
The patch I posted causes ToArchive to write the 'ToArchive invoked
' me
Yes, the qrunner log shows the shutdown and startup
from mailmanctl. I've also checked and ToArchive is in
the pipeline (it's not commented out or changed in any
conf file). This is why it's so odd.
--- Mark Sapiro <[EMAIL PROTECTED]> wrote:
> stupidmail4me wrote:
>
> >Nothing. It doesn't create
stupidmail4me wrote:
>Nothing. It doesn't create any log and there's no
>appropriate entries in any log.
If you applied the patch and then restarted Mailman and you get no
'debug' log with any messages, either the ToArchive handler is not in
the pipeline, or you're not looking in the right direc
Nothing. It doesn't create any log and there's no
appropriate entries in any log.
I've checked the headers for the delivered messages
and there's no x-archive headers (they're not being
myteriously added).
--- Mark Sapiro <[EMAIL PROTECTED]> wrote:
> stupidmail4me wrote:
>
> >It is set to Yes.
stupidmail4me wrote:
>It is set to Yes.
>
>--- Mark Sapiro <[EMAIL PROTECTED]> wrote:
>
>> Is the list's archive attribute set to Yes?
>> (Archiving Options in the
>> web admin interface)
Apply the attached patch to your mailman installation, restart Mailman,
post a message to the list and repor
It is set to Yes.
--- Mark Sapiro <[EMAIL PROTECTED]> wrote:
> stupidmail4me wrote:
>
> >Nothing in the error logs.
>
>
> Is the list's archive attribute set to Yes?
> (Archiving Options in the
> web admin interface)
>
> --
> Mark Sapiro <[EMAIL PROTECTED]> The highway is
> for gamble
stupidmail4me wrote:
>Nothing in the error logs.
Is the list's archive attribute set to Yes? (Archiving Options in the
web admin interface)
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
---
Nothing in the error logs.
mm_cfg.py:
MTA = None
DEFAULT_URL_PATTERN = 'https://%s/'
DEFAULT_EMAIL_HOST = 'lists.foo.org'
DEFAULT_URL_HOST= 'lists.foo.org'
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
--- Mark Sapiro <[EMAIL PROTECTED]> wrote:
> stu
stupidmail4me wrote:
>Yes, ArchRunner is running...
>30014 ?? I 2:00.15 /usr/local/bin/python2.3
>/usr/local/lib/mailman/bin/qrunner
>--runner=ArchRunner:0:1 -s
>
>But no, there's nothing in qfiles/archive.
Once again, is there anything in Mailman's error log?
Also, are there any setting
Yes, ArchRunner is running...
30014 ?? I 2:00.15 /usr/local/bin/python2.3
/usr/local/lib/mailman/bin/qrunner
--runner=ArchRunner:0:1 -s
But no, there's nothing in qfiles/archive.
--- Mark Sapiro <[EMAIL PROTECTED]> wrote:
> stupidmail4me wrote:
>
> >Mail is sending through
> >the lists a
Mark Sapiro wrote:
>
>Is ArchiveRunner running?
That should be "Is ArchRunner running?". Sorry for any confusion.
--
Mark Sapiro <[EMAIL PROTECTED]> The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
stupidmail4me wrote:
>Mail is sending through
>the lists appropriately, but it's not archiving at
>all. I've checked Defaults.py and mm_cfg.py and the
>list's configuration options and they're all set to
>archive. I've checked permissions in
>/var/spool/archive/* and they appear to be fine (if I
>
I'm running Mailman-2.1.8p0 on an OpenBSD 3.9 box. I
have everything set up correctly (I've installed
successfully using older versions on older versions of
OpenBSD) as far as I can see. Mail is sending through
the lists appropriately, but it's not archiving at
all. I've checked Defaults.py and mm_
We had a problem where Mailman completely broke. We have since restored
it, but it is not archiving the lists' messages to the html page. What
is really strange is that one list's messages are being archived???
Thanks for any help on this.
Nancy
--
Nancy M. Montano|| 224 Cruz Alta Rd,
32 matches
Mail list logo
