On Tue, 22 Jun 2010 09:51:08 -0400
W B Hacker wrote:
> May one ask where an address of that form is originating - how it is getting
> into Exim's environment, and whether it really is at 'smtp time' (a submission
> session with a correspondent).
>
> as in:
>
> - MUA with 'experimental' settings
>
> - On-box (binary invocation, queue injection, smtp session) MLM,
>
> - script or web-app
>
> - *prior* address-rewrite
>
> or, perchance, is the '*' in your example actually a wildcard that does not
> itself exist, but rahtehr represents a variety of other possible strings?
>
> I ask because, *as shown* the right side is not a legal/recognizable domain.tld
> format, with a literal '*' in it, never mind .admin' not being any tld or
> country I'm aware of...
>
> More to the point, if you can share what the end goal is, the 'why you need it'
> situation, perhaps someone here may have another way that is already proven.
>
I have setup Exim with Dovecot as imap server. Dovecot has such feature as "master users" - such users can login as "other-user" account, so if you want login as user 'test@???' you enter 'test@???(separator)master_user'. Separator is configurable.
When you logged in as master user, MUA (in my setup webmail) set headers from, sender, etc in format user@domain*master_user. This prevent exim from sending mail originating by master_users.
More often became situation - when I got ticket in helpdesk - "Please send mail as sender X, because he is in vacation to client Y", "Or forward e-mail from mailbox X to Y, owner of X is not available now" etc.
I want exim to solve this issues, and master_user can handle such requests.
With S flag added to rewrite I'm able to send e-mail, but headers still contain identity of master_user - this should be fixed.
