At 07:07 PM 1/2/01, Dan Mick wrote:
>??? "Implicit destination" means, as has been said, "the list address is
>not mentioned
>in To: or Cc:"; the *number* of recipients doesn't affect and isn't
>affected by
>the *content* of recipients. No, this has nothing to do with the problem of
>seeing me
Hmmm. I'd tried running a script similar to the one you've got below, but
not out of tmp just to shorten the pathname. I tried running it out of tmp,
but no dice. It might be something stupid but it leaves no logs (that I've
found yet, anyway) and it really makes me scratch my head.
I ended u
> "MM" == Marc MERLIN <[EMAIL PROTECTED]> writes:
MM> Note that he did a newlist BETA. If he had done cp
MM> lists/ALPHA/config.db lists/BETA/config.db, and then a
MM> move_list BETA, that would have kept the list membership, but
MM> a newlist BETA creates an empty list, and
> "B" == Bob <[EMAIL PROTECTED]> writes:
B> I'd really rather see entirely new versions, instead of
B> patches. Makes it much more difficult for newbies when they
B> have to patch stuff. I still have not seen any clear, concise
B> doc file explaining how to implement your
> | > I think I found a solution, but wanted to check with the list to see if I
am
> | > correct.
> | > I was poking around the excerpts and found that people were sending
messages
> | > to my list "[EMAIL PROTECTED]" with addresses such as "[EMAIL PROTECTED];
> | > [EMAIL PROTECTED]; [EMAIL PR
On Tue, 02 Jan 2001 15:11:25 -0800
Dan Mick <[EMAIL PROTECTED]> wrote:
> As for "cron logs"...is this really a worry? I've got about a
> megabyte in log and olog on Solaris. A megabyte is ignorable in
> these days of "20GB is entry-level" disks.
syslog-ng can be a good friend for cases like t
I have created a new filter in the style of bowa-strip and am unsure of
how to use it for a mailing list.
Could someone let me know?
For your interest, I have copied the filter below - it is designed to
spamproof email addresses in emails forwarded to Usenet.
Ian.
--
# import gnu_public_licens
Dan Mick <[EMAIL PROTECTED]> writes:
| Douglas Munoz wrote:
| >
| > I think I found a solution, but wanted to check with the list to see if I am
| > correct.
| > I was poking around the excerpts and found that people were sending messages
| > to my list "[EMAIL PROTECTED]" with addresses such as
Douglas Munoz wrote:
>
> I think I found a solution, but wanted to check with the list to see if I am
> correct.
> I was poking around the excerpts and found that people were sending messages
> to my list "[EMAIL PROTECTED]" with addresses such as "[EMAIL PROTECTED];
> [EMAIL PROTECTED]; [EMAIL
I think I found a solution, but wanted to check with the list to see if I am
correct.
I was poking around the excerpts and found that people were sending messages
to my list "[EMAIL PROTECTED]" with addresses such as "[EMAIL PROTECTED];
[EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]; etc.
On Tue, Jan 02, 2001 at 05:56:41PM -0500, Barry A. Warsaw wrote:
>
> > "MM" == Marc MERLIN <[EMAIL PROTECTED]> writes:
>
> On Tue, Dec 26, 2000 at 02:11:25PM -0500, Kenneth Jacker wrote:
> > I'd like to use "config_list" to transfer list ALPHA's configuration
> > to a new list BETA. Is this
Matt Thoene wrote:
>
> Cron question...why would I need for cron to retry failed deliveries once per
>minute?
Well, to answer the question you asked explicitly: so the failed deliveries get changed
into successful deliveries. For the question you didn't ask: virtually all mail is
sent by
q
Hi Barry,
I'd really rather see entirely new versions, instead of patches. Makes it much more
difficult for newbies when they have to patch stuff. I still have not seen any clear,
concise doc file explaining how to implement your patches.
Bob
Anyone seen this error message before? It's mailed to the list admin
occasionally, but nothing appears to be broken.
-Original Message-
From: CronDaemon [mailto:[EMAIL PROTECTED]]On Behalf Of Cron Daemon
Sent: Sunday, December 31, 2000 2:34 AM
To: [EMAIL PROTECTED]
Subject: Cron /usr/bi
> "MM" == Marc MERLIN <[EMAIL PROTECTED]> writes:
On Tue, Dec 26, 2000 at 02:11:25PM -0500, Kenneth Jacker wrote:
> I'd like to use "config_list" to transfer list ALPHA's configuration
> to a new list BETA. Is this the recommended procedure?
>
>
> 1) bin/config_list -o config.ALPHA ALP
Cron question...why would I need for cron to retry failed deliveries once per minute?
Do any of you keep this setting as is? It's filling up my cron log big time.
Thanks for the input.
-Matt
--
Mailman-Users maillist - [EMAIL PROTECTED]
h
> "CV" == Christopher VanOosterhout <[EMAIL PROTECTED]> writes:
CV> 1) ABOUT MMSITEPASS COMMAND What if my some odd chance a user
CV> selects the password set using the mmsitepass command? Will
CV> they be allowed to use that password? If so, they could in
CV> fact access a
> "P" == Phydeaux <[EMAIL PROTECTED]> writes:
P> I've not had this problem, but I tried to change the chunk size
P> via the mm_cfg.py file. I set this:
P> DEFAULT_ADMIN_MEMBER_CHUNKSIZE = 100
P> with no effect. I still get chunks of 30. I could change it in
P> Defaults
> "MD" == Michael Dunston <[EMAIL PROTECTED]> writes:
MD> I recently upgraded both Python (1.52 -> 2.0) and Mailman
MD> (2.0b5 -> 2.0) and now appear to have duplicate python files
MD> in the 'Mailman' directory. (Mac OSXS 1.2)
MD> ex: aliases.py
| aliases.pyc
|
> "JC" == Jesse Chan-Norris <[EMAIL PROTECTED]> writes:
JC> http://www.python.org/pipermail/mailman-users/2000-September/007523.html
JC> This url appears to be 404 (there was just a rebuild of the
JC> archives or something similar, correct?)
Use this one instead:
http://ma
> "DK" == Dave Klingler <[EMAIL PROTECTED]> writes:
DK> Essentially the problem here is just to pass a piece of
DK> information from a program with no privileges running as
DK> nobody to a program with the ability to update the aliases
DK> file and run newlist.
As more MTAs
> "DM" == Dan Mick <[EMAIL PROTECTED]> writes:
DM> Users of bin/withlist may have noticed that the -r and -l
DM> options were broken in 2.0final; I just uploaded a SourceForge
DM> patch to fix that (and I've asked Barry what he wants to do
DM> process-wise with little nitty f
Hello all,
We have seen a problem with the Mailman-2.0 series (with
Python-2.0 on Solaris-x86) with large .msg files (typically over
5MB) with attachments which cause qrunner to go into an
infinite loop (I've seen it run over a weekend to no avail).
Qrunner holds the lock and hence causes ev
Yes, I noticed a bounce message to my main hostname, not to the listowner. (I have
several virtual domains, and mailman lists on them). Looks like the monthly mailer is
a waste of resources.
Bob
--
Mailman-Users maillist - [EMAIL PROTECTE
Hi I am a new mailing list manager using Mailman on my website, most of my
subscribers are getting the messages on text pagers or cell phone, is there a
way when I send a message without a Subject that the line saying NO SUBJECT
should not come up, also some times I am sending the message to th
At 7:24 AM -0500 1/2/01, Gary Wilson wrote:
>Anyway could someone post the correct link or pass along the information on
>what needs to be done to correctly upgrade from the beta version.
the trick is to upgrade all of the templates. The easy way to do this
is (using tcsh):
cd ~mailman/lists
f
Dear Sir
Some one is abusing your mailing list by subscribing a
whole bunch of people to his mailing list
"[EMAIL PROTECTED]" with out asking for
permission. And he continued to ignore requests to
remove people from his list.
This is illegal and it is considered violation of
peoples privacy.
I am preparing to upgrade from 2.0beta5 to the 2.0 release version. In the
Upgrading text file included with the distribution it says:
Mailman will NOT upgrade the template files for existing lists.
Chuq Von Rospach gives some useful advice in this message to the
users mailing list:
Thank you, Dan Mick. I encountered another problem: It looks to me that
/home/mailman/mail/wrapper didn't run well in my server.
I excute the following command:
"/home/mailman/mail/wrapper mailowner first"
I found a message in mail log file:
"Mailman mail-wrapper: Failure to exec scrip
29 matches
Mail list logo