all web suggestions refer to HTML format and Convert to HTML (in
Options) but of course none of them is working

--
/-\ /\/\ /\/\ /-\ /\/\ /\/\ /-\ T /-\
-=- -=- -=- -=- -=- -=- -=- -=- - -=-
........... [ al lavoro ] ...........

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Ammammata <[email protected]> wrote:

all web suggestions refer to HTML format and Convert to HTML (in
Options) but of course none of them is working

Been many years since I last used MS Outlook, a local e-mail client, but
my recollection is winmail.dat was used when the sender composes in RTF (Rich-Text Format) instead of plain text or HTML. winmail.dat is
attached when you send a message. It's already there when you receive a message. So I'd play with the sending formats to get away from RTF. Winmail.dat is an attachment to provide the Word formatting that would
be absent when composing a message. However, if the recipient doesn't
have Word, then all the formatting info (MS proprietary TNEF) in
winmail.dat does not get applied to the body of the message, so the
recipient will not see your message as how you saw it when you composed
it.

Used to be long ago that Outlook would call MS Word as an external
handler when you chose to use RTF. Later a stub of MS Word was included
in Outlook (and why you'd see remnants of Word in the registry even if
you did not install MS Word but had installed MS Outlook). When
composing a new message, you want to avoid using the Word stub in
Outlook. That means composing (for a new message, or for a reply which
is really a new message) in RTF.

Not sure what web suggestions you've read. Have you seen the following?

https://support.microsoft.com/en-us/topic/how-email-message-formats-affect-internet-email-messages-in-outlook-3b2c0536-c1c0-1d68-19f0-8cae13c26722

"Global - If you change your default email format to plain text or HTML,
it helps make sure that TNEF is not sent unless an Outlook feature needs
it."

That means TNEF might be used if you still use a feature in Outlook that requires it, like you added Voting to your message.

When you say "HTML format", does that mean you already tried the compose setting that has you select plain text or HTML formats, as mentioned in
Method 1 of the above article? The article mentions Outlook 2010, and
later, for the methods described. You never mention which version of
Outlook you are using. Finding similar settings in older versions of
Outlook likely means a different nav path through settings.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

After serious thinking VanguardLH wrote :

When you say "HTML format", does that mean you already tried the compose setting that has you select plain text or HTML formats, as mentioned in Method 1 of the above article?

yes, sure. the usual suggestions that you find on the web have been
checked and confirmed, but don't work

someone suggested also a server-side bad parameter, but our supplier
confirmed that all mail accounts in the organization have the same
config file, thus the fact that from address alfa I get the winmail.dat
and from address beta it doesn't happen would suggest that there is
something else external to outlook that creates the problem

--
/-\ /\/\ /\/\ /-\ /\/\ /\/\ /-\ T /-\
-=- -=- -=- -=- -=- -=- -=- -=- - -=-
........... [ al lavoro ] ...........

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

VanguardLH brought next idea :

Did you configure Outlook to append a signature to your outbound
messages? If so, perhaps your signature is more than plain text, like
it contains images, so the outbound format has to get changed to one
that supports images.

yes, every user received a "standard signature", with logo, to
configure in their computers/outlook, changing just the
name/role/mail/phone
I will try sending the mail without the signature: in case it works,
the user will rebuild the signature from scratch.

--
/-\ /\/\ /\/\ /-\ /\/\ /\/\ /-\ T /-\
-=- -=- -=- -=- -=- -=- -=- -=- - -=-
........... [ al lavoro ] ...........

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

Ammammata <[email protected]> wrote:

VanguardLH wrote :

When you say "HTML format", does that mean you already tried the compose
setting that has you select plain text or HTML formats, as mentioned in
Method 1 of the above article?

yes, sure. the usual suggestions that you find on the web have been
checked and confirmed, but don't work

someone suggested also a server-side bad parameter, but our supplier confirmed that all mail accounts in the organization have the same
config file, thus the fact that from address alfa I get the winmail.dat
and from address beta it doesn't happen would suggest that there is
something else external to outlook that creates the problem

It's the sender that dictates if winmail.dat will get attached. User
alpha is sending in RTF format. User beta is not. I don't see how a
preset config file obliterates the sender's choice in what format to
compose the message they send.

Since this is a company setup, you sure your company isn't modifying
outbound messages from the workstations, like appending a company
signature or logo? If so, you have no choice over what resultant format
your company's server in modifying your outbound messages.

Did you configure Outlook to append a signature to your outbound
messages? If so, perhaps your signature is more than plain text, like
it contains images, so the outbound format has to get changed to one
that supports images. Unlike attachments, signatures are inline to the
body of the message.

Are you wanting to remove winmail.dat attachments in messages you
receive, or are you trying to avoid attaching winmail.dat for messages
you send? Seems like the latter, but then you mention messages from
different senders (to you) where some have winmail.dat and some don't.

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)