On Thu, Dec 07, 2006 at 06:23:40PM -0600, Brad Knowles wrote:
At 4:57 PM -0500 12/7/06, Alan McConnell wrote:
Meanwhile, I am adminning(sp?), through my ISP, a new but quite active
E-list. But their mailman install is incomplete; they haven't put in
Pipermail(about which I know
Hello,
trying to setup mailman with virtual domains and postfix, no matter
what I tried I get No such mailbox, I postfix I set up the
alias_maps to hold the generated aliases that pipe to mailman and
virtual_alias_maps points to the file that holds the fully qualified
list addresses which
At 7:52 AM -0500 12/8/06, Alan McConnell quoted me:
Uh, what version of Mailman is that? I thought that Mailman had
fully integrated Pipermail along with the base code, for many years
now? Are they running Mailman 1.x or something?
mm 2.1.5 . But under Debian, so it has
Patrick Bogen wrote:
On 12/6/06, Anne Ramey [EMAIL PROTECTED] wrote:
I'm not sure how one of my list admins managed to do this, but they have
four members on their list that look like this in the membership list:
b
On Thu, 7 Dec 2006, Barry Warsaw wrote:
Have I mentioned recently how long I've been looking for a volunteer
to help make all this not suck? ;} Pipermail is just one of those
things that people either live with or ditch.
I've used Hypermail for probably a decade to archive Majordomo
Hello Brad,
First, many thanks for your long, useful and complete response (whaou...)
I'm not a email specialist but when I seen the message:
[ID 801593 mail.warning] kB6BcXf1016562: collect: premature EOM:
unexpected close )
I Think you are true, there is a problem on our Exchange server...
Mark Sapiro wrote:
Paul Tomblin wrote:
Quoting Barry Warsaw ([EMAIL PROTECTED]):
It already does escape From lines in the body of the message. It
does this by way of the email package's Generator class, which is
instantiated with mangle_from_=True.
Must be a newer version than the one in
Quoting Todd Zullinger ([EMAIL PROTECTED]):
Mark Sapiro wrote:
Paul Tomblin wrote:
Quoting Barry Warsaw ([EMAIL PROTECTED]):
It already does escape From lines in the body of the message. It
does this by way of the email package's Generator class, which is
instantiated with
Brad == Brad Knowles
Re: [Mailman-Users] Mailman archive messages(not rm, but install!)
Fri, 8 Dec 2006 08:52:26 -0600
Brad At 7:52 AM -0500 12/8/06, Alan McConnell quoted me:
Uh, what version of Mailman is that? I thought that Mailman
had fully integrated Pipermail along with
Paul Tomblin wrote:
Oh right, now I get it. I told you I didn't know Python, but I
should have been able to figure that
def __init__(self, outfp, mangle_from_=True, maxheaderlen=78):
meant that it defaulted to True in Generator.py so didn't need to be
changed in Mailman.
:-)
I actually
In honor of recent discussions on pipermail, I think I've found
another issue with archiving, though this seems to be in
Mailman.Scrubber.
In a few recent posts to the GnuPG lists, Werner Koch sent along some
signed patches fixing issues in the gpg code. Unfortunately, the
archives ate his
Anne Ramey wrote:
I should have mentioned that will not work for this case. You'll notice
that these are not all nice ascii characters. some are spaces, some
deletes, some other hex values...I don't know what they all are because
they will not copy and past nicely. They don't appear at all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Dec 8, 2006, at 11:10 AM, Paul Tomblin wrote:
In that case, shouldn't any message that reaches mailman with an
unescaped From_ line in the body already be handled properly? It
seems like something else must be borked. That or all of the
[EMAIL PROTECTED] wrote:
The mailman lists on my server have suddenly stopped delivering mail.
And what update to Mailman or Python was installed just before this
happened?
The error
of one of the messages is cut and paste below ... All the messages are being
shunted off and not delivered
Brad Knowles wrote:
At 7:52 AM -0500 12/8/06, Alan McConnell quoted me:
Uh, what version of Mailman is that? I thought that Mailman had
fully integrated Pipermail along with the base code, for many years
now? Are they running Mailman 1.x or something?
mm 2.1.5 . But under Debian,
The mailman lists on my server have suddenly stopped delivering
mail.
And what update to Mailman or Python was installed just before this
happened?
There was no update to either Mailman or Python ... but one of the
lists was hit with a *massive* amount of spam that caused too many
files
Todd Zullinger wrote:
In honor of recent discussions on pipermail, I think I've found
another issue with archiving, though this seems to be in
Mailman.Scrubber.
In a few recent posts to the GnuPG lists, Werner Koch sent along some
signed patches fixing issues in the gpg code. Unfortunately, the
SML wrote:
There was no update to either Mailman or Python ... but one of the
lists was hit with a *massive* amount of spam that caused too many
files open error, this same spam attack eventually caused the
server to run out of memory :(
And the reboot of the server could have caused things
Hi Mark,
Mark Sapiro wrote:
There seems to be another issue in that there is no 'link' to the
scrubbed part, just a relative URL which doesn't work.
Yes, there are other issues with the configuration there. Click on
the list info link and then follow that to the archives. You get into
the
All,
I am using mailman as installed and administered by a web host in
vancouver, webserve.ca.
When I set up a mailing list, the general contact address on the
mail.mail.domainname.ca/mailman/listinfo page is listed as
[EMAIL PROTECTED], rather than [EMAIL PROTECTED]
When I send a test email
Todd Zullinger wrote:
However, I created a fresh list on my system to see whether this was a
list configuration issue or not and it's reproduceable using a default
list setup. I initially thought it must be some over-agressive
content filtering, but after having it work on a virgin list I don't
Mark Sapiro wrote:
It shouldn't be a content filtering issue. If a part is missing a
Content-Type: header, the message methods get_content_type() and
get_content_maintype() which are used by MimeDel.py (content
filtering) return the default types which are text/plain and text
except for
Henrik wrote:
When I set up a mailing list, the general contact address on the
mail.mail.domainname.ca/mailman/listinfo page is listed as
[EMAIL PROTECTED], rather than [EMAIL PROTECTED]
The domain in this address depends on whether or not
VIRTUAL_HOST_OVERVIEW is set to Yes or No. The
Todd Zullinger wrote:
Attached is the original message from the list mbox and one that I
munged up to included a content-type: text/plain; charset=3Dus-ascii.
I see the symptom with the original message. I'll look further, but it
seems to have something to do with the fact that the first
At 11:43 AM -0500 12/8/06, John A. Martin wrote:
See http://packages.debian.org/unstable/mail/mailman for a
description of the Debian Mailman package that integrates
archiving Further down that page under the heading
Download mailman click on one of the list of files buttons
Quoting Brad Knowles ([EMAIL PROTECTED]):
At 11:43 AM -0500 12/8/06, John A. Martin wrote:
See http://packages.debian.org/unstable/mail/mailman for a
description of the Debian Mailman package that integrates
archiving Further down that page under the heading
Download
Thanks Mark,
If VIRTUAL_HOST_OVERVIEW is set to Yes, the domain is the result of
looking up the host domain from the URL used to access the page.
This appears to be the case:
In fact if I access the page with mail.domainname.ca/mailman/, the
contact address is [EMAIL PROTECTED], whereas if I
Henrik wrote:
If VIRTUAL_HOST_OVERVIEW is set to Yes, the domain is the result of
looking up the host domain from the URL used to access the page.
This appears to be the case:
In fact if I access the page with mail.domainname.ca/mailman/, the
contact address is [EMAIL PROTECTED], whereas if I
Paul == Paul Tomblin
Re: [Mailman-Users] Mailman archive messages(not rm, but install!)
Fri, 8 Dec 2006 20:04:51 -0500
Alan == Alan McConnell
Re: [Mailman-Users] Mailman archive messages(not rm, but install!)
Fri, 8 Dec 2006 07:52:33 -0500
Paul Quoting Brad Knowles ([EMAIL
At 10:17 PM -0500 12/8/06, John A. Martin wrote:
I've never claimed to be a Debian expert, and if they're
mucking about with packages that include certain features by
default in order to remove those features,
What makes you, Brad, think that Debian removes pipermail when
Brad Knowles writes:
I've never claimed to be a Debian expert, and if they're mucking
about with packages that include certain features by default in order
to remove those features, then there's not much I can do to help the
poor souls that are stuck with that kind of stuff.
That's
Hi all,
Mark Sapiro wrote:
Todd Zullinger wrote:
Attached is the original message from the list mbox and one that I
munged up to included a content-type: text/plain; charset=3Dus-ascii.
I see the symptom with the original message. I'll look further, but it
seems to have something to do
Brad == Brad Knowles
Re: [Mailman-Users] Mailman archive messages(not rm, but install!)
Fri, 8 Dec 2006 22:28:19 -0600
Brad At 10:17 PM -0500 12/8/06, John A. Martin wrote:
I've never claimed to be a Debian expert, and if they're
mucking about with packages that include
33 matches
Mail list logo
