Re: [cobalt-users] Pop before SMTP - I've had enough.

[flash22@xxxxxxx]

On Friday 29 March 2002 07:14 pm, Benedict wrote:
> Quoting Paul Jacobs <paul@xxxxxxxxxxxxxxxxxx>:
> > Are you using "APOP" or just passwords when you check your pop3 email?
>
> Another one that does not get it. Again:
> Guy from somewhere sends an email to address on cobalt-machine's
> mailserver, mailserver sends back the forementioned error about relaying
> and checking their mail. There is NO, I repeat, NO relaying involved here.

Yes, there is, you don't seem to understand the boundries of MTA ,
transport occurs from the interface of the machine to the internal
MailDeliveryAgent, it *is* relaying. It's connecting 2 transport
points. The fact they are both physically in the same box means nothing.

> The sender of the email uses his ISP's SMTP to send it to
> the Cobalt's domain's emailaddress, not using any relaying
> capability of the cobalt on the other end.

Unless the user is *inside* the box handing it to the MDA , it *is*
Relaying. Hint, access controls apply only to relaying here

> This is what makes the error so strange;

Not strange at all, except from the point of view of what you think is
happening verses what you want to see. 

When you tell the server 'Don't accept email for this domain' it
implicitly assumes someone else must, so the delivery isn't local by
definition, the only catch being that the mail server hasn't the slightest
clue what it's supposed to do about it in this case, it only knows it's
not allowed to attempt to deliver it to any other point.

> This error-warning should NOT be going to the sender of the email,
> not even when his mail apparently bounced back.

What error do you think the user should get? The reason it's 'relaying
denied' instead of 'user unknown' is because the mail server hasn't gotten
that far, it sees the domain, and rejects it based on authorization for
relaying. The access rules are explicitly
telling it 'you may not transport email for this domain name, eg, you are
not authorized to relay for this domain name/interface' to anywhere.

It's *exactly* the correct error.

Incidently, pop-before-smtp is a *relaying authenication* program, it
enables relaying , that's how it *works* ;P

gsh