It does appear to be the (exim?) filtering that is adding the foobar
account name. Receiving an email always adds Received and
X-Identified-User fields plus account name. While sending and replying
always delivers X-Identified-User plus account name.
Thanks for all the help. Will redirect focus on Exim.
On 2012-09-02 8:01 PM, RW wrote:
On Sun, 02 Sep 2012 18:48:15 -0400
drew....@gmail.com wrote:
Gentlemen,
Thanks for replying so quickly. I'm quite the newbee in this area and
am grateful for your advise. While the new header entries were first
noticed after enabling SA, it was not obvious that Exim could be
another suspect. I will investigate whether it can configured to
interpose or change the default identified user. I will also check
with our hoster whether the account name identifier can be replaced
by something else.
If that doesn't lead anywhere, would there be an SA option for
specifying an alternate identifier or agent name that is piped to the
glue and Exim layers?
Why do you care? Your concern was:
This is a huge security issue that can expose the account name when
users reply to incoming emails.
but email replies don't quote those header.
