[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: sasl authentication failed



On Sat, January 14, 2012 12:41 pm, Camale�n wrote:
> On Tue, 10 Jan 2012 20:09:21 -0500, Tony Baldwin wrote:
>
>> On Tue, Jan 10, 2012 at 08:01:17PM -0500, Tony Baldwin wrote:
>>> On Tue, Jan 10, 2012 at 05:21:24PM -0500, Tony Baldwin wrote:
>>> > On Tue, Jan 10, 2012 at 09:35:58PM +0000, Camaleón wrote:
>>> > > On Tue, 10 Jan 2012 13:12:25 -0500, Tony Baldwin wrote:
>>> > >
>>> > > > On Tue, Jan 10, 2012 at 01:05:16PM -0500, Tony Baldwin wrote:
>>> > > >> On Tue, Jan 10, 2012 at 04:58:06PM +0000, Camaleón wrote:
>>> > >
>>> > > (...)
>>> > >
>>> > > >> Okay, at this point, I am getting different errors. I think I
>>> > > >> resolved
>>> Crikey...
>>>

>
> Tony, I would forget about the SSL part until you have configured your
> Postfix to be in a workable state (sending/receiving e-mails with no
> errors). Afterwards, you can start to setup the SSL certificate but not
> before.
>

I do have it working now, but the cert is still wrong.


>> When I configured postfix, I gave it tonybaldwin.org tonybaldwin.org is
>> what shows in my main.cf I do know understand why anything says
>> vulcan.linode.com
>
> This can come from SSL certificate file :-?

yes, the cert says it is from vulcan.linode.com, while I am certain I have
my hostname set as vulcan.tonybaldwin.org
So, when I set up mutt at home, my laptop, etc., I see some error to the
effect that the cert is from vulcan.linode.com, which disagrees with the
host, vulcan.tonybaldwin.org.
I just choose "(a) accept always", and it works, but it seems to me it
would be better to have the cert correct.

As far as the rest, it seems there was some ghost sendmail process hogging
port 25.  I just killed that pid and restarted postfix and it works now.

./tony
-- 
http://tonybaldwin.me
all tony, all the time


Reply to: