On 8/29/07 at 5:40 PM, PowerMail Engineering ([EMAIL PROTECTED]) said:
>Hi Steve,
>
>>This broke the other day when I had to let my ISP have access to my
>>mailbox to run a test. I quit PM, logged into the web admin for my
>>mailbox and changed the password, and gave them access. When they were
>>done, I logged into the web admin for the account, changed the password
>>back, and then launched PM.
>>
>>Nothing in PM changed - it wasn't even running, yet I'm now getting this
>>authentication error. The only thing I changed was my password, and I
>>changed it back - if I hadn't changed it back successfully, I wouldn't
>>be able to fetch mail on that account, and I can.
>
>The POP (or IMAP) password is not necessarily the same as the one used
>for SMTP when authentification is required by the server. Maybe you, or
>your ISP, changed the authentication method or password? If your ISP had
>to run a test, I assume there was something wrong or something they have
>changed, maybe this is related?
Jerome,
I've been on the phone with my ISP for over an hour today, very politely
but firmly trying to dig deeper into this. It was clearly happening only
with PowerMail (setting up the account in Mail.app worked fine), and
only on accounts that were created or modified recently: I could change
the password on an account and change it right back, and sending would
stop working with PowerMail.
Mail problems are all pretty simple, so they didn't want to dig too
deep, but I finally had an encryption discussion with a senior tech, and
he sent back this:
>...we think we've figured out how to make Communigate play nice with
>Powermail. Our default encryption method appears to have stopped working
>with powermail. We do have some options, so as a test we changed from
>the default (U-crpt) to another (A-crpt) that seems to work on our tests.
It does seem to have fixed the problem. My guess is that a version of
CommuniGate at some point started using U-crpt as a default for new
passwords, and only because I hadn't touched mine did they still work
(because, goes my theory, they still used the old default). Once a
password was touched, it re-encrypted with the new default, and
PowerMail couldn't authenticate anymore.
This is a very good knowledgebase article to have in the discussion
archives, as it's very obscure, and difficult to diagnose, but rather
concrete when you get down to it. And possibly a good new feature for
PowerMail 5.5.4, to be able to handle U-crpt, whatever it is.
Any further advice - like what encryption PowerMail likes best on the
server side - would be greatly appreciated.
Thanks,
Steve
(who can finally send from his account again - yay!!)
Steve Abrahamson
Ascending Technologies
FileMaker 7 & 8 Certified Developer
http://www.asctech.com
[EMAIL PROTECTED]
