Many of our users are upset with our webmail not processing the .dat issue. If someone can guide me on what has to be written in surgemail to process this .dat files I will get it developed and will be more than happy to share the source code.
We cannot ask the senders of Outlook to fix the problem on their end. There are too many people who are using outlook who send us emails. Our clients argue that yahoo and google are handling .dat files, so we too should.
On 8/31/06, BG Mahesh < bgmaheshgmail.com">bgmaheshgmail.com> wrote:
hi
Some of our users are getting datfiles as attachments which surgemail is not able to parse [I know it could be Outlook issue]. But the users are forwarding that very same email to their yahoo account and the attachment is viewable in their yahoo account.
Can something be done by which this issue is resolved within surgemail?
Two things here(one is a pet peeve of mine and is causing some issues
here) EDIT the subject line and remove the word SPAM from the subject.
The issue here is that Outlook is creating emails in RTF format(rich
text format). I cann't help you convert them, but leaving the
offending sender as is will cause them other problems. I became aware
of this issue when sending email to one of my computer parts supplier.
They were complaining that they were getting blank emails.
We discovered that even Microsoft(who invented RTF) decided it was evil
and was converting RTF to HTML within Exchange on incoming email.
However Microsoft's conversion routines were faulty and was passing
blank emails to the receiver. If Microsoft can not write a bullet
proof converter, how do you expect anyone else to?
It is in the best interests of the sender to change their
Outlook/Outlook Express and to stop using RTF for sending email.
Lyle Giese
LCR Computer Services, Inc.
BG Mahesh wrote:
mail.gmail.com"
type="cite">
Many of our users are upset with our webmail not processing the .dat
issue. If someone can guide me on what has to be written in surgemail
to process this .dat files I will get it developed and will be more
than happy to share the source code.
We cannot ask the senders of Outlook to fix the problem on their end.
There are too many people who are using outlook who send us emails. Our
clients argue that yahoo and google are handling .dat files, so we too
should.
Some of our users are getting datfiles as attachments
which surgemail is not able to parse [I know it could be Outlook
issue]. But the users are forwarding that very same email to their
yahoo account and the attachment is viewable in their yahoo account.
Can something be done by which this issue is resolved within surgemail?