[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Pop before SMTP - I've had enough.
- Subject: Re: [cobalt-users] Pop before SMTP - I've had enough.
- From: Larry Smith <lesmith@xxxxxxxxx>
- Date: Sat Mar 30 09:28:14 2002
- Organization: ECSIS.NET
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
INRE Re: [cobalt-users] Pop before SMTP - I've had enough.:
> This *is* a pop-before-smtp issue!!!
This is *NOT* necessarily a pop-before-smtp issue.....
It depends upon whether or not the address is question actually "resides" on
that box - - - AND whether or not the box recognizes that fact.
If I have a box that serves "domain.com"
and I have an account "myname" on box domain.com
that should result in "myname@xxxxxxxxxx" being "valid" for that box.
true so far ????
So if joe@xxxxxxxxxxxxx sends a message to myname@xxxxxxxxxx
the box should "accept" that mail - iregardless of the pop-b4-smtp settings
since it is "addressed" to a local account on that box. (baring access
denials, etc which are another issue totally).
If it does *not* accept it - then the "box" is obviously not recognizing that
either "myname" or "domain.com" are "local" to the box itself.
We have already been over the "no such user" part, so the answer is that for
some reason the "box" does not "believe" that "domain.com" is "local" and
hence falls through into the relay checks vice dropping out at the
"check_local" part of the sendmail.cf.
I agree that something is wrong - but it is *not* necessarily pop-b4-smtp.
It appears to be something else has gotten "out-of-wack" with the sendmail.cf
or one or more of the configuration files.
The answer will *not* come from us tossing emails back and forth - it will
only come from someone connecting to a box that is not working "correctly"
and running sendmail in "test" (/usr/sbin/sendmail -bt) mode and working
through the various responses (test mail to "myname@xxxxxxxxxx" and see what
processing the sendmail.cf does on it) to determine "exactly" where the error
resides. Then it can be reported back to this list and hopefully many can
"learn" from the experience.
Larry Smith
SysAd ECSIS.NET
sysad@xxxxxxxxx