Re: [cobalt-users] POP3 e-mail limitation on RAQ3

["Jens Kristian Søgaard" <jens@xxxxxxxxxxxxxxxxxxxx>]

> I feel you have a serious misunderstanding of how e-mail works in

I think, that YOU have misunderstood, what he's asking.

> general, and on the RaQ specifically. There is no such thing as e-mail
> addresses per IP, and also, this 'problem' is not specific to a

Yes, there is. What he wans is:

user john on 1.1.1.1  is separate from user john on 2.2.2.2.

> particular brand of Unix. The limitation is in fact that the user
> account used to spool (and fetch) mail for a particular address (set
of
> addresses) has to be unique for the whole system, ie. having two

No it hasn't. Using the Cobalt utilities, yes it has that limitation.
But it is not inherent in the POP/SMTP standards that it have to be this
way.

> addresses like "info@xxxxxxxxxxx" and "info@xxxxxxxxxxx" is very well
> possible, yet the POP3 username for these two accounts cannot be the
> same. This is not a problem, it is inherent to this technology. Other

It's not inherent to the technology. It can be done, and he even
mentions that other firms has done this before.

The trick is, that you need a POP daemon that is aware of ip's. I.e. it
binds to the ports on the different interfaces / ip's, and then for
every connection that comes in, it checks what interface it came in on.
Using that information, you can set up different user databases for each
ip.

That means you have a user named joe on mail.domain1.com and a user
named joe on mail.domain2.com - and have both domains on the same
server. IF and only IF you have a seperate ip for those two.

I know that you can have joe@xxxxxxxxxxx and joe@xxxxxxxxxxx easily, but
you cannot have two pop accounts that has the same name on the standard
Cobalt RaQ. It's this limitation he wish to work-around.

It is possible - but it defeats the purpose of buying a RaQ. If he needs
this special setup, I would advise buying a regular Linux or *BSD
server.


--
Jens Kristian Søgaard, Mermaid Consulting I/S,
jens@xxxxxxxxxxxxxxxxxxxx
http://www.mermaidconsulting.com/