Todd Zullinger writes:
Nothing wrong with that. It's why open source is so nice. I have the
choice to find vendors and projects that share more of my values than
others may. If FHS compliance is really important to you, you'll like
the Red Hat mailman packages.
The problem is that
I'm sure this is a FAQ someplace but couldn't find anything relevant.
I've got an existing Mailman 2.1.9/Pipermail setup with the ht://Dig
integration set up, and several mailing lists using it - all with their
own existing archives using the built-in Pipermail.
I've been asked to take over some
Hello,
I am stuck with the following strange problem. I am using Debian/testing
and Exim4. Now I want to use Mailman for sending preprint announcements of
our institute. Using apt-get install was unfortunately not sufficient,
so I followed the instructions in README.Debian.Exim4 doing some
We're deploying mailman to deliver information to a lot of people (1200
suscribers). The suscribers can't post to the list.
We need to receive a notification that the suscribers had received the mail.
We where thinking in adding a header that makes the mail client return an
automatic answer.
Any
We want to discard posting mail users from certain domains. And we can't
achieve that using regular expressions. As far as we´ve read on the
documentation this is supposed to be posible, but we can´t find the way.
Thanks in advance
--
On 06-12-14, at 22:40, Brad Knowles wrote:
At 10:59 PM -0400 12/13/06, Pierre Igot wrote:
http://www.python.org/cgi-bin/faqw-mm.py?
req=showfile=faq01.021.htp
I am aware of this page and checked it before sending my request for
help. The page didn't provide any information that
Brad Knowles wrote:
At 11:35 AM -0500 12/14/06, Ryan Steele wrote:
Yes, I realize this. But, there's no reason for the log to indicate
that [EMAIL PROTECTED]
was being considered as an indiscernable address.
That's not quite what happened. Let's go back to an earlier message,
where
Hello,
I have now found the problem: the file virtual-mailman was not updated
correctly (I don't know why) when creating a new list. Only the lines for
the testit mailing list were in this file (maybe from earlier trials?).
Putting there the lines for recognizing mylist by hand made everything
Stephen J. Turnbull wrote:
Todd Zullinger writes:
Nothing wrong with that. It's why open source is so nice. I have
the choice to find vendors and projects that share more of my
values than others may. If FHS compliance is really important to
you, you'll like the Red Hat mailman
Thanks to Mark, Brad, and the rest who have lent their input. I have
one more question though, hopefully with an easy answer I'm simply not
seeing.
I've got a Mailman installation that was built on box A. Box A's
default domain is the .priv domain, but that domain is only visible to
the
Nicolas Neuss wrote:
I have now found the problem: the file virtual-mailman was not updated
correctly (I don't know why) when creating a new list. Only the lines for
the testit mailing list were in this file (maybe from earlier trials?).
Putting there the lines for recognizing mylist by hand
Andres Tarallo wrote:
We need to receive a notification that the suscribers had received the mail.
We where thinking in adding a header that makes the mail client return an
automatic answer.
Don't do it. It is totally unreliable, and only serves to annoy people.
No matter what Header(s) you
Mark Sapiro wrote:
Anne Ramey wrote:
Mark Sapiro wrote:
If the bad addresses don't appear in list_members (I don't know why
they wouldn't, but maybe they just appear with the control characters
that you don't see and thus look OK) you can do
bin/list_members listname |
Andres Tarallo wrote:
We want to discard posting mail users from certain domains. And we can't
achieve that using regular expressions. As far as we've read on the
documentation this is supposed to be posible, but we can't find the way.
In Privacy options...-Sender
Ryan Steele wrote:
I've got a Mailman installation that was built on box A. Box A's
default domain is the .priv domain, but that domain is only visible to
the internal network. So, box A's internal domain is .priv to all the
internal boxes; to the external boxes, it's A.foo.com.
This can
Hello ALL,
I've googled for this but cant find anything in regards to this issue.
After new posts are shown on our Archives at school by secretaries,most
users webbrowsers do not detect newly added messages to the list archives
until they do an F5 to refresh their webbrowser. I m sure there is a
Barry Cisna wrote:
Hello ALL,
I've googled for this but cant find anything in regards to this issue.
After new posts are shown on our Archives at school by secretaries,most
users webbrowsers do not detect newly added messages to the list archives
until they do an F5 to refresh their webbrowser. I
Anne Ramey wrote:
Mark Sapiro wrote:
Try this one
bin/list_members -i listname | bin/remove_members -f - -n listname
If that doesn't work, see http://veenet.value.net/~msapiro/scripts/
or http://fog.ccsf.edu/~msapiro/scripts/ for a link to an
experimental withlist script that should do
At 8:53 AM -0400 12/15/06, Pierre Igot wrote:
IMPORTANT: Please note that the correct spelling for Mac OS X and
Mac OS X Server is with a space between the Mac and the OS.
Those of us who have a long history with Mac OS (like, back to the
days of the single floppy disk Mac Plus) will tend
At 10:48 AM -0300 12/15/06, Andres Tarallo wrote:
We need to receive a notification that the suscribers had received the mail.
We where thinking in adding a header that makes the mail client return an
automatic answer.
You can put in a header that some mail clients will recognize, and
At 9:15 AM -0500 12/15/06, Ryan Steele wrote:
Ah, okay. I guess the fact that it first identified the message-id
implicitly and then explicitly lead me to believe it thought that,
in the case of the first line, it was identifying the indiscernible
address. Thank you very much for
At 11:05 AM -0800 12/15/06, Mark Sapiro wrote:
The inconsistency between Mailman mail and other mail is puzzling. Do
both paths send through the same initial MTA?
In any case, if the list's host_name is correct, I don't think it's
Mailman.
I would not be at all surprised if the fault is
Greetings,
I'm trying to apply this patch to a mailman-2.1.9 installation but I
don't know how. Would somebody please help.
Thanks.
--
***
Todd Seeleman, Systems Analyst
Penn Graduate School of Education
3440 Market
At 8:40 PM -0600 12/15/06, Brad Knowles wrote:
That said, I will make an effort to find and correct all entries
where this is misspelled. I probably wrote most of them, so I have
the responsibility to make sure that they are correct.
Found and corrected, in a surprising number of places.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 15, 2006, at 9:47 PM, Brad Knowles wrote:
Yeah, the stuff that Mailman logs is not always clear as to what
means what. After several years of dealing with it, I still get
confused about some less common types of log entries myself. This
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 15, 2006, at 9:40 PM, Brad Knowles wrote:
There's two places where the mailing lists are described. One place
is on the web pages at list.org (and mirrored at gnu.org), and one is
within the Mailman listinfo description itself. Only Barry
Hi,
Am I missing something here? I've got archiving set to private and
turned off for one particular list, and it's quite rightly not
archiving. However, it is saving attachments in the form
private/listname/attachments/mmdd/hash.
Is there a reason these attachments are being saved? And is
27 matches
Mail list logo
