Hi Sam,
esmtproutes:
====- 8< -===================================================
: smtp.broadband.rogers.com
====- 8< -===================================================
esmtpauthclient:
====- 8< -===================================================
smtp.broadband.rogers.com user...@rogers.com password
====- 8< -===================================================
(user...@rogers.com is the login name to be used. it does work with Postfix)
I've also tried adding the following to the esmtpauthclient:
smtp2.rog.mail.vip.re2.yahoo.com user...@rogers.com password
smtp106.rog.mail.re2.yahoo.com user...@rogers.com password
but it didn't make any difference
What else could I check here?
smtp-rog.mail.yahoo2.akadns.net user...@rogers.com password
Your ISP uses very stupid DNS records.
Wow! You're genius! It works! Thanks so much!
Would it be too bold of me to ask for more detailed explanation of what was
going on?
Is this because DNS record is different from reverse DNS or some sort of the
kind?
I'd really like to understand better how this whole thing works.
I was under impression that Courier would search esmtpauthclient for the same
hostname as it took
from esmtproutes. Is it trying to resolve it first?
And yes, this provider is famous for doing a lot of stupid things :(
10 messages in net.sourceforge.lists.courier-usersRe: [courier-users] smart host/relay ...
