Adam Parker, OD writes:
no, i'm not actually using that domain. Cpanel allows you to easily set up
a list - it just asks you for the name of the list and a password and does
the rest for you.
Actually, cPanel itself doesn't do anything except allow the hosting
staff to avoid interacting
Greg Zilberfarb writes:
I want to totally eliminate moderator intervention and let the
emails fly as they may from list members and non-members alike.
Even if you have had no spam problem to date, that can change at any
time. Make sure you know how to impose emergency moderation if you
get
Anthony R. Thompson writes:
At one point I had an address (chira...@gmail.com) which was subscribed
to the list (adf-www).
Do you mean (as implied by your access to the inbox) that this is your
personal address?
If so, I don't know if GMail allows this, but is it possible that you
Anthony R. Thompson writes:
It doesn't seem to me like someone should be able to post a message to a
private list just by changing the Reply-To field to an address they know
is on the private list.
Sure, but there's nothing you can do about that since anything in
email that can be used
Dwight A. Ernest writes:
Mark, this is exactly what I needed. Thanks for the pointers. All of the
missing list traffic is being delivered as I speak.
Yay! And thank you for the confirmation. It makes us all feel a
little more secure, I'm sure.
Ivan Van Laningham writes:
Now, gmail may, behind the scenes, insert a link to the sent folder, but
from a user's perspective it looks exactly like any other message in the
thread, except that to the left of my name is a very small (i.e., 8x8
pixels) light grey round icon with a white x
Mauricio Juarez writes:
Hi,
- I use mailman to administrate my email lists
- I need absolutely change the Admin Lists password
- I used the command: change_pw in my /bin Mailman directory, all was
OK, I can use my new password for all the lists but
My old password work
Steff Watkins writes:
One thought/idea I've had is to have a test list which has only my
work email address, an offsite email address and maybe one or two of my
colleagues (for verification purposes), lock it right down so that only
the members can use it, add the Me too tag so that we'd
Brad Knowles writes:
If there's more to it than that, then I would definitely be
inclined to be much tougher in my response.
Under the GPL, you don't have any grounds for anything except the kind
of campaign that might open you up to a libel suit as long as they're
distributing source with
Ivan Fetch writes:
One possibility we're exploring, is to change a student's mailing
list subscriptions, when they change their forwarding address. We
would iterate through these address changes and run clone_member,
like:
Clone_member --remove --admin o...@our.domain
bruce clark writes:
My problem: the users on my lists are waging a low-level war with
their sig files. I do not allow commercial posting so they have
started creating sig files with their commercial messages inside them.
First, consider whether this is really so bad. I know I would be
Brian J Mingus writes:
I am moderating a list with 4200 members. Clicking on any link is extremely
slow. I have asked that our server be upgraded, but I was told that the
problem is with the mailman software. They claim that every time I try to
perform any action mailman scans through
Tanstaafl writes:
Is there some kind of .conf parser for apache that will show the current
configs it is using, similar to 'postconf -n' for postfix?
Not that I know of.
Too bad, it would sure come in handy when troubleshooting apache
problems, especially in complex
Tanstaafl writes:
On 2010-12-30 4:52 PM, Tanstaafl wrote:
After the change to the DocRoot, now when I go to either one I get only
one error:
mod_mime_magic: can't read `/usr/lib64/mailman/cgi-bin/admin'
Forgot to ask - any other ideas on this error message? I'm looking into
Jason Bilbrey writes:
The other idea I had was to create a 2nd mailing list with the exact same
members and changing the reply for the 2nd list to go to the poster. That
makes it easy for the poster... Just wish I could automatically sync to the
two lists without having to manually
Mark Sapiro writes:
Other people think pdfs are ok (except some are too big for old machines
to donwload).
I also heard that a virus file could take on a fake extention, like .pdf,
and fool people.
As far as fake extensions/MIME types are concerned, it is entirely
possible to
Mark Sapiro writes:
Larry Havard lar...@havard.com wrote:
I have looked and cannot find it.
Is there a setting for bouncing message with multiple to's or to: and
CC:
We want mail coming in to our list to be only for our list and not
being
sent to others in the same message.
Mark Sapiro writes:
In any case, header folding/unfolding is done in the underlying Python
email package, and I don't think you'll see any change to this until
sometime in the Mailman 3 life cycle.
R. David Murray is making a lot of progress on the email package in
python 3, with
Noah writes:
Mark: Do you have any ideas about how to force apt-get to consider
using the version with the proper OS/arch version?
This really isn't appropriate for this list, you should be asking at
Ubuntu or Debian. Personally, I would recommend removing the distro's
package and
Doug Gaff writes:
I'm trying to track down a problem related to message from one
particular emailer not showing up on a list.
This person is not subscribed to the list. They send a message, and
the moderator approves the message, but it never shows up on the
list.
Look in the logs.
Patti Beadles writes:
Item D is throwing me for a loop. I can make it happen with a
one-line change to SpamDetect.py, but that's probably not going
to fly. The host runs multiple lists, and doing this would
constrain the other lists in ways that aren't really acceptable.
I do this
Clare Redstone writes:
I can warn everyone about this and suggest that, if they don't want
their details revealed, they only use an address that they won't
set out of office.
As Mark said, this is in some sense the best you can do. It's not
really possible to filter on contact details,
Clare Redstone writes:
How insecure? Are they more vulnerable than a members-only Yahoo or Google
group for example?
Probably a little more vulnerable, for social reasons. Your members-
only password at Yahoo/Google is your personal mail password; people
probably protect those fairly well
Chris Haumesser writes:
I was assuming the .keep folder had something to do with mailman
internals.
That looks like a distro device to make sure that the data
directories don't get deleted if you delete the package.
Possibly what is happening is that the distro's version is patched to
Mike Manning writes:
We use Mailman 2.1 with Qmail and Plesk (v10.2). Everything works nicely
with Mailman however it's not sending out the bounce emails
Bounce is a term of art; it means mail returned because it was
undeliverable. Mailman doesn't send out bounces to anybody, although
it
菊地時夫 writes:
How about putting that spam address in header_filter_rules in
private/spam interface and set it 'discard'.
He's already doing that, with an address that the user has abandoned.
The new problem address is legitimate, which I presume means a list
member.
菊地時夫 writes:
No. He put the address in discard_these_nonmembers on the
private/sender page but not have mentioned the private/spam settings.
I believe if you set the spam address in header_filter_rules of
privacy/spam page, the message should be discarded even if other
legitimate
Richard Stallman writes:
It sounds like this new spam technique is becoming xommon.
Would it make sense for Mailman's defaults to DTRT for it,
or reduce the amount of customization users need to do?
No. Mailman really shouldn't be doing any spam filtering at all. It
needs filtering, yes,
Richard Stallman writes:
Do you mean to say that the people at CSAIL ought to switch to using
SpamAssasin instead of filtering in Mailman?
I don't know anything about CSAIL, so I can't say for that particular
case. But I've yet to see a *good* reason for doing generic filtering
at the
Barry Warsaw writes:
What's the legitimate use case for multiple From headers?
Technically, there is none. RFC 5322 requires exactly one From field,
and that's that. http://www.ietf.org/rfc/rfc5322.txt, table in
section 3.6. (Resent-From, of course, is a different kettle of fish.)
However,
Ed Pastore writes:
I'm posting here to see if anyone has any better insights than I have
had so far and/or any comments on my existing document linked
above.
It looks like the webforum world is pretty thoroughly PHP-based, about
which I know nothing, so I have no technical comments.
Steven Jones writes:
8-
This list is not the appropriate place for your RedHat packaging issues.
8---
I can appreciate this, but Im trying to determine what is going
wrong so I can be sure in taking it to RH they have stuffed up.
This is *exactly* why you should go to
Nigel Woodley writes:
I understand other mailman type products offer this functionality for the
very reason that I have outlined.
What you are saying implies that an explicitly untrusted host is
allowed to inject content into a secure network based on the most
easily forged identification on
Chuck Peters writes:
According to earthlink our newsletter may be re-added in the future should
the server be discovered to again be open for relay. Just one big problem
with that statement, we have never been an open relay!
I have confirmed that the server at the IP you list is not
Larry Stone writes:
Speakeasy the ISP is speakeasy.net.
Ah, thank you for the correction.
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Steven Jones writes:
I just upgrade Mailman but for some reason it seems to be talking
to postfix on ::1 and postfix does a relay denyFor mailman is
this normal? Or do I have a misconfiguration?
I gather that you had a working Mailman installation that stopped
working on upgrade. If
J. Bakshi writes:
I have installed mailman here. I have followed the suse README file
shipped with this mailman package and done the configuration
accordingly.
Is the SuSE README file *specifically for virtual domains*? If not,
it is *very* likely that much of what is in there is
T6 Webmaster writes:
Is there a way to prevent the list email address appearing when a user
chooses Reply to All?
Not in the way you state it. That's under control of the user's mail
program, and inclusion of the list's address is the logical outcome of
a command called Reply to All.
There
Richard Haas writes:
Is there a more straightforward way to lock/unlock a mailing list?
Sure -- write your pruning code in Python.wink/
What's the big deal about a three-line withlist script? That's really
the only way to guarantee that you'll get correct locking in the
future with upgrades
Syafril Hermansyah writes:
And then when any list-administrator/moderators make approval (of held
messages) or add/remove any member, there is mail notification to
listname-owner/listname-moderators that message has been approved or new
member has been added or membership has been
Syafril Hermansyah writes:
So I speak for them, who has a little knowledge of IT but willing to run
mailing list.
Well, if they have little knowledge of IT, then you should do the
workflow analysis for them. It's not a good idea to just do what
users request, because they don't know what
Lindsay Haisley writes:
One of two things needs to happen. Either the list server should refuse
and bounce posts with no MIME text/plain part,
Refuse, maybe, but bouncing is a problem (spam-by-backscatter). But
refusing such mail is only going to confuse the kind of subscriber who
is as
Anne Wainwright writes:
The first is reflected in the users FAQ 3.10 How to enforce a
text-plain policy. The answer being with difficulty because this
option probably (as I read it) ensures that any message with
non-plain-text content is completely, utterly, and totally, rejected,
even
Serving Soon writes:
I followed the discussion on why this happening and I understand
the logic. But since Outlook is so spread among corporate users
worldwide, shouldn't mailman have its own workaround?
If there were a single workaround, that might make sense. But there's
a big
francis picabia writes:
On second thought what we needed is similar, but probably:
SENDER_HEADERS = ('from')
Would there be problems from this?
Yes; anybody who can reach your MTA can very easily spoof an internal
address in from, although even the envelope sender is not hard to
Jeffrey Walton writes:
I wish these list managers would get a f**king clue and do things
securely.
By which you mean what? What we've learned over the last 30 years is
that when application developers try to do security, they generally
miss something. AFAICS Mailman 2 did the right thing
Jeffrey Walton writes:
The best I can tell, Mailman 2 did the wrong thing.
Against what threats with what level of security do you have in mind?
Confer: list managers did not fix Mailman 2 (nor did they use other
software which was secure). Why would you expect them to research
and
Jeffrey Walton writes:
The best I can tell, the Mailman threat model is naive or unrealistic.
It's neither. It merely corresponds to a very low level of security,
and you are told that when you subscribe.
There are at least three threats which should be modeled.
Should. Why? And why
Christopher Woods \(CustomMade\) writes:
Crikey Mark, thanks for your great response
Yeah, +1 to that!
Have to cop to it - part of the reason I went with that specific
install guide was because I'm working in a DA environment (a little
nonstandard to begin with).
DA == disability
Gerard Henry writes:
i'm sorry if this is a newbie question, but why the moderator is not
taken as a member of a list?
-1
Some moderators moderate many lists (in some cases, hundreds, but
dozens are not uncommon), and are members of few. For those people
who operate that way,
Frank Bell writes:
I guess the payoff is that the software works well, is free, and
maintained for free.
Plus, we have Mr Sapiro who nicely answers our questions for free.
Thanks Mark!!
I'll certainly second this!
Sorry, the response just bugged me.
I understand your
Peter STUMPF writes:
*version of mailman: 2.1.1
Did you write that correctly? That's very old.
The message just disappeared.
Was it just one message, or is the fault repeatable?
I went to the logs of exim and found the message had been processed
correctly.
In the logs of
Stefan P. Wolf (NassRasur.com) writes:
Now I would like to be able to create also a *real* mail
account with the same address, for SENDING (outgoing mail)
only.
I think all you need to do is create the mailing list as usual, and
then create the system user with the same name. The mailing
Bruce Harrison writes:
Is there any way to identify which moderator approved a post.
I've looked thru the /logs files and didn't see anything.
Assuming it was done via the web interface, you could get the
timestamp from the Mailman logs, then go to the webserver log and find
out who accessed
Lucio Chiappetti writes:
I guess a quick workaround for me would be to use the To: field instead of
List-Id, but I wonder if a future mailman version could consider a way to
include the list management keywords in the Message/RFC822
components !
This wouldn't be hard to do, I think,
Larry Stone writes:
Why do you want to reply to email addressed to the list as the list rather
than as you. That is not the way lists are normally used (e.g. I am
replying to mail sent to this list as myself, not as the list).
Yup. But he explained this. The list is the public face of
Geoff Shang writes:
On Wed, 8 Feb 2012, Stephen J. Turnbull wrote:
Yup. But he explained this. The list is the public face of a
committee, and at least some outgoing mail should appear to be from
the committee.
Couldn't this be done by sending from an existing account
Lluis Montoliu writes:
At hosting level they keep indicating that mailman is outdated, no
longer maintained and that we should consider moving to other
programs
Your hosting service is either really failing to do their homework, or
outright lying to you. Mailman is very much
Frank Bell writes:
After an upgrade last night all our lists can send email except one.
It is rejected by the smtp server it says that address does not exist.
The mailman page for the list exists, the mbox file exists
Any thoughts on what went wrong and how to fix it? (just happens to be
Con Wieland writes:
for p in ; \
This is the problem. There is a variable that should contain a list,
and it's empty. I think you can probably get past this by wrapping
the variable in (not ''), but I don't know if that is TRT.
--
Mark Sapiro writes:
Stephen J. Turnbull wrote:
Con Wieland writes:
for p in ; \
This is the problem. There is a variable that should contain a list,
and it's empty. I think you can probably get past this by wrapping
the variable in (not ''), but I don't know
On Mon, Mar 12, 2012 at 8:28 AM, Sascha Rissel sas...@rissel.it wrote:
One general question, to Manuel and those who might be familiar:
I suppose there is no API like a web service or something available an APP
could use?
Not in Mailman 2, but there's a RESTful API in Mailman 3.
So parsing
Stephen J. Turnbull step...@xemacs.org
On Mon, Mar 12, 2012 at 8:28 AM, Sascha Rissel sas...@rissel.it wrote:
One general question, to Manuel and those who might be familiar:
I suppose there is no API like a web service or something available an
APP
could use?
Not in Mailman 2
On Sat, Mar 24, 2012 at 3:00 AM, Barry Warsaw ba...@list.org wrote:
Hello Mailman enthusiasts!
I'm also ecstatic to announce the first alpha release of Postorius, our new
official name for the Django-based Mailman 3 web user interface. The name was
suggested by core developer Florian Fuchs
On Tue, Mar 27, 2012 at 1:25 PM, Amit Bhatt misterbh...@gmail.com wrote:
What is the differentce between Postorius and Mailman,
They're different but related applications. Mailman handles mail and
provides an API for administration, including user management.
Postorius provides a web UI for
On Wed, Mar 28, 2012 at 9:34 PM, Steve Matzura sm...@noisynotes.com wrote:
user unknown in virtual mailbox table. My question is, why doesn't
the web interface create new list feature update the aliases file?
What aliases file? Exim, for example, doesn't need one at all. There
are many MTAs,
On Tue, Apr 3, 2012 at 6:56 AM, Khalil Abbas khillo...@hotmail.com wrote:
sorry I know it’s a dumb question after all these years, but how do you clear
the mailman queue from command line??
Why do you think you need to do this? I'm asking because I saw your
followup to Mark saying you
On Fri, Apr 20, 2012 at 5:56 AM, David d...@fiteyes.com wrote:
I'm not sure what you call the long tail of footers that accumulates on
messages,
Collateral damage from MUAs That Only A Professional Programmer Who
Hates His Job (And His Users) Could Love[tm]. Because of the
potential for
On Fri, Apr 20, 2012 at 1:06 PM, David d...@fiteyes.com wrote:
The main issue is that we include a personalized instant unsubscribe link
in the footer, no password required. Our users seem to really want/need
this.
Aha. Now this all makes sense.
An alternative to requiring a password is to
On Sat, Apr 21, 2012 at 12:16 PM, David Andrews dandr...@visi.com wrote:
Remember that top posting isn't the evil thing that some of you think it is,
Don't jump to conclusions:
http://turnbull.sk.tsukuba.ac.jp/Teach/IntroSES/socsys-8.html
The question is, why was there a problem, and it turns
On Sat, Apr 21, 2012 at 12:17 PM, David Andrews dandr...@visi.com wrote:
I run about 200 lists that serve the blind community, and we tend to prefer
top posting.
That makes sense. T. V. Raman top-posts even on Emacs lists.
It is easier to find the new content. So getting rid of footers in
Oops, premature send, stupid touchpad. Continuing.
On Sat, Apr 21, 2012 at 12:17 PM, David Andrews dandr...@visi.com wrote:
it would also be nice if digests had some kind of navigation between
original messages.
A decent MUA allows you to treat a digest as a folder, or as a mail
spool (so
On Mon, Apr 23, 2012 at 8:30 PM, Pearl Dean Newsletter
donotre...@pearlanddean.com wrote:
Having a problem with Mailman and Hotmail.
The Mailman and is redundant
All other e-mail providers are fine and show the correct Sender and Subject
line.
That is pretty strong evidence that
On Tue, Apr 24, 2012 at 12:31 PM, Mark Sapiro m...@msapiro.net wrote:
Patricia A Moss wrote:
I would like to move the very old archives off of the server and
into a text file, or perhaps a pdf, to clear space on my server.
There already is a plain text mbox format archive at
On Tue, Apr 24, 2012 at 2:48 AM, David d...@fiteyes.com wrote:
Yes, Mollem is designed for blogs and web forms. So what do most Mailman
admins use? Maia Mailguard, SpamAssassin, ClamAV? I guess this must be a
common question, but I don't see any mention of it in the Mailman FAQ. Is
it a more
On Wed, Apr 25, 2012 at 2:20 AM, Mark Sapiro m...@msapiro.net wrote:
Stephen J. Turnbull wrote:
I forget, have headers been cleaned out?
No, The LISTNAME.mbox file contains the entire message. Some
headers may have been removed by pipeline handlers [...], but [...]
Received: headers
On Thu, Apr 26, 2012 at 4:39 PM, Anne Wainwright
anothera...@fables.co.za wrote:
I recently sent an invite to an unknown third party.
Normally I agree with Brad Knowles on this kind of thing, but this
time I can't go 100%.
People regularly do make contacts with third parties that they have
not
David writes:
apparently I missed something. The problem was simply permissions -- the
well-known Ubuntu issue.
Not just Ubuntu. I believe pretty much every system that Mailman runs
on runs into these issues every once in a while.
It's important to run bin/check_perms every time you
dhanushka ranasinghe writes:
Hi..
As you correctly mention when i click the link in the mail, it ask to click
unsubscribe button unsubscripted ..After clicking , it get pormt
another page called *Enter confirmation cookie* Any idea why this is
happening..
Check that the cookie in
Lindsay Haisley writes:
It's probably just as easy to bypass the precompiled Ubuntu package and
work straight from the Mailman distribution. If I have issues, which
are ususally creative problems with Python, I'd much rather work with
the Mailman devs than with Canonical :-)
We do like
Mark J Bradakis writes:
So my mailing lists are getting hit by spam that goes to the lists
since it claims to be from some poor subscriber whose email got
hijacked. But to be more general, what are some of the current
best practices to filter out spam in a postfix mailman environment
Mark Sapiro writes:
rant
That sounds good,
Be fair, Mark. :-) When the distro package works, it *is* good. And
it works most of the time AFAIK.
but evidently, judging from the number of Debian/Ubuntu packge
users who come to this list with mail delivery issues because they
have
Jérôme writes:
Anyway, collaborating with the packagers to improve packages and avoid
troubles in the first place is of course the best, yet time-costly.
Ah, but Mark's time is the (second-most? :-)[1] valuable resource we
have. That's why I've more or less volunteered.
Footnotes:
[1]
Anne Wainwright writes:
This clearly makes the point that spam is defined by two factors
A message is Spam only if it is both Unsolicited and Bulk
That's true, but as far as I can remember definitions of UCE
(unsolicited commercial email) have no such restriction to bulk.
Anne Wainwright writes:
I have sinned and stand repentant. I hate spam as much as anyone and we
get plenty to deal with. Somehow the Viagra and get rich emails didn't
seem to stand on the same level as a once-off invite.
They don't, from the point of view of the sender or society at large.
Jeff Conley writes:
I tried to do this yesterday, and began receiving the below error
message. I also receive it when I try to set the global moderation
bit.
Any help would be greatly appreciated!
--
Not Acceptable
An appropriate
You probably should move this thread to mailman-developers; the
primary developer of Mailman 3 internals only intermittently hangs out
here, while most of the subscribers here are waiting for just two
words on Mailman 3: It's released! :-)
Danci Emanuel writes:
David writes:
If she pressed the this is SPAM/Junk-Button 23 times today, you
would think she would remember doing it when we asked her today.
It could be fat finger syndrome: Gmail, for example, puts the Report
Spam button next the Delete Message button. I wouldn't be surprised
if Yahoo!
David writes:
Is there any method to identify the user from the AOL feedback loop?
Not for sure. Over time, they seem redact ever more information from
the report.
If not, how does AOL expect us to unsubscribe the user who complained?
Why would they care? Customers rarely remember
Lindsay Haisley writes:
So what would be the implications of hacking an extra header into
outgoing posts on lists for which personalization is enabled, say
X-Subdata, with said header containing a hash of the subscriber
address to which the post is directed?
I would use
Lindsay Haisley writes:
Good suggestion. I assume that Mailman never inserts
Resent-Message-ID into posts, is that correct?
Currently it doesn't, it seems, but there have been proposals to make
it do so (related to DKIM IIRC). However, if and when it does, it
wouldn't hurt to add your
David writes:
In terms of privacy, as list admins we already have the member's
information. All we are doing in this case is helping that member stop
receiving messages they obviously no longer wish to receive. This is
clearly not an invasion of privacy (especially with a properly
Brad Knowles writes:
On Jun 18, 2012, at 11:44 AM, Lindsay Haisley wrote:
It might be very convenient to have what one might call EVERP, where the
recipient address is encrypted into the envelope sender address, as an
alternative choice to Mailman's VERP implementation.
It's just
Lindsay Haisley writes:
EVERP = Encrypted VERP
Ever heard of Occam's Razor? Most folks who run Mailman lists can't
expand VERP, and wouldn't understand the expansion when told. It's
not obvious to me that practioners would get it right, either. Let's
not proliferate unnecessary acronyms.
Geoff Shang writes:
Ah, but we can just say this allows us to VERP without exposing
addresses on anybody's disk; this helps protect your users' privacy.
Oh the irony.
Thank you for noticing!
--
Mailman-Users mailing list
Lindsay Haisley writes:
Well the implementation I've developed for use with Resent-Message-ID
incorporates a random factor into the AES encryption so that every
encryption of the same address is different, although all decrypt
properly using the key with which they were encrypted. This
Lindsay Haisley writes:
provided to properly unsubscribe from a list, so they just find all the
list posts that they can and report them as spam, hoping that AOL will
help them unsubscribe.
Which is exactly what AOL's feedback service is designed to
prevent. :-( More irony
The sad
Lindsay Haisley writes:
Any chance of requesting this in Mailman 3?
As usual, the advice is to file a bug report/RFE on Launchpad, Mailman
project, tag it Mailman 3 (or maybe that's milestone Mailman 3?)
If you want more discussion from the core people (well, Barry; Mark's
presumably already
Lindsay Haisley writes:
I posted code and patches earlier on this list, but the patch is against
Mailman 2.1.15 rather than Mailman 3, which is the current development
focus. I imagine it's rather different.
The code is organized quite differently, but I suspect that the
handler
Lindsay Haisley writes:
On the lists which I administer myself I try to make the unsubscribe
process very easy and transparent. Every user who tries,
unsuccessfully, to unsubscribe is sent the following clear and
unambiguous message with easy-to-follow instructions:
But no goats?!
501 - 600 of 1551 matches
Mail list logo
