We help IT Professionals succeed at work.

Check out our new AWS podcast with Certified Expert, Phil Phillips! Listen to "How to Execute a Seamless AWS Migration" on EE or on your favorite podcast platform. Listen Now

x

Virtual Mail Server

Medium Priority
254 Views
Last Modified: 2013-12-23
Hi folks. Looking to set up a UNIX virtualized mail server. One IP
multihosting domains with POP3 and SMTP access. Would have to use an
alternative authentication database other than the normal UNIX entries
(NIS, /etc/passwd, etc.). Basically, looking for as much information as
possible; code patches would be nice to review-- what ingredients you
mixed (ie, eric's sendmail, cucipop, and procmail, or whatever) would
still be appreciated a lot. Basically, if you've done this or know who
has, this would help me a lot from re-inventing the wheel here.

Thanks!
--Nathan.

--
____________________________________________________________________
Nathan Clemons
Assistant Network Engineer, New England Division
WinStar iCi
The New Phone Company

____________________________________________________________________
nathan@ici.net  www.ici.net  (v)508-594-1100  (f) 508-261-0430
Comment
Watch Question

Commented:
For starters, see <http://www.sendmail.org/virtual-hosting.html>.


You might also be able to hire a consultant from Sendmail, Inc. to help you with this.  See <http://www.sendmail.com/> or send e-mail to "info@sendmail.com".

Alternatively, post another note here (which I'll be notified of) that you want me to contact you directly by email, and I'll do so.

Author

Commented:
Nope. This isn't enough. The user must not have to be in the /etc/passwd or the NIS maps on the server. You should also be able to have usera@domain1.com and usera@domain2.com without having to remap usernames to avoid the problems of the same name. And consulting isn't an option, either, that's what they pay me for. =) Just trying to find more information or see if someone has already implemented this. I need independant authentication of usernames, some password file per domain storing information with a separate spool directory per domain avoiding username overlaps. This also allows us to quota the domains as a whole and not individual users. Make sense?

Commented:
See my email message.

Author

Commented:
Nope. This isn't enough. The user must not have to be in the /etc/passwd or the NIS maps on the server. You should also be able to have usera@domain1.com and usera@domain2.com without having to remap usernames to avoid the problems of the same name. And consulting isn't an option, either, that's what they pay me for. =) Just trying to find more information or see if someone has already implemented this. I need independant authentication of usernames, some password file per domain storing information with a separate spool directory per domain avoiding username overlaps. This also allows us to quota the domains as a whole and not individual users. Make sense?
Commented:
Unlock this solution with a free trial preview.
(No credit card required)
Get Preview

Author

Commented:
For some reason this system duplicated my rejection on the "For Starters" (*blinks at Expert's CGI system*). Thanks for the email, I dropped a reply. I think that when I hit reload to check if someone had updated this page, it probably reposted what I'd done last time. They might want to look into that... =)

Commented:
Ahh, okay.  I was really beginning to wonder about that.


Anyway, sorry if I came off rude.  It's been one of those days, and you were unfortunate enough to catch that.
Unlock the solution to this question.
Thanks for using Experts Exchange.

Please provide your email to receive a free trial preview!

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.