Ok, cool.. I added almost all of those just before you sent this in, and so far its all good.
Whats rather interesting is the textfmt catch all should have passed on my message previously as plain text, but it was coming up saying it couldnt identify what format the part was... Why would that happen? On 17-Jan-08, at 6:23 PM, Darren Nickerson wrote: Please see: You might want to add something like: #
# HTML support
0 string <!DOCTYPE HTML ps /usr/local/bin/html2ps %i >%o
0 string <!doctype html ps /usr/local/bin/html2ps %i >%o
0 string <HEAD ps /usr/local/bin/html2ps %i >%o
0 string <head ps /usr/local/bin/html2ps %i >%o
0 string <TITLE ps /usr/local/bin/html2ps %i >%o
0 string <title ps /usr/local/bin/html2ps %i >%o
0 string <HTML ps /usr/local/bin/html2ps %i >%o
0 string <html ps /usr/local/bin/html2ps %i >%o into your typerules file (assuming your converter is /usr/local/bin/html2ps). Make sure this comes before the generic match on text files that invokes textfmt! -Darren ----- Original Message ----- Sent: Thursday, January 17, 2008 9:15 PM Subject: Re: [hylafax-users] FaxMail + PDF Attachments + Email Header
OK, so how do i go about making it work, even remotely at all?
Currently if HTML is used at all, the message is rejected entirely. On 17-Jan-08, at 6:12 PM, Darren Nickerson wrote: Dayton, In 4.4.x faxmail submits attachments directly to HylaFAX for typing and conversion using typerules. The MIMEConverters are not used. Typerules work well for many file types, but not so well for HTML (there's a lot of magic combinations you need to add before you can type them reliably). If you make your own HTML and can constrain the format you should be able to add a matching rule and converter. In the current development snapshot of the next major release we've added MIMEConverters back in so you get the best of both worlds, but for now you should look into typerules. -Darren ----- Original Message ----- Sent: Thursday, January 17, 2008 8:42 PM Subject: Re: [hylafax-users] FaxMail + PDF Attachments + Email Header
Another HTML update:
In the email received, the second MIME part is:
--Apple-Mail-28--1026872698 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=ISO-8859-1
<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; = -webkit-line-break: after-white-space; ">Does it come through if i add = <b>bold?</b>=A0or <span class=3D"Apple-style-span" = style=3D"text-decoration: underline;">underline?</span></body></html>=
--Apple-Mail-28--1026872698--
I managed to capture the temp files faxmail creates, and look inside of the part.2 file to see why it was claiming it didnt know what kind of file it is. When it gets to this stage, part.2 contains:
<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; = -webkit-line-break: after-white-space; ">Does it come through if i add = <b>bold?</b>=A0or <span class=3D"Apple-style-span" = style=3D"text-decoration: underline;">underline?</span></body></html>= With no headers. Is part.2 what gets shipped off to be converted to .ps by a mime converter, and with no header, its not sure what to do?
On 17-Jan-08, at 12:39 PM, Aidan Van Dyk wrote: * Dayton Turner <dayton@xxxxxxxxx> [080117 15:12]: > Aidan, > > Thanks for the input. I'll look for a newer package in the debian > repository. In etch (4.0) currently its only at 4.4.0.
I have 4.4.3 packages here for etch: http://people.ifax.com/~aidan/apt/etch/
Unfortunately I don't have access to my etch box anymore, so I haven't had a chance to build 4.4.4 packages for etch. But you can build debian packages right from the hylafax-4.4.4 tarball.
> So I did try passing -T to faxmail, expecting that if i did not > include a message body, but did attach a PDF, for example, that i > would get just the PDF, and no mail headers, but i still got the > single page with the email headers all on their own. > > Ideas? I'll try -N out as well and see how it reacts.
The -T will "trim" the text parts (the main body) of the email, so if it's empty, it's suppressed.
the -N will suppress the "header" part. So, both the -N and -T together will cause both the "header" and the "body" parts to be suppressed.
Note that there was a bug in 4.4.0 which caused faxmail to submit an "empty" document to the server when both the header and text parts had been suppressed, which will cause you problems if you're still on 4.4.0.
a.
-- Aidan Van Dyk aidan@xxxxxxxx Senior Software Developer +1 215 825-8700 x8103 iFAX Solutions, Inc. http://www.ifax.com/
|