Koozali.org: home of the SME Server
Obsolete Releases => SME Server 7.x => Topic started by: RupDogg on April 04, 2007, 12:01:10 PM
-
Hi,
We've been using SME server for a while now, and have recently moved it from one box to another.. All went well, and the back/restore process was easy - however, it appears one thing now doesn't work!
We receive Purchase Orders from a specific customer that appears to MIME64 encode their messages. These messages and their attatchments weren't a problem on SME6.8, but on 7.0 or 7.2 are..
The message arrive at the client with "
The following is a multipart MIME message which was extracted
from a uu-encoded message.
------------=_1175268145-20440-0
FAO: XXX
AT: XXXXXXX Ltd
Please find attached purchase order number 20930
Please confirm receipt & delivery dates ASAP.
Regards
XXXXX
------------=_1175268145-20440-0
Content-Type: application/octet-stream; name="XXXX.DOC"; x-unix-mode="0666"
Content-Disposition: inline; filename="XXXX.DOC"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Mailer: MIME-tools 5.419 (Entity 5.419)
"
And then the mime encoded content....
I can use mimedecode.py to decode this message, but I'd rather have it done automatically.
Can anyone shed any light as to how I can achieve this!?
Thanks,
Rupes
-
#!/usr/bin/perl -wT
=head1 NAME
tnef2mime
=head1 DESCRIPTION
Plugin that converts ms-tnef attachments (winmail.dat) and uuencoded attachments to MIME.
perl-Convert-TNEF, perl-IO-stringy, perl-File-MMagic and perl-MIME-tools are required.
=head1 AUTHOR
Michael Weinberger, neddix Stuttgart, 2005
=head1 LICENSE
GNU GPL (GNU General Public License)
=cut
/sbin/e-smith/db configuration show smtpd
db configuration setprop smtpd tnef2mime disabled
signal-event email-update
http://forums.contribs.org/index.php?topic=30724.0
Might be the cause of your problem.
-
Thanks!
This has worked perfectly..
I was thinking that something was missing, not that something extra was there...
Rupes