AsterFax Beta 2 has been released to sourceforge.
AsterFax now includes a test application to help you in testing that your AsterFax SMTP gateway is working correctly.
Refer to the project home page (asterfax.sourceforge.net) under the section on testing for details.
AsterFax has now had over 30 downloads and is picking up momentum.
If you are intested in getting involved in development/testing then send me an email.
Regards,
Brett.
Looks like this might become a nice product. I haven’t dug into it to deeply but from reading up on it at sf it looks like you are working on implementing various attachment types for conversions. I wrote a REALBasic fax client for Hylafax that submits directly to an SMTP server for local delivery and does some procmail work to strip the attachment which is a postscript file because i use an Apple PS driver and a port monitor i had written (not a c++ programmer) to create the postscript file that i submit to the SMTP server. The email contains the attachment and some key:value pairs in the body of the message that sets the fax number, to, to company, etc… One of the key:value pairs is quasy security id that the sender must know to submit the fax and must match the id in the procmail scripts or the message is discarded. I mention that because you had talked about some security algorithms so buy doing something similar and restricting access the port to your internal network it would be fairly secure. You could also implement a user/security id algorithm to allow reporting on faxes sent by users i.e. to what numbers, page count, whatever, etc… Throw that info in a db and pretty cool app.
So the jist of my message is are you implementing a postscript conversion process…
Can’t say I’d considered postscript, but considering I’m using ghost to do pdf conversions to tiff, I don’t think it would be a big deal.
If you know how to use ghost you can actually add the conversion yourself its quite easy just a couple of entries in the AsterFax.xml. If you want some help I’m happy to assist.
Either way I will look into it.
BTW thanks for the ideas on security.
I think the first thing I’m going to do is add authentication which is native to smtp and supported by most clients.
This doesn’t require any special id’s in the email message and will fit into existing schemes.
The following is a possible solution for AsterFax to support postscript.
It requries ghost script.
The conversion is untested but there is a reasonable chance it will work.
Simply replace the contents of AsterFax.xml with the following:
Note: you will need to redo any changes you have made to AsterFax.xml
Hope this helps and let me know if it works/doesn’t work.
Regards,
Brett
<Converter>
<Mime-Type>application/msword</Mime-Type>
<Application>/usr/bin/ooconvert.sh</Application>
<Arguments>%src% %dest% .sxw writer_pdf_Export</Arguments>
</Converter>
<Converter>
<Mime-Type>application/msexcel</Mime-Type>
<Application>/usr/bin/ooconvert.sh</Application>
<Arguments>%src% %dest% .sxc calc_pdf_Export</Arguments>
</Converter>
<Converter>
<Mime-Type>image/postscript</Mime-Type>
<Application>/usr/bin/gs</Application>
<Arguments>
>-q -sDEVICE=tiffg3 -sPAPERSIZE=a4 -r204x196 -dNOPAUSE
-sOutputFile=%dest% — '%src%
</Arguments>
</Converter>
</Converters>
<Converter>
<Mime-Type>application/postscript</Mime-Type>
<Application>/usr/bin/gs</Application>
<Arguments>
>-q -sDEVICE=tiffg3 -sPAPERSIZE=a4 -r204x196 -dNOPAUSE
-sOutputFile=%dest% — '%src%
</Arguments>
</Converter>
</Converters>
<Asterisk>
<Host>10.0.5.55</Host>
<Username>admin</Username>
<Password>amp111</Password>
<Channel>SIP/202</Channel>
<Context>default</Context>
</Asterisk>
<Settings>
<Outbox>
c:\dev\workspace\AsteriskSMTPFaxGateway\working\outbox
</Outbox>
<SpoolFolder>
c:\dev\workspace\AsteriskSMTPFaxGateway\working\spool
</SpoolFolder>
<CompanyName>Noojee IT</CompanyName>
</Settings>
Please note the sample configuration file I posted is now redundant. As of beta three postscript is supported natively (with the help of ghostscript).