No problem! I appreciate the help over on the QMT list! Michael J. Colvin NorCal Internet Services www.norcalisp.com
> -----Original Message----- > From: [email protected] [mailto:spamdyke-users- > [email protected]] On Behalf Of Eric Shubert > Sent: Wednesday, January 12, 2011 4:38 PM > To: [email protected] > Subject: Re: [spamdyke-users] SpamAssassin not getting Invoked > > You're correct. I didn't read it thoroughly. Sorry. > -- > -Eric 'shubes' > > On 01/12/2011 04:56 PM, Michael Colvin wrote: > >> > > > >> Did you try using Upper Case ALLOW (not shouting)? That's what's shown > > > >> in the documentation. > > > >> > > > >> In any case, I would expect Spamdyke to show some sort of error > if/when > > > >> configuration parameters aren't quite kosher. > > > >> > > > > No, because that's not what I'm seeing in the documentation. Taken from > > here: http://www.spamdyke.org/documentation/README.html#RELAYING > > > > Each line in the access file should use one of the following formats: > > > > remote_i...@remote_ip:ACCESS > > > > remote_i...@=remote_name:ACCESS > > > > REMOTE_IP:ACCESS > > > > REMOTE_NAME:ACCESS > > > > :ACCESS > > > > ... > > > > ACCESS is the permission setting -- either allow or deny. Connections > > are allowed by default (if no match is found). If access is denied, no > > mail is accepted at all, whether relayed or not. > > > > ... > > > > For example, if the remote server's IP address is 11.22.33.44 and its > > rDNS name is mail.example.com, each of the following lines will match, > > allow connections and set several environment variables: > > > > 11.22.33.44:allow,FOOVAR="foovalue",BARVAR=.barvalue.,BAZVAR=-bazvalue- > > > > 11.20-100.33.44:allow,FOOVAR="foovalue",BARVAR=.barvalue.,BAZVAR=- > bazvalue- > > > > 11.22.:allow,FOOVAR="foovalue",BARVAR=.barvalue.,BAZVAR=-bazvalue- > > > > 11.22.33.0/24:allow,FOOVAR="foovalue",BARVAR=.barvalue.,BAZVAR=- > bazvalue- > > > > 11.22.0.0/255.255.0.0:allow,FOOVAR="foovalue",BARVAR=.barvalue.,BAZVAR=- > bazvalue- > > > > > > =mail.example.com:allow,FOOVAR="foovalue",BARVAR=.barvalue.,BAZVAR=- > bazvalue- > > > > > > =.example.com:allow,FOOVAR="foovalue",BARVAR=.barvalue.,BAZVAR=- > bazvalue- > > > > =.com:allow,FOOVAR="foovalue",BARVAR=.barvalue.,BAZVAR=-bazvalue- > > > > :allow,FOOVAR="foovalue",BARVAR=.barvalue.,BAZVAR=-bazvalue- > > > > So, in the docs, it shows "ACCESS" in uppercase, but ACCESS appears to > > me to be a representation of either "allow" or "deny", depending on the > > usage. > > > > The group of examples also show "allow" or "deny" in lowercase, but they > > also show additional information that I don't believe I need in my > > case... Unless I'm misreading something. :-) > > > > Michael J. Colvin > > > > NorCal Internet Services > > > > www.norcalisp.com > > > > > > > > _______________________________________________ > > spamdyke-users mailing list > > [email protected] > > http://www.spamdyke.org/mailman/listinfo/spamdyke-users > > > _______________________________________________ > spamdyke-users mailing list > [email protected] > http://www.spamdyke.org/mailman/listinfo/spamdyke-users _______________________________________________ spamdyke-users mailing list [email protected] http://www.spamdyke.org/mailman/listinfo/spamdyke-users
