Mailinglist Archive: opensuse (2831 mails)

["jdow" <jdow@xxxxxxxxxxxxx>]

From: "Anders Johansson" <andjoh@xxxxxxxxxx>

> On Thursday 20 July 2006 02:42, jdow wrote:

> I didn't consider spam filtering, that should be done on the external machine, 
> normally

I've been doing this since SpamAssassin 2.3x days. It works. The
brief digression that involved PostFix (on a Mandrake build just
before they became Mandrival) was at best a qualified success. The
spam filtering is done before it gets to the inboxes due to the
emailer I am using. (I make my money with Windows development for
broadcast video uses. I telecommute. I'm constantly shipping builds
to the customer. It's easier if I don't have to change machines. The
Linux machines enter for security and some fun. But it HAS lead to
a small inconsequential patch to partition and filesystem handling
in the Linux kernel. {^_-} Winks and pats self on back, too.)

> > Fetchmail grabs the email from the each user's accounts on the ISP.
> > As it happens I have it setup for two savvy people with several
> > email accounts each. We run fetchmail via a little script in each
> > user's directory with individual .fetchmailrc files. This took place
> > way back in time when this seemed to function better than the global
> > fetchmailrc file approach. YMMV. I simply have not fixed what is not
> > broken. The important .fetchmailrc for this is simply:
> >
> > defaults mda "/usr/bin/procmail -d <user>"
> >
> > Replace <user> with the user ID, of course.
>
> and no config at all for server address, username on the remote server, 
> password??? There will be at least one more line, I'm sure.

The rest is standard fetchmail boilerplate. The line I quoted was the
key for bypassing SendMail/QMail/EXIM/PostFix/whathaveyou. (<cough> it
also avoids amavisd-new, too. I've watched too many people have problems
getting it setup. What I have works. I'm disinclined to fix it. {^_-})

> > Procmail can deliver the email to the /var/spool/mail/<user> file
> > directly. I place necessary lines for running SpamAssassin (and black
> > holing certain email pests.)
> >
> > Once the email is in the spool file reception is done. Now I have to
> > send it to the user. For that I simply use DoveCot. Normally you'd
> > simply fire it up and tell it where the spool files live and go. I
> > have a somewhat more complex configuration for automating user
> > interactive Bayes training for SpamAssassin. Normal mail is fetched
> > via POP3S directly from the spool file. Then there are per user mail
> > storage directories for IMAPS access to the spam training mail folders.
> >
> > Note that there is no need to involve more than simply fetchmail,
> > procmail, and dovecot for the simplest configuration. I use this simply
> > because it allows far simpler access to per user Bayes and rules for
> > SpamAssassin. The postfix/cyrus route proved very difficult to build
> > into this required configuration.
> >
> > If the original query was from a fellow who needed to pull email from
> > an ISP and then distribute it accessibly on the Internet note that this
> > is what I am doing via useage of the POP3S and IMAPS ports. I let them
> > be open on the firewall. I do not allow raw POP3 or raw IMAP access
> > outside the internal network.
>
> This is of course a valid and usable setup, but I don't think it's that much 
> less work than my suggestion
>
> And the less I have to do with procmail, the better

It is arcane. However, since I sit right next to the server I played some
procmail games. When I receive customer email or email from my partner it
plays different sound files to alert me. It also proved useful before the
PerMsgStatus.pm bug which caused (partially) scored but unmarked missed
spam in my mailbox. I simply ran it twice if the first time failed. There
is an absurd kind of logic to the way you can do that with procmail. I can
also easily skip spam processing for email from the spamassassin mailing
lists. That is QUITE helpful. My partner writes some of the SARE rules
and I also do some SA hacking.

If I was doing simple mail reception I'd still go global fetchmail,
procmail with a REALLY simple boilerplate to deliver the mail, and
DoveCot. It'd still take me more than 4 minutes. I have a small case
of RTFMitis, I tend to read manuals then do when I can. I realize this
detracts from my reputation. But, gee, I can't help it. And I can't 
find any 12 step programs....

{^_-}    Joanne

--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx