alanpatriot.net
Date: Tue Apr 01 2008 - 18:48:29 CDT

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

> * Patrick Ben Koetter <pstate-of-mind.de>:
>> > -- mechanisms on smtp.patriot.net --
>>
>

>> If you get that too, then truly no mechanism is available and that would
>> match your error message:
>>
>> (SASL authentication failed; cannot authenticate to server
>> smtp.patriot.net[209.249.176.3]: no mechanism available)
>>

> However if you set smtp.patriot.net as relayhost and if you provide SMTP
> AUTH
> credentials in a sasl map, Postfix will try to authenticate.
>
> Sure, you set the correct relayhost? Did they change the setup and you
> think
> its your configuration because you udpated at the same time?
>
> We need telnet output from your host to smtp.patriot.net to find out if it
> offers AUTH to your host.

1. I am very grateful to all for your suggestions. I am forwarding on
all your E-mails to the tech-person at PatriotNet, who has also been
taken aback by the difficulty.

2. As previously remarked: the relayhost port 587 was put in at a
suggestion of the PatriotNet techie. He keeps suspecting that this
problem has something to do with the fact that I am using Verizon
to get my (dynamic) address. He is only partly convinced by my
assertion that I have been using my standard method/configuration
of postfix for the past several months, whereas my difficulties came
in only when I upgraded from sarge to etch eight days ago.

3. I am having an eye de-cataracted tomorrow, so I may not be as much
on line for the next couple of days as I could wish. At the moment
I'm doing E-mail on line, using the PatriotNet implementation of
squirrelmail. Need I say that this _sucks_?

Again my thanks to all. Maybe the PatriotNet tech-person will be
able to use your ideas and comments to get us straightened out.

Alan

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