T.R | Title | User | Personal Name | Date | Lines |
---|
3164.1 | | FORTY2::BOYES | My karma ran over my dogma | Wed Apr 09 1997 12:57 | 7 |
| 1) There is still not much in the manuals in V2.1, just the brefeerence to the
(heavily commented) example files.
2) The decoder is activated automatically by the gateway on any SMTP message
that is identified not to be MIME.
+Mark+
|
3164.2 | Re: .1 - Still not clear | VMSNET::R_HARRIS | | Wed Apr 09 1997 16:58 | 14 |
| Re: .1
<< The decoder is activated automatically by the gateway on any SMTP
message that is identified not to be MIME.>>
How do I get the converter to invoke? There is not a Decoder
Attribute on the SMTP entity. Do I just replace the decoder files with
the new one I create. The documentation is unclear.
Thanks in advance for your support.
Regards,
Randy
|
3164.3 | | FORTY2::BOYES | My karma ran over my dogma | Wed Apr 09 1997 17:11 | 5 |
| If a file exists with the pathname specified in the docs
(mumble/custom_decode) it will automatically be used as the second-best
alternative to MIME decoding. The existence of the file triggers its use.
+Mark+
|
3164.4 | And the real problem | VMSNET::R_HARRIS | | Thu Apr 10 1997 18:58 | 16 |
| Re: .3
Thank you for your responses. Now, the real problem is
unvealed. Mail messages are coming over as UUENCODED messages. He must
manually copy the message to disk, and run the DECODER manually.
He wants to create a decoder that will DECODE the messages on the fly.
Is this possible?
The decoders in /var/smtpgw do not seem to be working.
Thanks in adavnce for your support.
Regards,
Randy
|
3164.5 | | FORTY2::BOYES | My karma ran over my dogma | Sat Apr 12 1997 13:03 | 10 |
| The uuencode etc. scripts present by default in the /var/smtpgw
directory are not the ones you are looking for: they are for atypical
MIME content-type conversions (well-behaved MIME should be doing
base64). The one you want to modify and copy to the location in the
manual (preserving a copy of the original, as always) is
/var/smtpgw/examples/custom_decode. With *this* file in the right
place, it will be used as the decoder should the first pass by the
hardcoded MIME-parsing of the gateway draw a blank.
+Mark+
|