SysKoll wrote:I am still quite confused about what that feature would do. Could you give a few examples, specifying everything what the source, destination and message transformation would be?
Ok...
Domain mappingLets say that my spamgourmet account is mika84. And I have domain mika84.com. All I wanna do is point my XM to spamgourmet and tell that mika84 is my domain.
Instead of using address
word.mika84@spamgourmet.com i would use
word@mika84.com directly.
Hmm...
Optionally domain mapping without usermapping could also be possible. So mydomain.com would 100% match spamgourmet.com as it currently works.
Forwarding mode I don't know if
gourmet@spamgourmet.com works that way, but I don't see any reason why it couldn't.
But lets once again say that I have my domain mika84.com and I'm unable to control MX records. But I can configure generic mailforwarding so
ANYTHING@mika84.com will be forwarded to
gourmet@spamgourmet.com could spamgourmet check messages To header and process message according it.
Using selectable option of these two:
A) only domain mask. word.userid@mydomain -> word.user@mydomain
B) Instead use domain to tell also the userid as suggested above with MX support.
So was that so hard to understand? And naturally easy to use user interface for these features. I guess I don't need to draw sample pics for this?
I know, my first thougs were really messy. But I had the image in my mind. It's like FBI's remote viewing...
I see some round shapes and purple color... Yeah, it's login window...
Yeah, writing good specs is hard, isn't it? That's what half a successful software project is about...
I unfortunately know that. I'm software project manager...
It seems that you just code... It's first very hard to get information from customer what they REALLY want before figuring real solution for that and then writing specs for coders...