Can't talk with gmail after software migration

So I spent some time playing with different jabber server software packages, trying to decide which one to use. I finally decided to go with ejabberd, so I shut down my old wildfire installation and got ejabberd running. I was the only user, so I didn't bother trying to migrate settings from the old software to the new one. After installing ejabberd, I re-created my account and added all my old contacts.

Now I can't communicate with gmail. My contacts at two other jabber servers can chat with me just fine, but my server is (evidently) unable to authenticate itself to the gmail server. I'm getting a bunch of these in my logs:

=INFO REPORT==== 2007-05-01 13:04:06 ===
I(<0.307.0>:ejabberd_s2s_out:106): started: {"cjones.org",
"gmail.com",
{new,"(int)"}}

...as well as a few of these:

=INFO REPORT==== 2007-05-01 13:34:51 ===
I(<0.378.0>:ejabberd_s2s_in:317): GET KEY: {"cjones.org",
"gmail.com",
[],
"(base64)"}

=INFO REPORT==== 2007-05-01 13:34:51 ===
I(<0.380.0>:ejabberd_s2s_out:106): started: {"cjones.org",
"gmail.com",
{verify,
<0.378.0>,
"(base64)",
"(int)"}}

...I've edited out the actual data being exchanged, as I don't know if it's sensitive or not. Have I completely clobbered the association between these two servers? If so, why am I able to communicate with other servers with previous associations?

Have you read this FAQ

Have you read this FAQ entry?

Ha! I saw that many times

Ha! I saw that many times and always assumed it didn't apply to me. I have my SRV records correct already.

I had to actually read the thing to realize it was a workaround for buggy interpretation of other people's SRV records.

Thanks for pointing out the obvious to me.

Syndicate content