On 2/17/2011 11:44 PM, Daniel Lemke wrote:
Michael Scheidell wrote:
[...]
I now need to set a proxy server to do sa-updates through, but could not
find any information on settings for a proxy server.
[...]
Added cmd options:
-x --proxy
-U --proxy-user
-P --proxy-password
-t --connect
h to provide such a feature is kind of weird. Would it be
possible to make the patch official? At least it'd be great if one could
specify username and password in addition to the proxy url by using
environment variables for LWP::Agent.
Any comments on this?
Daniel
--
View this message
Wonder if that would help the cronjob.
Guess that might do it.
Especially since sa-update does use the LWP libaries.
That's just like *NIX utilities.
57 varaties of how to do the same job.
Michael Scheidell <[EMAIL PROTECTED]> [24-06-2006 17:28]:
[...]
> I now need to set a proxy server to do sa-updates through, but could not
> find any information on settings for a proxy server.
echo 'alias sa-update="http_proxy=http://login:[EMAIL PROTECTED]:port/ ' \
'sa-update"' >> ~/.p
> -Original Message-
> From: Michael Scheidell
> Sent: Saturday, June 24, 2006 11:28 AM
> To: users@spamassassin.apache.org
> Subject: Sa-update and proxy servers
> Patch attached. (works here(tm))
In fact, my nightly cronjob runs 'sa-cover' script:
(exit
I think I noticed small change in sa-update for 3.13.
It is now using port 8090 for outgoing connections. (or did it always?)
This happened to make it immediately fail on servers in the DMZ which
have a strict set of outgoing egress rules.
I now need to set a proxy server to do sa-updates throug
