On 2/16/2012 6:18 PM, email builder wrote: >> >>> Letting trusted_networks empty is not generally a good idea. In >>> particular, if your SA server is using a private IP, it will default to >>> trusting too much. Specify your local networks in trusted_networks and >>> see if that helps your problem. >>> >>> Leaving trusted_networks empty does not mean "trust nothing"; it >>> >>> means "let SA figure out what to trust". >> Makes sense, especially if my hunch about the "relayed through one or >> more trusted relays, cannot use header-based Envelope-From, skipping" >> part of the debug output I just sent to this list is on track. >> >> Is there a way to set trusted_networks on the command line of the >> spamassassin command just for testing? > This didn't work: > > spamassassin -D --cf='trusted_networks 127.0.0.1' -t example_email_no_spf > 2>&1 | grep -i SPF > > All my local handoffs are to localhost [127.0.0.1] so I wouldn't know what > else to use (it's an all-in-one single server simple system)
I'm not sure if that format will work or not. If your normal process uses Amavisd_new or spamd, you can just edit the config files for your tests. Changes to the config files will not affect the daemons until they are restarted. At some point, there has to be an external IP to accept mail from the Internet. That is what you need to add to trusted_networks. 127.0.0.1 should be automatically trusted. The simplest solution (unless you don't trust your network for some reason) is to add all of the IP blocks that you control to trusted_networks. -- Bowie
