emails stuck in queues (inside our domain queues)

We have the following configuration 1 FE to 3 BEs running on w2k3 SP1,
Ex2k3 SP2. A new FE is setup but no email is going to is as the mx/dns
records has not been setup/changed yet.

On May 16th I implemented Recipient Filtering, Sender Filtering &
Connection Filtering (also reverse DNS lookup); and shortly turn then
off as some legitimate email was being stopped, this being finals weeks
it was decided best retry next week on implementation. The biggest
mistake was not having the list servers on the Accept list for the
Connection filter - my hands have been slapped.

After turning off the filters everything seemed to get back to normal
except emails sent to our list servers; they are not leaving thier
queues.

My guess is something got messed up when I turned on and off the
filters, but can't find what. I have checked the following:

1 - nslookup from FE to mailman server - everything looks fine
2 - nslookup from FE to mailman server with -q=mx - everything
looks find
3 - check with co-works to verify no dns/name server changes made -
none made
4 - check if can telnet to mailman server and send email - works
5 - triple check that the filters are off - all 3 boxes are NOT
checked


The queues that are 'stuck' status & additional status says "the
remote server did not respond to the connection attempt" or "no
additional information available"

Anyone have suggestions?


Output of my nslookup & telnet with hidden

nslookup mailman.<ourdomain>
Server: artemis.<ourdomain>
Address: 10.125.4.40

Name: loki.<ourdomain>
Address: 10.125.4.44
Aliases: mailman.<ourdomain>

nslookup -q=mx mailman.<ourdomain>
Server: artemis.<ourdomain>
Address: 10.125.4.40

mailman.<ourdomain> canonical name = loki.<ourdomain>

telnet mailman.<ourdomain> smtp

helo <ourdomain>
250 loki.<ourdomain>
mail from:adamski@<ourdomain>
250 Ok
rcpt to:todd-l@mailman.<ourdomain>
250 Ok
data
354 End data with <CR><LF>.<CR><LF>
test
..
250 Ok: queued as 4E85C935F
quit
221 Bye

Connection to host lost.


John Adamski
Network Sepcialist/DBA
Graceland University

.

Relevant Pages

  • Re: SMTP logging
    ... the headers from the monitoring ones sent internally do have the IP of the sending server in the headers. ... The various list combinations make my head hurt, but originally I didn't even have the Connection Filter (or Sender ID) enabled so had nothing in General, which only applies to those two. ... So then I investigated the problem and through that article found that it was the Accept List in Connection Filtering that allows you to make IMF host exceptions. ...
    (microsoft.public.windows.server.sbs)
  • Re: Building a mail server
    ... qmail uses Maildir exclusively. ... vpopmail supports virtual domains and you can set catch-all accounts ... > filtering to happen on the server so it's already filtered no matter what MUA ...
    (Debian-User)
  • Re: emails stuck in queues (inside our domain queues)
    ... Its a little unclear but are you saying that outbound mail is not working or ... On May 16th I implemented Recipient Filtering, ... Connection Filtering; ... - check if can telnet to mailman server and send email - works ...
    (microsoft.public.exchange.admin)
  • Re: Slow Logon related to groups - Update!
    ... Sent update to server: 192.1.1.1 ... Group Policy processing aborted. ... Filtering: Denied ...
    (microsoft.public.windows.server.sbs)
  • Re: SOPHOS Antivirus
    ... > This one feature can eliminate 99% of the virus infected inbound email ... By definition a firewall has no mail filtering function. ... > updates for every 4 hours on the server and have the server push the ... > updates to the desktops. ...
    (alt.computer.security)