Barry S. Finkel writes:
> The ">" in front of "From " in message bodies IS REQUIRED.
Only by the archive builder.
Specifically, AFAIK you are correct, Pipermail will split an mbox to
messages on any line matching "^From ", and leave any ">From " lines
in the resulting archive. There are two wa
On 05/10/2013 01:54 PM, Mark Sapiro wrote:
> On 05/10/2013 09:18 AM, Xie, Wei wrote:
>>
>> In the file Defaults.py, I see ARCHIVE_TO_MBOX = 2.
>
>
> That is the normal default meaning archive to moth pipermail and mbox.
s/moth/both/
--
Mark Sapiro The highway is for gamblers,
San Fran
On 05/10/2013 09:18 AM, Xie, Wei wrote:
>
> In the file Defaults.py, I see ARCHIVE_TO_MBOX = 2.
That is the normal default meaning archive to moth pipermail and mbox.
> Also, archiving for other mailing lists work well including
> creating/updating LISTNAME.mbox/LISTNAME.mbox file.
>
> The
On 5/10/2013 3:18 PM, Barry S. Finkel wrote:
The ">" in front of "From " in message bodies IS REQUIRED.
Of course it's required -- as long as the file is serving as a real
mbox. That's why I put the ">" back in before having Mailman index the
files for the archives of the new lists. ("Undo
On 5/10/2013 10:27 AM, Larry Kuenning wrote, in part:
Fortunately my old archives were already in mbox format. Or rather,
almost in mbox format. The old incarnation of my lists had been on a
server where I had a low usage quota, so I had been downloading all
archives over a year old and storing
Mark,
>>> If ARCHIVE_TO_MBOX is set to 0 in mm_cfg.py, Mailman will not create/update
>>> LISTNAME.mbox/LISTNAME.mbox files.
In the file mm_cfg.py, there is no ARCHIVE_TO_MBOX setting. There are ONLY
following two parameters related to archive.
ARCHIVE_HTML_SANITIZER = 1
DEFAULT_ARCHIVE = Off
On 05/10/2013 08:27 AM, Larry Kuenning wrote:
>
> Moral: You can import old mbox files to a Mailman archive, but be sure
> to clean up the headers before you generate the index.
Yes, that's what bin/arch was designed for.
Also, there is a bin/cleanarch tool, but all it does is look for
unescap
This is not a request for help but a report of experience in case
someone else finds it helpful.
I recently migrated some old mailing lists into Mailman. They had
previously run on different software (my own), and at first I assumed
I'd need to keep two sets of archives, putting the old ones
On 05/10/2013 06:35 AM, Xie, Wei wrote:
>
> Here we have one customer to request migrating all old archived files of
> mailing list ‘kinejapan’ under directory
> /usr/local/mailman/archives/private/kinejapan prior to 2009 (as attached
> file) to Yale university. Yale university IT guys needs us t
On 05/10/2013 12:36 AM, KEY5 wrote:
>
> Now I've put the sender's address in the "hold_these_nonmembers" list
> and I solved. (Admin > Privacy options > Sender filters )
> yet I do not know the reason of the problem but fortunately it's not a
> problem anymore.
Of all the reasons I gave in my pr
On 05/10/2013 07:53 AM, Larry Kuenning wrote:
> On 5/10/2013 9:03 AM, I wrote:
>
>> If this creates valid files, will Postfix start using the new
>> versions immediately, or do I need to do something else to draw its
>> attention to the changes?
>
> After updating transport.db and virtual.db, and
On 05/10/2013 06:03 AM, Larry Kuenning wrote:
> On 5/9/2013 9:43 PM, Mark Sapiro wrote:
>
>> If those plain text files aren't in the same directory, they are
>> somewhere, but I can't imagine why they're not there. You might try
>> locate or find to find them.
>
> They're not there, or anywhere e
On 5/10/2013 9:03 AM, I wrote:
My current idea is to add "mailman" lines similar to all the "test"
lines in transport and virtual and then update transport.db and
virtual.db with postmap. (After first making backups of the current
> forms!)
I tried this and it works: I can now post to the s
On 5/9/2013 9:43 PM, Mark Sapiro wrote:
There should be both an aliases (plain text) and an aliases.db
(database) and likewise for virtual(.db) and transport(.db). The .db
files are made from the plain text files by the Postfix commands
postalias in the case of aliases and postmap in the case of
On 5/9/2013 10:00 PM, David Benfell wrote:
It looks like the relevant commands are postalias (which I've never
used, at least by that name) and postmap.
Thanks! Actually I ran across postalias and postmap a couple of hours
before I saw your post, but it's nice to have this confirmed by someo
I found the message and it was discarded without expressed reason.
I've read this can happen in many cases.
Maybe it's because the sender's address domain is different from the
incoming smtp request.
Now I've put the sender's address in the "hold_these_nonmembers" list
and I solved. (Admin > Priva
16 matches
Mail list logo
