RE: updates.spamassassin.org not resolving?

2022-02-06 Thread Marc
> >> > >> 6.4.3.updates.spamassassin.org. 3600 IN CNAME > >> 3.3.3.updates.spamassassin.org. > >> 3.3.3.updates.spamassassin.org. 3600 IN TXT "1897787" > >> > >> the "updates.spamassassin.org" itself has no data. > > On 06.02.22 14:27, Marc wrote: > >Oh ok, I did the dig because I got this > >

RE: getting spamass-milter to work with remote spamd (on CentOS8)

2022-02-06 Thread Marc
> > ~]# spamass-milter -h > > spamass-milter: invalid option -- 'h' > > spamass-milter - Version 0.4.0 > > SpamAssassin Sendmail Milter Plugin > > Usage: spamass-milter -p socket [-b|-B bucket] [-d xx[,yy...]] [-D host] > > [-e defaultdomain] [-f] [-i networks] [-m] [-M] > >

Re: updates.spamassassin.org not resolving?

2022-02-06 Thread Matus UHLAR - fantomas
>[@svr ~]# dig +short @8.8.8.8 updates.spamassassin.org it resolves, but it does not resolve to A record dig searches for by default: 6.4.3.updates.spamassassin.org. 3600 IN CNAME 3.3.3.updates.spamassassin.org. 3.3.3.updates.spamassassin.org. 3600 IN TXT "1897787" the "updates.spamassassin

Re: getting spamass-milter to work with remote spamd (on CentOS8)

2022-02-06 Thread Greg Troxel
Marc writes: >> On 06.02.22 14:02, Marc wrote: >> >Thanks! Got it to work with this: >> >EXTRA_FLAGS=" -D xx.xxx.xxx -- -p 34219" >> >> the man page for spamass-milter says: >> >> -D host >> Connects to a remote spamd server on host, instead of using >> one >>

RE: updates.spamassassin.org not resolving?

2022-02-06 Thread Marc
> >[@svr ~]# dig +short @8.8.8.8 updates.spamassassin.org > > it resolves, but it does not resolve to A record dig searches for by > default: > > 6.4.3.updates.spamassassin.org. 3600 IN CNAME > 3.3.3.updates.spamassassin.org. > 3.3.3.updates.spamassassin.org. 3600 IN TXT "1897787" > > the "u

RE: getting spamass-milter to work with remote spamd (on CentOS8)

2022-02-06 Thread Marc
> On 06.02.22 14:02, Marc wrote: > >Thanks! Got it to work with this: > >EXTRA_FLAGS=" -D xx.xxx.xxx -- -p 34219" > > the man page for spamass-milter says: > > -D host > Connects to a remote spamd server on host, instead of using > one > on localhost. This opti

Re: updates.spamassassin.org not resolving?

2022-02-06 Thread Matus UHLAR - fantomas
On 06.02.22 14:17, Marc wrote: [@svr ~]# dig +short @8.8.8.8 updates.spamassassin.org it resolves, but it does not resolve to A record dig searches for by default: 6.4.3.updates.spamassassin.org. 3600 IN CNAME 3.3.3.updates.spamassassin.org. 3.3.3.updates.spamassassin.org. 3600 IN TXT "1

Re: getting spamass-milter to work with remote spamd (on CentOS8)

2022-02-06 Thread Matus UHLAR - fantomas
Usually a SpamAssassin milter can accept additional arguments after ‘--’ that it will pass to spamc. So: spamassassin-milter ...other args... -- -d 192.168.10.243 -p 34219 Or configure the connection in /etc/spamassassin/spamc.conf, that works too. On 06.02.22 14:02, Marc wrote: Thanks! Got i

updates.spamassassin.org not resolving?

2022-02-06 Thread Marc
[@svr ~]# dig +short @8.8.8.8 updates.spamassassin.org [@svr ~]#

RE: getting spamass-milter to work with remote spamd (on CentOS8)

2022-02-06 Thread Marc
> Usually a SpamAssassin milter can accept additional arguments after ‘--’ > that it will pass to spamc. So: > > spamassassin-milter ...other args... -- -d 192.168.10.243 -p 34219 > > Or configure the connection in /etc/spamassassin/spamc.conf, that works > too. Thanks! Got it to work with this:

Re: getting spamass-milter to work with remote spamd (on CentOS8)

2022-02-06 Thread David Bürgin
Marc: > I have problems configuring the spamass-milter to connect to the remote > spamd. I am constantly getting > > getaddrinfo(192.168.10.243:34219) failed: Name or service not known > could not resolve any hosts (192.168.10.243:34219): no such host > > Nothing of these seem to work > -D 192.1

getting spamass-milter to work with remote spamd (on CentOS8)

2022-02-06 Thread Marc
I have problems configuring the spamass-milter to connect to the remote spamd. I am constantly getting getaddrinfo(192.168.10.243:34219) failed: Name or service not known could not resolve any hosts (192.168.10.243:34219): no such host Nothing of these seem to work -D 192.168.10.243:34219 inet: