Setup: Debian AMD64 (mixed testing/stable)
Exim 4.62 (exim-daemon-heavy)
Mailman 2.1.8 compiled from source, non-std debian policy install
Per domain independent installation of mailman in
/var/virtual/$domain/mailman/...
Bretton Vine said the following on 2006/09/13 09:28 AM:
Sep 03 13:52:25 2006 qrunner(7888): charset, language, value =
decode_rfc2231(EMPTYSTRING.join(value))
Sep 03 13:52:25 2006 qrunner(7888): File MMHOME/pythonlib/email/Utils.py,
line 284, in decode_rfc2231
http://rfc.net/rfc2231.html
Am Do, 7.09.2006, 15:57, schrieb Mário Filipe:
Hello
I have two problems with digests, and maybe you can help me:
- on one mailing list some users complain that they don't get their own
posts when they get the digest. I've tried this on a test list and i get
my posts so my question is if
Hi,
for our University I want to setup automatically mailinglists for each
course and study year (some 10.000 mailing lists).
I wonder, is something available for this aim?
I could adapt newlist to make it non-interactive
and script it with add_members,
but probably some of you did this
Am Mi, 13.09.2006, 12:58, schrieb Hans-Juergen Beie:
Am Do, 7.09.2006, 15:57, schrieb Mário Filipe:
Hello
I have two problems with digests, and maybe you can help me:
- on one mailing list some users complain that they don't get their own
posts when they get the digest. I've tried this on a
In short:
Replace the first line in /usr/lib/mailman/cron/senddigests
# ! /usr/bin/python
by
#! /usr/bin/python2.3
if you have a Python2.3 installed.
As this problem appeared here (debian/etch, Mailman 2.1.8-2) after
upgrading Python 2.3 to 2.4 this seems to be reasonable.
Hi, I
Tokio Kikuchi wrote:
In short:
Replace the first line in /usr/lib/mailman/cron/senddigests
# ! /usr/bin/python
by
#! /usr/bin/python2.3
if you have a Python2.3 installed.
As this problem appeared here (debian/etch, Mailman 2.1.8-2) after
upgrading Python 2.3 to 2.4 this seems to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the GNU Mailman development team, I'm please to announce
GNU Mailman 2.1.9. This is primarily a security and bug fix release
and it is highly recommended that all sites upgrade to this version.
Mailman 2.1.9 also contains support
Hello
Some users of our mailing lists are complaining that when using the
archives, sorted by date, some messages are skipped when using the Next
message and Previous message links. For example:
Message 1
Message 2
Message 3
Message 4
Message 5
Message 6
Message 7
Message 8
Message 9
Message 10
Op Wednesday 13 September 2006 13:30, schreef Frederik Questier:
Hi,
for our University I want to setup automatically mailinglists for each
course and study year (some 10.000 mailing lists).
I wonder, is something available for this aim?
I could adapt newlist to make it non-interactive
Can I go directly from Mailman 2.1.6 to Mailman 2.1.9 by doing the following
./configure
make install
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ:
How can I set mailman to use the MX record instead of localhost (or one
static address) for sending mail?
Thanks!
Jay Vaagen
Certified Technician
Abadata Computer Corporation, Inc.
mailto:[EMAIL PROTECTED] [EMAIL PROTECTED]
Phone: 989 883 3411
Fax: 989 883 9313
Tokio Kikuchi said the following on 2006/09/13 02:45 PM:
Can you try these and check the email version?
snip
The email-3.0.x in Python 2.4 is not suitable for mailman. Mailman
2.1.8(or 9) works best with the email-2.5.7(or 8) which is the bug fix
version of Python 2.3 library.
Working
On 9/13/06, Kory Wheatley [EMAIL PROTECTED] wrote:
Can I go directly from Mailman 2.1.6 to Mailman 2.1.9 by doing the following
./configure
make install
Yes*.
(You need to make sure you run ./configure with the same options you
ran it with originally, otherwise you might end up with duplicate
Hello,
Looking at similar problems in the future...interesting to think about.
We're looking at PHPlist,
PHPList is all web-based, isn't it? Some clients may want to respond over
email.
DadaMail and other packages. We need to be
able to send up to 100,000 at a shot, announce only, use
On Wed, Sep 13, 2006 at 11:59:04AM -0400, Kucera, Rich wrote:
DadaMail and other packages. We need to be
able to send up to 100,000 at a shot, announce only, use MySQL
Have you dbdump-ed a list pickle? Do you really want all that in MySQL?
What for?
Share some of the information with
Barry Warsaw said the following on 2006/09/13 04:00 PM:
On behalf of the GNU Mailman development team, I'm please to announce
GNU Mailman 2.1.9. This is primarily a security and bug fix release
and it is highly recommended that all sites upgrade to this version.
Excellent news, just one
On 9/13/06, Jay Vaagen [EMAIL PROTECTED] wrote:
How can I set mailman to use the MX record instead of localhost (or one
static address) for sending mail?
I've added FAQ 4.72
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.072.htp
as a simple answer for this.
P.S., to the list, this
use MySQL
What for?
Share some of the information with other applications, eg: name, email,
password.
Well if you're talking strategic SQL access, either of these (*if only* they
supported ODBC calling mechanisms) you could bolt it onto mailman and have at
it:
At 11:54 AM -0400 2006-09-13, Jay Vaagen wrote:
How can I set mailman to use the MX record instead of localhost (or one
static address) for sending mail?
You don't. Mailman is not an MTA, so it knows nothing of MX records.
Maybe you can tell us more about where you want to get, and then
Patrick Bogen wrote:
On 9/13/06, Jay Vaagen [EMAIL PROTECTED] wrote:
How can I set mailman to use the MX record instead of localhost (or one
static address) for sending mail?
I've added FAQ 4.72
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq04.072.htp
as a simple answer for this.
Jim Popovitch wrote:
The problem with this approach is that Mailman will still only use the
single specified mail server, rather than processing a list of
mailservers defined as MX records for a DNS domain.
If I have a domain name for which there are 3 MXs setup in a Round
Robin
Ok, so after reading all this it becomes clear to me that this is not going
to be an easy fix..
If I understand all this correctly, there's no current feature that will
allow mailman to send mail from the correct virtual domain's hostname, and
not localhost.. correct?
Let's say I have these
In a flurry of recycled electrons, Jay Vaagen wrote:
If I understand all this correctly, there's no current feature that will
allow mailman to send mail from the correct virtual domain's hostname, and
not localhost.. correct?
As I understand the current implimentation of virtual domains, much
Carl Zwanzig wrote:
Probably the easiest way to get the 'multiple' domains that you want
is to run one instance of mailman for each domain. Yoy can then configure
the smtphost for that specific domain.
And to second this part of Carl's e-mail, this is exactly what I'm
doing on my end. I
Hi,
The email-3.0.x in Python 2.4 is not suitable for mailman. Mailman
2.1.8(or 9) works best with the email-2.5.7(or 8) which is the bug fix
version of Python 2.3 library.
I see. How can I fix that?
I suspect the debian people have omitted the mailman-2.5.x package from
their ports.
Bretton Vine writes:
What gives? What is odd is that some files with ' in the
filename go to the list while others don't. I've tried changing
characterset in mail client to no avail.
This is a completely different issue IIRC. For reasons I don't think
I've ever seen explained, the
On 9/12/06 11:26 AM, Dragon [EMAIL PROTECTED] wrote:
Version 2.1.5 is rather old. I believe there are some security issues
that have been fixed since that release. IMO it is a good idea to use
the latest version to preclude as many potential issues as possible.
The security fixes are very
At 1:53 PM -0400 2006-09-13, Jim Popovitch wrote:
The problem with this approach is that Mailman will still only use the
single specified mail server, rather than processing a list of
mailservers defined as MX records for a DNS domain.
Mailman is a Mailing List Management system. It is
At 2:57 PM -0400 2006-09-13, Jay Vaagen wrote:
If I understand all this correctly, there's no current feature that will
allow mailman to send mail from the correct virtual domain's hostname, and
not localhost.. correct?
Mailman is a Mailing List Management system, not an MTA. The kind of
On Wed, 2006-09-13 at 23:23 -0500, Brad Knowles wrote:
At 1:53 PM -0400 2006-09-13, Jim Popovitch wrote:
The problem with this approach is that Mailman will still only use the
single specified mail server, rather than processing a list of
mailservers defined as MX records for a DNS
At 12:51 AM -0400 2006-09-14, Jim Popovitch wrote:
Looking up MX records is also the job of an MUA, and Mailman is very
much like an MUA, albeit on steroids. IMHO of course.
I don't know of an MUA on the planet that looks up MX records.
Check your RFCs. Checking MX records is most
32 matches
Mail list logo
