> From: Eric Robibaro <[EMAIL PROTECTED]>
>
> Answers/questions inline
>
> --On February 4, 2003 17:52 -0800 John Rudd <[EMAIL PROTECTED]> wrote:
>
> >
> > 1) So, if I'm not going to put user spools in AFS space, for the reasons
> > already discussed, are there any problem with putting them in NFS
> > space?
> And the nfs platform you choose should be
> rock-solid... Perhaps someone on the list has a recommendation? I've heard
> good noise about freebsd and tru64unix in this particular case, while some
> linux kernels(the older ones) had headaches in store...
We'd probably end up with either Solaris (8 or 9), or a NetApp.
> >
> > 2) Has anyone set up a means of using SpamAssassin and Sophos SAVI with
> > Courier? I currently use them via MailScanner and sendmail. It would
> > be particularly nice if the setup could allow me to have the headers
> > look like the same headers I'm using under Mailscanner (so that my users
> > don't have to re-write their procmail, eudora, netscape, and mail
> > sorting/filtering rules).
> Spamassasin adds its own headers
Well, yes, and no. SpamAssassin has it's own headers, but MailScanner
doesn't directly use them.
For example, in our test environment, he headers look like this:
X-UCSC-TEST-MailScanner: Found to be clean
X-UCSC-TEST-MailScanner-SpamCheck: not spam, SpamAssassin (score=1,
required 5, KNOWN_MAILING_LIST, SPAM_PHRASE_03_05,
USER_AGENT_OUTLOOK)
X-UCSC-TEST-MailScanner-SpamScore: s
The first header there is the virus scanner output, the second is the
result of all of MailScanner's spam checks (blackholes and SpamAssassin
both, but we only use Spam Assassin; we could also use blackhole checking
via Spam Assassin, but we don't use it there either). The last one is
similar to one of the headers SpamAssassin generates (well, so is the
reporrt part of the second one, but still), only using s'es instead of
*'s (easier to write filters around characters that aren't also meta-
characters).
TEST will change to "CATS" (our central IT group) once this machine goes
into production. The first header, with CATS instead of TEST, already
shows up on the production servers, but we don't have spam marking in
production yet. But, the filters for that are already being written
by the user support group, so the names and formats of the headers are
already written in stone. That's why I'd like to be able to keep the same
header names/formats. I suppose one option is "spamc | sed" or something.
Though, right now, that's all running on machines seperate from our POP
server. We have two SMTP servers and a POP server. If we were to just put
courier on the POP+IMAP servers, and leave sendmail+mailscanner on the
SMTP servers, we wouldn't have to worry about this. But, then we don't get
the full benefit of courier mailing lists and stuff (since that expansion
happens on the SMTP servers). So, I dunno.
> > 4) Similar question to #3, but with MMDF folders. While I've got mbox
> > folders on my home mail server, the campus POP server, which I will also
> > probably convert in the near future, uses MMDF format, and thus doesn't
> > have the unix "From " envelope. It would be a more complex task to have
> > to create an envelope "From " header for each message in each folder.
> I believe the c-client library understands mmdf and may be of help,
> otherwise, I hope someone knows more about this format and pipes in...
Hm. yeah. Though, I wasn't clear about this part: the POP server isn't
running UW-IMAP/POP. It's running qpopper. But I suppose getting UW's
tools and stuff installed on that machine wouldn't be a big deal.
Or I could try munging something via fetchmail.
> I hope I have been of help to you...
Yes, both responses so far have been very helpful. Thanks :-)
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
