D> I’d be happy to clarify things for you. What this was trying to say that
D> you can set up all those filters using our interface, which is the web
D> panel itself. For example, you could set your email addresses to forward
D> mail to a shell user where they can be processed by the script that’s in
D> the shell user’s home directory.
D> So go to https://panel.dreamhost.com/index.cgi?tree=mail.filters&, edit
D> the email address you have listed there, then click the Add Filter
D> button, and you’ll see all the options listed for filtering. Among them,
D> there is the “Forward it to a shell account:”. That’s what that note
D> refers to, that you can do all this through our web panel. Sorry about
D> the confusion.
I assume not touching “When an email’s … contains …” will match
all mail no matter what headers they have or lack.
Is this open source so I can be sure? Maybe it is in one of the
$ dpkg -l ndn* packages.
D> you need to use that option to send the message to your shell user
D> for the processing you set up there. Also, you can either use Pine
D> to check mail directly under your shell user, or you can use the
D> X-Loop to send it back to your original address.
D> It appears that another customer posted a reply too, you can check his
D> explanation at
That is wildly more complicated than older user me can handle, And
indeed, as I do not use bayes, I need not take that route. So all it
seems I would need is add the X-Loop as above.
However I could then not also read the messages on the shell account
(with mutt). I could only to use IMAP or webmail. I could no longer
use all three depending on what is best from what computer I’m
connecting from that day (home:IMAP; public library:webmail as no
putty allowed; friends house:putty ssh then mutt).
Ah, I will in my (hosting account’s .procmailrc) forward back
with X-Loop, and also save a local copy, so I can read the messages by
all three methods (IMAP, webmail, mutt).
And I will rig up a script to do
$ ssh hosting_server expire_messages
after I am happy I read them all via IMAP or webmail so I don’t need a
Anyway, perhaps the .procmailrc making script on the new
closed mail server is open source, so I can see what will happen with
no Subject, and if X-loop will really work.
Also we see “This feature will not work if you have a .procmailrc file
already.” on the panel. But perhaps that refers to on one machine that
now becomes two, etc. etc.
Anyway, please don’t start counting the 72 hours until I can
understand and get this all in place. I estimate it will need a few
weeks, especially as I cannot see the code of how you intend to handle
X-loop so fear disaster.
Another solution I will examine is
$ ssh hosting_server ‘start up a personal IMAP process which I then connect to to download my mail’
That would eliminate the need to “forward backward”, but still means I
couldn’t use webmail, unless there is a webmail listener alive on the
Of course all this would take a few weeks for me to figure out.
Another option is to please put me deeper into the waiting list of
users to be affected, and hope other users complaints will cause
Dreamhost to back off on requiring this tangled mess and then when the
time rolls around for me to be affected, I needn’t do anything.
This reply posted to discussion board and emailed to support.