Faxes to Germany/Attachments
axel....@uni.de
> Your facsimile job to +495252974215 was rejected because:
> Document preparation failed: Too many pages in submission; max 20
>
> ---- Unsent job status ----
>
> Destination: +495252974215
> JobID: 25976
> GroupID: 25976
> Sender: axel.husung
> Mailaddr: axel....@uni.de
> Submitted From: localhost
> Page Width: 209 (mm)
> Page Length: 296 (mm)
> Resolution: 98 (lpi)
> Status: Document preparation failed: Too many pages in submission; max 20
> Dialogs: 0 (exchanges with remote device)
> Dials: 0 (consecutive failed calls to destination)
> Calls: 0 (total phone calls placed)
> Pages: 0 (pages transmitted)
> TotPages: 21 (total pages to transmit)
> Attempts: 0 (attempts to send current page)
> Dirnum: 0 (directory of next page to send)
>
> Subject: test
_____________________________________________________________________
Question 1:
Hi folks,
yesterday I sent a fax to Germany and got the above-mentioned
results.
Can someone explain it to me ?
Question 2:
I attached a Tiff file and a PS file to the message and get results
on the fax as follows:
This message contains a file prepared for transmission using the MIME
BASE 64 transfer encoding scheme. If you are using Pegasus Mail or
another Mime-compliant system, you should be able to extract it from
within your mailer. of you cannot, please ask your system
administrator for help !
Can someone help ?
Thanks for your help in advance !
Kind regards,
Axel Husung
Paul Yau
> Date: Wed, 31 Dec 1997 10:08:04 -0500
> To: tpc...@info.tpc.int
> From: Vivian Yan <vy...@interlog.com>
> Subject: Re: Faxes to Germany/Attachments
> Hello Axel,
>
> Sorry about the delay, I finally had a chance to look at the files you sent
> me.
>
> Based on what I received from you, I saw two problems.
>
> (1) Did you send tif and ps files to TPC the same way as you sent them to me?
> If you did, I am pretty sure it won't work. The two graphic files you sent me
> were "attached" inside the body of the email message (technically this is
> called "embedded" graphic files). The fax server treats all email body as text
> file only and will not look for and analyze the graphic file inside the
> body of
> the email message. You have to attache the graphic files as an attachment to
> the email message. To do this in Euodora, click Message and then click Attach
> File, then pick the appropriate file and click Open. After you have done this,
> you will find the selected filename will appear in the message header, under
> "Attached:". When files are attached this way, they are attached to the email,
> but separate from the body of the message and the fax server will be able to
> analyze and process them.
>
> When you see the following lines:
> >
> >This message contains a file prepared for transmission using the
> >MIME BASE64 transfer encoding scheme. If you are using Pegasus
> >Mail or another MIME-compliant system, you should be able to extract
> >it from within your mailer. If you cannot, please ask your system
> >administrator for help.
> >
> You know you file was embedded inside the body of the email message.
>
>
>
>
> (2) The TIF file you sent me was properly prepared. I was able to view it with
> me graphic file viewer. You shouldn't have any trouble sending it to a fax
> server. However the PS file is a totally different story. The contents of a PS
> file is in ASCII text characters and you should be able to load it into you
> word processor and view it. The first few lines of a typical ps file looks
> like
> this:
> %!PS-Adobe-3.0
> %%Title: Graphic1
> %%BoundingBox: 16 9 597 784
> %%CreationDate: 12/27/97 17:23:32
> %%Pages: 1
> %%Requirements: None
> %%LanguageLevel: 1
> %%EndComments
> But the ps file you sent me contains all binary values. The first 300 bytes
> were zeros, then followed by '1B 45 1B 2A 6F .......'. If you import this file
> to your word processor, you'll see some strange symbols, such as
> '¬¿0w0w0w0w0w0w0'. I really can't tell what was wrong. My guess was that you
> selected a printer driver other than a postscript printer driver.
>
> Did you install the Apple Laserwriter II NT postscript printer driver? Did you
> select it before you 'print to file'?
>
> Hope you'll find the above helpful. Write to me again you need further
> asistance. Meanwhile have a
>
> Happy New Year !
>
>
>
>
>
> Vivian Yan
> Toronto/Canada
> 31Dec97
>
>
>
Hello Axel & Vivian,
Answers to your questions,
1) It's clear that the job was rejected because of sending too many
(over 20) pages in a call. This limitation might be setup by the
remote print server or by the called fax machine.
If u were sure that it's not, then
2) Axel, u didn't properly select the file types of "TIFF/image" &
"PostScript" when u attached files to your message. They had been
treated as plain text and that's why it's over 21 pages. Do NOT
let mailer (Pegasus mail) decide it for u. Check
http://www-usa.tpc.int/faq/tpcfaq.html
for the MIME types accepted by the remote printer servers.
3) The file description was created by Pegasus mail automatically and
can not be removed.
To avoid a separated phone call (to save the free resources) u
should click on "Send enclosures instead of attachments" on
Pegasus mail or "Put text attachments in body of message" on
Eudora.
4) This is my recommendation to u.
Read TPC FAQ carefully. Before u make any test, send the
messages and files to yourselves 1st. Try to understand more of
your email clients. Since u are using Pegasus mail, press Ctrl-H
for message header and see what's composing the message.
Regards,
Paul Yau
Adam H. Kerman
>From: Paul Yau <pau...@ms2.accmail.com.tw>
>Date: Mon, 5 Jan 1998 03:18:03 +0800
>To avoid a separated phone call (to save the free resources) u should click on
>"Send enclosures instead of attachments" on Pegasus mail or "Put text
>attachments in body of message" on Eudora.
I don't use either Pegasus nor Eudora. To my ear, this sounds like non-standard
MIME implementation.
Are you implying that in lieu of sending an attachment, a separate message is
sent, under default Pegasus behavior? What is a MIME enclosure vs. MIME
attachment?
And, in Eudora, where else would one put an attachment but in the body of a
message? You can't put them in the header! Again, are you implying that default
behavior is tend send what should be an attachment as a separate message?
If I ever used either, I would hate it if I expected the MUA to do one
according to standards, but its default behavior is to do another.