Page 2 -
Problem receiving emails with attachments
Page 2 - Discuss Problem receiving emails with attachments in the Mail Server Help forum on Dev Shed. Problem receiving emails with attachments Mail Server Help forum discussing tips, tricks, techniques and Spam containment solutions. Topics include mail servers such as Sendmail and Qmail, webmail interfaces such as Squirrelmail and Horde and spam solutions such as SpamAssassin and Bayesian
Receive the tools necessary to be the rock star of your field. Our 12-month program teaches you the evolving world of multi-channel marketing as well as the complex issues and opportunities found in the industry.
ASP Free and Iron Speed Designer are giving away $5,500+ in FREE licenses. Iron Speed's RAD CASE toolset can save up to 80% of your coding time. One free license per week, one perpetual license per month! Download and Activate to enter!
Web development can be a daunting task, even for specialists. There is a lot of information to absorb and a lot of technologies to learn in order to manage a superior website. When trying to learn the ropes, developers need a reliable source to introduce new ideas that can be easily implemented. When working on large projects, even web veterans may run into a technology or an aspect of a technology that they are unfamiliar with.
Posts: 2,120
Time spent in forums: 2 Weeks 7 m 16 sec
Reputation Power: 1830
You can view the raw exchange logs, usually located in C:\Program Files\Exchsrvr I believe. If the logs don't reveal anything I would call Comcast. You can also try running wireshark on the network interface your Exchange server uses when you send a test email to see if traffic is hitting the server.
Posts: 204
Time spent in forums: 3 Days 16 h 27 m 2 sec
Reputation Power: 51
Picking this back up... haven't called Comcast because we've been quite busy with other things and we just used an external email account as a temporary workaround.
Now, I finally have a little more time, and I just received a bounceback that had some more information on it. I'm not sure at this point if the user is using Comcast or not:
Quote:
Reason: Remote host said: 601 Attempted to send the message to the following ip's: xx.xx.xx.xx
-- The header and top 20 lines of the message follows --
The ip address listed in the email is the WAN interface of our firewall, the interface that's hooked to our router. I ramped up the firewall logs to see if there's anything noteworthy there, but I suspect it'll take some time to sift through. Our firewall does have a Content Filtering system, but I checked and the only forbidden attachments are batch files, executables and other potentially malicious extensions. The emails that are bouncing typically have either .rtf, Word docs, or PDF files (none of which we have problems receiving on a regular basis). If anyone has any ideas, please let me know. I'll post back once I can monitor the firewall logs for a while.
Posts: 2,120
Time spent in forums: 2 Weeks 7 m 16 sec
Reputation Power: 1830
Hi Slam,
Unfortunately there's not a lot of information out there that I could find about this error. A few forums suggested validating that your MX record is setup correctly, and the corresponding A record is correct. I'm pretty sure in a previous post you said this was ok though right? If you could double check that would be helpful. I don't thin it's a content filtering issue. In my experience the mail comes through, it's just routed to a spam/quarentine location so you can retrieve it if you need to (either that or the message is just stripped of the attachment).
Is it still only an issue with Comcast users? What did Comcast ever say in response?
Del.icio.us
Digg
Google
Spurl
Blink
Furl
Simpy
Y! MyWeb
Linear Mode
