On Thu, 2010-07-22 at 11:51 -0700, Neil Hodge wrote:
> 2010/7/22 Karsten Bräckelmann <guent...@rudersport.de>:
> >
> > So, did you just say, that you check mail for one account (you mentioned
> > a single ISP only) from two different places, namely home and work? That
> > scenario spells IMAP to me -- your *own* IMAP server at home.
> >
> > That way, you will need a single SA only, and a single server to
> > maintain.
>
> Well, I hadn't really expected to find anyone on the list who is
> willing to be so helpful, but since you are . . . :)
>
> Basically, your understanding of my description is correct. Of
OK. Then I guess I don't see how exactly you meant to implement this. :)
So your plan was, to access your ISPs IMAP server (and keep mail on that
server!?), while adding a second line of defense -- your own SA. That
right so far?
Unfortunately, your description of checking mail from $n places, and
having SA running at all these places, sounds like client side
filtering. Fire up the MUA, download all the junk, thump through it and
weed out all the left over spam -- time to get a coffee, if you didn't
do that in a while, say, over night.
Client side filtering; download spam, process spam locally. Server side
filtering; start your MUA and enjoy all the nasty buggers never even hit
your Inbox.
There is one piece to the puzzle, I don't understand how exactly you
want to use it -- procmail. That doesn't fit in the general picture of
client side filtering...
> course, my own first thought when I started thinking about this was
> precisely what you just suggested. The problem with that is that I am
> with one of the big commercial ISPs (Comcast), and I don't have a
> static IP address, so I can't point to my router from any arbitrary
> machine on the internet. I do believe that I can do some kind of
> dynamic DNS with my router. Then I can probably pass incoming
Yes, dyndns.org for example. Your router is likely to support it, if it
supports any such service.
> connections to port (whatever for imap) through to my home machine.
> At some point, it just seems that the "right" solution is too much
> hassle, so I was just looking for a lower energy solution.
IMAP*S*, please. ;) Or maybe even better, an openvpn tunnel. Access
your local data the way you want, while keeping a single, encrypted
connection. But yeah, that might be more work, and aways can be added
later.
> I could completely believe that the solution I came up with might have
> some fatal flaw, but I thought I would give it a shot first . . .
One possible scenario I've been using a couple of times already:
fetchmail to periodically poll mail every few minutes. Ideally a local
SMTP server like postfix. procmail, which you already mentioned, feeding
the mail to spamc and delivering spam to a dedicated folder. An IMAP
server like dovecot.
Yes, that might sound like lots of work, but actually should be rather
easy and quick to setup. On the other hand, there *are* downsides to
multiple SA installations, actually handling a single low-volume stream.
Two immediately coming to mind, there sure are more.
* You got two different Bayes databases. Thus, it will be harder to
reach the threshold of incoming ham and spam before it will start to
work. More training necessary. And they will produce different results.
Especially if one of them is likely to see some particular messages, the
other might never see. Think some stuff you generally get on weekends
only. Or during the day, weekdays.
* DNS. In addition to set-up and maintain two SA installations, you will
need local caching (non-forwarding) DNS servers. Why is that? You simply
cannot use your ISPs DNS, since it will not return hits for the most
valuable blacklists.
Personally, I would go the single-site route, bite the bullet and set up
my own IMAP server. No wait, I did. ;)
Added benefit: Virtually no network delay whatsoever from home. Plus,
you got access to the IMAP server's storage, so training bayes becomes a
breeze.
Even if you really prefer running SA client-side, IMHO there is a far
better solution than multiple SA installations. Namely the spamc -d
option, of using a common spamd (and thus fully configured and
maintained SA). Satellite systems then only need spamc installed, not SA
itself.
guenther
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
