Re: Email stuck in SMTP Queue

You create the rule and stick it just ahead of the default SBS
internet access rule. You block outbound smtp from internal with an
exception for the computer called server. Or whatever computer you add
which is your SBS.

On Fri, 9 Jan 2009 15:27:27 -0500, "Thomas Kroljic"
<tkroljic@xxxxxxxxx> wrote:

Jim,
We are running ISA but I'm not sure where to look to see if we have a
rule set up for the server only sending out SMTP. Can you point me in the
right direction?

"Jim Behning SBS MVP" <jimbehning@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:6iicm4523cr3ofi7mo2dl32skfkb482i64@xxxxxxxxxx
mxtoolbox.com to double check stuff.

If you are running ISA then set a rule so only the server can send out
smtp.

If you are running a router/firewall set it up so only the server can
send out smtp. If your router/firewall does not let you do this then
you should rethink your router/firewall.

On Thu, 8 Jan 2009 11:13:46 -0600, "Les Connor"
<les.connor@xxxxxxxxxxxx> wrote:

Sorry - I don't have any tips, I presume whatever is on their website is
authoritative.

--
Les Connor [SBS-MVP]


____________________________
"Thomas Kroljic" <tkroljic@xxxxxxxxx> wrote in message
news:u3Lu%23AbcJHA.5748@xxxxxxxxxxxxxxxxxxxxxxx
Les,
We're still listed on Sorbs.net. I just doubled checked and I entered
in
the wrong IP address by mistake. Any thoughts on how to get off this
list?
I followed there Support form about two days ago and I haven't heard
anything back from them.

Damn, I thought I was in the clear :)

"Thomas Kroljic" <tkroljic@xxxxxxxxx> wrote in message
news:eH0NksacJHA.1328@xxxxxxxxxxxxxxxxxxxxxxx
Les,
just checked on the Sorbs.net website:

[64.105.207.105] was not found in the SORBS database.

This is good.

"Les Connor" <les.connor@xxxxxxxxxxxx> wrote in message
news:OZcZoSacJHA.572@xxxxxxxxxxxxxxxxxxxxxxx
Not everyone uses the spamhaus/sorbs RBLs, but for those that do, and
if
you're listed, your emails will be blocked when sending to those
servers.

The more important issue is that you're listed, especially at
spamhaus.
They don't list you for no reason, and while you can remove your IP,
if
you don't take action to correct the original problem you'll be listed
again and then it's not so easy to get de-listed.

Go to spamhaus; find out why you're listed, and address the issue.

If you're concerned about the length of time it takes to receive delay
notifications, that can be changed in exchange system manager.

If spamhaus lists you because of your IP range (dynamic, shouldn't be
hosting a mail server) you have the option of sending via smarthost
(via
your ISPs mail server) rather than directly (using DNS).

--
Les Connor [SBS-MVP]


____________________________
"Thomas Kroljic" <tkroljic@xxxxxxxxx> wrote in message
news:eVnyYqZcJHA.5412@xxxxxxxxxxxxxxxxxxxxxxx
<<so it isn't spam or a spam relay>>
This is my worry. This was my initial thought as to why these email
messages are stacking up in the SMTP queues.

I'll let the emails sit until the time-out period, but it worries me
that certain emails may or may not get out. And when you're running a
business, this can become a big problem.

The other day, i had one user who tried to send an email and was
notified immediately that the email failed to reach it's destination
due to being on a Spam/Virus blocklist. I had to go to something
called
spamhaus.org to remove our IP address. We also received another email
two days ago saying the email couldn't be sent because the IP address
was blacklisted at Sorbs.net.

Why would most (98%) of our emails get sent and just a small number
of
them either sit in the queue or are immediately returned due to being
blacklisted?

Thanks for the explanation and helpful suggestions.

"Cliff Galiher" <cgaliher@xxxxxxxxx> wrote in message
news:OLGZkLQcJHA.5748@xxxxxxxxxxxxxxxxxxxxxxx
After re-reading the thread, I don't think you have anything to
worry
about. These appear to be mails originating from within your
organization and going out...so it isn't spam or a spam relay.

Usually a person sends an email from your organization and it goes
out
successfully. So you see it in your queue briefly. Sometimes
though,
the person mistypes an email address, but gets the domain name
right.
Most receiving servers (let us use hotmail as an example) will check
the name and return a hard-fail if the name doesn't exist. Because
it
was a hard failure, Exchange generates an NDR for you and drops the
mail from the queue. So again, you only see it in the queue while
this short transaction happens.

