Hello,
I just want to let you know how I solved the spam problem on my server
and reduced the mail load dramatically:
Mails arriving on my server get tagged by spamassassin before they reach
mailman:
postfix - spamassassin - postfix - mailman
(see
hi,
when i send the mail i happen to see this in the sendmail
error log stat=unknown mailer error 1 any clue why is that because
of?
--
regards,
Prashanth
http://munichlinux.blogspot.com
--
Mailman-Users mailing list
Quoting Michael Geiger [EMAIL PROTECTED]:
2. create a new wrapper-script mailman (chown mailman:mailman, chmod 755):
- BEGIN -
#!/bin/sh
/usr/bin/procmail -m /opt/mailman/mail/mailman.procmailrc $*
- END -
3. create the file mailman.procmailrc (chown mailman:mailman,
Quoting Luke Daly [EMAIL PROTECTED]:
We currently run a hundred or so lists at a university our biggest
one (22000 students at a university) is obviously moderated.
As a side note, I work at a public research University with ~50,000
students and ~20,000 faculty and staff.
bringing the
Quoting Prashanth [EMAIL PROTECTED]:
when i send the mail i happen to see this in the sendmail
error log stat=unknown mailer error 1 any clue why is that because
of?
You don't give us any useful information, so we're not going to be
able to give you a useful answer.
Please see
On Mon, 14 Apr 2008, Mark Sapiro wrote:
This is a security and bug fix release and it is highly recommended
that all sites upgrade to this version. Mailman 2.1.10 also adds support
Quick clarification: It's somewhat unusuall for it to be recommended that
all sites upgrade to a release
Christopher X. Candreva wrote:
On Mon, 14 Apr 2008, Mark Sapiro wrote:
This is a security and bug fix release and it is highly recommended
that all sites upgrade to this version. Mailman 2.1.10 also adds support
Quick clarification: It's somewhat unusuall for it to be recommended that
all
Hi,
We have internal Mailing List server running Mailman 2.1.9 and SENDMAIL
8.13.8. Whenever someone sent email to particular mailing list
([EMAIL PROTECTED])consisting app 300 users recipients receive
it after several hours. E.g see the following Email I sent yesterday at
3:19PM that came in at
* Patil, Manjiri S [EMAIL PROTECTED]:
Hi,
We have internal Mailing List server running Mailman 2.1.9 and SENDMAIL
8.13.8. Whenever someone sent email to particular mailing list
([EMAIL PROTECTED])consisting app 300 users recipients receive
it after several hours. E.g see the following
Ralf Hildebrandt wrote:
* Patil, Manjiri S [EMAIL PROTECTED]:
Hi,
We have internal Mailing List server running Mailman 2.1.9 and SENDMAIL
8.13.8. Whenever someone sent email to particular mailing list
([EMAIL PROTECTED])consisting app 300 users recipients receive
it after several hours.
get the message text plus
-- next part --
An HTML attachment was scrubbed...
URL: http://maillists.uci.edu/mailman/public/test/attachments/
20080415/846539df/attachment-0002.html
-- next part --
A non-text attachment was scrubbed...
Name
Mark Sapiro wrote:
You can do this with a withlist script such as the set_topics.py.txt
script attached. You would save this in Mailman's bin/ directory as
set_topics.py and run it via
bin/withlist -l -r set_topics list user-email [topic ...]'
Sorry, I forgot the attachment. Here it is.
--
to the archives though I get the message text plus
-- next part --
An HTML attachment was scrubbed...
URL: http://maillists.uci.edu/mailman/public/test/attachments/
20080415/846539df/attachment-0002.html
-- next part --
A non-text attachment was scrubbed
both the text and the attachment. When
I go to the archives though I get the message text plus
-- next part --
An HTML attachment was scrubbed...
URL: http://maillists.uci.edu/mailman/public/test/attachments/
20080415/846539df/attachment-0002.html
-- next part
Con Wieland wrote:
On Apr 15, 2008, at 2:58 PM, Mark Sapiro wrote:
Con Wieland wrote:
My questions are, why am I getting the html attachments?
Because the sender's MUA is sending them and your content filtering is
either not on or is not removing HTML and not collapsing alternatives.
On Tue, Apr 15, 2008 at 11:56 AM, Mark Sapiro [EMAIL PROTECTED] wrote:
There are two security issues mentioned in the announcement.
harsh criticism
How much sense does it make to announce security issues in a release
CANDIDATE? Come on guys, release a STABLE version (or FIX), then
announce.
I have a large list (22000) users. it is configured with the following settings
:
Action to take when a moderated member posts to the list. = Discard
Action to take for postings from non-members for which no explicit action is
defined. = Discard
All users are moderated except where they are an
Luke Daly wrote:
I have a large list (22000) users. it is configured with the following
settings :
Action to take when a moderated member posts to the list. = Discard
Action to take for postings from non-members for which no explicit action is
defined. = Discard
All users are moderated except
On Tue, April 15, 2008 16:24, Jim Popovitch wrote:
On Tue, Apr 15, 2008 at 11:56 AM, Mark Sapiro [EMAIL PROTECTED] wrote:
There are two security issues mentioned in the announcement.
harsh criticism
How much sense does it make to announce security issues in a release
CANDIDATE? Come on
On Tue, Apr 15, 2008 at 8:49 PM, Dragon [EMAIL PROTECTED] wrote:
I'm going to be harshly critical as well. Did you even read the release
notes in the announcement?
Yes, I did.
You are completely off base here. While Mark did not explicitly say so in
his reply, the fixes for the security
On Tue, Apr 15, 2008 at 9:10 PM, Barry Warsaw [EMAIL PROTECTED] wrote:
Better to get a release out asap after that and let the community know
that there are important fixes contained within.
Fair enough. Where's the release then?
Look, I know you folks are working hard on this, and I
Quoting Jim Popovitch [EMAIL PROTECTED]:
Fair enough. Where's the release then?
Dragon is right -- the code is up-to-date and waiting for translation,
as do pretty much all RCs released by this project.
Look, I know you folks are working hard on this, and I certainly don't
dis-respect
On Tue, Apr 15, 2008 at 9:44 PM, Brad Knowles [EMAIL PROTECTED] wrote:
Quoting Jim Popovitch [EMAIL PROTECTED]:
Fair enough. Where's the release then?
Dragon is right -- the code is up-to-date and waiting for translation, as
do pretty much all RCs released by this project.
Look, I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Apr 15, 2008, at 8:49 PM, Dragon wrote:
My experience has been that by the time a release candidate is
announced
by this project, it is usually quite close to the final version and
the
only changes that are made in a stable release are
Jim Popovitch wrote:
Fair enough. Where's the release then?
Look, I know you folks are working hard on this, and I certainly don't
dis-respect that. HOWEVER, the process flow needs some re-thinking.
You should not publicly release security vulnerability details before
fixes are identified for
If you want to do something that is actually productive here, why
don't you find a way to use your own resources and your own personal
free time to resolve this issue?
Maybe you could run a very large mailing list server you'd be willing
to use as a guinea pig for all RC's, so that we would
On Tue, Apr 15, 2008 at 11:04 PM, Mark Sapiro [EMAIL PROTECTED] wrote:
I appreciate your view Jim, and I was remis in not making patches for
2.1.9 publicly announced and available[1], however, if you don't trust
my 2.1.10 beta or rc release to be stable enough for production use,
why would
On 4/16/08, Jim Popovitch wrote:
I can appreciate the significance of that situation. I don't know
that I have a solution other than to ask what does ClamAV or
SpamAssassin do in similar situations?
Dunno. Do they have to support twenty different languages?
Can those translations only
28 matches
Mail list logo
