Associate Email Address with Shell User?


#1

Why can you no longer associate an email address with a user with shell privileges?

All i can find is support for HOW to associate them, with a note saying that it no longer works.

Is there a workaround for this? I’m trying to pipe email to a PHP script.


#2

http://wiki.dreamhost.com/V10.03_March_2008
#####################################
2. Mail is Mail, FTP/Shell is FTP/Shell!

Really.

And, I’m sorry for this new “feature”, but it’s our first step in a
whole new paradigm of hosting at DreamHost brought on by this Blingy
debacle.

We’re no longer allowing (new) FTP/SHELL users to have an email address
associated with them.

The reason for this, I’m sorry to say, is that we are planning on a LESS
centralized hosting infrastructure for the future. One with fewer "eggs"
in each “basket”. And, part of this is being able to separate the
storage we use for email (which is 10% of the total size but 90% of the
access) from the storage we use for user’s home directories (which is
90% of the total size but only guess what percent of the total access?).

Fortunately, this change should be more or less invisible to everybody!
The only thing lost is the ability to see and manipulate your mail files
via FTP/Shell… (and even that is only for new users from now on).
Whoop-dee-do, I say!

And for those of you who DID want to do that for some reason, I have
something for you that might appease your new-found rage:

I’m sorry.

#########################################

So much to atone for,
Josh Jones


#3

The blog has this:

-Scott


#4

Hmm, I wonder how that forward to username@machine.dreamhost.com works if the machine isn’t running smtp service? Not to mention questions about access and processing that follow if in fact this is the case.

Good luck, OP. Let us know how your quest turns out.


jt


#5

Those machines should be running SMTP (/usr/sbin/sendmail) (mine is) as shown by doing “telnet localhost 25”.

-Scott


#6

Ah, so that blog entry misspeaks slightly? All web machines should continue running SMTP while some(all new setups) will no longer have IMAP/POP?

It would be good to have clarity on this point for all that view this thread…


jt


#7

Considering that they are “grandfathering” existing shell users’ email accounts, I’m thinking you are right! :wink:

–rlparker
–DreamHost Tech Support


#8

SMTP is what delivers mail from machine to machine. POP/IMAP is how you retrieve your mail from the server.

What’s changed is that new FTP users no longer have email addresses, which caused their mail to reside on the webserver. FTP users still technically have mail, but not at their domain; just on the webserver which does not offer POP/IMAP access.

-Scott


#9

Uhm, perhaps I haven’t been clear about the correction/clarification I was seeking…

Rest assured, I understand the difference between IMAP/POP and SMTP and a bit of it’s interaction with MDAs like procmail. But in the blog entry you cite, there is the statement, “The only difference really is that we don’t run pop/imap/smtp on those web servers…” which may not be correct.

Subtract smtp from that list, correct?


jt


#10

Ah, got it. Yeah, turning off SMTP doesn’t make sense, so that probably wasn’t accurate. At a minimum, contradictory.

-Scott