In response to Bruce Bowler:
> Management would like me to set up an email address, lets call it
> suggestions@???. Employees could then send messages to
> suggestions@??? and they'd be forwarded on to
> bigcheese@???. The catch is that there must be "no way" for
> bigcheese to know who sent the message.
Use a pipe transport to pipe the message into a script which removes
the relevant headers, ie everything except the Subject I think, and
then re-sends the message to bigcheese. You certainly need to get rid
of Received: , Reply-To: , Sender: , From: , and Message-Id: as that
will contain the name of the originating machine, so you might just as
well remove everything. The From: field that the script generates
should be suggestions-request or something similar.
> In the "ideal world", the
> postmaster wouldn't be able to tell either, but as long as the postmaster
> can convince bigcheese that it's non-traceable, that's OK.
You could maybe make the script wait a random amount of time before
re-sending the message so that there isn't an obvious correlation in
the logs between the message being received from
whinger@??? and being sent on.
> One additional
> thing that I'd like to see is that unless the message comes from within
> bigelow.org, it gets blackholed to prevent spam etc from getting into the
> suggestion box.
Use a director with something like
senders = "*@*.bigelow.org:*@bigelow.org"
> One enhancement that might be asked for, so any design
> shouldn't preclude it is that the "subject", if it's an RFC compliant
> address, could be used as the "target" address rather than bigcheese.
You could do that in a script -- no problem there, surely?
> Has anyone else done this or does anyone have any ideas on where to start
It sounds fairly strightforward to me unless I've missed something in
the original message.
Gyan.
--
*** Exim information can be found at
http://www.exim.org/ ***
