On 22 Dec 2006 at 11:43, Micheal Espinola Jr wrote:
The email is quite typical.
Does the recipient address match any re or list in the config?
paul
-
Take Surveys. Earn Cash. Influence the Future of IT
Join
Does the recipient address match any re or list in the config?
I think we found the problem. ASSP did the right thing to see an
attachment, which was not allowed. Winmail.dat is generated by MS
Exchange if the recipient can not understand RTF.
http://support.microsoft.com/kb/138053
On 23 Dec 2006 at 13:13, Fritz Borgstedt wrote:
Ah, That TNEF stuff. Bah!
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT
[EMAIL PROTECTED] wrote:
Does the recipient address match any re or list in the config?
No.
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share
Fritz Borgstedt wrote:
I think we found the problem. ASSP did the right thing to see an
attachment, which was not allowed. Winmail.dat is generated by MS
Exchange if the recipient can not understand RTF.
http://support.microsoft.com/kb/138053
(catching up after having been away)
Yes, that
Fritz Borgstedt wrote:
Does the recipient address match any re or list in the config?
I think we found the problem. ASSP did the right thing to see an
attachment, which was not allowed. Winmail.dat is generated by MS
Exchange if the recipient can not understand RTF.
[EMAIL PROTECTED] wrote:
Ah, That TNEF stuff. Bah!
I haven't had a chance to verify it yet, but my thoughts exactly. Being
an Exchange/Outlook admin, I cant beleive that I neglected to add .dat
to my allowed attachments list!
Shame on me! :-)
Dave Emory wrote:
So if there's not a bug, why did this message only fail to make it through
the ASSP proxy when there were multiple recipients?
Depending on the sending client (most likely Outlook or Outlook Express
on the Windows platform), each recipient could have individual TNEF or
RTF
