Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 7076
  • Last Modified:

Why all the messages in C:\Inetpub\mailroot\Queue?

I am running Windows server 2003 sp2 and using the IIS- SMTP service to send email.  Last time we sent out emails it's was around 30000 and for some reason 6800 of those are stuck in the C:\Inetpub\mailroot\Queue folder.  How do i figure out why those got stuck in this folder, how do i get them sent out, and how can i prevent this from happening in the future?
0
jjones2002
Asked:
jjones2002
  • 3
  • 2
1 Solution
 
chaferCommented:
Here is one possibility.  When mail ends up in the badmail queue, it means that it was undeliverable to a recepient in your domain, but notice could also not be sent back to the sender.  If you are sending 30,000 e-mails and it is not a carefully vetted list, you may have a lot of bad addresses.  Some of these servers will then send notice back to you.  Many people sending out to a large list use an address for sending that will not receive a reply.  If this is the case, these non-delivery notices will return to your domain, but will have nowhere to go, thus they end up in the badmail queues.
0
 
jjones2002Author Commented:
HI - thanks for the comment - I agree that we should get some bouncebacks, but not 1/5 of the emails we send out.  That seems way too high a number, especially since these are customers who have signed up with us and put in their own correct email addresses.
I'm wondering whether it's an issue with the email address we are sending these from.
This server is not located on our LAN and has a different ip address than that of the mail server associated with the email address that all these 30000 emails come from.
Should email you are sending come from the domain associated with the ip address of that server in DNS records?
0
 
chaferCommented:
Your sending server could be a problem.  For example, if it has no reverse DNS record, all the large ISPs will reject your e-mail and you'll end up with a lot of bounce backs.  As to sending from a different domain, technically this is not a violation of the rules for DNS.  However, many ISPs block e-mail for this reason even though it is technically valid.
Another possibility is that if the server being used for sending is sending a lot of other people's e-mail as well, the IP address could be blacklisted.  Even though it is not your specific e-mail causing it, the fact that the address is blacklisted can cause a lot of bouncebacks.  Whatever the reason, it rally does sound like the root cause is undeliverable bouncebacks.
0
 
jjones2002Author Commented:
Ok - so i setup an mx record for the domain that the points to the server that is sending the emails and i changed the fqdn in the Delivery properties for the sending smtp server to reflect that mx record.  Was that the right thing to do?  Should i put the domain only there?
I don't see the queue shrinking at all though - how do i get those emails that are stuck sent out?

We are also setting up a reverse DNS entry - is that the right thing to do in this case?
0
 
jjones2002Author Commented:
After implementing a reverse DNS record our bounce backs dropped by a large percentage, we do still get bounce backs caused by sending email from a email address that is associated with a different server than the one sending.
0

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now