[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [cobalt-users] RaQ3 Authentication Failures after Customer In stalls Firewall
- Subject: RE: [cobalt-users] RaQ3 Authentication Failures after Customer In stalls Firewall
- From: Chris Jones <chris@xxxxxxxxxxxxxx>
- Date: Mon Apr 2 09:07:44 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
>>Scenario: Customer installs private network, complete with
>>firewall and
>>masquerading. Immediately the customer can no longer connect
>>to retrieve email
>>from their domain housed on our systems. Customer complains:
>>
>>>Your mail server seems to require some kind of different
>>>configuration than standard for e-mail clients,
>>
>>Of course it must be "our" problem since they can no longer
>>connect after
>>setting up a new network and firewall. <geezzz>
>>
>>Any suggestions or input on how to resolve this issue? Are
>>the authentication
>>failures resulting from sendmail (on the RaQ3) trying to
>>perform reverse
>>lookups or is it rejecting the connection because they're
>>masquerading their
>>network?
First thoughts would be what error message are they getting?
If they are unable to connect at all to the RaQ then the problem will be a
routing issue with the firewall/masq.
Ask them to make sure the corrects ports are open to send/receive mail.
There should be no setting on your machine (assuming you have no strange
homebrew running) that would prevent someone from at least a simple POP3
check. Might be an issue to send but that is a whole other can of worms.
In other words, if others are able to do it on other domains on the same
machine, they should be able to also. It is obviously a setup/config issue
on their end.
Be Nice, but Be Firm 8-)
Chris