This is indeed so, you will need to hack the proram that calls spamd to supply the correct username (or hack spamd). Since there is no way spamd can know the 'real' adress this is delevered too.
I did a little hack on qmail-scanner for that purpose (really easy, one SQL-Statement and case is closed). Greetz Kobe ----- Original Message ----- From: "Lindsey Simon" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, November 27, 2002 12:13 AM Subject: [SAtalk] Aliases and SQL configuration > We use SpamAssassin here at our newspaper. Many editors have email > aliases like [EMAIL PROTECTED] which points to > [EMAIL PROTECTED] and they use [EMAIL PROTECTED] > for listserves etc.. The problem is that their configuration using > the php/mySQL setup only configures things for username foo. So > they think they've whitelisted an address, but it gets delivered to > them based on the default configs and not their personalized one. > > Is there any way to tell spamassassin to map to the proper username? > Or maybe some kind of mapfile? Or configuration option? > > I wonder if anyone else has encountered this. > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Get the new Palm Tungsten T > handheld. Power & Color in a compact size! > http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en > _______________________________________________ > Spamassassin-talk mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/spamassassin-talk > ------------------------------------------------------- This SF.net email is sponsored by: Get the new Palm Tungsten T handheld. Power & Color in a compact size! http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0002en _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