But sometimes a mail provider does a 'soft' fail. Maybe the mailbox
at the receiving end was full. Or maybe the directory service to
check the name was offline. Or maybe they just have a sysadmin that
misconfigured their email server. Who knows. But exchange handles
a
soft fail by holding onto the message and retrying. So that message
will stay in your queue until the retry succeeds or a preset
time-out
passes. Since your initial post indicated that you were seeing
messages from "a couple days" ago, it is reasonable to assume that
you
are simply seeing messages that could not be delivered (yet) but
haven't timed out either.

You don't need to delete these from the queue. Let exchange manage
it
for you. It'll keep trying periodically until the time-out is
reached
and then generate an NDR for the user who sent the email. This is a
*good* thing because you want the sender to know that their email
failed. If you start seeing messages stack up in the queue that are
older than the time-out you've set (as I recall the default is 5
days,
but I might be off) then you can start to worry. Otherwise I'd just
leave it be. :)

-Cliff


"Thomas Kroljic" <tkroljic@xxxxxxxxx> wrote in message
news:eN7fE7PcJHA.5540@xxxxxxxxxxxxxxxxxxxxxxx
If I click on the queue names, here is some of the information that
is showing up under the "additional queue information"

- No additional information
- An STMP protocol error occurred
- Unable to bind to the destination server in DNS
- the connector was dropped by the remote host
- the remote server did not respond to a connection attempt

Not sure what these mean.


"Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx> wrote
in
message news:uPGMW4OcJHA.3948@xxxxxxxxxxxxxxxxxxxxxxx
While viewing Queues in Exchange System Manager, select the queue
containing the stuck messages. Is there any useful information at
the bottom under "additional queue information?"


"Thomas Kroljic" <tkroljic@xxxxxxxxx> wrote in message
news:ugTgkuOcJHA.4660@xxxxxxxxxxxxxxxxxxxxxxx
We are running SBS 2003 R2 w/Exchange Server. About 5 days ago I
noticed a number of emails sitting in our SMTP Virtual Connector
queues. Not sure how to release them. Most, about 99% of our
emails
get sent out, but we do have a number of emails from a few days
ago
and even today that are sitting in the queues.

can anyone either shed some light on this matter or point me in
the
right direction on a) how to release these emails and b)
determine
what is causing this problem.

I am not an Exchange expert but with a little help should be able
to figure this problem out.

Thank you,
Thomas Kroljic.











See what SBS support is working on
http://blogs.technet.com/sbs/default.aspx
Check your SBS with the SBS Best Practices Analyzer
http://blogs.technet.com/sbs/archive/tags/BPA/default.aspx

See what SBS support is working on
http://blogs.technet.com/sbs/default.aspx
Check your SBS with the SBS Best Practices Analyzer
http://blogs.technet.com/sbs/archive/tags/BPA/default.aspx
.

Relevant Pages

  • RE: Exchange, BadMail Folder
    ... always growing after you have removed files from folder and unplug server ... Furthermore,Please refer to the following KB article to clean up the SMTP ... click SmallBusiness SMTP Connector under ... them in a single queue for the SmallBusiness SMTP Connector or for the one ...
    (microsoft.public.windows.server.sbs)
  • Re: Email Queue Error
    ... the value "SMTP Server Remote Queue Length" ... If your clients do send many e-mails, it is a normal behavior and you can ...
    (microsoft.public.windows.server.sbs)
  • RE: SBCs SMTP server quit working with SMTP connector
    ... Thank you for posting in the SBS newsgroup. ... Connector and Default SMTP Virtual Server. ...
    (microsoft.public.windows.server.sbs)
  • Re: Cant Send Mail - SMTP Issues
    ... Internet mail server does not have the correct DNS configuration required ... AOL.com also requires that for every inbound SMTP connection, ... Currently, if you SBS clients use Fixed IP address, it is better for them ... SMTP connector in SBS 2k3 is automatically ...
    (microsoft.public.windows.server.sbs)
  • RE: SBCs SMTP server quit working with SMTP connector
    ... SMTP connector and default SMTP virtual server. ... > Thank you for posting in the SBS newsgroup. ...
    (microsoft.public.windows.server.sbs)
Loading