Major incidents can send mastered service desk processes into disorder. Systems and tools produce the data needed to resolve these incidents, but your challenge is getting that information to the right people fast. Check out the Survival Guide and begin bringing order to chaos.
Course Of The Month
5 days, 12 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Undeliverable: The e-mail account does not exist at the organization
Posted on 2008-10-16
I am having trouble sending mail.
we have a ticket system that runs on our webserver, emails sent to sales@domain.com are automatically piped into the system.
We also have a catchall account that is picked up by our exchange server.
I am trying to reply to the EXTERNAL account (sales@domain.com) so that i can reply to my tickets directly from Outlook, but every time i try to send i get the following error:
Your message did not reach some or all of the intended recipients.
Subject: RE: New Ticket - [SALES !YHE-462417]: another test [Scanned]
Sent: 16/10/2008 14:36
The following recipient(s) cannot be reached:
sales@domain on 16/10/2008 14:36
The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address.
<domain.com #5.1.1>
It seems to me that it's looking only on the internal network - i need to send it to our webserver so that it can be piped into the ticket system.
I am using Kayako SupportSuite for the ticket system.
Thanks :)
we have a ticket system that runs on our webserver, emails sent to sales@domain.com are automatically piped into the system.
We also have a catchall account that is picked up by our exchange server.
I am trying to reply to the EXTERNAL account (sales@domain.com) so that i can reply to my tickets directly from Outlook, but every time i try to send i get the following error:
Your message did not reach some or all of the intended recipients.
Subject: RE: New Ticket - [SALES !YHE-462417]: another test [Scanned]
Sent: 16/10/2008 14:36
The following recipient(s) cannot be reached:
sales@domain on 16/10/2008 14:36
The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address.
<domain.com #5.1.1>
It seems to me that it's looking only on the internal network - i need to send it to our webserver so that it can be piped into the ticket system.
I am using Kayako SupportSuite for the ticket system.
Thanks :)
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
4-
4
8 Comments
that "domain.com" is your INTERNAL AD domain, right?
If so, then you need to have a SMTP address sales@domain.com configured in your AD in order to receive from internal.
If so, then you need to have a SMTP address sales@domain.com configured in your AD in order to receive from internal.
our internal domain is: domain.local
Our website is: leapfrogavit.com
The error is:
The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address.
<leapfrogavit.com #5.1.1>
i know sales@ address works because i just sent an email to it from my gmail account :)
Our website is: leapfrogavit.com
The error is:
The e-mail account does not exist at the organization this message was sent to. Check the e-mail address, or contact the recipient directly to find out the correct address.
<leapfrogavit.com #5.1.1>
i know sales@ address works because i just sent an email to it from my gmail account :)
you use leapfrogavit.com as your internal email domain, right? (in other words, your employee's email addresses are xxxx@leapfrogavit.com, is this correct?)
You can send from your gmail that's because you have a catchall setting, so your exchange knows to put emails sent to sales into that catchall account. Whereas when you are internal, your exchange knows that's the domain (leapfrogavit.com) it is looking after, then it will find where's that sales account, if no, then NDR is sent.
You can send from your gmail that's because you have a catchall setting, so your exchange knows to put emails sent to sales into that catchall account. Whereas when you are internal, your exchange knows that's the domain (leapfrogavit.com) it is looking after, then it will find where's that sales account, if no, then NDR is sent.
yes thats right :)
but our catchall is held on the webserver, and collected using the Exchange POP3 Connector
how can i make exchange check to see if the account exists OUTSIDE of our internal LAN if no address is found internally?
but our catchall is held on the webserver, and collected using the Exchange POP3 Connector
how can i make exchange check to see if the account exists OUTSIDE of our internal LAN if no address is found internally?
"how can i make exchange check to see if the account exists OUTSIDE of our internal LAN if no address is found internally?"
I don't think that's possible. so
1. Why do you need send emails to that sales account from Internal?
2. Can you setup sales@leapfrogavit.com as a secodary smtp address for the account that collect the catchall?
I don't think that's possible. so
1. Why do you need send emails to that sales account from Internal?
2. Can you setup sales@leapfrogavit.com as a secodary smtp address for the account that collect the catchall?
Here is a flowchart of how it should work:
Customer Creates Ticket
|
Email sent to helpdesk staff
|
email collected by catchall
|
emails distributed by exchange
|
user replies to email
|
email sent through exchange
|
email arrives at webserver
|
email piped to ticket desk
|
ticket desk emails customer
Customer Creates Ticket
|
Email sent to helpdesk staff
|
email collected by catchall
|
emails distributed by exchange
|
user replies to email
|
email sent through exchange
|
email arrives at webserver
|
email piped to ticket desk
|
ticket desk emails customer
I was able to resolve this issue by using the "forward all mail with unresolved recipitants to host" on the virtual SMTP connector properties :)
Featured Post
What are the business impacts of how well businesses communicate during an IT incident? Targeting, speed, and transparency all matter. Find out more in this infographic.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
When the s#!t hits the fan, you don’t have time to look up who’s on call, draft emails, call collaborators, or send text messages. An instant chat window is definitely the way to go, especially one like HipChat.
HipChat is a true business app. An…
This article will help to fix the below errors for MS Exchange Server 2013
I. Certificate error "name on the security certificate is invalid or does not match the name of the site"
II. Out of Office not working
III. Make Internal URLs and Externa…
The video tutorial explains the basics of the Exchange server Database Availability groups.
The components of this video include:
1. Automatic Failover
2. Failover Clustering
3. Active Manager
This video discusses moving either the default database or any database to a new volume.
Suggested Courses
Course of the Month5 days, 12 hours left to enroll
707 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.