alanpatriot.net
Date: Tue Apr 01 2008 - 13:45:03 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

With the upgrade from an Ancient Debian to merely a Middle-aged one, I
got of course a new version of postfix.

I had been using postfix as my MTA from my home machine to the outside
world, using the machine smtp.patriot.net as my relayhost. My postfix at
home is configured so that all mail goes out through this smart-host, and
appears to come from alanpatriot.net , and mail to me goes to the
PatriotNet system. I bring it home using fetchmail.

This has worked from me for several years. I had some difficulties a couple
of years ago, when PatriotNet installed SASL authentification, but after some
experimentation, some modules installed, and some counseling<g>, I got the
authentification working.

But this seems now to be broken. I try to send out E-mail and a call to
mailq reveals the message:
(SASL authentication failed; cannot authenticate to server
smtp.patriot.net[209.249.176.3]: no mechanism available)

I, and a tech support person at PatriotNet, have tried various schemes.
We have, I hope, all necessary libs installed, including libsasl2 and
libsasl2-modules, and I have the relevant files in /etc/postfix/:
the standard main.cf and master.cf, as well as smtp_sasl_passwd and
smtp_sasl_passwd.db.

I should also remark that I am using Verizon as my present "provider",
in the sense that Verizon gives me my dynamic address. This started
in the first week of January of this year. But I still use PatriotNet
as my E-mail provider, as described in the second paragraph of this
E-mail. This worked fine until I upgraded from Debian sarge to Debian
etch a week ago.

Any help/suggestions gratefully received. In particular, if this or
a similar problem had already been discussed, I'd appreciate a pointer
to the archives.

TIA,

Alan

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]