I administer our own exchange server and imf filter. Recently users here have told me of messages they have not received here but have successfully been forwarded to them from other mail severs. I have not yet identify any pattern or reason our exchnage server does not deliver these messages however I have noticed a trend: If the senders email address has a second dot within their name/address this appears to prevent the delivery. e.g. john.smith@anyplace.com appears to be problematic however johnsmith@anyplace.com is deleivered OK. Another real world example of addresses not delivered is johnsmith@regionaloffice.anyplace.com The first and third examples both have a second dot in the address and there are not delivered while the second example reaches its recipient. This problem has just recently come up and is solving it is a work in progress. I have adjusted our imf filter from delete spam to move suspicious messages to a folder for my review but I have not seenthe suspectmessages. As we get more than 10,000 junk messages each day, I don't spend a tremendous amount of time checking spam before setting our filter back to "delete". One big problem I've had with creating a list of acceptable addresses in imf filter occurs when trying to identify the smtp ip address of certain senders. Most organizations are (understandably) releuctant to give out ip addresses of their mail servers Has anyone else noticed this behaviour of addresses with a second dot in the name? My personal address has a second dot in its address and is not accepted through our exchange server either. If anyone needs clarification please post to this forum. If this topic has been posted before, I appologize in advance and askto be directed to its solution.

Can you verify that you have MX records for your regionaloffice.anyplace.com subdomains and that your Exchange server is configured in the Recipient Policies to accept SMTP mail for those domains? In my experience, Exchange does not really care how many "dots" are there provided the sending systems can resolve MX (or host) records and as long as Exchange is configured in a recipient policy to accept mail for that domain.