Victor Duchovni wrote:
On Fri, Jan 23, 2009 at 04:09:07PM -0500, sean darcy wrote:
I have a voip server that receives faxes in a tif file. I use fax2email
to convert the tif to a pdf and send it as an attachment over postfix.
My isp blocks port 22, so I've setup a gmail account to use as a relay.
That generally works.
But, every once in a while, authentication fails. When I try to log in
over the web, gmail requires not just userword and password, but also a
CAPTCHA. That's obviously why postfix authentication won't work.
I've unlocked the CAPTCHA, so the gmail account works now.
Anybody know why the gmail account required the CAPTCHA? How can I keep
it from happening again? The account is only used by postfix for this
purpose. Is there some postfix magic I'm missing?
Using a stronger (as deemd by Gmail) password may help, but they probably
have abuse heuristics that trigger re-CAPTCHA of accounts that appear
compromised. Sending high volumes of mail via automation (non-personal
use) may fairly reliably trigger this. Gmail is not a submission service
for MTAs handling something other than mail composed (infrequently) by
humans.
We probably email 3-5 faxes a day, never more than 10, so it's hardly
high volume. In any event, how can gmail know it's not me at the command
line?
I will try a scarier password.
sean
