At 7:05 PM -0700 2004-08-30, Adam Boettiger wrote:
Of the following, is there a distribution that plays better with Mailman
than any of the others? :)
CentOS 3.1
Debian 3.0r1
Fedora Core 1
Gentoo Linux 2004-06-29
Mandrake 9.1
Red Hat 8.0
Red Hat 9.0
Slackware 10
Slackware 9.0
Well, if y
On Tue, 2004-08-31 at 10:00 +0200, Brad Knowles wrote:
> At 7:05 PM -0700 2004-08-30, Adam Boettiger wrote:
> Well, if you check the archives and the FAQ, in the past Red Hat
> and Red Hat derived distributions have had certain known problems
> with the RPMs that they have made available, b
At 9:39 AM -0700 2004-08-30, Adam Boettiger wrote:
Apologies in advance for this basic of a question but this is
technical in nature and thus doesn't seem appropriate for the
users or list owners lists.
BTW, I'd like to thank you for your good questions. This will
make excellent fodder for th
Brad Knowles wrote:
BTW, I'd like to thank you for your good questions. This will make
excellent fodder for the FAQ, and I'm surprised that it wasn't already
there.
Brad - No worries. Happy to be the guinea pig. ;)
Here's something else you may want to add as I'm sure I'm not the
only one
On Tue, 2004-08-31 at 04:00, Brad Knowles wrote:
> Well, if you check the archives and the FAQ, in the past Red Hat
> and Red Hat derived distributions have had certain known problems
> with the RPMs that they have made available, but I don't know about
> the current RPMs. Given their pas
On Aug 31, 2004, at 5:00 AM, Nigel Metheringham wrote:
I'd tend to take this as:-
* Mailman is a bitch to package
* RH have packaged it for a while
* RH found a good few of the gotchas in packaging Mailman
* RH have subsequently learnt from their mistakes and recently
On Tue, 31 Aug 2004 12:19:29 -0400
Terri Oda <[EMAIL PROTECTED]> wrote:
> On Aug 31, 2004, at 5:00 AM, Nigel Metheringham wrote:
>> Mailman is a bitch to package
> I believe point number one there says it all. :)
Many python applications are a bitch to package, especially if you also
want to m
At 10:45 AM -0400 2004-08-31, John Dennis wrote:
To the best of my knowledge the problems were addressed and there are
many satisfied users. We did ship a package with an install problem, but
then again bugs happen, its the nature of software. I'm not sure it's
fair for you to maintain a mailma
On Tue, 2004-08-31 at 14:06, Brad Knowles wrote:
> At 10:45 AM -0400 2004-08-31, John Dennis wrote:
>
> > To the best of my knowledge the problems were addressed and there are
> > many satisfied users. We did ship a package with an install problem, but
> > then again bugs happen, its the nature
I've read both FAQ's and used the FAQ Search Tool and it came up
empty, so this is something else you may want to add to the FAQ:
I see that you can insert customized fields into outgoing
messages by using the tag. Where can I find a
list of all field names available for insertion in this tag?
On Aug 31, 2004, at 3:18 PM, Adam Boettiger wrote:
I've read both FAQ's and used the FAQ Search Tool and it came up
empty, so this is something else you may want to add to the FAQ:
I see that you can insert customized fields into outgoing messages by
using the tag. Where can I find a list of al
Forgot to mention: I think there are also at least one verp-specific
variable that I didn't list, but I don't have time to search for 'em
right now. If someone knows what those variables are, please add them
to the FAQ entry too:
http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq03.041
Hi!
On Di, Aug 31, 2004 at 03:27:37 -0400, Terri Oda wrote:
> On Aug 31, 2004, at 3:18 PM, Adam Boettiger wrote:
>
> >I've read both FAQ's and used the FAQ Search Tool and it came up
> >empty, so this is something else you may want to add to the FAQ:
> >
> >I see that you can insert customized f
At 7:30 AM -0700 2004-08-31, Adam Boettiger wrote:
BTW, I'd like to thank you for your good questions. This will
make excellent fodder for the FAQ, and I'm surprised that it wasn't
already there.
Brad - No worries. Happy to be the guinea pig. ;)
Alright, I've spent some time writing and
14 matches
Mail list logo