Hello,
If anyone knows the regex string that defines "any" mail address
reagrdless of what stands before and after "@", please give me an exact
example of the string.
thanx,
Luka
Recently, I've looked at the freelists.org running on ecartis:
http://www.ecartis.org/
It seems that the lists on freelists have some interesting options, which
Mailman haven't got, so maybe you could introduce some of them into Mailman.
I put some screenshots over there:
http://znik.wbc.lublin.pl/~ak/rozne/ecartis/
Description of the options:
http://www.freelists.org/help/
I like that it has statistics, quoting limits and strip-headers (a colon
seperated list of headers to remove from outgoing messages). One of my
subscribers unsubscribed from my list just because X-confirm-reading was
distributed over it. Bad quoting is also often a problem, so it would be good
if Mailman could have similar solution to that used in freelists.
Statistics is also very nice feature.
ak
Hi!
Is there any way to setup mailman to stop distributing X-Confirm-Reading-
To requests sent by some list users?
One user has unsubscribed from my list just because it was distributed
over the list.
Regards
ak
Does anyone know if it is possible to clone a list instead of manually
creating each one from scratch?
Scott Hardy
Director Technical Support
I-many, Inc.
6th Floor
511 Congress St
Portland, ME 04101
Phone: 207-228-2326
Fax: 207-828-0491
Using Mailman 2.1.3, we have had problems with virus-generated messages with
spoofed senders getting through to a one-way list.
The only 'solution' I have found is to to disallow any non-moderated users
or administrators. This forces all messages, even from list admins, to be
moderated.
Under Privacy options: [Recipient filters], we set "Ceiling on acceptable
number of recipients for a posting" to 1.
And also turned on 'Emergency moderation of all list traffic is enabled' in
General Options.
However this is not ideal. Back in the dark ages I used Majodomo. As
primtive as that program was, these virus messages would not be getting
through. Reason? The moderated users had to include a password with each
post. Could that password type feature be added?
A virus might forge the 'form' and the envelope. But it is aweful hard to
forge a good password that also matches that from.
Any thoughts?
I'm the maintainer of mandrake mailman package. I have a bug report
about wrong perms for logs files, see:
http://qa.mandrakesoft.com/show_bug.cgi?id=9319
Even if I changed layout drastically to achieve FHS compliance, this
kind of problem is quite curious. Those files are created at run-time,
and I guess the various scripts take care of ensuring correct perms,
whereas group ownership is ensured by the setgid bit for the log
directory. For instance, smtp and qrunner log files are OK. So, what
could have get wrong here ?
--
That's not a "bug", thats a feature !
-- Thoreau's Theories of Adaption n°4
All,
At the institution where I work, we are in the process of deploying
mailman as a replacement to our old mailing list system based on mmdf.
However, one very valuable asset to using mmdf was that we could embed
both other mailing lists as well as individual users in any given
mailing list.
This feature seems to be excluded and replaced in mailman 2.1.2 with
a-- imho-- less functional "umbrella list" setting that is defined on a
per-list basis, and if I understand correctly, this means that it is
difficult to embed both:
joe.user(a)server.org
and
marys-list(a)server.org
into a mailman mailing list.
I am wondering what the timeframe might be as far as being able to
define types (e.g. user vs list) for a subscriber on an individual
member basis.
If I am incorrect in assuming that this feature does not exist, I would
be more than happy to accept illumination. Furthermore, if there is a
legitimate reason why the developers have opted for the umbrella list
setting as compared to a less restrictive model, I would be highly
appreciative to have this explained.
Thank you very much,
Eizan Miyamoto
OK, I've located the SMTP thing in SMTPDirect.py, lines
while chunks:
chunk = chunks.pop()
msgdata['recips'] = chunk
try:
deliveryfunc(mlist, msg, msgdata, envsender, refused, conn)
I'd really love to add somme sleep() function just after the deliveryfunc()
call, something that would set Mailman to sleep about 1/10th of a second per
recipient. I don't know any python, but I guess it would be something like
while chunks:
chunk = chunks.pop()
msgdata['recips'] = chunk
try:
deliveryfunc(mlist, msg, msgdata, envsender, refused, conn)
sleep(sizeof(chunk)/10)
Can someone help with the code? I'll test the concept :)
-- Fil
Barry,
This guy (see forwarded message) is using a Challenge Response
Authentication Program (CRAP - appropriate acronym) on stuff he is
receiving using a mailing list. Unfortunately its broken enough that
the replies are going back to the original poster. Can you terminate
him (or just remove his list membership).
If possible I'd mod Mailman to make it extremely unfriendly to such
programs, unfortunately this one is so completely broken that just
kicking the idiot off the list is the only appropriate response.
[BTW I haven't replied with the magic token since there is nothing civil
I could say to him - shame the system won't automatically block any mail
he tries to send me]
Nigel.
-----Forwarded Message-----
> From: CARTER Anthony <a.carter(a)intrasoft.lu>
> To: Nigel.Metheringham(a)dev.InTechnology.co.uk
> Subject: Re: Re: [Mailman-Developers] sleep() after sending a chunk? (Spam Ender: BLOCKED 1R92-SE45602-Nigel.Metheringham(a)dev.InTechnology.co.uk)
> Date: Tue, 30 Mar 2004 14:58:20 +0200
>
> In an effort to eliminate unsolicited e-mail, I have installed SpamEnder.
> Please REPLY to this e-mail, without modifying the subject line, so that I
> can receive your original message. Upon my approval, future e-mails you send
> to me will be released automatically. If you do not REPLY to this e-mail,
> SpamEnder will block all future e-mails from this address and will not give
> you another opportunity to reply.
>
> Sorry for any inconvenience.
> Anthony Carter
>
> ----------------------------------------------------------
> Excerpt from original message:
> On Mon, 2004-03-29 at 17:39, Fil wrote:
> > I'd really love to add somme sleep() function just after the
> deliveryfunc()
> > call, something that would set Mailman to sleep about 1/10th of a second
> per
> > recipient.
>
> I just don't see the point of this. You may have stopped a large list
> inject being so aggressive on CPU usage, but you have increased the
> lifetime of processes by a factor of 30 or so (on your figures), and so
> increased the memory pressure and likelihood of swapping etc due to
> processes being just as fat but lasting longer.
>
> Your users may notice the big lists getting much slower - and having
> deliveries smeared over a much longer period.
>
> You may find you have made things less efficient by having 2 deliveries
> to a single list slowed down so that different messages to the same
> recipient can no longer be put in the same SMTP session (if your MTA
> does that). For that matter can multiple deliveries be made against the
> same list at the same time?
>
> Why not just run the cron jobs under nice instead?
>
> Nigel.
--
[ Nigel Metheringham Nigel.Metheringham(a)InTechnology.co.uk ]
[ - Comments in this message are my own and not ITO opinion/policy - ]
Hi.
According to the comments in mailman/Mailman/MailList.py,
respond_to_post_requests should be configurable, but it isn't.
288 # This stuff is configurable
289 self.respond_to_post_requests = 1
See attached patches to fix this.
Should I fill a bugreport or can anyone add this to CVS?
I'm using Mailman version 2.1.4 from Debian Backport 2.1.4-0.backports.org.1
But this appears in the latest 2.x CVS-tree, too.
Thank you all for mailman development.
--
cheers,
Steffen Mueller
diff -urN mailman/Mailman/MailList.py mailman/Mailman/MailList_patched.py
--- MailList.py 2004-03-30 02:34:40.000000000 +0200
+++ MailList_patched.py 2004-03-30 02:35:56.000000000 +0200
@@ -286,7 +286,7 @@
self.new_member_options = mm_cfg.DEFAULT_NEW_MEMBER_OPTIONS
# This stuff is configurable
- self.respond_to_post_requests = 1
+ self.respond_to_post_requests = mm_cfg.DEFAULT_RESPOND_TO_POST_REQUESTS
self.advertised = mm_cfg.DEFAULT_LIST_ADVERTISED
self.max_num_recipients = mm_cfg.DEFAULT_MAX_NUM_RECIPIENTS
self.max_message_size = mm_cfg.DEFAULT_MAX_MESSAGE_SIZE
diff -urN mailman/Mailman/Defaults.py.in mailman/Mailman/Defaults_patched.py
--- Defaults.py.in 2004-03-30 02:38:55.000000000 +0200
+++ Defaults_patched.py 2004-03-30 02:41:39.000000000 +0200
@@ -805,6 +805,9 @@
# Is the list owner notified of subscribes/unsubscribes?
DEFAULT_ADMIN_NOTIFY_MCHANGES = No
+# Send mail to poster when their posting is held for approval?
+DEFAULT_RESPOND_TO_POST_REQUESTS = Yes
+
# Should list members, by default, have their posts be moderated?
DEFAULT_DEFAULT_MEMBER_MODERATION = No