Eino Tuominen wrote:
Mark Sapiro wrote:
The log you posted previously seems to say the MTA delivering to
Mailman is 'middleman'. I don't know anything at all about this MTA.
Another hint in a prior post tells me it may have some programatic way
(rather than aliases) for determining
I can't find it in the FAQ or listname-request help dialogue, but I thought
there's a way to approve held messages by replying to the notice that I have
held messages? Tnx - John
--
Mailman-Users mailing list
Mailman-Users@python.org
John Fleming wrote:
I can't find it in the FAQ or listname-request help dialogue, but I thought
there's a way to approve held messages by replying to the notice that I have
held messages? Tnx - John
There is no way to approve messaged by replying to the summary 'nn
listname moderator
I have a Mailman 2.1.9 list where the membership is re-built from
an external source. The list contains all of the occupants of a
certain building who list an e-mail address in the Human Resources
Database. I assumed that anyone on the list should be able to post
to the list, but the building IT
* Barry Finkel [EMAIL PROTECTED]:
Note that I cannot easily turn off the moderated bit on the
moderators' e-mail addresses, as the list is rebuilt nightly from the
HR Database.
How do you rebuild the list?
Do you use symc_members? Or do you remove everybody and add them later?
--
Ralf
* Ralf Hildebrandt [EMAIL PROTECTED]:
* Barry Finkel [EMAIL PROTECTED]:
Note that I cannot easily turn off the moderated bit on the
moderators' e-mail addresses, as the list is rebuilt nightly from the
HR Database.
How do you rebuild the list?
Do you use symc_members? Or do you remove
Mark Sapiro wrote:
James Dinkel wrote:
For some reason our archive web pages try to display attachments inline
instead of displaying a link to download the attachment. If I
understand correctly, this process is called scrubbing. From what
I've read the default behavior is to scrub
Barry Finkel wrote:
We added some moderator e-mail addresses via the administrative
web page, and we set a moderator password. There is one minor
problem: the moderators are set to those persons whom we want to
be able to post to the list (e.g., the building manager). But those
moderators are
I want to make sure some lists are definitely not used before deleting
them. To temporarily disable a list, is moving the list directory
(/home/mailman/lists/list_name) to a temporary directory an acceptable
solution or is there a better way to go about this?
Thanks you,
--
Robin D.
James Dinkel wrote:
They have all been pdf files. Will it not scrub pdf files? I don't
exactly know what the
MIME Content-Type: is.
For purposes of the scrubber, MIME Content-Type: is the value of the
Content-Type: header of the respective MIME message part.
PDF attachments should be
Robin Bartholomew wrote:
I want to make sure some lists are definitely not used before deleting
them. To temporarily disable a list, is moving the list directory
(/home/mailman/lists/list_name) to a temporary directory an acceptable
solution or is there a better way to go about this?
If you
On May 7, 2007, at 10:44 AM, Robin Bartholomew wrote:
I want to make sure some lists are definitely not used before deleting
them. To temporarily disable a list, is moving the list directory
(/home/mailman/lists/list_name) to a temporary directory an acceptable
solution or is there a better
I wrote:
Note that I cannot easily turn off the moderated bit on the
moderators' e-mail addresses, as the list is rebuilt nightly from the
HR Database.
and Ralf Hildebrand replied:
How do you rebuild the list?
Do you use symc_members? Or do you remove everybody and add them later?
I meant
* Barry Finkel [EMAIL PROTECTED]:
We sync our lists like this:
bin/sync_members -w=no -g=no -d=no -a=no -f
file_with_membership_addresses.txt name_of_list
I use
./remove_members --all --nouserack --noadminack $destfile
./add_members -w n -r $destdir/$destfile
because I
On May 7, 2007, at 11:15 AM, Barry Finkel wrote:
Ralf Hildebrand replied:
We sync our lists like this:
bin/sync_members -w=no -g=no -d=no -a=no -f
file_with_membership_addresses.txt name_of_list
I use
./remove_members --all --nouserack --noadminack $destfile
./add_members -w n
We have a fairly large list (more than 26,000 subscribers), and recently it
appears a very small fraction of the subscribers have started receiving
duplicate messages -- sometimes as many as a dozen or more. This behavior
just started happening within the last couple of weeks, and it seems to only
* Jason LaMar [EMAIL PROTECTED]:
We have a fairly large list (more than 26,000 subscribers), and recently it
appears a very small fraction of the subscribers have started receiving
duplicate messages -- sometimes as many as a dozen or more. This behavior
just started happening within the last
Jason LaMar wrote:
We have a fairly large list (more than 26,000 subscribers), and recently it
appears a very small fraction of the subscribers have started receiving
duplicate messages -- sometimes as many as a dozen or more. This behavior
just started happening within the last couple of weeks,
Dragon wrote:
Far more likely is that the subscribers are getting multiple copies
of replies to their posts or they have filter rules that are copying
the posts instead of moving them.
End original message. -
That didn't come out exactly how I meant it.
What
-- Jason LaMar wrote:
-- We have a fairly large list (more than 26,000 subscribers), and recently it
-- appears a very small fraction of the subscribers have started receiving
-- duplicate messages -- sometimes as many as a dozen or more. This behavior
-- just started happening within the last
Dragon wrote:
Are you committed to Red Hat's way of doing things? If you don't
really care about their file hierarchy system, I would suggest
dumping the RPM and compiling from source yourself.
Even if you do care about FHS, you can still install from source.
RedHat's FHS patch is attached to
21 matches
Mail list logo
