Am 20. Nov, 2000 schwäzte Dave C. so:
> You could also tell pine to inject the messages via SMTP instead of
> locally (as would likely be the case if you were setting up for an ISP
> supporting users who might have multiple addresses)..
Tried that and that didn't fix it either. In setting this up in the near
future it would be in an office situation where there would be a mix of
using the MTA as a smarthost for client machines and people sshing to the
mail server to use pine/mutt locally. The first way is probably the more
intelligent way to handle mail :).
OK, found a workaround. This is in pine, not exim. Before I get the addy
up and going (and even for a few that I don't use very often) I just
change the From: header from within pine and don't setup a role. I turned
on debugging for exim and noticed that mail was coming from
"der.hans@..." not from "newrole@...". The From: header was still being
set correctly, but pine seems to be using the roles pre-configured
From: header when sending the mail.
After establishing a role for the new addy and using it everything worked
fine.
Note all of my messages to the exim-users list prior to this were done by
manually editing the From: header at the time of writing the mail, so this
usually works :).
Dave, thanks for your suggestions.
cioa,
der.hans
--
# der.hans@??? home.pages.de/~lufthans/
www.Opnix.com
# kill telnet, long live ssh - der.hans
