certificate not trusted

I have been using Mutt or many years, but just recently it ceased to retrieve mail. I tested it with fetchmail -c and got the following error: fetchmail: Server certificate verification error: unable to get local issuer certificate fetchmail: Server certificate verification error: certificate n

Re: Refused by Server

For the use of any others who use Leopard Migration Assistant and find they have hammered their previous postfix settings. The previous /etc/postfix/main.cf configuration file does NOT get moved to the new location by Migration Assistant, and must be placed there manually. When I replaced /

Refused by Server

When sending mail from mutt I have begun getting the following message in /var/log/mail.log: Jan 31 07:02:37 bill-2 postfix/smtp[868]: E0F13CD105: to=<[EMAIL PROTECTED]>, relay=mx1.comcast.net[76.96.62.116]:25, delay=0.73, delays=0.29/0.1/0.33/0, dsn=4.0.0, status=deferred (host mx1.comcast.net

Re: Leopard Migration Hammered Mutt

Here's what I was able to come up with about path_helper: ___ "In Leopard, Apple has introduced a new mechanism for managing and maintaining your system path ($PATH). Previously (and in most current Linux environments) paths were managed by

Re: Leopard Migration Hammered Mutt

Thanks for the thorough explanation. It helped me to grasp how the whole Path thing works. Since I would like to add /sw/bin to my /etc/profile I opened it, but only discovered: ___ # System-wide .profile for sh(1) if [ -x /usr/libexe

Re: Leopard Migration Hammered Mutt

Thanks, Your suggestion below pointed out that .bash_profile is the initialization file. But .bash_profile has no references to Path in it. I can add PATH=$PATH:/sw/bin as you suggested, but will adding this override my original Path variable, or simply add it to the existing path? If it

Re: Leopard Migration Hammered Mutt

export shows: PATH="/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin" Mutt is in /sw/bin/ How can I add /sw/bin/ to my path? Thanks, Bj ___ -- Original message -- From: Jonas Jacobsson <[EMAIL PR

Leopard Migration Hammered Mutt

Recently, I switched from and older MacBook Pro to a new MacBook using Apple's Migration Assistant. All User issues went well, but unix issues did not fair so well. One of which was my mutt setup which had worked for years, and even many months under Leopard. Now I get the following when I at

Re: What Version for Leopard?

Thanks Kyle: >my guess is that you really just need to recompile mutt (and > possibly all the libraries you installed that it relies on) ... Since it's been a long time since I did any of this, your suggestion sounds a bit daunting. This is the bit where I need you to go slow ... What I don't

Re: What Version for Leopard?

Kyle: Thanks for the clear explanation. My reason for asking all of these questions is since installing Leopard Mutt, more than often not, goes into processor sucking mode (taking as much as 60% to 80%), until i finally have to kill it. This never happened all of the time I used Mutt under Tig

Re: What Version for Leopard?

Thanks Brendan: Your reply got me researching how I originally installed Fetchmail, and it appears I used Darwin Ports. port search 'fetchmail' fetchmailmail/fetchmail @6.2.5 Do you have any idea if Fetchmail can be upgraded through Darwin Ports, or does the new version have to be comple

What Version for Leopard?

I've been using Mutt for a couple of years and have recently updated from OS X Tiger to OS X Leopard. #1. Are there any known issues with Mutt 1.4.2.1i and Leopard? #2. What is the recommended version of Mutt for Leopard? #3. How does one go about upgrading to a newer version of Mutt? (go s