Are there any way to send different welcome messages
to subscribers which depend of their class?
For example, I have announcement list with two classes of subscribers:
- posters, who are allowed to post to the list (subscribed by admin)
- silent members who just receive posts from the first class members
(subscribed by theirselves)
It would be great if I can send different welcome message tho
this two classes of subscribers.
Are there any chance it will be implemented?
Ok we are running version 2.1.5 on an old White Box server and are
encountering this bug which is preventing us from accessing the
membership management pages for some (but not all) of our mailing
"if bucket not in digits + '_' + lowercase:
TypeError: 'in <string>' requires character as left operand"
I added the '_' to the first line thinking maybe someone used an
underscore as the first character in the address and mailman didn't like
that but no joy. I asked the Google overlords for an answer with no help
(maybe my google-fu needs honing) so I apologize if this is an issue
that's been fixed 100 times over.
Any help on what to twiddle would be helpful. It can't be as simple as
something like adding '' to the if statement right? My Python skills are
quite rudimentary (read: neanderthal).
I just checked.
My apologies. Google App Engine used to be set up so that no email
could be recevied at all. Now that is the default, but it can
Can we get mailman to work under these Google App Engine restrictions?
I don't know anybody who has done this, but I don't know everybody on
this planet, 'natch. Somebody else will be sure to speak up now that
I have put my foot in it.
I've noticed that output of bin scripts depends on $LANG environment variable.
I can switch languages of output by issue "export LANG=en_US (or ru_RU)".
But what I could not find is how to switch a charset of output.
I tried to issue "export LANG=ru_RU.UTF-8", "export LANG=ru_RU.koi8-r"
but output remains the same.
For example, nano text editor reacts on commands listed above and become
unreadable in any encoding other than "ru_RU.UTF-8".
In a message of Wed, 04 Feb 2015 15:50:54 -0600, cha charle writes:
>Thanks for your quick reply; then is it possible to continue run a Mailman
>server and still have my email move to Google App. Thanks!
>On Wed, Feb 4, 2015 at 1:42 PM, Laura Creighton <lac(a)openend.se> wrote:
>> Unless Google App Engine has changed recently, it cannot receive any
>> mail at all. So you need to move your mailing list software to
>> someplace else, mailman friendly. There is no hope of doing what you
>> Sorry about that,
>> Laura Creighton
I don't know what you mean by 'have my email move to Google App'. As far
as I know, you cannot have your email move to Google app engine, at all,
period, and this is the #1 limitation of such a thing. So you move your
mailing list software someplace else that is mailman-friendly, and then
you run the rest of your app with AppEngine, assuming this is what you
want to do.
Someone will correct me if things have changed since the last time I
Currently, we have Postfix and Mailman on our server, but will migrate our
server to Google App. From what I read, Mailman will not work with Google
App. So, does anyone have any suggestion how should I proceed with Mailman?
I have a list using MM2 and I'm wondering, if I started using MM3, would I
be able to just plug in the same database that I'm using with MM2? Or would
I have to do anything different to keep the archives?
In a message of Wed, 04 Feb 2015 08:09:13 -0800, Mark Sapiro writes:
>> This was the place I was sort of hoping that 'once a day' could be
>> changed to 'once every 6 hours', but my rather cursory glance at the
>> code made me conclude -- nope, not here.
>In Mailman's crontab - see my last reply.
I have a filter to block the word "test" from Subject because some people won't receive list mail for a few hours and think it's broken so they
And once one person does it everybody else feels obligated to "test".
So I use
Problem with that is that it also blocks "latest" and "testimony".
I suck at regular expressions and would appreciate some help.
I also don't have a test list to test this :)
In a message of Thu, 05 Feb 2015 00:33:19 +0900, "Stephen J. Turnbull" writes:
>Laura Creighton writes:
> > While some people want to continue receiving digests, and some
> > people don't, everybody is in favour of having the mail only go out
> > in batches at set intervals during the day. So maybe once a day is
> > too infrequent, and 3 times a day would be nicer, but what is not
> > wanted is 'deliver this as soon as it arrives'.
>Mailman delivers as soon as the mail arrives, except for digests.
>This is not configurable in Mailman. You might be able to run a cron
>job which starts Mailman at 0, 8, and 16 hours, and stops it at 1, 9,
>and 17 hours. Seems kinda kludgy but should work (untested, of
>course). I thought about just stopping the outgoing runner, but
>that's going to be really messy.
Okay then. Nice to know I wasn't finding anything because it wasn't
there to be found. :)
>Digests are delivered when the size limit is reached (if
>digest_size_threshold > 0), or once a day (if digest_send_periodic is
>set), which ever comes first. The size limit is set on the "Digest
>Options" view of the "Administration" page for the list.
This was the place I was sort of hoping that 'once a day' could be
changed to 'once every 6 hours', but my rather cursory glance at the
code made me conclude -- nope, not here.
>I suppose it might be possible to modify Mailman to hang on to posts
>for a few hours and send them out in batches, but this might cause a
>large load on the mail server during that period.
I can guarantee that this would not be a problem for our particular
user community. ;) Even if every one of us decided to passionately
wade in and post to the max on a huge-and-pointless flame war -- there
still aren't enough of us to provide a large load. But your point is
well-taken. The flame-war part is precisely why people want deliveries
to be once, or a few times a day. The belief is that people who have to
think about what they are writing -- as they only get one crack at it every
24 hours -- produce more reasoned responses than those people who are more
accustomed to shooting from the hip and then apologising later if they
turn out to be wrong.
Thus in the eternal 'give mailman 3.0 everything that we cannot do now'
discussion, a 'cool-down' period has just now shown up as a thing that
real users have been asking for, and which would have ended up as a
blocker for moving from 25 year old software to mailman -- except that
if I cannot convince them I know how to hack a cron job, then I am
just rubbish as a spokesman, and that's all. :)
Thanks very much Stephen. Always a pleasure.