[ 
https://issues.apache.org/jira/browse/JAMES-4242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18145486#comment-18145486
 ] 

Felix Auringer commented on JAMES-4242:
---------------------------------------

What about only changing the display name and reply-to header for these 
services? Example headers:

{{From: Felix <[email protected]>}}
{{Reply-To: <[email protected]>}}

I know that our GitLab instance does this for comments. The username of the 
person commenting is shown as display name but I can still see that the email 
was actually sent by GitLab. As far as I know, James does not deny emails based 
on the reply-to header, so that should also work.

> Add authorized From addresses without alias
> -------------------------------------------
>
>                 Key: JAMES-4242
>                 URL: https://issues.apache.org/jira/browse/JAMES-4242
>             Project: James Server
>          Issue Type: New Feature
>          Components: RRT
>            Reporter: Brian Banerjee
>            Priority: Major
>
> Currently, the only way to authorize a user to send mail with a different 
> From header is to add an alias or domain alias in the RRT. This has the 
> implication that mail sent to the alias address will be received by the user.
> I am looking for a way to authorize a user to send mail with a particular 
> From header (using the same semantics as an alias) butĀ *not* receive/access 
> mail sent to that address.
> WebAdmin routes for this feature can be similar to the WebAdmin routes for 
> aliases.
> DisablingĀ {{verifyIdentity}} in smtpserver.xml is not acceptable for security 
> reasons.
> h2. Usecase:
> An application or service needs to send transactional mail on behalf of an 
> existing user, but replies, bounces, and incoming mail will only be monitored 
> by the user directly. I want to have a service account that can use the 
> user's From header but cannot access any mail received by the user.
> The service account must use a different username and password from the user 
> for security (principle of least privilege, accurate audit logs) and to 
> prevent errors when the user changes their password.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to