Jens Hatlak wrote:
Bill Davidsen wrote:
Thanks for the info, now the next question is why it works for anyone
with the official 2.0 release.
Bug 484656 comment 18 suggests that only people with a
mail.server.serverX.realhostname pref are affected. I for one have no
account with such a pref and I don't know which action would create it.
The first part is easy, you get that when you have an account and the mail
server you have been using is shut down and the service moves to another
machine. So you have an account named My.Org and the server name is mail.my.org
and it works. Then that server is shut down and you now get mail from
inbound4.my.org instead. Your email address is still [email protected], but the
actual server name changes. I find I had two accounts like that since you told
me what to look for. I think I just changed the name of the server, it has
changed three time since the account was new, I have traces of 'gatekeeper',
'pvt-gate' (private network NIC of mailgate1), and realname now points to
mailgate2. Odd, but nothing that doesn't happen in an organization.
That's how it happens. How it would happen on a new account on a non-migrated
SM-2.0 I can not clarify.
Is there any doc on all those config fields, particularly those which only
appear when you know they exist? Would make submitting a useful bug report
easier, and source is not really a great resource, even if you know how to read
it, it takes time.
--
Bill Davidsen <[email protected]>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
