-
Suggestion
-
Resolution: Fixed
-
16
-
40
-
NOTE: This suggestion is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding suggestion.
Atlassian Update – 21 December 2022
Hi all,
Thank you so much for your votes and comments on this suggestion. I’m happy to announce that we have shipped this feature as part of Jira Service Management Data Center 5.5 release. Jira admins now have more control over how email requests that your customers send are filtered by Jira Service Management.
The first change we've introducing is giving admins the option to turn the auto-generated email and bulk email filters on or off, depending on your preferences. The new settings are available in Administration > Applications > Email requests.
We’ve also added a global allowlist and blocklist for all of your service projects. The lists let you decide which requests should always be processed and help you get rid of spam.
Please see our documentation to learn more about receiving requests by email.
Kind regards,
Charlie Marriott
Jira Service Management, Data Center
As an admin, I would like the ability to configure the Bulk Settings used by Service Desk Mail Handler. This is because when some mails auto-forward or redirect emails, they will generate the auto-submitted: auto-generated header. This header will cause the request to be not created.
The incoming-mail.log will display the following error
2014-10-14 22:54:34,151 DEBUG [Mail server for xxxx@email.com. Created by JIRA Service Desk.] atlassian-scheduler-quartz1.clustered_Worker-1 ServiceRunner Mail handler used by JIRA Service Desk. Do not modify or delete. 10,200 The message has been rejected (Rejecting message due to failed bulk check.):
This is causing problems as we have multiple mail accounts and unable to configure alias due to particular reasons so we have to use redirection/forwarding but both of these will generate the said header.
Update as of 21 May 2015
Hi everyone,
Just to give you a quick update: we've been monitoring this suggestion and understand that this is not the ideal situation. This is not on our short-term roadmap and we'll come back to it later.
Cheers,
The JIRA Service Desk team
- is related to
-
- Closed
-
- Gathering Interest
- relates to
-
- Future Consideration
- mentioned in
-
Page Failed to load
-
Page Failed to load
-
Page Loading...
-
-
(3 mentioned in)
[JSDSERVER-973] As an admin I want the ability to configure the *Bulk Settings* used by the Service Desk mail handler
| Fix Version/s | New: 5.5.0 [ 104101 ] | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: In Progress [ 3 ] | New: Closed [ 6 ] |
| Description |
Original:
{panel:bgColor=#e7f4fa}
*NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-973]. {panel} {panel:title=Atlassian Update – 15 Sept 2022|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff} Hi all, Thank you so much for your votes and comments on this suggestion. We are currently working on a solution for this ticket. We have a few open questions about the design of this feature and would love to hear your feedback. Please send an email to [lwalsh2@atlassian.com|mailto:lwalsh2@atlassian.com] if you would like to join a 45-minute session over video conference on this topic in the next couple of weeks. In the email, please include the following details: * your company’s industry * the size of your company * how your company uses Jira Service Management (JSM) * a summary of how this problem affects your team Although we can't guarantee that we will be able to speak with all interested parties, we definitely appreciate your interest and enthusiasm to help us make JSM DC easier and more enjoyable to use. Thanks, Lisa {panel} As an admin, I would like the ability to configure the *Bulk Settings* used by Service Desk Mail Handler. This is because when some mails auto-forward or redirect emails, they will generate the *auto-submitted: auto-generated* header. This header will cause the request to be not created. The incoming-mail.log will display the following error {noformat}2014-10-14 22:54:34,151 DEBUG [Mail server for xxxx@email.com. Created by JIRA Service Desk.] atlassian-scheduler-quartz1.clustered_Worker-1 ServiceRunner Mail handler used by JIRA Service Desk. Do not modify or delete. 10,200 The message has been rejected (Rejecting message due to failed bulk check.): {noformat} This is causing problems as we have multiple mail accounts and unable to configure alias due to particular reasons so we have to use redirection/forwarding but both of these will generate the said header. {panel:title=Update as of 21 May 2015|bgColor=#f5f5f5} Hi everyone, Just to give you a quick update: we've been monitoring this suggestion and understand that this is not the ideal situation. This is not on our short-term roadmap and we'll come back to it later. Cheers, The JIRA Service Desk team {panel} |
New:
{panel:bgColor=#e7f4fa}
*NOTE:* This suggestion is for {*}JIRA Service Desk Server{*}. Using {*}JIRA Service Desk Cloud{*}? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-973]. {panel} {panel:title=Atlassian Update – 21 December 2022|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff} Hi all, Thank you so much for your votes and comments on this suggestion. I’m happy to announce that we have shipped this feature as part of [Jira Service Management Data Center 5.5 release|https://confluence.atlassian.com/servicemanagement/jira-service-management-5-5-x-release-notes-1189488545.html#JiraServiceManagement5.5.xreleasenotes-email]. Jira admins now have more control over how email requests that your customers send are filtered by Jira Service Management. The first change we've introducing is giving admins the option to turn the *auto-generated email* and *bulk email filters* on or off, depending on your preferences. The new settings are available in Administration > Applications > Email requests. We’ve also added a global allowlist and blocklist for all of your service projects. The lists let you decide which requests should always be processed and help you get rid of spam. [Please see our documentation to learn more about receiving requests by email|https://confluence.atlassian.com/servicemanagementserver/receiving-requests-by-email-939926303.html]. Kind regards, Charlie Marriott Jira Service Management, Data Center {panel} As an admin, I would like the ability to configure the *Bulk Settings* used by Service Desk Mail Handler. This is because when some mails auto-forward or redirect emails, they will generate the *auto-submitted: auto-generated* header. This header will cause the request to be not created. The incoming-mail.log will display the following error {noformat} 2014-10-14 22:54:34,151 DEBUG [Mail server for xxxx@email.com. Created by JIRA Service Desk.] atlassian-scheduler-quartz1.clustered_Worker-1 ServiceRunner Mail handler used by JIRA Service Desk. Do not modify or delete. 10,200 The message has been rejected (Rejecting message due to failed bulk check.): {noformat} This is causing problems as we have multiple mail accounts and unable to configure alias due to particular reasons so we have to use redirection/forwarding but both of these will generate the said header. {panel:title=Update as of 21 May 2015|titleBGColor=#f5f5f5|bgColor=#f5f5f5} Hi everyone, Just to give you a quick update: we've been monitoring this suggestion and understand that this is not the ideal situation. This is not on our short-term roadmap and we'll come back to it later. Cheers, The JIRA Service Desk team {panel} |
| UIS | Original: 23 | New: 16 |
| UIS | Original: 25 | New: 23 |
| UIS | Original: 28 | New: 25 |
| UIS | Original: 19 | New: 28 |
| Description |
Original:
{panel:bgColor=#e7f4fa}
*NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-973]. {panel} {panel:title=Atlassian Update – 15 Sept 2023|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff} Hi all, Thank you so much for your votes and comments on this suggestion. We are currently working on a solution for this ticket. We have a few open questions about the design of this feature and would love to hear your feedback. Please send an email to [lwalsh2@atlassian.com|mailto:lwalsh2@atlassian.com] if you would like to join a 45-minute session over video conference on this topic in the next couple of weeks. In the email, please include the following details: * your company’s industry * the size of your company * how your company uses Jira Service Management (JSM) * a summary of how this problem affects your team Although we can't guarantee that we will be able to speak with all interested parties, we definitely appreciate your interest and enthusiasm to help us make JSM DC easier and more enjoyable to use. Thanks, Lisa {panel} As an admin, I would like the ability to configure the *Bulk Settings* used by Service Desk Mail Handler. This is because when some mails auto-forward or redirect emails, they will generate the *auto-submitted: auto-generated* header. This header will cause the request to be not created. The incoming-mail.log will display the following error {noformat}2014-10-14 22:54:34,151 DEBUG [Mail server for xxxx@email.com. Created by JIRA Service Desk.] atlassian-scheduler-quartz1.clustered_Worker-1 ServiceRunner Mail handler used by JIRA Service Desk. Do not modify or delete. 10,200 The message has been rejected (Rejecting message due to failed bulk check.): {noformat} This is causing problems as we have multiple mail accounts and unable to configure alias due to particular reasons so we have to use redirection/forwarding but both of these will generate the said header. {panel:title=Update as of 21 May 2015|bgColor=#f5f5f5} Hi everyone, Just to give you a quick update: we've been monitoring this suggestion and understand that this is not the ideal situation. This is not on our short-term roadmap and we'll come back to it later. Cheers, The JIRA Service Desk team {panel} |
New:
{panel:bgColor=#e7f4fa}
*NOTE:* This suggestion is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JSDCLOUD-973]. {panel} {panel:title=Atlassian Update – 15 Sept 2022|borderStyle=solid|borderColor=#deebff|titleBGColor=#deebff|bgColor=#deebff} Hi all, Thank you so much for your votes and comments on this suggestion. We are currently working on a solution for this ticket. We have a few open questions about the design of this feature and would love to hear your feedback. Please send an email to [lwalsh2@atlassian.com|mailto:lwalsh2@atlassian.com] if you would like to join a 45-minute session over video conference on this topic in the next couple of weeks. In the email, please include the following details: * your company’s industry * the size of your company * how your company uses Jira Service Management (JSM) * a summary of how this problem affects your team Although we can't guarantee that we will be able to speak with all interested parties, we definitely appreciate your interest and enthusiasm to help us make JSM DC easier and more enjoyable to use. Thanks, Lisa {panel} As an admin, I would like the ability to configure the *Bulk Settings* used by Service Desk Mail Handler. This is because when some mails auto-forward or redirect emails, they will generate the *auto-submitted: auto-generated* header. This header will cause the request to be not created. The incoming-mail.log will display the following error {noformat}2014-10-14 22:54:34,151 DEBUG [Mail server for xxxx@email.com. Created by JIRA Service Desk.] atlassian-scheduler-quartz1.clustered_Worker-1 ServiceRunner Mail handler used by JIRA Service Desk. Do not modify or delete. 10,200 The message has been rejected (Rejecting message due to failed bulk check.): {noformat} This is causing problems as we have multiple mail accounts and unable to configure alias due to particular reasons so we have to use redirection/forwarding but both of these will generate the said header. {panel:title=Update as of 21 May 2015|bgColor=#f5f5f5} Hi everyone, Just to give you a quick update: we've been monitoring this suggestion and understand that this is not the ideal situation. This is not on our short-term roadmap and we'll come back to it later. Cheers, The JIRA Service Desk team {panel} |
| UIS | Original: 28 | New: 19 |
| UIS | Original: 37 | New: 28 |
Hi all,
Thank you so much for your votes and comments on this suggestion. I’m happy to announce that we have shipped this feature as part of Jira Service Management Data Center 5.5 release. Jira admins now have more control over how email requests that your customers send are filtered by Jira Service Management.
The first change we've introducing is giving admins the option to turn the auto-generated email and bulk email filters on or off, depending on your preferences. The new settings are available in Administration > Applications > Email requests.
We’ve also added a global allowlist and blocklist for all of your service projects. The lists let you decide which requests should always be processed and help you get rid of spam.
Please see our documentation to learn more about receiving requests by email.
Kind regards,
Charlie Marriott
Jira Service Management, Data Center