Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
It only seems to happen when the receiving server is M$ Exchange 2007.
If you put it that way then this is not an interoperability problem on the GNU/Linux side of things. This is the Linuxquestions.org Linux - Networking forum. Not a mcrsft forum. That'll be /General. Please first search the vendors knowledgebase first for support for their proprietary commercial products. In this case you might want to check the software for available service packs as I understand there's been some fixes for conversion errors, else check Technet for troubleshooting at "Managing Content Conversion Tracing". Thanks for understanding that a freely accessable, provided-at-no-cost, volunteer-driven GNU/Linux forum should not have to cater to problems on the proprietary, commercial, standard-breaking ClippyOS side of things.
If you are not willing to try and help me with an issue that I have with the GNU/Linux side of things, that is all you have to say.
I only receive an back error from Exchange servers. The emails is received fine by other mail servers, but the attachment is not reported as the correct mime type. The file is still readable though.
I have contacted the people responsible for the servers we are having problems with, and they say that they are not having issues with email from any other source. Since there are many of them, and only one of us, it makes sense to start with our server.
I have also posted on the ClakConect forum, with no luck either. It seems that the community is no longer willing to help us guys who need the help.
Let's break things down so you understand: your colleague uses an OSS MUA. You use an OSS MUA. You admitted you received the email OK using another email address (other MTA mail route). You clearly said that your colleague had a problem when sending email through a certain brand MTA and the returned message supports that. I say the fact that you find you do not receive the answer you expect does in no way reflect back on this community or its willingness to help out. That said, BinHex makes sense because it's a Mac but if you believe it's something with the MIME type then you should have posted that more clearly and support it with the necessary details.
NP. Ask your colleague to resend the attachment but have him configure MUA compression for "AppleDouble" or "base64" (UUE) format. If that doesn't work ask him to compress it with (tar and) gzip and then use 'mpack' to send it. Let me know if those arrive OK through the troublesome MTA.
I have had them pack the file into a zip. This email was received fine, but the attachment couldn't be opened at the other end. I am waiting on them to try using AppleDouble or base64. Will report with the results.