prefix BUG?

[Guest]

--- I'll use the "John Doe" as an example ---

As I wanted an 0 forwarding but nice emailadress for usenet I created an account with my lastname, and created

j.doe@dfgh.net

The next step was to create an prefix j, so I could make nice looking and relative secure disposable addresses like j.something.doe@dfgh.net.

But what happens:

no matter what I put between j and doe they all count for the address j.doe@dfg.net!!! Strange isn't that? A possible bug?

Because now I'll need to reset j.doe@dfgh.net constantly as I've already gave out 23 j.something.doe@dfgh.net addresses. Help!

[josh]

I'm not following all the way through -- the normal format for a prefixed address has three dots before the at sign (four elements):

prefix.word.number.user@spamgourmet.com

three elements are treated as not having a prefix:

word.number.user@spamgourmet.com

and two elements are treated as not having a prefix, and having the number 3 implicit:

word.user@spamgourmet.com

so, when you used the address j.doe@dfgh.net, that would be the same as:

j.3.doe@dfgh.net

'j' would be the word, and 3 would be the number -- but if you had a prefix enabled on your account (that is, existing), the address wouldn't have been created, since there's no prefix in it.

after that, a three element address like

j.something.doe@dfgh.net

would still be interpreted as word.number.user, so the word would be 'j' (same as the other one), and the count *would* be 19 ('s', the first letter in 'something' is the 19th letter of the alphabet), but would be ignored because the number had already been set to 3 for the word 'j' by the first address above.

[Guest]

three elements are treated as not having a prefix

Ahh, that explains a lot ....

So that means I'll _have_ to use: j.something.NUMBER.doe@dfgh.net if I want to use a prefix.

( As you can see I found the domains without spam in it )