FaxSTF fails to send - but only from my main user account!

Question

I bought FaxSTF in version 6 for OS 9, and version 10.5.3 for OS X. My woes with it in OS X are not so much of the kind that I've read while searching this area for answers; they are rather peculiar, and I suspect FaxSTF might not even be at fault (though I can't be sure). For what it's worth, let me also state up front that under OS 9 it worked almost rock-solidly. It was very, very versatile and amazingly reliable. Not so much in OS X; versatility and reliability are out the window. I'll explain:
In my main user account ('alex', admin account) no matter which application I try to fax from, when I click on the blue throbbing 'Fax' button, it stops throbbing and becomes grey and nothing else happens. I can only dismiss the print dialog by clicking on 'Cancel'. There is nothing I have tried which can change this behavior.
Things are better, though, in secondary, standard or admin user accounts on the same machines. From them, I can fax things with no problem whatsoever.
This is the second powerbook on which this is happening: the other one is my TiBook 550MHz running Tiger, also. What it's meant basically is that when I need to send a fax, I have to:
•save my document in a directory accessible by my other, secondary, accounts, then
•use Fast User Switching (thank goodness for that) and through my other account ...
•open the document (usually a PDF by now, so I only have to use Preview which loads fast enough) and
•enter the fax number manually (since my Address Book database is not accessible by the secondary account) and click on Fax.
Of course, if I need to keep track of sent faxes, I then have the additional step of exporting the fax into Fax format from FaxSTF from the secondary account, then over at my main account go into FaxSTF and import it for my records.
Not so practical...
Thankfully, FaxSTF is fine when receiving faxes while logged in my main account.
I was hoping that some useful hints/help will be available through the Discussion Area, as opposed to SmithMicro customer support; they take up to months to reply to an incident posted on their web-driven database, and when they do, their responses are almost meaningless most of the time, assuring me that my problem is not really happening, and reminding me of the correct procedure for doing things (it's the very procedure that doesn't work with me, but often times they haven't even read/understood my incident post in the first place. Very polite people, though; I'll give them that!)
As always, thanks in advance, people.

Answer 1

I would look into if the ports the smtp is using are open at all
if they are closed over 3g then it should work over wifi unles your wifi router block them too
and of cause if you set the wrong encryption or some of the other smtp settings then that too would
explain it