>>> On 3/29/2012 at 7:17 PM, "j...@j4computers.com"
>>> wrote:
>> If you trust those ISPs to not forge headers, then add them to the trusted
>> list too, and that will push the checking boundary back to where they
>> received the me
> If you trust those ISPs to not forge headers, then add them to the trusted
> list too, and that will push the checking boundary back to where they
> received the message from.
>
> --
> John Hardin KA7OHZhttp://www.impsec.org/~jhardin/
> jhar...@impsec.orgFALaholic
>> Hmm, I use fetchmail to grab mail from various accounts.
> add the ip address (last received) from each account to trusted_networks
> in local.cf.
>
>
>> S . . . the actual source or "IP of interest" will not be the
> connection IP.
>
Thanks, but the "last received" will always be t
Continuing my learning curve with spamassassin, I find a fly in the ointment.
Some SPAM continues to slip thru. I thought, oh well, I'll just block by IP.
Hmm, I use fetchmail to grab mail from various accounts. S . . . the
actual source or "IP of interest" will not be the connection
However, this link -> http://gtmp.org/doku.php/pub_sa-postfix.en.html
says there is nothing to see here . . . move along . . . move along . . .
>>> "j...@j4computers.com" 03/27/12 10:27 AM >>>
And, if I had read a bit further, I would have seen the bit about s
And, if I had read a bit further, I would have seen the bit about setting up
postfix alias(s) for just this purpose.
Sorry for the bother. Still, suggestions welcome.
>>> "j...@j4computers.com" 03/27/12 10:23 AM >>>
I see that, to report SPAM and have spa
I see that, to report SPAM and have spamassassin "learn", I can do
"spamassassin -r < message.txt".
However, it is not clear what form "message.txt" should take. Since, by the
time my mail client receives the missed SPAM, it has been altered from its
"native" internet email form, I will have
>>> On 3/26/2012 at 11:21 PM, Duane Hill wrote:
> On Tuesday, March 27, 2012 at 02:48:08 UTC, jer...@fluxlabs.net confabulated:
>
>> Sa-update should reload SA, therefore reloading rules. What error are you
> getting ?
>
> You have to reload spamd after sa-update if any rules were updated to
>
>>> On 3/26/2012 at 10:48 PM, Jeremy McSpadden wrote:
> Sa-update should reload SA, therefore reloading rules. What error are you
> getting ?
>
>
> --
> Jeremy McSpadden
Running "/usr/sbin/spamassassin reload" produces
"warn: archive-iterator: unable to open reload: No such file or directory
After running sa-update, will restarting spamd load the new rulesets? I see
references to "spamassassin reload" but that seems to present an error message.
>>>> Ralf Hildebrandt 03/26/12 9:40 AM >>>
>* j...@j4computers.com :
>> SpamAssassin Server version 3.2.4
>> running on Perl 5.8.8
>> with SSL support (IO::Socket::SSL 0.97)
>> with zlib support (Compress::Zlib 1.35)
>>
>> Had i
SpamAssassin Server version 3.2.4
running on Perl 5.8.8
with SSL support (IO::Socket::SSL 0.97)
with zlib support (Compress::Zlib 1.35)
Had it working, but . . . now seeing in /var/log/mail 'transport unavailable'.
. . .'spamfilter.dummy . . . no such file or directory' (paraphrased)
Was
. . .
>
> Must be a configuration issue?
Working now after some fiddling and a reboot. Odd that stopping and starting
postfix and spamd did not seem to "see" the changes, but it worked after a
reboot.
My first effort at Spamassassin. Just installed on SUSE SLES10 (SP3):
SpamAssassin Server version 3.2.4
running on Perl 5.8.8
with SSL support (IO::Socket::SSL 0.97)
with zlib support (Compress::Zlib 1.35)
Basically seems to work - "spamassassin -tD < test messages" seems to create
good
14 matches
Mail list logo
