wojtek opened 6 months ago
|
|||||
Hmm... another, somewhat related issue - it seems that only mails addressed to |
|||||
Check service desk setting of a project, you can customized the address send to a particular project. |
|||||
But in there you have only Thus at best the email for the whole deployment is always the same (e.g. |
|||||
This adds extra complexity of the setup. Why not just tell your customer to only send service email to a single address (or project specific email address)? |
|||||
Because we exist for a long time, have a number of customers and over the course of history we used 2-3 emails and we have to (should) support a couple of them. I'm not sure that at the basic removing requirement for |
|||||
System email address is still required, as otherwise OneDev does not know which address to be used as sender address. |
|||||
Agreed, but could it be renamed/repurposed as "Sender email" only? |
|||||
System email address is particularly phrased as such as it services not only sender address, but also target address for all incoming emails. Also as I mentioned, OneDev has mechanisms to create issues in different projects, either via plus addressing, or by checking sender address if target address does not include project info. Adding another mechanism to create issues in different projects based on target email address itselt just complicates things and causes confusions. I'd suggest to forward the emails at your mail server side to project specific addresses as necessary for this historical reason. |
|||||
From what I understand 1dev relies heavily on subaddressing (custom projects, replies to issues, etc). Wouldn't it be possible to just ignore what localpart is and just use subaddress part?
Again: I given up on setting up issues in different project at this point in our conversation. What I'm asking is just for parsing/handling all incoming emails from mailbox (instead of filtering by configured email). If the mail matches the configured address/subaddressing then fine, do the additional filtering but don't drop incoming emails processing if it doesn't match configure email - just process it with default configuration and put it in default project. Right now we don't do forwarding - we simply have a couple of aliased localparts to one mailbox so setting up forwarding to subaddress address would be somewhat convoluted and inefficient (maintaining multiple mailboxes) |
|||||
The mailbox you already have is for In your existing mailbox you setup a forwarding rule without subaddresses and configure in OneDev what should happen for mails from |
|||||
Robin Shen changed title 6 months ago
|
|||||
OneDev changed state to 'Closed' 6 months ago
|
|||||
State changed as code fixing the issue is committed (9c94f36f) |
|||||
Referenced from commit 6 months ago
|
|||||
OneDev changed state to 'Released' 6 months ago
|
|||||
State changed as build #4264 is successful |
|||||
@wojtek this can now be achieved by turning off option |
|||||
This sounds perfect! Thank you. |
Type |
New Feature
|
Priority |
Normal
|
Assignee | |
Labels |
No labels
|
Currently, 1dev allows assigning project based on sender address. It would be nice to have more conditions, at least using
to
(in addition to Sender'sfrom
) would be desiread.In our setup we have single mailbox that handles messages sent do various addresses (same limitation is in 1dev as it can check only single email account). Previously we simply used sieve to filter those messages to different folders (and YouTrack simply polled different mailboxes and created issues accordingly but it wasn't very efficient).