Henning Brauer <[EMAIL PROTECTED]> writes:
> pleeeeeeeease fix your quoting.
Heh. Sorry. I will try (probably unsuccessfully).
> 1) joe user registers example.com.
> 2) the MX for example.com is automatically set to your host.
> 3) if mail for example.com arrives (and joe user didn't sign up with you),
> you bounce the message.
>
> What is the point of beeing MX then in the first place?!
Well, there is no real "point" if by "point" you mean legitimate, goal-oriented reason :). The problem that our partners are trying to solve is that *they* (the partners) want to be the point-of-service for sign-up for new domain registration, while they want *us* to be the point-of-service for email access (we host the space, the webmail client, pop-access, etc.). Therefore, they want the end-user who wants a domain to go to *them*, and *they* want to add the CNAME and MX records that point to us, but then they want the user to go to us to set up mailboxes.
> This has a lot of disadvantages. To the outside you claim there is mail
> service for this domain, but there really isn't.
> You burn ressources on your systems (accept mail, try delivery, bounce back)
> for no reason.
> You burn ressources on the remote systems (send mail instead of bouncing
> immediately due to lack of MX, receive bounce, deliver bounce) for no reason.
>
> I still call this insane.
>
> clean solution: become MX once they sign up with you.
> less clean but still better solution: be MX immediately but do NOT add the
> domain to locals and rcpthosts. still burns some ressources on both sides
> for the delivery attempt.
Ok. The best thing (given limiting parameters) I can think to do is this:
1) email arrives at qmail proposing to be delivered to [EMAIL PROTECTED]
2) somehow, we determine whether two conditions are met:
a) joe.com MX points to us
b) joe has a mailbox there
3) if not a && b, then we say no rcpthost (we don't deliver for joe.com)
4) otherwise, we allow, and say 'is local'
5) we deliver mail to the known-good joe box at joe.com
I *think* this is the 'less clean but better solution.' Am I right? If so, *how do I implement this*? Must I just put on my gardening gloves, and go to town on the qmail sources? I know it will burn resources, but, presumably the business goal supports the expenditure *shrug*. Thanks again for your help,
-Eddie
[EMAIL PROTECTED]
