Cannot receive mail from

Owner's spouse cannot send email from to anyone in our domain.  However, when owner's spouse uses comcast's webmail app, the mail comes through.  How do I get the pop3 mail from their Outlook 2007 client to come through?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

brwwigginsIT ManagerCommented:
This sounds more like issues on the comcast side. The only thing I can suggest is the following:

(1) Make sure you have your MX and PTR records configured properly for your mail server. If possible, also make sure the name presented by your SMTP server matches the reverse lookup record. Some services are sensitive to this as an anti-spam measure

(2) Have the user verify their outlook settings in regards to the outgoing SMTP server. The webmail app may use a different SMTP host than the client.
ITKNGAuthor Commented:
I was just on the phone with AT&T (my ISP) and verified MX and PTR information for my domain ( to be correct.  I have the Outlook ( client that does not send to in my possession and the client is configured as recommended on the Comcast website.  It does not send very well!  Until about ten days ago I would have said this was a Comcast only issue until my Mother started getting mail returned occasionally using her AOL account.  The Comcast messages that are bounced contain errors like:
> Error reading SMTP packet; response to dot-stuffed message expected;
> likely problem with network or remote SMTP server
Delivery to the following recipients is still underway after 12.3 hour(s):
Will keep trying and contact you if the message can't be delivered permanently.
Your e-mail is being returned to you because there was a problem with its
delivery.  The address which was undeliverable is listed in the section
labeled: "----- The following addresses had permanent fatal errors -----".
The reason your mail is being returned to you is listed in the section
labeled: "----- Transcript of Session Follows -----".
The line beginning with "<<<" describes the specific reason your e-mail could
not be delivered.  The next line contains a second error message which is a
general translation for other e-mail servers.
Please direct further questions regarding this message to the e-mail
administrator or Postmaster at that destination.
--AOL Postmaster
   ----- The following addresses had permanent fatal errors -----
    (reason: 451 4.4.1 reply: read error from
   ----- Transcript of session follows -----
451 4.4.1 reply: read error from
451 4.4.1 reply: read error from
<>... Deferred: Connection timed out with
Message could not be delivered for 3 hours
Message will be deleted from queue

I also had my Domino vendor look into our server with no luck.  He cranked up the verbosity of the SMTP server and we could not find anything other than what appeared to be the messages being dropped before they were received.  I will work tomorrow to get a snapshot of those logs added here.

brwwigginsIT ManagerCommented:
does your domino server receive the SMTP mail directly or does it go through some anti-spam appliance/software?

I was not able to do a normal SMTP transaction with your server from a command line ( which makes me think it is your server config. Screenshot of SMTP
Starting with Angular 5

Learn the essential features and functions of the popular JavaScript framework for building mobile, desktop and web applications.

Sjef BosmanGroupware ConsultantCommented:
And do you see anything out of the ordinary in your server's log.nsf database, under Miscellaneous, around the times the mails were sent?
ITKNGAuthor Commented:
We use SMSDOM 8.0.7 - recently upgraded on 3/25 from an earlier v8 in hopes of getting relief to this issue - no luck.  There is no indication in the symantec product that this is the barrier.  I do not think the message is being received for the mail security app to catch it.  I have white listed with no luck.   We have also tried with SMSDOM turned completely off with no luck.
About an hour ago I sent 3 messages from the Comcast user’s laptop to my account.  Upon restarting the server after white listing Comcast again, these three messages were attempted to be delivered back to back as shown below.  We never get to DATA as with other messages.  My vendor kept saying it was like Comcast is dropping the connection before it delivers.  For that reason, he up’ed the SMTPTimeoutMultiplier to 3.  It has been that way since 3/25.
04/12/2011 01:50:13 PM  SMTP Server: ( connected
04/12/2011 01:50:13 PM  SMSDOM: PAS SMTP PROXY: [] connected.
04/12/2011 01:50:13 PM  SMTP Server: ( connected
04/12/2011 01:50:13 PM  SMSDOM: PAS SMTP PROXY: [] connected.
04/12/2011 01:50:13 PM  SMTP Server: ( connected
04/12/2011 01:50:13 PM  SMSDOM: PAS SMTP PROXY: [] connected.
04/12/2011 01:50:13 PM  SMTP Server: Originator: <>
04/12/2011 01:50:13 PM  SMTP Server: Originator: <>
04/12/2011 01:50:13 PM  SMTP Server: Originator: <>
04/12/2011 01:50:14 PM  SMTP Server: Recipient: <>
04/12/2011 01:50:14 PM  SMTP Server: Recipient: <>
04/12/2011 01:50:14 PM  SMTP Server: Recipient: <>
- nothing related to these messages afterwards
brwwigginsIT ManagerCommented:
To me it sounds like something is in between the domino server and the outside that is translating the SMTP commands. The response I get from telnetting on port 25 is not typical.

You might have to enable debugging on SMTP (SMTPDebugIO=3 and see here for reference -->

ITKNGAuthor Commented:
In the attached file you can see where the vendor attemtped to debugg with the SMTPDebugIO=3 and other settings.  The log results were never conclusive at least to us.  If you search on "charlottew" there are specific examples for this problem. outfile-Office-2011-03-25-17-07-.txt
Sjef BosmanGroupware ConsultantCommented:
Rather weird behaviour: several QUITs and RSETs, but those could be in response to spam, and many timeouts on the local server ( You could try to up the timeout delay maybe, I'd have to check where to do that, and if it's possible for incoming SMTP only.

By the way, how many mailboxes do you run on the server, i.e. the number in the Configuration document for the server, under Router/SMTP, Basics?
brwwigginsIT ManagerCommented:
What version of SMSDOM are you running? Do you have any third party blacklist filters enabled? Also I wonder if there is anything in the SMSDOM logs.
brwwigginsIT ManagerCommented:
nevermind, found my own answer on the version in the logs :)

I did see this article from Symantec that was interesting (

also, do you know if the sender is sending signed/encrypted e-mail? I see this (250-AUTH LOGIN<CRLF>) in the log that leads me to believe so but I could be reading it wrong.

I would start looking at the SMSDOM logs and settings. There are some Symantec technotes regarding issues with malformed MIME and encrypted mail.

They're just a guess right now until you look at the SMSDOM logs
ITKNGAuthor Commented:
> You could try to up the timeout delay maybe
Timeout is defaulted to 5 minutes.  The multiplier set now at 3 makes it 15 minutes.

> How many mailboxes do you run on the server
One mailbox

> What version of SMSDOM are you running?; I really do not think it is a symantec issue as we tested this issue remains when SMSDOM is shutdown

> Do you have any third party blacklist filters enabled?
DNS Blacklist filters: Disabled
Private Blacklist filter: Disabled

> Also I wonder if there is anything in the SMSDOM logs.
Never any evidence of this.  

FYI - I feel SMSDOM does well as I also feel we get a great deal of spam for about 30 Internet Users.

> tell sav info
    EMail Scanning:             on
    Write Scanning:             on
  Mass-Mailer Cleanup:          on
  Security Risk Detection:      on
  Premium Antispam Services:    on
  Standard Antispam Service:    off
  Content Filtering:            off
  Multimedia-Executable analysis: on
  Outbreak Detection:           on
  Virus Definitions:            04/12/2011 rev. 003
  Spam Definitions:             07/29/2009
  Premium Antispam Rules:       04/13/11 07:14:04
  Last Threat Found:            04/12/2011 04:43:25 PM
    Description:                SMSDOM detected the threat Trojan.Malscript!html in database John's Mail...The document was QUARANTINED.
  Quarantined Documents:        28
    Unrestored:                 17
  Statistics Since:             03/25/2011 10:20:06 AM
      Files Infected:           19
      Files Repaired:           7
      Files Deleted:            8
      Files Unrepaired:         4
    Other Scans:
      Files Infected:           0
      Files Repaired:           0
      Files Deleted:            0
      Files Unrepaired:         0
    Mass-Mailer Cleanup:
      Messages Deleted:         0
    Security Risks Detected:    0
    Spam Mails Detected:        10725
    Scan Errors Detected:       54
  Current product license: FULL LICENSE. Final product license expiration: NONE.
  Current content license: FULL LICENSE. Final content license expiration: 04/02/2012.
  Current premium antispam license: FULL LICENSE. Final premium antispam license expiration: 04/02/2012.

ITKNGAuthor Commented:
How does one go about reaching a good resource at Comcast?
brwwigginsIT ManagerCommented:
SMSDOM is not a bad product. We use it where I work as well but just for the AV portion.

As for the comcast contact, the only suggestion I can offer is check out their Postmaster page (

The only time i've ever personally run into something like this was with AOL who had blacklisted us but usually you see this when sending to comcast and not receiving.

You might have to open a support ticket with IBM and see if they can further help debug the error you are seeing

> 03/25/2011 05:24:50.66 PM [1FF4:000A-1994] SMTP CITask RecvErrorHandler> ERROR: ( Receive failed (did not timeout), error = 0A02h (Remote system no longer responding)
03/25/2011 05:24:50.68 PM [1FF4:000A-1994] SMTP CITask RecvErrorHandler> Running default handler, error = 0A02h (Remote system no longer responding)

or up the debu level to 4 instead of 3
ITKNGAuthor Commented:
I discovered a private whitelist filter in Domino.  I added and the messages started to come through.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ITKNGAuthor Commented:
Found partial solution on my own.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Lotus IBM

From novice to tech pro — start learning today.