Thank you for the link, Joe. I think that, alone, proves that preline is not necessary. Reading up on it, it seems to set headers that would only make sense to courierdeliver. I don't know, maybe lots of folks are using courierdeliver, but isn't that what vdelivermail is for?
> -----Original Message----- > From: Joe Young [mailto:[EMAIL PROTECTED] > Sent: Tuesday, July 08, 2003 3:41 PM > To: Benjamin Tomhave > Subject: Re: [qmailadmin] Help with code! SpamAssassin integration > > > Joseph Young > Involved.com > System Admin > > > The > | /var/qmail/bin/preline /usr/local/bin/maildrop > /home/vpopmail/etc/mailfilter > is the default that qmailadmin uses. The preline command info is found at > > http://www.courier-mta.org/preline.html > > > joe > > > ----- Original Message ----- > From: "Benjamin Tomhave" <[EMAIL PROTECTED]> > To: "Joe Young" <[EMAIL PROTECTED]> > Cc: <[EMAIL PROTECTED]> > Sent: Tuesday, July 08, 2003 12:51 PM > Subject: RE: [qmailadmin] Help with code! SpamAssassin integration > > > Just curious, but is the "preline" needed? I'm just using "| maildrop > mailfilter" in my .qmail-default file today and it seems to work > just fine. > > > -----Original Message----- > > From: Joe Young [mailto:[EMAIL PROTECTED] > > Sent: Tuesday, July 08, 2003 1:36 PM > > To: Derek Watson; [EMAIL PROTECTED] > > Subject: Re: [qmailadmin] Help with code! SpamAssassin integration > > > > > > Joseph Young > > Involved.com > > System Admin > > > > The patch that I was creating will not be finished as that > > QmailAdmin 1.0.22 > > has the code I needed. > > it adds to .qmail-default the "preline maildrop mailfilter" bit. > > > > > > joe > > > > > > > > > > > > > > ----- Original Message ----- > > From: "Derek Watson" <[EMAIL PROTECTED]> > > To: <[EMAIL PROTECTED]> > > Sent: Tuesday, July 08, 2003 8:29 AM > > Subject: [qmailadmin] Help with code! SpamAssassin integration > > > > > > > > Hello everybody -- I would like to pick up the pieces of this patch > > project and make it happen (if possible). What is the furthest anybody > > has come with this? > > > > Just to recap: > > > > The community wants SpamAssassin integration in QmailAdmin. We need the > > ability to apply SpamAssassin processing to incoming email on a > > per-domain or per-account basis. Forwards and aliases should work, > > where applicable. This means mangling the .qmail-default file (per > > domain) and individual users .qmail files (per user). The system should > > also support enabling/disabling this feature via a .qmailadmin-limits > > directive and provide some way for each admin to specify the path to the > > filter. > > > > Please respond ASAP on this if you have any information as I'd like to > > get working today. > > > > Derek > > > > PS -- what are the chances of this making it into the main QmailAdmin > > tree if success is achieved? > > > > Joseph Young wrote: > > > > -------------------------- > > > > I have qmailadmin to show a check box that is checked if there is the > > line,"enable_spamassassin", to .qmailadmin-limits. So the next > step is to > > have in user.c to add the line,"|/var/qmail/bin/preline > > /usr/local/bin/maildrop /home/vpopmail/etc/mailfilter", in the > > user's .qmail > > when it when user selects it. > > > > I need help in writing the code to modusergo() in user.c to check > > .qmail and > > to write to .qmail. > > > > > > >
