Interesting problem! I would tackle this by:
- renaming the newlist command to something like orig.newlist and then
- writing a script that collects the data necessary for newlist,
- feed that data into orig.newlist,
- capture the output, and then
- run the "imsimta" command for each of th
I suspect that your config.db for one of your lists is corrupt.
Reasoning: "require_explicit)destination is an attribute of your mailing
list. If the program Hold.py can't find this attribute, then it may be
missing from your list - ergo corrupt.
You can use the ~mailman/bin/check_db program to
Dear All,
How to install mailman (I mean the complete step
script) ? I use Readhat distributions. Thank you.
__
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com
---
On 12 Oct 2002, Jon Carnes wrote:
> Really the best solution is to teach folks the proper way to setup a
> vacation message. Vacation messages should *only* respond to emails
> where either the TO: or CC: of the message has the users email address
> in it.
> On Fri, 2002-10-11 at 10:18, [EMAIL
On 14 Oct 2002, Jon Carnes wrote:
> As someone else mentioned, the Beta has this feature.
>
> Also, if you have sysadmin rights to the server running Mailman,
> then you can setup one of the work-arounds. There are a couple of
> work-arounds that allow you to discard the messages silently.
>
> Ch
I am new to the list and to mailman so I apologize in advance if this
has been covered...
We are running Sun ONE/iPlanet messenger in Solaris 8. For those
using the same, here's the issue that we're up against:
imsimta program -a .. forces programs to be registered with command
line arguments
I have started getting this error since last Friday in my mailman logs and
can't figure out how to fix it:
Oct 14 14:47:01 2002 (2656) Delivery exception: require_explicit_destination
Oct 14 14:47:01 2002 (2656) Traceback (innermost last):
File "/home/mailman/Mailman/Handlers/HandlerAPI.py",
On Mon, 14 Oct 2002, Matt Filizzi wrote:
> Just as an update, what the problem was is someone subscribed with
> an ' in their email address. (ex. o'[EMAIL PROTECTED]) Does anyone know
> if this is valid for email addresses?
It is valid.
> I couldn't find any mention in the RFC about it.
See
Hello.
Yesterday Mailman decided that most of the people subscribed to
the lists I run at my site were bouncing and disabled hundreds of
accounts. The problem is that they're not bouncing at all! I had to
disable bounce detection and manually enable the affected accounts. If I
enable
Just as an update, what the problem was is someone subscribed with an '
in their email address. (ex. o'[EMAIL PROTECTED]) Does anyone know if this
is valid for email addresses? I couldn't find any mention in the RFC
about it.
Jon Carnes wrote:
> Check the log files for mailman.
>
> Check th
On Mon, Oct 14, 2002 at 11:11:39AM -0600, Armando Soto Baeza wrote:
> Check procmail-sanitizer, it's great!
>
> http://www.impsec.org/email-tools/procmail-security.html
>
> > What is a good virus (worm) protection tool for mailman?
> >
> > I have a virus message in the archives now. How do I re
Check procmail-sanitizer, it's great!
http://www.impsec.org/email-tools/procmail-security.html
> What is a good virus (worm) protection tool for mailman?
>
> I have a virus message in the archives now. How do I remove a single
> message from the archives?
>
> thanks much!
>
> --
> Paul L. Schum
This is not the first time it's happened! You might want to contact the
person in charge of maintaining that package for SuSE.
It may be that they make some assumptions as to which mailserver you are
using, and you used a different mailserver. If that is the case, then
you might find a package
You need to look at your mail transport logs and see where the error is
coming from. I'm guessing that you tightened up the local servers
relaying (/etc/mail/access - for sendmail) and that you probably turned
off relaying for localhost.
If that is the case, then Mailman will only be able to del
As someone else mentioned, the Beta has this feature.
Also, if you have sysadmin rights to the server running Mailman, then
you can setup one of the work-arounds. There are a couple of
work-arounds that allow you to discard the messages silently.
Check out FAQ article 1.12 and article 4.15
Good
Off hand, I would say that your server ran out of space (or something
worse). In which case, only the sysadmin can rescue you!
Good Luck
On Sun, 2002-10-13 at 23:14, Ashley M. Kirchner wrote:
> WhitmoreWebWorks wrote:
>
> > Do you think there could be something
> > wrong with the server that
This is definitely an FAQ... Send some mail to the list, wait a day and
then check (or run the archiver by hand *after* sending some mail to the
list).
The archives are created automatically - but only after some mail is
sent, and the arch script is run (from cron).
Good luck - Jon Carnes
On
If I read that warning correctly, it is simply telling you that the
email address [EMAIL PROTECTED] is bouncing.
What happens when you send an email to "[EMAIL PROTECTED]"? Does
it bounce? Are only Mailman messages bouncing to that address?
On Wed, 2002-01-02 at 07:06, Fuss, Christian wrote:
>
Up grade to the Beta version it has that feature
John
On Monday 14 Oct 2002 10:12 am, Mark Goodge wrote:
> Hi,
>
> I run several mailing lists, all of which have posting restricted to
> members only, some of which require approval for subscriptions and one of
> which is moderated (requires posts
Hi,
I run several mailing lists, all of which have posting restricted to
members only, some of which require approval for subscriptions and one of
which is moderated (requires posts to be approved). This means there are
quite a lot of administrative requests to be dealt with every day.
One th
Hi,
i do have a really urgent Problem with my Mailman.
Actually everythings working fine except of sending the mails to the
list-members.
I get following failure in the smtp-failures
log:
Oct 12 19:49:11 2002 (2292) delivery to [EMAIL PROTECTED] failed with
code 553: 5.3.0 <[EMAIL PROTE
21 matches
Mail list logo
