I've been asked to implement the following, which I know violates just
about every conceivable RFC involved in the addressing and traceability of
email but here goes...
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. 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. 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.. 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.
Has anyone else done this or does anyone have any ideas on where to start
or why *not* to do this?
TIA,
Bruce
Bruce Bowler, Research Associate 207.633.9600 (voice)
Bigelow Laboratory for Ocean Sciences 207.633.9641 (fax)
PO Box 475 BBowler@??? (email)
West Boothbay Harbor ME 04575 http://www.bigelow.org/
--
*** Exim information can be found at
http://www.exim.org/ ***
