Anders Bandholm wrote:
I have the same problem because our production mail server (for security
reasons) does not have a web-server.
I solved the problem by adding a receiver to the list, which is under my
control on the other server. The user in question runs filter (from Elm) out
of his ".forward" file to archive the messages in the right archives. Rules
like the following will do the trick:
Well, actually, the mail filter is not a problem. All the mail goes to
one server, as it should, and all gets archived together. But, I just
don't have the space on the sever that gets and processes the mail, so
I want to keep the HTML files on another server, then delete them from
the first server. But, I want to make sure I can still do updates
properly. So, I thought maybe I could just FTP the database file over to
the first server, create the HTML files, and then FTP them over to the
second server. Is this workable, does anyone know? Any details on how
to do this? Thanks in advance.