WINMAIL.DAT

[desmo]

Hi,

Thanks for the insight, omshowux shows:

MIME Mailnode : internet
TNEF Mailnode : internet,tnef
TNEF Domains :
Dist List Abbreviation Limit : 0

I sent an email from Outlook 2003 to an address not in the contacts, using Plain Text and "Let Outlook decide what format" and I got winmail.dat. Same thing when sending HTML and letting Outlook decide what's best, or specifying Plain text in both message format and contact preferences, this all to the same address to a sendmail server.
Unfortunately I had not logging enabled at the time and cannot reproduce it now from my account/Outlook.

NEWS:

I think I got it. It is NOD32, if I enable scan of outgoing messages I receive winmail.dat no matter if I send Plain/Rich Text/HTML.
If NOD32 is disabled I can send Rich Text/HTML/Plain and I get the message and the attachments just fine.

Now, is there anything I should do to confirm this with a proof so that if it is the issue it can be addressed and solved?

Cheers

Simone

[Richard Hall]

Hi Simone,

I don't know anything about NOD32, is this a plug-in to the Outlook client?
Perhaps it can be configured to suppress the creation of WINMAIL.DAT attachments? Anyone else use this email scanner?

Richard

[desmo]

Hi,

NOD32 is a very good antivirus solution that integrates with Outlook ( http://www.eset.com/)
The module that integrates with Outlook is EMON, and disabling only the scan for outgoing emails seems to solve the issue. Considering we use ClamAV on Scalix for incoming and outgoing emails this doesn't really affect our environment, incoming emails are scanned twice (once on Scalix/ClamAV and then NOD32 on Outlook), outgoing emails only once on Scalix.

That said, I think it would be useful to find somewhere in the logs where and why this is happening, so that if this is an issue it can be solved. I enabled full logging on Outlook and collected logs for NOD32 enabled and disabled in case this can help. If there's any other test/logging I should do please let me know.

Thanks for the help you all provided, much appreciated

Simone

[axelu]

We have the same problem, but only with tasks.

When we send the tasks with another Mailserver, everything is fine.
So it is definitely not an Outlook- or a virus-scanner-problem.

Our Scalix-Server is an out-of-the-box-configuration with no tnef routes etc..

[KevinAnderson]

No spam or virus scanning, server or desktop?

Kev.

[axelu]

Yes - we have fsecure desktop scanner.

[KevinAnderson]

If you disable it, does the problem disappear?

[axelu]

No it doesn´t disappear - same problem.

I have now discovered, that if the Mails go through the internet-queue, it does not work.
When it goes through the local-queue, everything is fine...

The question is, why are some recipients going through the internet-queue, even if they come out of the scalix-system-addressbook?

Somebody told me, it could be the Outlook-address-cache (nk2-files)?

[KevinAnderson]

That's possible, I suppose. You can clean the NK2 files by deleting them from c:\Documents and Settings\<Profilename>\Application Data\Microsoft\Outlook

I'll recommend backing them up. It's possible that your users will want them back.

That would confirm that this resolves the problem, but it still seems strange to me.

Kev.

[axelu]

Solved!

omconfux -T mydomain.de

was the solution. The hostname of the Scalix-Server is scalix.mydomain.com, so he always used the internet-queue for mydomain.de.

So I set the Domain as a TNEF-Domain and now it works.

Thanks to all for your help.

[axelu]

By the way - the TNEF-feature is only for SBS or Enterprise-Edition, not Community...