Mailman v. 2.1.12 - Mac OS 10.4.11
Tried to configure, and got the following results in config.log under
Core Tests:
configure:1714: checking for --with-python
configure:1726: result: no
configure:1733: checking for python
configure:1751: found
1. Mailman aliases not working (like in my case)
2. Unable to access my email, but have access to web (which is common
for those of us behind corporate firewalls)
3. My email is broken, but my internet it still working
However, even with these reasons, I wouldn't consider it a big deal,
At 7:32 PM +0900 on 11/23/09, Stephen J. Turnbull wrote:
Bill Catambay writes:
1. Mailman aliases not working (like in my case)
2. Unable to access my email, but have access to web (which is common
for those of us behind corporate firewalls)
3. My email is broken, but my internet
At 7:56 AM -0800 on 11/23/09, Mark Sapiro wrote:
I see two requests in this thread. The original appeared to be a
request for a way to send a regular post to a list via the admin web
interface, which would be useful in cases where for whatever reason,
the list was working but email delivery
At 11:05 AM -0500 on 11/23/09, Barry Warsaw wrote:
The second request, which might also satisfy the first if it were
implemented as a web service, seems to be for a way to send a message
right now to all members of a list (or all lists?) regardless of
digest and nomail settings.
Actually,
).
--
,,,
(o o)
===oOO==(_)==OOo=
Bill Catambay
Santa Clara, CA
bill.catam...@excaliburworld.com
Discovery consists of seeing what everybody has seen,
and thinking what nobody has thought.
.oooO Oooo
At 8:52 AM -0800 on 11/23/09, Mark Sapiro wrote:
Bill Catambay wrote:
If by send a message, you mean email a message to the normal
foo-list email address, then I'm back to square one (i.e., it will
never reach anyone on the list because of the aliases being whacked).
But, I hope you
Okay, today was quite the rollercoaster. I finally got an email from
my ISP's Operations group stating that the foo-list-mod email was
working, but when I tried, it didn't work. Bounced just like before.
I called them up, and when I told them it was still bouncing, they
insisted that it was
How about changing the text?
At 4:21 PM -0800 on 11/23/09, Mark Sapiro wrote:
Bill Catambay wrote:
In any case, I did have one follow-up question (suggestion, actually,
from a member of my list). In the digests, is there any setting that
is available to *me* that will let me put
Okay, thanks for the info. I'll go stealth for awhile. :)
At 4:38 PM -0800 on 11/23/09, Mark Sapiro wrote:
Bill Catambay wrote:
How about changing the text?
The text is built from the masthead.txt template. A list specific
version of this template can be installed (see the FAQ at
http
Given my current situation (as rare as this situation may be), I have
come to realize that an emergency broadcast feature would be an
indispensable tool to have right now. Since my host made the alias
change on my mailing list, but did not create the MX record for the
new email, it is
The weekend crew at my ISP are general tech support (i.e., they
really only handle internet connection issues). My ISP does have an
Operations group which usually are pretty knowledgeable, but I they
simply aren't working on the weekend.
For what it's worth, they are the best ISP I have had
Looks like I'm half-way there unfortunately, half-way means one
step back before the two steps forward.
I got my ISP to create the aliases:
foo-list: |/opt/mailman/mail/mailman owner foo-list
foo-list-mod: |/opt/mailman/mail/mailman post foo-list
It
At 7:48 PM -0800 on 11/17/09, Mark Sapiro wrote:
I think the aliases together with the modified Moderate handler for
your list will be your DREAM SOLUTION. And this has the advantage that
while it is some work for the host to set up, it affects only your
list so thay can't say no solely on the
At 12:21 PM -0500 on 8/15/09, Shop at \ Just Brits \ wrote:
So IMHO Bill needs to tell The List not only the version of MM BUT
the source of
install so that everybody is playing with a FULL deck of cards.
Right-:) ???
I don't remember if I answered this question before or not, but just
to
Hi Steve, et al,
Awhile back I asked some questions about managing my Mailman list
such that it worked like it did back on Autoshare (an old Mac OS 9
listserver). I received some good advice, and have made some great
progress in attaining most of my goals. There were still some
unresolved
I am trying to customize our Options page, and I want to add links to
our main website within the page (really the only changes I am
making). When I try to save, I get:
The page you saved contains suspicious HTML that could potentially
expose your users to cross-site scripting attacks. This
I have an update on this. I was trying to pinpoint exactly what
change caused this, and as I deleted changes, starting with the
link, I still kept getting the same rejection. Then I just went to
edit the page, and made no changes at all, clicked on Submit Changes,
and it *still* gave me the
At 2:12 PM +0900 on 8/14/09, Stephen J. Turnbull wrote:
Mark Sapiro writes:
Stephen J. Turnbull wrote:
NB. As he needs them to means that the *list moderator* be
recognized as the *envelope sender*, and the message be approved in
that case.
Bottom line, a new feature is needed for
At 11:40 AM +0900 on 8/14/09, Stephen J. Turnbull wrote:
Mark Sapiro writes:
Stephen J. Turnbull wrote:
Bill Catambay writes:
My ISP is using Mailman 2.1.11. Is that the latest? I'm guessing
no, since it is currently NOT recognizing the envelope sender. This
sounds like
At 1:41 AM +0900 on 8/14/09, Stephen J. Turnbull wrote:
This can be done by setting up aliases as follows (pseudo-syntax, your
mileage will vary):
foo-list: modera...@example.com
foo-list-moderated: | mailman post foo-list
That requires modifying the mailman aliases
21 matches
Mail list logo
