So what is the problem? The way it's setup, I have SquirrelMail running on my webserver so my users can check their mail from anywhere that they have web access. But in this instance, a user was dialed up from Earthlink and her email that she sent using SquirrelMail got tagged as spam because of the Earthlink dialup. What I was wondering was if there was a way to tell SA that any emails that are from the SquirrelMail frontend machine should be whitelisted/trusted even if the user is dialing in from an account known to the RBLs.
Thanks. On Thu, Aug 05, 2004 at 06:20:51AM -0400, Cirelle Enterprises wrote: > Your problem is not squirrelmail > > ----- Original Message ----- > From: "Henry Kwan" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, August 04, 2004 8:18 PM > Subject: Whitelisting or trusting a SquirrelMail frontend... > > > | Hi, > | > | Is there a way to whitelist a SquirrelMail frontend machine? > | > | A recent email got FP tagged as spam even though the user had send the email > | via the SquirrelMail web frontend (with an Earthlink account to access the > | web page). How can I make it so that any email sent via the web frontend > | gets trusted or whitelisted? > | > | I have trusted_networks set to my IP block but that didn't seem to work in > | this case.
