> First, thanks all that sent me help to get a test message to > work. I was > able to successfully get SA to trigger. > > It appears that SA is only currently working on my local mail accounts > and not the alias/forward emails. > > So what I have is an Hosting provider which hosts my domain, that I > setup alias emails for myself and others which then forwards > the emails > onto their local ISP providers email account. > > So is SA not going to work for me? Or is there an option that > I need to > talk to for my hosting provider to get it to work on forwarders?
Whether SpamAssassin runs for a message is probably based on the MTA rules. Some providers screen only local accounts, while others screen everything. The difficulty may come in which MTA and SA integration method. I'll give you an example: If you're running CommuniGate Pro as the MTA and using CGPSA, one of the two main integration apps for CommuniGate Pro, you basically can't scan forwarders if you enable user or domain-based settings. The reason for this is that the destination address is resolved prior to scanning the message. So you'd have to apply global settings to messages that weren't destined for local accounts since they resolve to external domains like AOL, HotMail, Yahoo, or whatever. In addition to that there are probably other customers whose addresses would resolve to those domains, so they can't simply allow you to determine what gets scanned and which rules are applied since it would affect others. I'm sure something could be done to implement per-user settings based on the hosted address, but it would require programming changes to CGPSA. So, I don't know which MTA or integration app your provider runs. But this would be something that you'd have to discuss with them. HTH, Bret
