Do you have an MX record set up in DNS for your local domain? I have seen this type of error on isolated mail systems before, where a product would try to grab the MX record, fail, and then connect to whatever was entered in the app configuration for the SMTP server. E.g. if you have "mail.somedomain.ext" entered as the SMTP server, it will first query DNS to get the MX record for that domain (to see if it gets back "mail25.mail.somedomain.ext" or something along those lines), then when it fails, connect directly to the system (in this case, "mail.somedomain.ext") on port 25.
I have not seen it with a BES yet, because our BES has access to our internal DNS, so I don't know for sure if that's what's happening.
|