Daniel Black wrote:
On Thursday 08 October 2009 17:07:30 Stephen J. Turnbull wrote:
Wouldn't it be more straightforward (not to mention that it would work
for many more lists) to have an LDSP RFC, whose first draft simply
takes the ADSP RFC and substitutes "mailing list" for "author"
everywhe
Thomas Hochstein wrote:
> Barry Warsaw schrieb:
[2... signed email]
>> 4. Add a new shared password just for this purpose. [...]
>
> I'd prefer that.
+1 for ((2 || 4) || (2 && 4))
>> 1. We can drop the concept altogether. This means there'd be no way
>> to post a message as coming from an
--On Thursday, September 28, 2006 11:39 PM -0500 Brad Knowles
<[EMAIL PROTECTED]> wrote:
> At 11:19 PM -0400 9/28/06, emf wrote:
>
>> It seems to me like anyone likely to end up with a huge enough incoming
>> mailman queue to care about Maildir's inefficiencies would also be able
>> to put a s
--On Thursday, September 28, 2006 1:07 AM -0400 Barry Warsaw
<[EMAIL PROTECTED]> wrote:
> Or is there some way I'm missing that would allow us to segregate
> some domain traffic to Mailman's LMTP server and other traffic to
> Postfix's standard transports? What about Sendmail?
Shouldn't be an i
--On Wednesday, September 27, 2006 11:54 PM -0400 Barry Warsaw
<[EMAIL PROTECTED]> wrote:
> Looking at Postfix, what other options are readily available? I suppose
> you could try to hook into the transport maps, but if I understand them
> correctly, you're still talking about forking a proce
--On Wednesday, September 27, 2006 10:09 PM -0400 Barry Warsaw
<[EMAIL PROTECTED]> wrote:
> I'm not up on the development/release plans of RHEL. When do you
> think they might release a version with Python 2.4 support? The same
> kind of goes for OS X, which ships with Python 2.3 on Tiger. I h
--On Wednesday, September 27, 2006 3:04 PM -0400 Barry Warsaw
<[EMAIL PROTECTED]> wrote:
> I'd like to know what you think about updating our Postfix virtual
> delivery hooks to use this technique, and about making Maildir
> delivery the default. We'd keep the old way around for MTAs that
> don'
--On Wednesday, September 27, 2006 11:54 AM -0400 Barry Warsaw
<[EMAIL PROTECTED]> wrote:
> Then there is the question of what versions we support for Mailman
> 2.2, which is currently under development. Previously we've said
> we'll support Python 2.3 but I think we should revisit that decision
If the invited person uses the link included in an invite and tries to
cancel the invitation themselves, this happens
Bug in Mailman version 2.1.5
We're sorry, we hit a bug!
If you would like to help us identify the problem, please email a copy of
this page to the webmaster for this site with
--On Wednesday, June 23, 2004 20:21:14 -0400 J C Lawrence <[EMAIL PROTECTED]>
wrote:
On Thu, 24 Jun 2004 00:46:09 +0200
Brad Knowles <[EMAIL PROTECTED]> wrote:
At 10:22 AM -0400 2004-06-19, J C Lawrence wrote:
If the client generates the VERP, the MTA should pass that through
unchanged. At tha
--On Thursday, May 20, 2004 13:45:57 -0400 John Dennis <[EMAIL PROTECTED]>
wrote:
FC2 which was just released has 2.3.3 as will RHEL4. Red Hat users if
they use Red Hat rpms will never have to build Python from source.
Speaking as a RHEL 3.0 (3.1 Real Soon Now - maybe this one will work!)
custom
[ I am on the list, guys - no need to CC me... ]
--On Tuesday, May 04, 2004 12:40:27 -0400 J C Lawrence <[EMAIL PROTECTED]>
wrote:
That's true only while you maintain the "RFC-standard DSNs" qualifier.
Very few of the DSNs my lists receive are RFC-conformant.
So if they aren't compliant, we trea
--On Tuesday, May 04, 2004 10:25 AM -0400 J C Lawrence <[EMAIL PROTECTED]>
wrote:
On Tue, 4 May 2004 07:03:26 -0400
Paul Tomblin <[EMAIL PROTECTED]> wrote:
I do have some control over the MTA. But it does seem a little
ridiculous to filter out warnings (but not errors) just because
mailman ins
--On Friday, January 30, 2004 08:52:05 -0500 Kevin McCann
<[EMAIL PROTECTED]> wrote:
Why is it, then, that Lyris can send personalized messages to lists with
hundreds of thousands of members with no problem? I don't personally
If you'd read your own thread, you'd know the answer already. Lyris
It appears that my lists' password reminders are being sent from a now
bogus (but previously valid) envelope from address. I can't seem to track
down where it's getting the ancient address from. All the list traffic has
the correct envelope from address, it's just the password reminders that
ar
Currently, when you subscribe to a mailing list, the following occurs:
-> -request "subscribe"
<- received subscribe
(optional cookie send, respond)
<- subscribe results
<- list welcome
I'd _really_ like to not send the "I parsed your request and got no errors"
e-mail, as it is entirely redundan
A few questions have come up from one of my list users that I can't answer
(without delving into python source, anyway ;-).
I've mentioned the first one before, but I'm hoping the answer may have
changed with new code - is there any way to force line breaks in messages
without leaving a blank l
--On Wednesday, November 13, 2002 5:41 PM -0500 "Barry A. Warsaw"
<[EMAIL PROTECTED]> wrote:
BTW, I usually run current cvs on my personal domains, and very nearly
cvs on python.org, so if there's a serious regression in cvs, I
usually find out about it pretty quickly.
He fixed my "2.1b4 has
--On Monday, November 11, 2002 9:51 AM -0500 "Barry A. Warsaw"
<[EMAIL PROTECTED]> wrote:
Typo. LookupError is builtin.
Thanks! Much better - everything looks good so far.
--
Carson
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail
I just tried upgrading to the latest CVS (as 2.1b4 had some nasty bugs
reported), and got the following when trying to go to an admin page:
Bug in Mailman version 2.1b4+
We're sorry, we hit a bug!
If you would like to help us identify the problem, please email a copy of
this page to the webmast
, and fall back to Sender: if it doesn't.
--
Carson Gaspar - [EMAIL PROTECTED]
Queen Trapped in a Butch Body
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers
OK, personally, I think subject prefixes are evil, but I understand some
folks like them. But:
"[Mailman-Developers] [ mailman-Feature Requests-502278 ]"
as a subject prefix is just INSANE.
Can someone please do _something_ useful about this?
--
Carson
___
ise. If the mail list system in the DMZ can get the subscriber
data from the system inside your firewall, then so can any attacker that
compromises the mail list system. If you have some sort of read-only access
to the datastore, then you may be protected from corruption, but not
disclosu
--On Friday, March 08, 2002 11:49 AM -0500 "Barry A. Warsaw"
<[EMAIL PROTECTED]> wrote:
> There might be a way to defer this until SMTP delivery time, in which
> case we'd only create the copies in memory when talking to the smtpd.
Please! Exploding onto slow disk is bad...
Also, why create
--On Tuesday, March 05, 2002 4:38 PM -0500 "Barry A. Warsaw"
<[EMAIL PROTECTED]> wrote:
>
>>>>>> "CG" == Carson Gaspar <[EMAIL PROTECTED]> writes:
>
> CG> So, am I missing some cool feature of wrap?
>
> Yup, any line
I just added a feature to wrap, that lets you specify line breaks. If the
last 2 characters on a line are \n, those characters are removed, and that
line is not filled.
--- Utils.py.DIST Tue Mar 5 13:42:25 2002
+++ Utils.pyTue Mar 5 13:42:31 2002
@@ -107,6 +107,9 @@
(Yesterday's CVS, Python 2.1.2, Solaris 8 SPARC)
I'm trying to customize the e-mail messages that go out in response to a
subscription (verify.txt and subscribeack.txt). Out-of-the-box, they get
mangled by Util.wrap(), causing havoc with our attempts at formatting. For
example, we can't have:
--On Tuesday, March 05, 2002 11:35 AM -0500 "Barry A. Warsaw"
<[EMAIL PROTECTED]> wrote:
> I, and lots of people, are using Python 2.2 today. I do all my
> primary testing on Python 2.2, so I feel confident in recommending
> it.
FYI, 2.2 is completely DOA on Solaris 8/SPARC. After I got it t
['bluefeather.org', 'boardstiffny.org']
Yet after running genaliases, my /var/mailman/data/virtual-mailman is
zero-length.
--
Carson Gaspar - [EMAIL PROTECTED]
Queen Trapped in a Butch Body
___
Mailman-Developers mailing list
Also, check_perms does _not_ complain about qfiles/in being missing.
--
Carson Gaspar - [EMAIL PROTECTED]
Queen Trapped in a Butch Body
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
unOS 5.8 box
with Forte 6.x.
*sigh* The problems with running such a low market share platform like
Solaris/SPARC *snort*
Again, can someone who knows how the Python team works please feed back
this info? I have no burning desire to get involved in Python core
development.
--
Carson Gaspar
x this, or if this is really a broken build process?
Now to try and fix audioop and fpectl...
--
Carson Gaspar - [EMAIL PROTECTED]
Queen Trapped in a Butch Body
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
? Can I just use my python 2.0
installation until someone else makes this nightmare go away?
--
Carson Gaspar - [EMAIL PROTECTED]
Queen Trapped in a Butch Body
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
--On Friday, June 22, 2001 1:59 AM -0400 "Barry A. Warsaw"
<[EMAIL PROTECTED]> wrote:
> - incoming commands (i.e. bounces, -request, -owner, -admin, -join,
> -leave)
> It's fairly easy to add more queues, although I'm not sure what else
> would be useful. Some other features of the 2.1 queue
h was preventing anything from getting done, and
making the machine _very_ unhappy.
So I recommend a quick fix of splitting the queue into 3 parts, and a
medium term fix of adopting one of the tiered directory structures
(postfix, new sendmail, etc.).
--
Carson Gaspar - [EMAIL PROTECTED]
Queen tr
red, will retry soon,
etc.).
What I want to do is ignore the bounce (don't flag the list member), but
_not_ forward the message to the list admins. The current API seems
incapable of doing this. Am I missing something?
--
Carson Gaspar - [EMAIL PROTECTED]
Quee
Attached is one of the postfix messages that the bounce handler misses.
--
Carson Gaspar - [EMAIL PROTECTED]
Security Architect - Global Networking and Computing, Inc.
This is the Postfix program at host mail.knoware.nl
mailman 2.0.5 does not handle Postfix DSN messages for delayed mail. Has
this been fixed in the development tree, or should I attempt to patch the
code myself?
--
Carson Gaspar - [EMAIL PROTECTED]
Queen trapped in a butch body
___
Mailman
38 matches
Mail list logo
