My personal guess is that removing the tcp.smtp will be fine but I have
not tested. I know personally Tonix so I have been using his script for
many years now.
Remo
On 9/14/17 11:06 AM, Eric Broch wrote:
>
> No, haven't gotten to that yet. Any suggestions?
>
>
> On 9/14/2017 11:44 AM, Remo Matt
No, haven't gotten to that yet. Any suggestions?
On 9/14/2017 11:44 AM, Remo Mattei wrote:
Hi Eric,
did you remove the info in the (/etc/tcprules.d/tcp.smtp) for the smtp?
Thanks,
Remo
On 9/14/17 10:19 AM, Eric Broch wrote:
Rajesh,
I got this working, here's how:
1) # wget https://www.spa
Hi Eric,
did you remove the info in the (/etc/tcprules.d/tcp.smtp) for the smtp?
Thanks,
Remo
On 9/14/17 10:19 AM, Eric Broch wrote:
>
> Rajesh,
>
> I got this working, here's how:
>
> 1) # wget https://www.spamdyke.org/releases/spamdyke-5.0.1.tgz
>
> 2) # tar zxvf spamdyke-5.0.1.tgz
>
> 3) # cd
Rajesh,
I got this working, here's how:
1) # wget https://www.spamdyke.org/releases/spamdyke-5.0.1.tgz
2) # tar zxvf spamdyke-5.0.1.tgz
3) # cd spamdyke-5.0.1/spamdyke-qrv
4) # VALIAS_PATH=/home/vpopmail/bin/valias
VUSERINFO_PATH=/home/vpopmail/bin/vuserinfo ./configure
--with-vpopmail-supp
thanks eric
rajesh
- Original Message -
From: Eric Broch [mailto:ebr...@whitehorsetc.com]
To: qmailtoaster-list@qmailtoaster.com
Sent: Thu, 14 Sep 2017 00:04:55 -0600
Subject:
It looks like you'll need to download the spamdyke source and compile it
as follows:
1) ./configure --with-vpo
It looks like you'll need to download the spamdyke source and compile it
as follows:
1) ./configure --with-vpopmail-support VALIAS_PATH=/path/to/valias
VUSERINFO_PATH=/path/to/vuserinfo
2) make
3) make install
4) vi /etc/spamdyke/spamdyke.conf (Add)
recipient-validation-command=/path/to/sp
Hi Rajesh,
This may be what you're looking for.
https://www.spamdyke.org/documentation/README_spamdyke_qrv.html
Although I don't know how to implement it.
Eric
On 9/13/2017 9:59 PM, Rajesh M wrote:
Hi
noted that spamdyke is checking port 25 for the number of emails in one
session, mx dns,
Hi
noted that spamdyke is checking port 25 for the number of emails in one
session, mx dns, etc
lot of duplicate functions between spamdyke and chkusr
is there any reason to continue keeping chkusr ?
can spamdyke also handle cases when emails from outside are sent to non-exiting
recipients ?