At 4:02 PM -0800 2005-03-25, John W. Baxter wrote:

 And I have no way to help them.  I could probably manage to configure the
 old Exim to work with the new Mailman, but I have no interest in doing so.

Therein lies a big part of the problem. If you're not willing to help, and the rest of the Exim community feels the same way, then the people who are in this situation are doomed unless they switch to other software.


 On the other hand, the Python adjustment (if one is careful on an ancient
 RedHat installation, where much breaks if one removes Python 1.5.2, or
 points the name python at anything newer) is easier than the Exim upgrade,
 since there is a large canyon between Exim 3 and Exim 4.

This whole Exim 3/Exim 4 thing is not a problem with postfix. Don't get me wrong, postfix isn't perfect. But what flaws it has tend to be less visible than this, and the issue of upgrading from one version to another usually has more to do with whether or not a binary package with the new version has yet been prepared, or whether they're willing to take the risk of going straight to the original source.


--
Brad Knowles, <[EMAIL PROTECTED]>

"Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety."

    -- Benjamin Franklin (1706-1790), reply of the Pennsylvania
    Assembly to the Governor, November 11, 1755

  SAGE member since 1995.  See <http://www.sage.org/> for more info.
------------------------------------------------------
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=show&amp;file=faq01.027.htp

Reply via email to