Topic: MAPI 1.0 not supported?

[mishash]

Sending an email from Outlook 2003 with attached ITEM ( contact or calendar ) comes to recipient with error
" This attachment is a MAPI 1.0 embedded message and is not supported by this mail system." ( as attached txt file )
Worked in previous e-smith ( 5 and 6 ) versions. Problem starts right after upgrading POP3 server from version 6 to 7. No changes was made on SMTP SME 5.5 ( other dedicated machine )
Any ideas? Or it's just really not supported?
   Thanks. Michael.

[sbaker712]

As stated by the original poster I would also like to know if MAPI 1.0 support is going be supported again? About 2 months ago I had moved servers from 6.01 to 7. So far the spam protection and the virus protection have been excellent. But just recently I have noticed that MAPI 1.0 is not supported. Granted this is not a deal breaker but I would like to know why the support is no longer available. I have noticed many people are viewing this post over the last couple of months but no reply post has been made. Anyone have any ideas?

[mike_mattos]

I don't have an answer for you, I did recently encounter a Windows XP Media Edition system that won't handle MAPI, all other computers on the network are working ( emailing invoices from Simply Accounting )

[jonic]

I've recently encountered the same problem on a SME v.7.1. Does anyone know a way around this? (i'm trying to attach a contact to a message using outlook XP/2003 - and instead of the contact the receipient gets a txt file with : " This attachment is a MAPI 1.0 embedded message and is not supported by this mail system." )

[p-jones]

Is this not an issue with the setup of the mail client ?? I would expect that maybe moving away from an RTF format on the client may resolve this.

http://support.microsoft.com/kb/224817

[jonic]

Is this not an issue with the setup of the mail client ?? I would expect that maybe moving away from an RTF format on the client may resolve this.

In Outlook XP I have an option to change the attachment format between:
 - MIME
 - UUENCODE
 - BINHEX

using any of this formats I still receive the same error. I 've tried sending the message to myself, so to be sure it' not a problem on the receipient's side, and I got only the txt file with the error message in it.

In conclusion I can't find a way to solve it on the client side.

[p-jones]

Does it relate to the specific encoding of the attachment or the aditional proprietary TNEF  wrapper that microsoft puts around the entire message ?? I am trying to get my head around it also.

From my understanding, I would have left the decoding of attachments at the default values and changed the message format from RTF to either plain text or HTML format.

http://support.microsoft.com/kb/197066/EN-US/

[william_syd]

There is a qpsmtp plugin tnef2mime that mail goes through.

Plugin that converts ms-tnef attachments (winmail.dat) and uuencoded attachments to MIME.

Code: [Select]

smtpd=service
    Authentication=disabled
    Instances=40
    InstancesPerIP=5
    MaximumDateOffset=1
    PatternsScan=enabled
    Proxy=enabled
    TCPPort=25
    TCPProxyPort=25
    VirusScan=enabled
    access=public
    status=enabled
    tnef2mime=enabled


[jonic]

From my understanding, I would have left the decoding of attachments at the default values and changed the message format from RTF to either plain text or HTML format.
http://support.microsoft.com/kb/197066/EN-US/

Fom the micrsoft link:

When using Plain Text or HTML as your message format, you are still free to attach files of any type to the message. The attachments will be successfully delivered to non-TNEF aware clients.

You will not be able to attach Outlook items, an Outlook contact for example, since Outlook items are special Outlook data that require TNEF, rather than regular file attachments.

Attaching Outlook items is exactly what I'm trying to do, so this is not a solution for me.

There is a qpsmtp plugin tnef2mime that mail goes through.

I have the tnef2mime plugin enabled, should I disable it then?

[william_syd]

I have the tnef2mime plugin enabled, should I disable it then?

Your call. I don't use outlook so I don't know what difference it will make.

Switching it on and off is easy enough.

Off

Code: [Select]

db configuration setprop smtpd tnef2mime disabled
signal-event email-update

On

Code: [Select]

db configuration setprop smtpd tnef2mime enabled
signal-event email-update

Its possible that this plugin just unpacks tnef attachments so they can be scanned for viri etc.

[CharlieBrady]

Sending an email from Outlook 2003 with attached ITEM ( contact or calendar ) comes to recipient with error
" This attachment is a MAPI 1.0 embedded message and is not supported by this mail system." ( as attached txt file )
Worked in previous e-smith ( 5 and 6 ) versions. Problem starts right after upgrading POP3 server from version 6 to 7.

Anything which stops working between versions should be reported via the Bug Tracker (unless the Release Notes say that the feature has been removed).

[jonic]

I switched the tnef2mime plugin off and got rid of the error  .

Thanks for the help!

Anything which stops working between versions should be reported via the Bug Tracker (unless the Release Notes say that the feature has been removed).

I am unexperienced with SME so I'm a little cautious about reporting every problem via the bugtracker, cause usually it's not a bug, but something I don't know about SME.

If you think I should report this in the bugtracker, I will.

[william_syd]

I

If you think I should report this in the bugtracker, I will.

I think you should. Even if it just ends up with the documentation team for inclusion in a FAQ/Manual.

[jonic]

I think you should. Even if it just ends up with the documentation team for inclusion in a FAQ/Manual.

Ok, done. http://bugs.contribs.org/show_bug.cgi?id=2339