Re: [qmailtoaster] Spamdyke and Spamcop - blacklisting

[Gary Bowling]

  
  


Yes, I'm an old guy, so I know it's been around since the 90s.
  But not in as widespread use by "companies" as it is today. Many
  companies in the 90s had onsite microsoft mail servers, or
  sun/unix/linux mail servers  and a lot of the shared hosting was
  used by individuals and casual users, and spammers.


These days many of the small businesses my clients work with
  outsource their mail to hosted exchange or google. I realize a lot
  of spam originates from all the various MS domains and from gmail,
  but I cannot afford to completely block any of those servers. It
  kills my clients as they don't get emails from their customers and
  partners. 



g



On 3/22/2024 10:58 AM, William
  Silverstein wrote:


  

On Fri, March 22, 2024 4:40 am, Gary Bowling wrote:

  




In the spamdyke config, the default is to use spamcop for
blacklisting. I've had a lot of trouble recently with spamcop.   They
keep adding the outlook.com servers to their database. Which   means
every company that uses Microsoft office 365 for mail gets   blocked.
This has caused me a lot of problems as there are a lot   of companies
in the US that use office365 for mail hosting.





I am wondering if in these days we should be blacklisting server   ip
addresses. So many users are on shared services that blocking   entire
servers by ip seems like a bad idea. They also block entire   ip
ranges from hosting providers.


  
  Shared hosting has been around since the 1990s.

That was part of the idea behind blacklisting. That by blocking IP ranges,
it would encourage providers to stop spam because it would cause harm to
more than just the spamming customer.





  


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Spamdyke and Spamcop

[Leonardo]

I had the same problem with office/outlook senders.
I had to whitelist a big prefix (40.107.0.0/16) in 
/etc/spamdyke/whitelist_ip file, because I had tried whitelist_senders 
before and it wont work.


Regards



Em 22/03/2024 08:40, Gary Bowling escreveu:



In the spamdyke config, the default is to use spamcop for 
blacklisting. I've had a lot of trouble recently with spamcop. They 
keep adding the outlook.com servers to their database. Which means 
every company that uses Microsoft office 365 for mail gets blocked. 
This has caused me a lot of problems as there are a lot of companies 
in the US that use office365 for mail hosting.



I am wondering if in these days we should be blacklisting server ip 
addresses. So many users are on shared services that blocking entire 
servers by ip seems like a bad idea. They also block entire ip ranges 
from hosting providers.



I'm thinking of removing all the blacklisting services in spamdyke. 
How do you guys handle this?



Thanks, Gary
- 
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com 
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com 

Re: [qmailtoaster] Spamdyke and Spamcop - blacklisting

[William Silverstein]

On Fri, March 22, 2024 4:40 am, Gary Bowling wrote:
>
>
>
>
> In the spamdyke config, the default is to use spamcop for
> blacklisting. I've had a lot of trouble recently with spamcop.   They
> keep adding the outlook.com servers to their database. Which   means
> every company that uses Microsoft office 365 for mail gets   blocked.
> This has caused me a lot of problems as there are a lot   of companies
> in the US that use office365 for mail hosting.
>
>
>
>
>
> I am wondering if in these days we should be blacklisting server   ip
> addresses. So many users are on shared services that blocking   entire
> servers by ip seems like a bad idea. They also block entire   ip
> ranges from hosting providers.
>
Shared hosting has been around since the 1990s.

That was part of the idea behind blacklisting. That by blocking IP ranges,
it would encourage providers to stop spam because it would cause harm to
more than just the spamming customer.



-- 
William G. Silverstein, Esq.
Litigation Counsel
Licensed in California.




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] Spamdyke and Spamcop

[Gary Bowling]

  
  


In the spamdyke config, the default is to use spamcop for
  blacklisting. I've had a lot of trouble recently with spamcop.
  They keep adding the outlook.com servers to their database. Which
  means every company that uses Microsoft office 365 for mail gets
  blocked. This has caused me a lot of problems as there are a lot
  of companies in the US that use office365 for mail hosting. 



I am wondering if in these days we should be blacklisting server
  ip addresses. So many users are on shared services that blocking
  entire servers by ip seems like a bad idea. They also block entire
  ip ranges from hosting providers.



I'm thinking of removing all the blacklisting services in
  spamdyke. How do you guys handle this? 



Thanks, Gary

  


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke spf block - whitelist not working

[Leonardo Porto]

No worry.

I tried the exact senders address instead the domain but apparently did 
not work, I will give a try on @domain and the dnswl.org whitelist.



Em 24/07/2023 10:49, Eric Broch escreveu:


Sorry,

This is what I meant (below). You can use a domain name instead of IP 
to white list. If I remember correctly and entry would be 
@somedomain.com.



Whitelisting Senders and Recipients


  |recipient-whitelist-entry|
  |recipient-whitelist-file|
  |sender-whitelist-entry|
  |sender-whitelist-file|

Sometimes, adding IP addresses and reverse DNS names to whitelist 
files is not enough to satisfy some users. Either they continue to 
receive mail from unexpected places or they just think spamdyke is 
blocking their email. In those cases, a last resort can be to 
whitelist the sender or recipient address.


*NOTE: Using these features is a bad idea!*Sender addresses 
are_very_easy to forge; this is why spam is so hard to block. 
Recipient addresses are obviously already known to the spammers; this 
is why spam is delivered. Whitelisting any addresses this 
way_will_allow spam to get through.


To whitelist a sender or recipient address, 
the|sender-whitelist-entry|or|recipient-whitelist-entry|option should 
be used, respectively. The entries can use the same formats as those 
for|sender-blacklist-entry|and|recipient-blacklist-entry|; 
seeRejecting Recipients 
for 
details.


Whitelist entries can be placed in files and referenced 
with|sender-whitelist-file|or|recipient-whitelist-file|. This is more 
efficient for more than a few entries.




On 7/24/2023 7:39 AM, Leonardo Porto wrote:


Hi Eric,

Here is my spamdyke.conf:

dns-blacklist-entry=b.barracudacentral.org
dns-blacklist-entry=bl.spamcop.net
dns-blacklist-entry=dnsbl.spfbl.net
graylist-dir=/var/spamdyke/graylist
graylist-level=none
graylist-max-secs=2678400
graylist-min-secs=180
greeting-delay-secs=6
header-blacklist-entry=From:*>,*<*
idle-timeout-secs=60
ip-blacklist-file=/etc/spamdyke/blacklist_ip
ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords
ip-in-rdns-keyword-whitelist-file=/etc/spamdyke/whitelist_keywords
ip-whitelist-file=/etc/spamdyke/whitelist_ip
qmail-rcpthosts-file=/var/qmail/control/rcpthosts
log-level=info
max-recipients=50
rdns-blacklist-file=/etc/spamdyke/blacklist_rdns
rdns-whitelist-file=/etc/spamdyke/whitelist_rdns
recipient-blacklist-file=/etc/spamdyke/blacklist_recipients
recipient-whitelist-file=/etc/spamdyke/whitelist_recipients
reject-empty-rdns
reject-sender=no-mx
reject-unresolvable-rdns
sender-blacklist-file=/etc/spamdyke/blacklist_senders
sender-whitelist-file=/etc/spamdyke/whitelist_senders
tls-certificate-file=/var/qmail/control/servercert.pem
tls-level=smtp

Despite that configuration I don't use graylists, 
black/white-keywords, black/white-rdns, black/white-recipients or 
black/white-senders files, I only use whitelist_ip file and those 
three blacklists at the top (barracuda, spamcop and spfbl).


I may try this dns-whitelist, do you know and recommend any list?



Em 24/07/2023 10:10, Eric Broch escreveu:


Leonardo,

Did you see the option to block DNS? Or did you try this?


DNS Whitelists


  |dns-whitelist-entry|
  |dns-whitelist-file|
  |rhs-whitelist-entry|
  |rhs-whitelist-file|

spamdyke has the ability to consult DNS whitelists and allow 
connections from hosts or senders who match entries on them. DNS 
whitelists are essentially DNS RBLs and DNS RHSBLs that list allowed 
IP addresses and domain names instead of blocked ones. All of the 
same cautionary statements apply to DNS whitelists as to DNS 
blacklists. SeeDNS RBLs 
andDNS 
RHSBLs 
for 
details.


To use a DNS Realtime Whitelist (the opposite of a DNS RBL), the 
option|dns-whitelist-entry|should be given. To use a DNS 
Righthand-side Whitelist, the option|rhs-whitelist-entry|should be 
given. By default, spamdyke does not use a DNS whitelist. If either 
option is given multiple times, each list will be consulted before 
the connection is blocked.


If more than a few lists are given, 
the|dns-whitelist-file|or|rhs-whitelist-file|options may be used to 
provide the lists in files.


*NOTE: Checking DNS whitelists can impose a serious performance 
penalty. Using more than three DNS whitelists is not recommended.*


*
*

*
*

On 7/24/2023 6:23 AM, Leonardo Porto wrote:


Hello there,

My Toaster is blocking a customer domain because they are sending 
messages from a Google server that is not allowed in their SPF policy:


Jul 21 10:28:45 app1 spamdyke[24853]: DENIED_OTHER from: 
per...@jeduca.org.br to: user@mydomain origin_ip: 209.85.215.172 
origin_rdns: mail-pg1-f172.google.com auth: (unknown) encryption: 
TLS reason: 

Re: [qmailtoaster] spamdyke spf block - whitelist not working

[Eric Broch]

Sorry,

This is what I meant (below). You can use a domain name instead of IP to 
white list. If I remember correctly and entry would be @somedomain.com.



   Whitelisting Senders and Recipients


 |recipient-whitelist-entry|
 |recipient-whitelist-file|
 |sender-whitelist-entry|
 |sender-whitelist-file|

Sometimes, adding IP addresses and reverse DNS names to whitelist files 
is not enough to satisfy some users. Either they continue to receive 
mail from unexpected places or they just think spamdyke is blocking 
their email. In those cases, a last resort can be to whitelist the 
sender or recipient address.


*NOTE: Using these features is a bad idea!*Sender addresses 
are_very_easy to forge; this is why spam is so hard to block. Recipient 
addresses are obviously already known to the spammers; this is why spam 
is delivered. Whitelisting any addresses this way_will_allow spam to get 
through.


To whitelist a sender or recipient address, 
the|sender-whitelist-entry|or|recipient-whitelist-entry|option should be 
used, respectively. The entries can use the same formats as those 
for|sender-blacklist-entry|and|recipient-blacklist-entry|; seeRejecting 
Recipients 
for 
details.


Whitelist entries can be placed in files and referenced 
with|sender-whitelist-file|or|recipient-whitelist-file|. This is more 
efficient for more than a few entries.




On 7/24/2023 7:39 AM, Leonardo Porto wrote:


Hi Eric,

Here is my spamdyke.conf:

dns-blacklist-entry=b.barracudacentral.org
dns-blacklist-entry=bl.spamcop.net
dns-blacklist-entry=dnsbl.spfbl.net
graylist-dir=/var/spamdyke/graylist
graylist-level=none
graylist-max-secs=2678400
graylist-min-secs=180
greeting-delay-secs=6
header-blacklist-entry=From:*>,*<*
idle-timeout-secs=60
ip-blacklist-file=/etc/spamdyke/blacklist_ip
ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords
ip-in-rdns-keyword-whitelist-file=/etc/spamdyke/whitelist_keywords
ip-whitelist-file=/etc/spamdyke/whitelist_ip
qmail-rcpthosts-file=/var/qmail/control/rcpthosts
log-level=info
max-recipients=50
rdns-blacklist-file=/etc/spamdyke/blacklist_rdns
rdns-whitelist-file=/etc/spamdyke/whitelist_rdns
recipient-blacklist-file=/etc/spamdyke/blacklist_recipients
recipient-whitelist-file=/etc/spamdyke/whitelist_recipients
reject-empty-rdns
reject-sender=no-mx
reject-unresolvable-rdns
sender-blacklist-file=/etc/spamdyke/blacklist_senders
sender-whitelist-file=/etc/spamdyke/whitelist_senders
tls-certificate-file=/var/qmail/control/servercert.pem
tls-level=smtp

Despite that configuration I don't use graylists, 
black/white-keywords, black/white-rdns, black/white-recipients or 
black/white-senders files, I only use whitelist_ip file and those 
three blacklists at the top (barracuda, spamcop and spfbl).


I may try this dns-whitelist, do you know and recommend any list?



Em 24/07/2023 10:10, Eric Broch escreveu:


Leonardo,

Did you see the option to block DNS? Or did you try this?


DNS Whitelists


  |dns-whitelist-entry|
  |dns-whitelist-file|
  |rhs-whitelist-entry|
  |rhs-whitelist-file|

spamdyke has the ability to consult DNS whitelists and allow 
connections from hosts or senders who match entries on them. DNS 
whitelists are essentially DNS RBLs and DNS RHSBLs that list allowed 
IP addresses and domain names instead of blocked ones. All of the 
same cautionary statements apply to DNS whitelists as to DNS 
blacklists. SeeDNS RBLs 
andDNS 
RHSBLs 
for details.


To use a DNS Realtime Whitelist (the opposite of a DNS RBL), the 
option|dns-whitelist-entry|should be given. To use a DNS 
Righthand-side Whitelist, the option|rhs-whitelist-entry|should be 
given. By default, spamdyke does not use a DNS whitelist. If either 
option is given multiple times, each list will be consulted before 
the connection is blocked.


If more than a few lists are given, 
the|dns-whitelist-file|or|rhs-whitelist-file|options may be used to 
provide the lists in files.


*NOTE: Checking DNS whitelists can impose a serious performance 
penalty. Using more than three DNS whitelists is not recommended.*


*
*

*
*

On 7/24/2023 6:23 AM, Leonardo Porto wrote:


Hello there,

My Toaster is blocking a customer domain because they are sending 
messages from a Google server that is not allowed in their SPF policy:


Jul 21 10:28:45 app1 spamdyke[24853]: DENIED_OTHER from: 
per...@jeduca.org.br to: user@mydomain origin_ip: 209.85.215.172 
origin_rdns: mail-pg1-f172.google.com auth: (unknown) encryption: 
TLS reason: 
550_See_http://spf.pobox.com/why.html?sender=person%40jeduca.org.br=209.85.215.172=myserver_(#5.7.1)


As you can see at their SPF checking:

https://www.spf-record.com/spf-lookup/jeduca.org.br?ip=209.85.215.172

Everytime they send a messagem it comes from a diverse IP so I tried 
to 

Re: [qmailtoaster] spamdyke spf block - whitelist not working

[Leonardo Porto]

Hi Eric,

Here is my spamdyke.conf:

dns-blacklist-entry=b.barracudacentral.org
dns-blacklist-entry=bl.spamcop.net
dns-blacklist-entry=dnsbl.spfbl.net
graylist-dir=/var/spamdyke/graylist
graylist-level=none
graylist-max-secs=2678400
graylist-min-secs=180
greeting-delay-secs=6
header-blacklist-entry=From:*>,*<*
idle-timeout-secs=60
ip-blacklist-file=/etc/spamdyke/blacklist_ip
ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords
ip-in-rdns-keyword-whitelist-file=/etc/spamdyke/whitelist_keywords
ip-whitelist-file=/etc/spamdyke/whitelist_ip
qmail-rcpthosts-file=/var/qmail/control/rcpthosts
log-level=info
max-recipients=50
rdns-blacklist-file=/etc/spamdyke/blacklist_rdns
rdns-whitelist-file=/etc/spamdyke/whitelist_rdns
recipient-blacklist-file=/etc/spamdyke/blacklist_recipients
recipient-whitelist-file=/etc/spamdyke/whitelist_recipients
reject-empty-rdns
reject-sender=no-mx
reject-unresolvable-rdns
sender-blacklist-file=/etc/spamdyke/blacklist_senders
sender-whitelist-file=/etc/spamdyke/whitelist_senders
tls-certificate-file=/var/qmail/control/servercert.pem
tls-level=smtp

Despite that configuration I don't use graylists, black/white-keywords, 
black/white-rdns, black/white-recipients or black/white-senders files, I 
only use whitelist_ip file and those three blacklists at the top 
(barracuda, spamcop and spfbl).


I may try this dns-whitelist, do you know and recommend any list?



Em 24/07/2023 10:10, Eric Broch escreveu:


Leonardo,

Did you see the option to block DNS? Or did you try this?


DNS Whitelists


  |dns-whitelist-entry|
  |dns-whitelist-file|
  |rhs-whitelist-entry|
  |rhs-whitelist-file|

spamdyke has the ability to consult DNS whitelists and allow 
connections from hosts or senders who match entries on them. DNS 
whitelists are essentially DNS RBLs and DNS RHSBLs that list allowed 
IP addresses and domain names instead of blocked ones. All of the same 
cautionary statements apply to DNS whitelists as to DNS blacklists. 
SeeDNS RBLs 
andDNS 
RHSBLs 
for details.


To use a DNS Realtime Whitelist (the opposite of a DNS RBL), the 
option|dns-whitelist-entry|should be given. To use a DNS 
Righthand-side Whitelist, the option|rhs-whitelist-entry|should be 
given. By default, spamdyke does not use a DNS whitelist. If either 
option is given multiple times, each list will be consulted before the 
connection is blocked.


If more than a few lists are given, 
the|dns-whitelist-file|or|rhs-whitelist-file|options may be used to 
provide the lists in files.


*NOTE: Checking DNS whitelists can impose a serious performance 
penalty. Using more than three DNS whitelists is not recommended.*


*
*

*
*

On 7/24/2023 6:23 AM, Leonardo Porto wrote:


Hello there,

My Toaster is blocking a customer domain because they are sending 
messages from a Google server that is not allowed in their SPF policy:


Jul 21 10:28:45 app1 spamdyke[24853]: DENIED_OTHER from: 
per...@jeduca.org.br to: user@mydomain origin_ip: 209.85.215.172 
origin_rdns: mail-pg1-f172.google.com auth: (unknown) encryption: TLS 
reason: 
550_See_http://spf.pobox.com/why.html?sender=person%40jeduca.org.br=209.85.215.172=myserver_(#5.7.1)


As you can see at their SPF checking:

https://www.spf-record.com/spf-lookup/jeduca.org.br?ip=209.85.215.172

Everytime they send a messagem it comes from a diverse IP so I tried 
to whitelist them at /etc/spamdyke/whitelist_senders putting one 
sender per line but it did not work.


Do you guys have any adivise?

qmail-1.03-3.1.qt.el7.x86_64
spamdyke 5.0.1+TLS+CONFIGTEST+DEBUG
Centos 7

Re: [qmailtoaster] spamdyke spf block - whitelist not working

[Eric Broch]

Leonardo,

Did you see the option to block DNS? Or did you try this?


   DNS Whitelists


 |dns-whitelist-entry|
 |dns-whitelist-file|
 |rhs-whitelist-entry|
 |rhs-whitelist-file|

spamdyke has the ability to consult DNS whitelists and allow connections 
from hosts or senders who match entries on them. DNS whitelists are 
essentially DNS RBLs and DNS RHSBLs that list allowed IP addresses and 
domain names instead of blocked ones. All of the same cautionary 
statements apply to DNS whitelists as to DNS blacklists. SeeDNS RBLs 
andDNS RHSBLs 
for details.


To use a DNS Realtime Whitelist (the opposite of a DNS RBL), the 
option|dns-whitelist-entry|should be given. To use a DNS Righthand-side 
Whitelist, the option|rhs-whitelist-entry|should be given. By default, 
spamdyke does not use a DNS whitelist. If either option is given 
multiple times, each list will be consulted before the connection is 
blocked.


If more than a few lists are given, 
the|dns-whitelist-file|or|rhs-whitelist-file|options may be used to 
provide the lists in files.


*NOTE: Checking DNS whitelists can impose a serious performance penalty. 
Using more than three DNS whitelists is not recommended.*


*
*

*
*

On 7/24/2023 6:23 AM, Leonardo Porto wrote:


Hello there,

My Toaster is blocking a customer domain because they are sending 
messages from a Google server that is not allowed in their SPF policy:


Jul 21 10:28:45 app1 spamdyke[24853]: DENIED_OTHER from: 
per...@jeduca.org.br to: user@mydomain origin_ip: 209.85.215.172 
origin_rdns: mail-pg1-f172.google.com auth: (unknown) encryption: TLS 
reason: 
550_See_http://spf.pobox.com/why.html?sender=person%40jeduca.org.br=209.85.215.172=myserver_(#5.7.1)


As you can see at their SPF checking:

https://www.spf-record.com/spf-lookup/jeduca.org.br?ip=209.85.215.172

Everytime they send a messagem it comes from a diverse IP so I tried 
to whitelist them at /etc/spamdyke/whitelist_senders putting one 
sender per line but it did not work.


Do you guys have any adivise?

qmail-1.03-3.1.qt.el7.x86_64
spamdyke 5.0.1+TLS+CONFIGTEST+DEBUG
Centos 7

[qmailtoaster] spamdyke spf block - whitelist not working

[Leonardo Porto]

Hello there,

My Toaster is blocking a customer domain because they are sending 
messages from a Google server that is not allowed in their SPF policy:


Jul 21 10:28:45 app1 spamdyke[24853]: DENIED_OTHER from: 
per...@jeduca.org.br to: user@mydomain origin_ip: 209.85.215.172 
origin_rdns: mail-pg1-f172.google.com auth: (unknown) encryption: TLS 
reason: 
550_See_http://spf.pobox.com/why.html?sender=person%40jeduca.org.br=209.85.215.172=myserver_(#5.7.1)


As you can see at their SPF checking:

https://www.spf-record.com/spf-lookup/jeduca.org.br?ip=209.85.215.172

Everytime they send a messagem it comes from a diverse IP so I tried to 
whitelist them at /etc/spamdyke/whitelist_senders putting one sender per 
line but it did not work.


Do you guys have any adivise?

qmail-1.03-3.1.qt.el7.x86_64
spamdyke 5.0.1+TLS+CONFIGTEST+DEBUG
Centos 7

Re: [qmailtoaster] Spamdyke RDNS Whitelist

[Gary Bowling]

  
  


So it's the same as for addresses. Ok, I'll give that a try. 



Thanks as always!


Gary

On 1/5/2023 3:15 PM, Eric Broch wrote:


  
  I think it would be
  @domain1.com
  @domain2.com
  @domain3.com
  
  
  On 1/5/2023 12:41 PM, Gary Bowling
wrote:
  
  



I thought the syntax for whitelisting RDNS via a file was to
  make a file with entries as follows:
.domain1.com
  .domain2.com
  .domain3.com


and that would whitelist anything ending in those. So it
  would whitelist and machine whose name is mail1.domain1.com,
  mail2.domain1.com as well as just domain1.com

However, either that's not working right or I have something
  else configure incorrectly. 



Can someone verify the whitelist file syntax? I looked
  through the spamdyke documentation but I don't see any
  examples. All I see is the syntax @domain1.com, but I thought
  that was only for the files with senders and the like. E.g. a
  whitelist for email address syntax. 



Any help would be appreciated. 



Gary

-- 
  
  Gary Bowling
   The Moderns on Spotify 
  

- To
unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
  

  


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Spamdyke RDNS Whitelist

[Remo]

Hi this is what I have on mine

more whitelist_rdns
*.jpmio.com
*@etrade.com
@webmain5.rm.ht

—
Ciao,
Remo

> On Thursday, Jan 05, 2023 at 12:15, Eric Broch  (mailto:ebr...@whitehorsetc.com)> wrote:
>
> I think it would be
>
> @domain1.com
> @domain2.com
> @domain3.com
>
>
>
>
> On 1/5/2023 12:41 PM, Gary Bowling wrote:
> >
> >
> >
> >
> >
> > I thought the syntax for whitelisting RDNS via a file was to make a file 
> > with entries as follows:
> >
> >
> > .domain1.com
> > .domain2.com
> > .domain3.com
> >
> >
> >
> >
> >
> >
> > and that would whitelist anything ending in those. So it would whitelist 
> > and machine whose name is mail1.domain1.com, mail2.domain1.com as well as 
> > just domain1.com
> >
> >
> >
> > However, either that's not working right or I have something else configure 
> > incorrectly.
> >
> >
> >
> >
> >
> >
> >
> > Can someone verify the whitelist file syntax? I looked through the spamdyke 
> > documentation but I don't see any examples. All I see is the syntax 
> > @domain1.com, but I thought that was only for the files with senders and 
> > the like. E.g. a whitelist for email address syntax.
> >
> >
> >
> >
> >
> >
> >
> > Any help would be appreciated.
> >
> >
> >
> >
> >
> >
> >
> > Gary
> >
> >
> > --
> > 
> > Gary Bowling
> > The Moderns on Spotify (https://distrokid.com/hyperfollow/themoderns/bbrs)
> > 
> > - To 
> > unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com 
> > (mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com) For additional 
> > commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com 
> > (mailto:qmailtoaster-list-h...@qmailtoaster.com)

signature.asc
Description: PGP signature

Re: [qmailtoaster] Spamdyke RDNS Whitelist

[Eric Broch]

I think it would be

@domain1.com
@domain2.com
@domain3.com


On 1/5/2023 12:41 PM, Gary Bowling wrote:



I thought the syntax for whitelisting RDNS via a file was to make a 
file with entries as follows:


.domain1.com
.domain2.com
.domain3.com


and that would whitelist anything ending in those. So it would 
whitelist and machine whose name is mail1.domain1.com, 
mail2.domain1.com as well as just domain1.com


However, either that's not working right or I have something else 
configure incorrectly.



Can someone verify the whitelist file syntax? I looked through the 
spamdyke documentation but I don't see any examples. All I see is the 
syntax @domain1.com, but I thought that was only for the files with 
senders and the like. E.g. a whitelist for email address syntax.



Any help would be appreciated.


Gary

--

Gary Bowling
The Moderns on Spotify 

- 
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com 
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com 

[qmailtoaster] Spamdyke RDNS Whitelist

[Gary Bowling]

  
  


I thought the syntax for whitelisting RDNS via a file was to make
  a file with entries as follows:
.domain1.com
  .domain2.com
  .domain3.com


and that would whitelist anything ending in those. So it would
  whitelist and machine whose name is mail1.domain1.com,
  mail2.domain1.com as well as just domain1.com

However, either that's not working right or I have something else
  configure incorrectly. 



Can someone verify the whitelist file syntax? I looked through
  the spamdyke documentation but I don't see any examples. All I see
  is the syntax @domain1.com, but I thought that was only for the
  files with senders and the like. E.g. a whitelist for email
  address syntax. 



Any help would be appreciated. 



Gary

-- 
  
  Gary Bowling
   The
Moderns on Spotify 
  

  


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] Spamdyke RDNS Question

[Gary Bowling]

  
  


In my maillog I get messages like this. The user/domain/ip have
  been changed, but they are all valid:


spamdyke[10162]: DENIED_RDNS_RESOLVE from: fromu...@domain.com
  to: tou...@otherdomain.com origin_ip: 162.xxx.sss.yyy origin_rdns:
  server.domain.com auth: (unknown) encryption: TLS reason: (empty)


These messages get rejected by my server. My understanding is the
  messages are getting rejected by spamdyke due to un-resolvable
  reverse dns (DENIED_RDNS_RESOLVE).


However, further down in the same log message it lists
  "origin_rdns: server.domain.com" which IS the valid
  reverse dns of the domain that sent the message. 



So how can it be rejected by reverse DNS but then show the proper
  reverse DNS?? What am I missing here?


Thanks, GB

-- 

  


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Spamdyke RDNS Question

[Gary Bowling]

  
  


Thanks, that's what I did. There clearly is something I don't
  understand about how denying reverse DNS works.


I whitelisted the IP and not the domain. My logic is. Someone
  from anywhere could try to fake the "domain" so whitelisting that
  might expose the server. The IP address belongs to Comcast
  Business and is likely to never belong to anyone else. So even
  thought that IP might eventually belong to someone else, it's not
  likely to belong to a bad actor.



Gary



On 7/16/2021 11:42 AM, Eric Broch
  wrote:

whitelist
  it in spamdyke
  
  
  On 7/16/2021 8:28 AM, Gary Bowling wrote:
  
  


I have an issue with mail getting rejected from a specific
domain. It's getting rejected due to Spamdyke and RDNS. Here's
the line out of the log.



Jul 16 09:02:41 vm1 spamdyke[32358]: DENIED_RDNS_RESOLVE from:
***@**nd.com to: ***@**ion.com origin_ip: 50.**.**.98
origin_rdns: 50-**-**-98-static.**.comcastbusiness.net auth:
(unknown) encryption: (none) reason: (empty)



From looking at the log. It says spamdyke is blocking it due to
RNDS not resolving. But then on the same line it shows the
"origin_rdns" and it looks like a valid reverse dns to me.



Why is this getting blocked?



Gary


- To
unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com For additional
commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com 
  
-
  
  To unsubscribe, e-mail:
  qmailtoaster-list-unsubscr...@qmailtoaster.com
  
  For additional commands, e-mail:
  qmailtoaster-list-h...@qmailtoaster.com
  
  

  


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Spamdyke RDNS Question

[Eric Broch]

whitelist it in spamdyke

On 7/16/2021 8:28 AM, Gary Bowling wrote:



I have an issue with mail getting rejected from a specific domain. 
It's getting rejected due to Spamdyke and RDNS. Here's the line out of 
the log.



Jul 16 09:02:41 vm1 spamdyke[32358]: DENIED_RDNS_RESOLVE from: 
***@**nd.com to: ***@**ion.com origin_ip: 50.**.**.98 origin_rdns: 
50-**-**-98-static.**.comcastbusiness.net auth: (unknown) encryption: 
(none) reason: (empty)



From looking at the log. It says spamdyke is blocking it due to RNDS 
not resolving. But then on the same line it shows the "origin_rdns" 
and it looks like a valid reverse dns to me.



Why is this getting blocked?


Gary

- 
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com 
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com 


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] Spamdyke RDNS Question

[Gary Bowling]

  
  


I have an issue with mail getting rejected from a specific
  domain. It's getting rejected due to Spamdyke and RDNS. Here's the
  line out of the log. 



Jul 16 09:02:41 vm1 spamdyke[32358]: DENIED_RDNS_RESOLVE from:
  ***@**nd.com to: ***@**ion.com origin_ip: 50.**.**.98 origin_rdns:
  50-**-**-98-static.**.comcastbusiness.net auth: (unknown)
  encryption: (none) reason: (empty)


From looking at the log. It says spamdyke is blocking it due to
  RNDS not resolving. But then on the same line it shows the
  "origin_rdns" and it looks like a valid reverse dns to me.


Why is this getting blocked?


Gary

  


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke and spamassassin

[ChandranManikandan]

Hi Eric,

My Spamassassin config below

ok_locales all
skip_rbl_checks 0

required_hits 5.0
report_safe 0
#rewrite_header Subject [SPAM]

use_pyzor 0

ok_languages all

use_auto_whitelist 0

use_bayes 1
use_bayes_rules 1
bayes_auto_learn 1
use_razor2 0
use_dcc 0

#Spamassassin config
#Spamzen config below url:
http://www.intra2net.com/en/support/antispam/blacklist.php_dnsbl=RCVD_IN_SPAMHAUS_ZEN.html

header RCVD_IN_ZEN eval:check_rbl('zen-lastexternal','zen.spamhaus.org.')
describe RCVD_IN_ZEN Received via a relay in Spamhaus Zen
tflags  RCVD_IN_ZEN   net

#xbl.spamhaus.org url:
http://www.intra2net.com/en/support/antispam/blacklist.php_dnsbl=RCVD_IN_XBL.html

#header  RCVD_IN_XBL
eval:check_rbl_sub('zen-lastexternal','127.0.0.[45678]')
#describeRCVD_IN_XBL Received via a relay in Spamhaus XBL
#tflags  RCVD_IN_XBL net
#score   RCVD_IN_XBL 0 # please adjust the score value

#cbl.abuseat.org url:
http://www.intra2net.com/en/support/antispam/blacklist.php_dnsbl=RCVD_IN_CBL.html

#header  RCVD_IN_CBL
 eval:check_rbl('cbl-lastexternal','cbl.abuseat.org.')
#describeRCVD_IN_CBL  Listed in cbl.abuseat.org
#tflags  RCVD_IN_CBL  net
#score   RCVD_IN_CBL  0 # please adjust score value

#dcc1.dcc-servers.net url:
http://www.intra2net.com/en/support/antispam/blacklist.php_dnsbl=DCC_CHECK.html

#ifplugin Mail::SpamAssassin::Plugin::DCC

#full DCC_CHECK  eval:check_dcc()
#describe DCC_CHECK  Listed in DCC (http://rhyolite.com/anti-spam/dcc/)
#tflags   DCC_CHECK  net
#scoreDCC_CHECK  0 # please adjust the score value
#endif

#dnsbl-1.uceprotect.net url:
http://www.intra2net.com/en/support/antispam/blacklist.php_dnsbl=RCVD_IN_UCEPROTECT1.html

#header   RCVD_IN_UCEPROTECT1
 eval:check_rbl_txt('uceprotect1-lastexternal',
 'dnsbl-1.uceprotect.net.')
#describe RCVD_IN_UCEPROTECT1  Listed in dnsbl-1.uceprotect.net (open
relay/proxy/dialup)
#tflags   RCVD_IN_UCEPROTECT1  net
#scoreRCVD_IN_UCEPROTECT1  0 # please adjust the score value

#hostkarma.junkemailfilter.com url:
http://www.intra2net.com/en/support/antispam/blacklist.php_dnsbl=RCVD_IN_JMF_BL.html

#header  RCVD_IN_JMF_BL
 eval:check_rbl_sub('JMF-lastexternal','127.0.0.2')
#describeRCVD_IN_JMF_BLSender listed in JMF-BLACK
#tflags  RCVD_IN_JMF_BLnet
#score   RCVD_IN_JMF_BL0 # please adjust the score value

#psbl.surriel.com url:
http://www.intra2net.com/en/support/antispam/blacklist.php_dnsbl=RCVD_IN_PSBL.html

#header RCVD_IN_PSBL
eval:check_rbl('psbl-lastexternal','psbl.surriel.com.')
#describe   RCVD_IN_PSBL   Received via a relay in PSBL (psbl.surriel.com)
#tflags RCVD_IN_PSBL   net
#score  RCVD_IN_PSBL   0 # please adjust the score value

#db.wpbl.info url:
http://www.intra2net.com/en/support/antispam/blacklist.php_dnsbl=RCVD_IN_WPBL.html

#headerRCVD_IN_WPBL
 eval:check_rbl('wpbl-lastexternal','db.wpbl.info.','127.0.0.2')
#describe  RCVD_IN_WPBL  Listed in wpbl
#tflagsRCVD_IN_WPBL  net
#score RCVD_IN_WPBL  0 # please adjust the score value

On Wed, May 27, 2020 at 5:19 PM Eric Broch  wrote:

> It looks like spamdyke and spamassassin are in place and working. Have you
> tried using bayes with spamassassin?
> On 5/26/2020 11:17 PM, ChandranManikandan wrote:
>
> Hi Eric,
>
> I have given details below as per your advise.
>
> Incoming Email headers below
>
>
>
>
>
> *Received: by simscan 1.4.0 ppid: 27966, pid: 27969, t: 0.4328s
>  scanners: attach: 1.4.0 clamav: 0.102.2/m:59/d:25824 spam: 3.4.2
> X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
> mail.panasiagroup.net  X-Spam-Level: **
>
> #  cat /var/log/maillog | grep spamdyke
>
> *May 27 13:12:23 mail spamdyke[5970]: DENIED_RDNS_RESOLVE from*
>
> # cat /var/qmail/supervise/smtp/run
>
> *#!/bin/sh QMAILDUID=`id -u vpopmail` NOFILESGID=`id -g vpopmail`
> MAXSMTPD=`cat /var/qmail/control/concurrencyincoming`
> SPAMDYKE="/usr/bin/spamdyke" SPAMDYKE_CONF="/etc/spamdyke/spamdyke.conf"
> SMTPD="/var/qmail/bin/qmail-smtpd" TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"
> HOSTNAME=`hostname` VCHKPW="/home/vpopmail/bin/vchkpw" REQUIRE_AUTH=0 exec
> /usr/bin/softlimit -m 6400 \  /usr/bin/tcpserver -v -R -H -l
> $HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \  -u "$QMAILDUID" -g
> "$NOFILESGID" 0 smtp \  $SPAMDYKE --config-file $SPAMDYKE_CONF \
>  $SMTPD $VCHKPW /bin/true 2>&1*
>
>
>
>
> On Tue, May 26, 2020 at 9:29 PM Eric Broch 
> wrote:
>
>> Do you have the following in your email headers
>>
>> Received: by simscan 1.4.0 ppid: 7614, pid: 7616, t: 0.7769s
>>  scanners: attach: 1.4.0 clamav: 0.102.2/m:59/d:25812 spam: 3.4.2
>>
>>
>> Run commands
>>
>> #  cat /var/log/maillog | grep spamdyke
>>
>> and
>>
>> # cat /var/qmail/supervise/smtp/run
>>
>> To see if spamdyke is running
>>
>>
>>
>>
>>
>> On 5/26/2020 2:32 AM, ChandranManikandan wrote:
>>
>> Hi Friends,
>>
>> Spams emails are 

Re: [qmailtoaster] spamdyke and spamassassin

[Eric Broch]

It looks like spamdyke and spamassassin are in place and working. Have 
you tried using bayes with spamassassin?


On 5/26/2020 11:17 PM, ChandranManikandan wrote:

Hi Eric,

I have given details below as per your advise.

Incoming Email headers below

*Received: by simscan 1.4.0 ppid: 27966, pid: 27969, t: 0.4328s
         scanners: attach: 1.4.0 clamav: 0.102.2/m:59/d:25824 spam: 3.4.2
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
mail.panasiagroup.net 
X-Spam-Level: **

#  cat /var/log/maillog | grep spamdyke
*May 27 13:12:23 mail spamdyke[5970]: DENIED_RDNS_RESOLVE from*
# cat /var/qmail/supervise/smtp/run
*#!/bin/sh QMAILDUID=`id -u vpopmail` NOFILESGID=`id -g vpopmail` 
MAXSMTPD=`cat /var/qmail/control/concurrencyincoming` 
SPAMDYKE="/usr/bin/spamdyke" 
SPAMDYKE_CONF="/etc/spamdyke/spamdyke.conf" 
SMTPD="/var/qmail/bin/qmail-smtpd" 
TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb" HOSTNAME=`hostname` 
VCHKPW="/home/vpopmail/bin/vchkpw" REQUIRE_AUTH=0 exec 
/usr/bin/softlimit -m 6400 \      /usr/bin/tcpserver -v -R -H -l 
$HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \      -u "$QMAILDUID" -g 
"$NOFILESGID" 0 smtp \      $SPAMDYKE --config-file $SPAMDYKE_CONF \   
   $SMTPD $VCHKPW /bin/true 2>&1*




On Tue, May 26, 2020 at 9:29 PM Eric Broch > wrote:


Do you have the following in your email headers

Received: by simscan 1.4.0 ppid: 7614, pid: 7616, t: 0.7769s
  scanners: attach: 1.4.0 clamav: 0.102.2/m:59/d:25812 spam: 3.4.2


Run commands

#  cat /var/log/maillog | grep spamdyke

and

# cat /var/qmail/supervise/smtp/run

To see if spamdyke is running




On 5/26/2020 2:32 AM, ChandranManikandan wrote:

Hi Friends,

Spams emails are continuously hitting my server even i blocked
both spamdyke and spamassasin.
I think spam filter is not working somehow.
Kindly advise do i need to run both or any one.
If suggest which one is powerful and how to remove another spam
engine.

Mine is Centos 7 64 bit server with qmailtoaster.
spamassassin-3.4.2-2.qt.el7.x86_64
spamdyke-5.0.1-0.qt.el7.x86_64

Appreciate your advise.
-- 
*/Regards,

Manikandan.C
/*




--
*/Regards,
Manikandan.C
/*

Re: [qmailtoaster] spamdyke and spamassassin

[ChandranManikandan]

Hi Eric,

I have given details below as per your advise.

Incoming Email headers below





*Received: by simscan 1.4.0 ppid: 27966, pid: 27969, t: 0.4328s
 scanners: attach: 1.4.0 clamav: 0.102.2/m:59/d:25824 spam:
3.4.2X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on
mail.panasiagroup.net X-Spam-Level: **

#  cat /var/log/maillog | grep spamdyke

*May 27 13:12:23 mail spamdyke[5970]: DENIED_RDNS_RESOLVE from*

# cat /var/qmail/supervise/smtp/run

















*#!/bin/shQMAILDUID=`id -u vpopmail`NOFILESGID=`id -g
vpopmail`MAXSMTPD=`cat
/var/qmail/control/concurrencyincoming`SPAMDYKE="/usr/bin/spamdyke"SPAMDYKE_CONF="/etc/spamdyke/spamdyke.conf"SMTPD="/var/qmail/bin/qmail-smtpd"TCP_CDB="/etc/tcprules.d/tcp.smtp.cdb"HOSTNAME=`hostname`VCHKPW="/home/vpopmail/bin/vchkpw"REQUIRE_AUTH=0exec
/usr/bin/softlimit -m 6400 \ /usr/bin/tcpserver -v -R -H -l
$HOSTNAME -x $TCP_CDB -c "$MAXSMTPD" \ -u "$QMAILDUID" -g "$NOFILESGID"
0 smtp \ $SPAMDYKE --config-file $SPAMDYKE_CONF \ $SMTPD $VCHKPW
/bin/true 2>&1*




On Tue, May 26, 2020 at 9:29 PM Eric Broch  wrote:

> Do you have the following in your email headers
>
> Received: by simscan 1.4.0 ppid: 7614, pid: 7616, t: 0.7769s
>  scanners: attach: 1.4.0 clamav: 0.102.2/m:59/d:25812 spam: 3.4.2
>
>
> Run commands
>
> #  cat /var/log/maillog | grep spamdyke
>
> and
>
> # cat /var/qmail/supervise/smtp/run
>
> To see if spamdyke is running
>
>
>
>
>
> On 5/26/2020 2:32 AM, ChandranManikandan wrote:
>
> Hi Friends,
>
> Spams emails are continuously hitting my server even i blocked both
> spamdyke and spamassasin.
> I think spam filter is not working somehow.
> Kindly advise do i need to run both or any one.
> If suggest which one is powerful and how to remove another spam engine.
>
> Mine is Centos 7 64 bit server with qmailtoaster.
> spamassassin-3.4.2-2.qt.el7.x86_64
> spamdyke-5.0.1-0.qt.el7.x86_64
>
> Appreciate your advise.
> --
>
>
> *Regards, Manikandan.C *
>
>

-- 


*Regards,Manikandan.C*

Re: [qmailtoaster] spamdyke and spamassassin

[Eric Broch]

Do you have the following in your email headers

Received: by simscan 1.4.0 ppid: 7614, pid: 7616, t: 0.7769s
 scanners: attach: 1.4.0 clamav: 0.102.2/m:59/d:25812 spam: 3.4.2


Run commands

#  cat /var/log/maillog | grep spamdyke

and

# cat /var/qmail/supervise/smtp/run

To see if spamdyke is running




On 5/26/2020 2:32 AM, ChandranManikandan wrote:

Hi Friends,

Spams emails are continuously hitting my server even i blocked both 
spamdyke and spamassasin.

I think spam filter is not working somehow.
Kindly advise do i need to run both or any one.
If suggest which one is powerful and how to remove another spam engine.

Mine is Centos 7 64 bit server with qmailtoaster.
spamassassin-3.4.2-2.qt.el7.x86_64
spamdyke-5.0.1-0.qt.el7.x86_64

Appreciate your advise.
--
*/Regards,
Manikandan.C
/*

[qmailtoaster] spamdyke and spamassassin

[ChandranManikandan]

Hi Friends,

Spams emails are continuously hitting my server even i blocked both
spamdyke and spamassasin.
I think spam filter is not working somehow.
Kindly advise do i need to run both or any one.
If suggest which one is powerful and how to remove another spam engine.

Mine is Centos 7 64 bit server with qmailtoaster.
spamassassin-3.4.2-2.qt.el7.x86_64
spamdyke-5.0.1-0.qt.el7.x86_64

Appreciate your advise.
-- 


*Regards,Manikandan.C*

Re: [qmailtoaster] spamdyke rejecting all incoming messages

[Eric]

Yes, upgrade, but look in the clam log as well. I'd be interested to see 
if any errors showed up in the clam log...if it were my server. If 
upgrade doesn't help looking in the logs could be helpful in determining 
the issue.


On 10/27/2016 8:16 PM, Kelly Cobean wrote:

This test worked..with clamav turned off, mail is flowing normally.  So
you recommend doing as you suggested earlier regarding upgrading clamav?

On Thu, Oct 27, 2016 at 9:33 PM, Eric > wrote:

You can turn ClamAV off in /var/qmail/control/simcontrol
just to quickly eliminate, or verify, the problem:

From:
:clam=yes,spam=yes,spam_hits=12,attach=.mp3:.src:.bat:.pif
To:
:clam=no,spam=yes,spam_hits=12,attach=.mp3:.src:.bat:.pif

# qmailctl cdb
# qmailctl stop
# qmailctl start

On 10/27/2016 7:29 PM, Eric wrote:

I'd also look in /var/log/messages, /var/log/maillog (remember
corresponding times).

You could try updating ClamAV as well, one version at a time,
from old
ClamAV versions in this folder:

ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/5/current/x86_64/old/


to the newest stable ClamAV version in this folder:

ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/5/current/x86_64/


to the newest testing ClamAV version in this folder:

ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/5/testing/x86_64/




On 10/27/2016 7:15 PM, Kelly Cobean wrote:

Don't laugh, but:

CentOS release 5.11 (Final)


[root@www spamdyke]# freshclam
ClamAV update process started at Thu Oct 27 21:15:12 2016
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.97.5 Recommended version: 0.99.2
DON'T PANIC! Read http://www.clamav.net/support/faq

main.cvd is up to date (version: 57, sigs: 4218790, f-level: 60,
builder: amishhammer)
daily.cld is up to date (version: 22442, sigs: 789412,
f-level: 63,
builder: neo)
bytecode.cld is up to date (version: 283, sigs: 53, f-level: 63,
builder: neo)


On Thu, Oct 27, 2016 at 8:43 PM, Eric

>> wrote:

What system OS and version are you running?
ClamAV?


On 10/27/2016 4:48 PM, Kelly Cobean wrote:

Hey all,
My QMT install has been running for years and
admittedly
I've done
very little maintenance/patching.  I still run a few
domains
with EZ-MLM
lists and individual accounts and recently, my
server stopped
accepting
all inbound messages.  There are only 2 messages in
my queue and
I've
stopped and restarted qmail (qmailctl stop/start)
and I've even
restarted the server.  There's plenty of disk space
on the
server.

The error logs indicate the following:

@4000581282090d55df2c tcpserver: status: 1/100
@4000581282090d55eae4 tcpserver: pid 15044 from
209.85.215.45  >
@4000581282090d55eae4 tcpserver: ok 15044
www.novagunrunners.com:66.151.32.133:25
:209.85.215.45 
>::35674
@40005812820b0c77db3c CHKUSER accepted sender: from
 remote

>> rcpt <> :
sender accepted
@40005812820b119a188c CHKUSER accepted any rcpt:
from
 remote

>> rcpt

>

Re: [qmailtoaster] spamdyke rejecting all incoming messages

[Kelly Cobean]

This test worked..with clamav turned off, mail is flowing normally.  So you
recommend doing as you suggested earlier regarding upgrading clamav?

On Thu, Oct 27, 2016 at 9:33 PM, Eric  wrote:

> You can turn ClamAV off in /var/qmail/control/simcontrol
> just to quickly eliminate, or verify, the problem:
>
> From:
> :clam=yes,spam=yes,spam_hits=12,attach=.mp3:.src:.bat:.pif
> To:
> :clam=no,spam=yes,spam_hits=12,attach=.mp3:.src:.bat:.pif
>
> # qmailctl cdb
> # qmailctl stop
> # qmailctl start
>
> On 10/27/2016 7:29 PM, Eric wrote:
>
>> I'd also look in /var/log/messages, /var/log/maillog (remember
>> corresponding times).
>>
>> You could try updating ClamAV as well, one version at a time, from old
>> ClamAV versions in this folder:
>>
>> ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/5/current/x86_64/old/
>>
>> to the newest stable ClamAV version in this folder:
>>
>> ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/5/current/x86_64/
>>
>> to the newest testing ClamAV version in this folder:
>>
>> ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/5/testing/x86_64/
>>
>>
>>
>> On 10/27/2016 7:15 PM, Kelly Cobean wrote:
>>
>>> Don't laugh, but:
>>>
>>> CentOS release 5.11 (Final)
>>>
>>>
>>> [root@www spamdyke]# freshclam
>>> ClamAV update process started at Thu Oct 27 21:15:12 2016
>>> WARNING: Your ClamAV installation is OUTDATED!
>>> WARNING: Local version: 0.97.5 Recommended version: 0.99.2
>>> DON'T PANIC! Read http://www.clamav.net/support/faq
>>> main.cvd is up to date (version: 57, sigs: 4218790, f-level: 60,
>>> builder: amishhammer)
>>> daily.cld is up to date (version: 22442, sigs: 789412, f-level: 63,
>>> builder: neo)
>>> bytecode.cld is up to date (version: 283, sigs: 53, f-level: 63,
>>> builder: neo)
>>>
>>>
>>> On Thu, Oct 27, 2016 at 8:43 PM, Eric >> > wrote:
>>>
>>> What system OS and version are you running?
>>> ClamAV?
>>>
>>>
>>> On 10/27/2016 4:48 PM, Kelly Cobean wrote:
>>>
>>> Hey all,
>>> My QMT install has been running for years and admittedly
>>> I've done
>>> very little maintenance/patching.  I still run a few domains
>>> with EZ-MLM
>>> lists and individual accounts and recently, my server stopped
>>> accepting
>>> all inbound messages.  There are only 2 messages in my queue and
>>> I've
>>> stopped and restarted qmail (qmailctl stop/start) and I've even
>>> restarted the server.  There's plenty of disk space on the
>>> server.
>>>
>>> The error logs indicate the following:
>>>
>>> @4000581282090d55df2c tcpserver: status: 1/100
>>> @4000581282090d55eae4 tcpserver: pid 15044 from
>>> 209.85.215.45 
>>> @4000581282090d55eae4 tcpserver: ok 15044
>>> www.novagunrunners.com:66.151.32.133:25 :209.85.215.45
>>> ::35674
>>> @40005812820b0c77db3c CHKUSER accepted sender: from
>>>  remote
>>> >> > rcpt <> : sender accepted
>>> @40005812820b119a188c CHKUSER accepted any rcpt: from
>>>  remote
>>> >> > rcpt
>>> 
>>> >>
>>> : accepted any
>>> recipient for this domain
>>> @40005812820b119a2444 policy_check: remote ke...@cobean.net
>>> 
>>> > -> local
>>> kcob...@vipercrazy.com 
>>> >
>>> (UNAUTHENTICATED SENDER)
>>> @40005812820b119a282c policy_check: policy allows
>>> transmission
>>> @40005812820c1bfa123c qmail-smtpd: qq soft reject (mail
>>> server
>>> temporarily rejected message (#4.3.0)):
>>> MAILFROM:
>>> >>
>>> RCPTTO:kcob...@vipercrazy.com
>>> 
>>> >> >
>>> @40005812820c1bfa1a0c spamdyke[15044]: DENIED_OTHER from:
>>> ke...@cobean.net 
>>> > to:
>>> kcob...@vipercrazy.com 
>>> >
>>> origin_ip: 209.85.215.45  origin_rdns:
>>> mail-lf0-f45.google.com 
>>> >> > auth: (unknown)
>>> encryption: TLS reason:
>>> 

Re: [qmailtoaster] spamdyke rejecting all incoming messages

[Eric]

You can turn ClamAV off in /var/qmail/control/simcontrol
just to quickly eliminate, or verify, the problem:

From:
:clam=yes,spam=yes,spam_hits=12,attach=.mp3:.src:.bat:.pif
To:
:clam=no,spam=yes,spam_hits=12,attach=.mp3:.src:.bat:.pif

# qmailctl cdb
# qmailctl stop
# qmailctl start

On 10/27/2016 7:29 PM, Eric wrote:

I'd also look in /var/log/messages, /var/log/maillog (remember
corresponding times).

You could try updating ClamAV as well, one version at a time, from old
ClamAV versions in this folder:

ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/5/current/x86_64/old/

to the newest stable ClamAV version in this folder:

ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/5/current/x86_64/

to the newest testing ClamAV version in this folder:

ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/5/testing/x86_64/



On 10/27/2016 7:15 PM, Kelly Cobean wrote:

Don't laugh, but:

CentOS release 5.11 (Final)


[root@www spamdyke]# freshclam
ClamAV update process started at Thu Oct 27 21:15:12 2016
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.97.5 Recommended version: 0.99.2
DON'T PANIC! Read http://www.clamav.net/support/faq
main.cvd is up to date (version: 57, sigs: 4218790, f-level: 60,
builder: amishhammer)
daily.cld is up to date (version: 22442, sigs: 789412, f-level: 63,
builder: neo)
bytecode.cld is up to date (version: 283, sigs: 53, f-level: 63,
builder: neo)


On Thu, Oct 27, 2016 at 8:43 PM, Eric > wrote:

What system OS and version are you running?
ClamAV?


On 10/27/2016 4:48 PM, Kelly Cobean wrote:

Hey all,
My QMT install has been running for years and admittedly
I've done
very little maintenance/patching.  I still run a few domains
with EZ-MLM
lists and individual accounts and recently, my server stopped
accepting
all inbound messages.  There are only 2 messages in my queue and
I've
stopped and restarted qmail (qmailctl stop/start) and I've even
restarted the server.  There's plenty of disk space on the
server.

The error logs indicate the following:

@4000581282090d55df2c tcpserver: status: 1/100
@4000581282090d55eae4 tcpserver: pid 15044 from
209.85.215.45 
@4000581282090d55eae4 tcpserver: ok 15044
www.novagunrunners.com:66.151.32.133:25 :209.85.215.45
::35674
@40005812820b0c77db3c CHKUSER accepted sender: from
 remote
> rcpt <> : sender accepted
@40005812820b119a188c CHKUSER accepted any rcpt: from
 remote
> rcpt

>>
: accepted any
recipient for this domain
@40005812820b119a2444 policy_check: remote ke...@cobean.net

> -> local
kcob...@vipercrazy.com 
>
(UNAUTHENTICATED SENDER)
@40005812820b119a282c policy_check: policy allows
transmission
@40005812820c1bfa123c qmail-smtpd: qq soft reject (mail
server
temporarily rejected message (#4.3.0)):
MAILFROM:
>>
RCPTTO:kcob...@vipercrazy.com

>
@40005812820c1bfa1a0c spamdyke[15044]: DENIED_OTHER from:
ke...@cobean.net 
> to:
kcob...@vipercrazy.com 
>
origin_ip: 209.85.215.45  origin_rdns:
mail-lf0-f45.google.com 
> auth: (unknown)
encryption: TLS reason:
451_mail_server_temporarily_rejected_message_(#4.3.0)
@40005812820c24ba9874 tcpserver: end 15044 status 0


 My spamdyke is probably old:

[root@www spamdyke]# spamdyke --version
spamdyke 4.3.1+TLS+CONFIGTEST+DEBUG (C)2012 Sam Clippinger, samc
(at)
silence (dot) org
http://www.spamdyke.org/


I've made no changes on the server.  Has anyone seen this
before? I
appreciate any help you can offer.


-
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com

Re: [qmailtoaster] spamdyke rejecting all incoming messages

[Eric]

I'd also look in /var/log/messages, /var/log/maillog (remember 
corresponding times).


You could try updating ClamAV as well, one version at a time, from old 
ClamAV versions in this folder:


ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/5/current/x86_64/old/

to the newest stable ClamAV version in this folder:

ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/5/current/x86_64/

to the newest testing ClamAV version in this folder:

ftp://ftp.qmailtoaster.com/pub/repo/qmt/CentOS/5/testing/x86_64/



On 10/27/2016 7:15 PM, Kelly Cobean wrote:

Don't laugh, but:

CentOS release 5.11 (Final)


[root@www spamdyke]# freshclam
ClamAV update process started at Thu Oct 27 21:15:12 2016
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.97.5 Recommended version: 0.99.2
DON'T PANIC! Read http://www.clamav.net/support/faq
main.cvd is up to date (version: 57, sigs: 4218790, f-level: 60,
builder: amishhammer)
daily.cld is up to date (version: 22442, sigs: 789412, f-level: 63,
builder: neo)
bytecode.cld is up to date (version: 283, sigs: 53, f-level: 63,
builder: neo)


On Thu, Oct 27, 2016 at 8:43 PM, Eric > wrote:

What system OS and version are you running?
ClamAV?


On 10/27/2016 4:48 PM, Kelly Cobean wrote:

Hey all,
My QMT install has been running for years and admittedly
I've done
very little maintenance/patching.  I still run a few domains
with EZ-MLM
lists and individual accounts and recently, my server stopped
accepting
all inbound messages.  There are only 2 messages in my queue and
I've
stopped and restarted qmail (qmailctl stop/start) and I've even
restarted the server.  There's plenty of disk space on the server.

The error logs indicate the following:

@4000581282090d55df2c tcpserver: status: 1/100
@4000581282090d55eae4 tcpserver: pid 15044 from
209.85.215.45 
@4000581282090d55eae4 tcpserver: ok 15044
www.novagunrunners.com:66.151.32.133:25 :209.85.215.45
::35674
@40005812820b0c77db3c CHKUSER accepted sender: from
 remote
> rcpt <> : sender accepted
@40005812820b119a188c CHKUSER accepted any rcpt: from
 remote
> rcpt

>>
: accepted any
recipient for this domain
@40005812820b119a2444 policy_check: remote ke...@cobean.net

> -> local
kcob...@vipercrazy.com 
>
(UNAUTHENTICATED SENDER)
@40005812820b119a282c policy_check: policy allows transmission
@40005812820c1bfa123c qmail-smtpd: qq soft reject (mail server
temporarily rejected message (#4.3.0)):
MAILFROM:
>>
RCPTTO:kcob...@vipercrazy.com

>
@40005812820c1bfa1a0c spamdyke[15044]: DENIED_OTHER from:
ke...@cobean.net 
> to:
kcob...@vipercrazy.com 
>
origin_ip: 209.85.215.45  origin_rdns:
mail-lf0-f45.google.com 
> auth: (unknown)
encryption: TLS reason:
451_mail_server_temporarily_rejected_message_(#4.3.0)
@40005812820c24ba9874 tcpserver: end 15044 status 0


 My spamdyke is probably old:

[root@www spamdyke]# spamdyke --version
spamdyke 4.3.1+TLS+CONFIGTEST+DEBUG (C)2012 Sam Clippinger, samc
(at)
silence (dot) org
http://www.spamdyke.org/


I've made no changes on the server.  Has anyone seen this before? I
appreciate any help you can offer.


-
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com





-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional 

Re: [qmailtoaster] spamdyke rejecting all incoming messages

[Eric]

I'd look take a look in your clam log. I think 
/var/log/qmail/clamav/current??? or something like that. Correspond the 
time of qq soft reject... with the time in the clamav log.


On 10/27/2016 7:15 PM, Kelly Cobean wrote:

Don't laugh, but:

CentOS release 5.11 (Final)


[root@www spamdyke]# freshclam
ClamAV update process started at Thu Oct 27 21:15:12 2016
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.97.5 Recommended version: 0.99.2
DON'T PANIC! Read http://www.clamav.net/support/faq
main.cvd is up to date (version: 57, sigs: 4218790, f-level: 60,
builder: amishhammer)
daily.cld is up to date (version: 22442, sigs: 789412, f-level: 63,
builder: neo)
bytecode.cld is up to date (version: 283, sigs: 53, f-level: 63,
builder: neo)


On Thu, Oct 27, 2016 at 8:43 PM, Eric > wrote:

What system OS and version are you running?
ClamAV?


On 10/27/2016 4:48 PM, Kelly Cobean wrote:

Hey all,
My QMT install has been running for years and admittedly
I've done
very little maintenance/patching.  I still run a few domains
with EZ-MLM
lists and individual accounts and recently, my server stopped
accepting
all inbound messages.  There are only 2 messages in my queue and
I've
stopped and restarted qmail (qmailctl stop/start) and I've even
restarted the server.  There's plenty of disk space on the server.

The error logs indicate the following:

@4000581282090d55df2c tcpserver: status: 1/100
@4000581282090d55eae4 tcpserver: pid 15044 from
209.85.215.45 
@4000581282090d55eae4 tcpserver: ok 15044
www.novagunrunners.com:66.151.32.133:25 :209.85.215.45
::35674
@40005812820b0c77db3c CHKUSER accepted sender: from
 remote
> rcpt <> : sender accepted
@40005812820b119a188c CHKUSER accepted any rcpt: from
 remote
> rcpt

>>
: accepted any
recipient for this domain
@40005812820b119a2444 policy_check: remote ke...@cobean.net

> -> local
kcob...@vipercrazy.com 
>
(UNAUTHENTICATED SENDER)
@40005812820b119a282c policy_check: policy allows transmission
@40005812820c1bfa123c qmail-smtpd: qq soft reject (mail server
temporarily rejected message (#4.3.0)):
MAILFROM:
>>
RCPTTO:kcob...@vipercrazy.com

>
@40005812820c1bfa1a0c spamdyke[15044]: DENIED_OTHER from:
ke...@cobean.net 
> to:
kcob...@vipercrazy.com 
>
origin_ip: 209.85.215.45  origin_rdns:
mail-lf0-f45.google.com 
> auth: (unknown)
encryption: TLS reason:
451_mail_server_temporarily_rejected_message_(#4.3.0)
@40005812820c24ba9874 tcpserver: end 15044 status 0


 My spamdyke is probably old:

[root@www spamdyke]# spamdyke --version
spamdyke 4.3.1+TLS+CONFIGTEST+DEBUG (C)2012 Sam Clippinger, samc
(at)
silence (dot) org
http://www.spamdyke.org/


I've made no changes on the server.  Has anyone seen this before? I
appreciate any help you can offer.


-
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com





-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke rejecting all incoming messages

[Kelly Cobean]

Don't laugh, but:

CentOS release 5.11 (Final)


[root@www spamdyke]# freshclam
ClamAV update process started at Thu Oct 27 21:15:12 2016
WARNING: Your ClamAV installation is OUTDATED!
WARNING: Local version: 0.97.5 Recommended version: 0.99.2
DON'T PANIC! Read http://www.clamav.net/support/faq
main.cvd is up to date (version: 57, sigs: 4218790, f-level: 60, builder:
amishhammer)
daily.cld is up to date (version: 22442, sigs: 789412, f-level: 63,
builder: neo)
bytecode.cld is up to date (version: 283, sigs: 53, f-level: 63, builder:
neo)


On Thu, Oct 27, 2016 at 8:43 PM, Eric  wrote:

> What system OS and version are you running?
> ClamAV?
>
>
> On 10/27/2016 4:48 PM, Kelly Cobean wrote:
>
>> Hey all,
>> My QMT install has been running for years and admittedly I've done
>> very little maintenance/patching.  I still run a few domains with EZ-MLM
>> lists and individual accounts and recently, my server stopped accepting
>> all inbound messages.  There are only 2 messages in my queue and I've
>> stopped and restarted qmail (qmailctl stop/start) and I've even
>> restarted the server.  There's plenty of disk space on the server.
>>
>> The error logs indicate the following:
>>
>> @4000581282090d55df2c tcpserver: status: 1/100
>> @4000581282090d55eae4 tcpserver: pid 15044 from 209.85.215.45
>> @4000581282090d55eae4 tcpserver: ok 15044
>> www.novagunrunners.com:66.151.32.133:25 :209.85.215.45::35674
>> @40005812820b0c77db3c CHKUSER accepted sender: from
>>  remote
>>  rcpt <> : sender accepted
>> @40005812820b119a188c CHKUSER accepted any rcpt: from
>>  remote
>>  rcpt
>> > : accepted any
>> recipient for this domain
>> @40005812820b119a2444 policy_check: remote ke...@cobean.net
>>  -> local kcob...@vipercrazy.com
>>  (UNAUTHENTICATED SENDER)
>> @40005812820b119a282c policy_check: policy allows transmission
>> @40005812820c1bfa123c qmail-smtpd: qq soft reject (mail server
>> temporarily rejected message (#4.3.0)): MAILFROM:> > RCPTTO:kcob...@vipercrazy.com
>> 
>> @40005812820c1bfa1a0c spamdyke[15044]: DENIED_OTHER from:
>> ke...@cobean.net  to: kcob...@vipercrazy.com
>>  origin_ip: 209.85.215.45 origin_rdns:
>> mail-lf0-f45.google.com  auth: (unknown)
>> encryption: TLS reason:
>> 451_mail_server_temporarily_rejected_message_(#4.3.0)
>> @40005812820c24ba9874 tcpserver: end 15044 status 0
>>
>>
>>  My spamdyke is probably old:
>>
>> [root@www spamdyke]# spamdyke --version
>> spamdyke 4.3.1+TLS+CONFIGTEST+DEBUG (C)2012 Sam Clippinger, samc (at)
>> silence (dot) org
>> http://www.spamdyke.org/
>>
>>
>> I've made no changes on the server.  Has anyone seen this before? I
>> appreciate any help you can offer.
>>
>>
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>
>

Re: [qmailtoaster] spamdyke rejecting all incoming messages

[Eric]

What system OS and version are you running?
ClamAV?


On 10/27/2016 4:48 PM, Kelly Cobean wrote:

Hey all,
My QMT install has been running for years and admittedly I've done
very little maintenance/patching.  I still run a few domains with EZ-MLM
lists and individual accounts and recently, my server stopped accepting
all inbound messages.  There are only 2 messages in my queue and I've
stopped and restarted qmail (qmailctl stop/start) and I've even
restarted the server.  There's plenty of disk space on the server.

The error logs indicate the following:

@4000581282090d55df2c tcpserver: status: 1/100
@4000581282090d55eae4 tcpserver: pid 15044 from 209.85.215.45
@4000581282090d55eae4 tcpserver: ok 15044
www.novagunrunners.com:66.151.32.133:25 :209.85.215.45::35674
@40005812820b0c77db3c CHKUSER accepted sender: from
 remote
 rcpt <> : sender accepted
@40005812820b119a188c CHKUSER accepted any rcpt: from
 remote
 rcpt
> : accepted any
recipient for this domain
@40005812820b119a2444 policy_check: remote ke...@cobean.net
 -> local kcob...@vipercrazy.com
 (UNAUTHENTICATED SENDER)
@40005812820b119a282c policy_check: policy allows transmission
@40005812820c1bfa123c qmail-smtpd: qq soft reject (mail server
temporarily rejected message (#4.3.0)): MAILFROM:> RCPTTO:kcob...@vipercrazy.com

@40005812820c1bfa1a0c spamdyke[15044]: DENIED_OTHER from:
ke...@cobean.net  to: kcob...@vipercrazy.com
 origin_ip: 209.85.215.45 origin_rdns:
mail-lf0-f45.google.com  auth: (unknown)
encryption: TLS reason:
451_mail_server_temporarily_rejected_message_(#4.3.0)
@40005812820c24ba9874 tcpserver: end 15044 status 0


 My spamdyke is probably old:

[root@www spamdyke]# spamdyke --version
spamdyke 4.3.1+TLS+CONFIGTEST+DEBUG (C)2012 Sam Clippinger, samc (at)
silence (dot) org
http://www.spamdyke.org/


I've made no changes on the server.  Has anyone seen this before? I
appreciate any help you can offer.



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke rejecting all incoming messages

[Jaime Lerner]

Maybe this would be helpful?

http://www.itechlounge.net/2015/12/linux-error-receiving-or-sending-email-wi
th-qmail-451_mail_server_temporarily_rejected_message_4-3-0/



From:  Kelly Cobean <ke...@cobean.net>
Reply-To:  <qmailtoaster-list@qmailtoaster.com>
Date:  Thursday, October 27, 2016 at 6:48 PM
To:  <qmailtoaster-list@qmailtoaster.com>
Subject:  [qmailtoaster] spamdyke rejecting all incoming messages

Hey all,
My QMT install has been running for years and admittedly I've done very
little maintenance/patching.  I still run a few domains with EZ-MLM lists
and individual accounts and recently, my server stopped accepting all
inbound messages.  There are only 2 messages in my queue and I've stopped
and restarted qmail (qmailctl stop/start) and I've even restarted the
server.  There's plenty of disk space on the server.

The error logs indicate the following:

@4000581282090d55df2c tcpserver: status: 1/100
@4000581282090d55eae4 tcpserver: pid 15044 from 209.85.215.45
@4000581282090d55eae4 tcpserver: ok 15044
www.novagunrunners.com:66.151.32.133:25 :209.85.215.45::35674
@40005812820b0c77db3c CHKUSER accepted sender: from <ke...@cobean.net::>
remote  rcpt <> : sender
accepted
@40005812820b119a188c CHKUSER accepted any rcpt: from
<ke...@cobean.net::> remote 
rcpt <kcob...@vipercrazy.com> : accepted any recipient for this domain
@40005812820b119a2444 policy_check: remote ke...@cobean.net -> local
kcob...@vipercrazy.com (UNAUTHENTICATED SENDER)
@40005812820b119a282c policy_check: policy allows transmission
@40005812820c1bfa123c qmail-smtpd: qq soft reject (mail server
temporarily rejected message (#4.3.0)): MAILFROM:<ke...@cobean.net>
RCPTTO:kcob...@vipercrazy.com <mailto:rcptto%3akcob...@vipercrazy.com>
@40005812820c1bfa1a0c spamdyke[15044]: DENIED_OTHER from:
ke...@cobean.net to: kcob...@vipercrazy.com origin_ip: 209.85.215.45
origin_rdns: mail-lf0-f45.google.com <http://mail-lf0-f45.google.com>  auth:
(unknown) encryption: TLS reason:
451_mail_server_temporarily_rejected_message_(#4.3.0)
@40005812820c24ba9874 tcpserver: end 15044 status 0


 My spamdyke is probably old:

[root@www spamdyke]# spamdyke --version
spamdyke 4.3.1+TLS+CONFIGTEST+DEBUG (C)2012 Sam Clippinger, samc (at)
silence (dot) org
http://www.spamdyke.org/


I've made no changes on the server.  Has anyone seen this before? I
appreciate any help you can offer.

Re: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64

[Eric]

Tony,

CentOS 5 x86_64 RPM:
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/5/testing/x86_64/spamdyke-5.0.1-0.qt.el5.x86_64.rpm

Remember to backup spamdyke.conf beforehand and run the script fixsd.sh 
(below) at CLI for spamdyke.conf after upgrade.



#!/bin/sh
sed -i \
-e 's/reject-missing-sender-mx/reject-sender=no-mx/g' \
-e 's/rejection-text-missing-sender-mx/rejection-text-sender-no-mx/g' \
-e 's/reject-identical-sender-recipient/reject-recipient=same-as-sender/g' \
-e 
's/rejection-text-identical-sender-recipient/rejection-text-recipient-same-as-sender/g' 
\

-e 's/local-domains-file/qmail-rcpthosts-file/g' \
-e 's/local-domains-entry=/#local-domains-entry=(Add these entries to 
qmail-rcpthosts-file)/g' \

-e 's/morercpthosts/qmail-morercpthosts-cdb/'g /etc/spamdyke/spamdyke.conf


Monitor SMTP log ( tail -f /var/log/qmail/smtp/current | tai64nlocal ) 
and send yourself an email to check for errors.


Let me know of any problems.

Eric

On 3/6/2016 10:46 PM, Tony White wrote:

Hi Eirc,
  Thank you I use x86_64.

best wishes
  Tony White

Yea Computing Services
http://www.ycs.com.au
4 The Crescent
Yea
Victoria
Australia 3717

Telephone No's
VIC : 03 9008 5614
FAX : 03 9008 5610 (FAX2Email)

Be aware: All calls to and from YCS landlines and mobiles are recorded

IMPORTANT NOTICE

This communication including any file attachments is intended solely for
the use of the individual or entity to whom it is addressed. If you are
not the intended recipient, or the person responsible for delivering
this communication to the intended recipient, please immediately notify
the sender by email and delete the original transmission and its
contents. Any unauthorised use, dissemination, forwarding, printing or
copying of this communication including file attachments is prohibited.
It is your responsibility to scan this communication including any file
attachments for viruses and other defects. To the extent permitted by
law, Yea Computing Services and its associates will not be liable for
any loss or damage arising in any way from this communication including
any file attachments.
You may not disclose this information to a third party without written
permission from the Author.

On 7/03/2016 16:20, Eric wrote:

Tony,

I had to take down my CentOS 5 vm for other purposes, so I'll get it 
up and running tomorrow and have those spamdyke rpms in the tree for 
you then. i386 or x86_64?


EricB

On 3/6/2016 9:56 PM, Tony White wrote:

Hi Eric,
   Looks good except I am still on CentOS5.
How do I add your repo to my repos please?

best wishes
  Tony White

On 7/03/2016 06:09, Eric wrote:

I was a bit hasty in my creation of the rpm's as the old 
spamdyke.conf file should be replaced. I'll get on that and have 
the rpms up by end of day.


On 3/6/2016 9:55 AM, Eric wrote:
Be mindful that some of the setting in the old spamdyke.conf will 
mess with mail delivery.

I had to comment out 2 lines

#local-domains-file=/var/qmail/control/rcpthosts
#reject-missing-sender-mx

Eric

On 3/6/2016 9:32 AM, Eric wrote:

CentOS 6:
rpm -Uvh 
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/6/testing/x86_64/spamdyke-5.0.1-0.qt.el6.x86_64.rpm

or
# yum --enablerepo=whtc-qmt-testing update
If you have White Horse repos in your yum configuration.

CentOS7:
rpm -Uvh 
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/7/testing/x86_64/spamdyke-5.0.1-0.qt.el7.x86_64.rpm

or
# yum --enablerepo=whtc-qmt-testing update
If you have White Horse repos in your yum configuration.

- 

To unsubscribe, e-mail: 
qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com





-
To unsubscribe, e-mail: 
qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com





-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com







-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com





-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com






-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: 

Re: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64

[Tony White]

Hi Eirc,
  Thank you I use x86_64.

best wishes
  Tony White

Yea Computing Services
http://www.ycs.com.au
4 The Crescent
Yea
Victoria
Australia 3717

Telephone No's
VIC : 03 9008 5614
FAX : 03 9008 5610 (FAX2Email)

Be aware: All calls to and from YCS landlines and mobiles are recorded

IMPORTANT NOTICE

This communication including any file attachments is intended solely for
the use of the individual or entity to whom it is addressed. If you are
not the intended recipient, or the person responsible for delivering
this communication to the intended recipient, please immediately notify
the sender by email and delete the original transmission and its
contents. Any unauthorised use, dissemination, forwarding, printing or
copying of this communication including file attachments is prohibited.
It is your responsibility to scan this communication including any file
attachments for viruses and other defects. To the extent permitted by
law, Yea Computing Services and its associates will not be liable for
any loss or damage arising in any way from this communication including
any file attachments.
You may not disclose this information to a third party without written
permission from the Author.

On 7/03/2016 16:20, Eric wrote:

Tony,

I had to take down my CentOS 5 vm for other purposes, so I'll get it up and running tomorrow and have those spamdyke rpms 
in the tree for you then. i386 or x86_64?


EricB

On 3/6/2016 9:56 PM, Tony White wrote:

Hi Eric,
   Looks good except I am still on CentOS5.
How do I add your repo to my repos please?

best wishes
  Tony White

On 7/03/2016 06:09, Eric wrote:

I was a bit hasty in my creation of the rpm's as the old spamdyke.conf file should be replaced. I'll get on that and 
have the rpms up by end of day.


On 3/6/2016 9:55 AM, Eric wrote:

Be mindful that some of the setting in the old spamdyke.conf will mess with 
mail delivery.
I had to comment out 2 lines

#local-domains-file=/var/qmail/control/rcpthosts
#reject-missing-sender-mx

Eric

On 3/6/2016 9:32 AM, Eric wrote:

CentOS 6:
rpm -Uvh 
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/6/testing/x86_64/spamdyke-5.0.1-0.qt.el6.x86_64.rpm
or
# yum --enablerepo=whtc-qmt-testing update
If you have White Horse repos in your yum configuration.

CentOS7:
rpm -Uvh 
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/7/testing/x86_64/spamdyke-5.0.1-0.qt.el7.x86_64.rpm
or
# yum --enablerepo=whtc-qmt-testing update
If you have White Horse repos in your yum configuration.

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com






-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com






-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64

[Eric]

Change the below script and use the full path to spamdyke.conf

Change on the last line:
'spamdyke.conf'
to
'/etc/spamdyke/spamdyke.conf

EricB


On 3/6/2016 10:22 PM, Eric wrote:


#!/bin/sh
sed -i \
-e 's/reject-missing-sender-mx/reject-sender=no-mx/g' \
-e 's/rejection-text-missing-sender-mx/rejection-text-sender-no-mx/g' \
-e 
's/reject-identical-sender-recipient/reject-recipient=same-as-sender/g' \
-e 
's/rejection-text-identical-sender-recipient/rejection-text-recipient-same-as-sender/g' 
\

-e 's/local-domains-file/qmail-rcpthosts-file/g' \
-e 's/local-domains-entry=/#local-domains-entry=(Add these entries to 
qmail-rcpthosts-file)/g' \

-e 's/morercpthosts/qmail-morercpthosts-cdb/'g spamdyke.conf
 



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64

[Eric]

Please, always have a backup of your original spamdyke.conf file if 
you've made special changes to it


On 3/6/2016 10:18 PM, Eric wrote:

Helmut,

I'm not sure what's in your current spamdyke.conf file, but there are 
three different ways to proceed.

1) Remove and reinstall spamdyke.
 I'm not sure, but your original spamdyke.conf may be lost when 
you remove spamdyke. So, if there's anything special in the conf file 
I'd opt for 2). On reinstall the qmail standard conf file 
with necessary 5.0.1 updates (below, *b) is installed.

2) Upgrade and run my script (*a).
Please make sure that spamdyke is running correctly and that you 
are able to send and receive email.
3) Upgrade and manually change spamdyke.conf (with configuration from 
my previous post to the list), or paste the updated spamdyke.conf(*b) 
provided in this email.
The conf file below is simply the original qmail version with the 
necessary 5.0.1 updates.


(*a)

#!/bin/sh
sed -i \
-e 's/reject-missing-sender-mx/reject-sender=no-mx/g' \
-e 's/rejection-text-missing-sender-mx/rejection-text-sender-no-mx/g' \
-e 
's/reject-identical-sender-recipient/reject-recipient=same-as-sender/g' \
-e 
's/rejection-text-identical-sender-recipient/rejection-text-recipient-same-as-sender/g' 
\

-e 's/local-domains-file/qmail-rcpthosts-file/g' \
-e 's/local-domains-entry=/#local-domains-entry=(Add these entries to 
qmail-rcpthosts-file)/g' \

-e 's/morercpthosts/qmail-morercpthosts-cdb/'g spamdyke.conf


(*b)

#dns-blacklist-entry=zombie.dnsbl.sorbs.net
#dns-blacklist-entry=dul.dnsbl.sorbs.net
#dns-blacklist-entry=bogons.cymru.com
dns-blacklist-entry=zen.spamhaus.org
dns-blacklist-entry=bl.spamcop.net
graylist-dir=/var/spamdyke/graylist
graylist-level=none
graylist-max-secs=2678400
graylist-min-secs=180
greeting-delay-secs=6
header-blacklist-entry=From:*>,*<*
idle-timeout-secs=60
ip-blacklist-file=/etc/spamdyke/blacklist_ip
ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords
ip-in-rdns-keyword-whitelist-file=/etc/spamdyke/whitelist_keywords
ip-whitelist-file=/etc/spamdyke/whitelist_ip
qmail-rcpthosts-file=/var/qmail/control/rcpthosts
#qmail-rcpthosts-file=/var/qmail/control/qmail-morercpthosts-cdb
log-level=info
max-recipients=50
#policy-url=http://my.policy.explanation.url/
rdns-blacklist-file=/etc/spamdyke/blacklist_rdns
rdns-whitelist-file=/etc/spamdyke/whitelist_rdns
recipient-blacklist-file=/etc/spamdyke/blacklist_recipients
recipient-whitelist-file=/etc/spamdyke/whitelist_recipients
reject-empty-rdns
#reject-ip-in-cc-rdns
reject-sender=no-mx
reject-unresolvable-rdns
sender-blacklist-file=/etc/spamdyke/blacklist_senders
sender-whitelist-file=/etc/spamdyke/whitelist_senders
tls-certificate-file=/var/qmail/control/servercert.pem
tls-level=smtp


As always, if you run into issues PLEASE let me know.

EricB.


On 3/6/2016 9:39 PM, Helmut Fritz wrote:
Thx Eric.  The below helps a lot.  Is there a recommended method?  
Remove and install anew or upgrade?


-Original Message-
From: Eric [mailto:ebr...@whitehorsetc.com]
Sent: Sunday, March 06, 2016 2:49 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64

Helmut,

Eventually it will be in general release unless you want it there 
sooner, it is in the testing tree presently (per previous posts), 
though; and I've already implemented 5.0.1-0 on my business 
production server. Be mindful that if you're upgrading (NOT A FRESH 
INSTALL) spamdyke from the testing tree you'll have to address the 
below 7 options in your server's spamdyke.conf file as an upgrade 
does not overwrite existing conf file. Without the adjustments below 
mail will not be delivered.


1)  If the "reject-missing-sender-mx" option is given, it should 
be changed to

"reject-sender" with a value of "no-mx".
2) If the "rejection-text-missing-sender-mx" option is given, it 
should be

renamed to "rejection-text-sender-no-mx".
3) If the "reject-identical-sender-recipient" option is given, it 
should be

changed to "reject-recipient" with a value of "same-as-sender".
4) If the "rejection-text-identical-sender-recipient" option is 
given, it should

be renamed to "rejection-text-recipient-same-as-sender".
5) If the option "local-domains-file" is given, it should be 
renamed to

"qmail-rcpthosts-file".
6) If the option "local-domains-entry" is given, it should be 
removed.  Any
domains given with this option should be added to the file given 
with

"qmail-rcpthosts-file".
7) If qmail's "morercpthosts" file is provided to spamdyke with the
"qmail-rcpthosts-file" option (formerly "lcoal-domains-file"), 
the CDB file
should be provided instead with the "qmail-morercpthosts-cdb" 
option.


EricB


On

Re: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64

[Eric]

Tony,

I had to take down my CentOS 5 vm for other purposes, so I'll get it up 
and running tomorrow and have those spamdyke rpms in the tree for you 
then. i386 or x86_64?


EricB

On 3/6/2016 9:56 PM, Tony White wrote:

Hi Eric,
   Looks good except I am still on CentOS5.
How do I add your repo to my repos please?

best wishes
  Tony White

On 7/03/2016 06:09, Eric wrote:

I was a bit hasty in my creation of the rpm's as the old 
spamdyke.conf file should be replaced. I'll get on that and have the 
rpms up by end of day.


On 3/6/2016 9:55 AM, Eric wrote:
Be mindful that some of the setting in the old spamdyke.conf will 
mess with mail delivery.

I had to comment out 2 lines

#local-domains-file=/var/qmail/control/rcpthosts
#reject-missing-sender-mx

Eric

On 3/6/2016 9:32 AM, Eric wrote:

CentOS 6:
rpm -Uvh 
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/6/testing/x86_64/spamdyke-5.0.1-0.qt.el6.x86_64.rpm

or
# yum --enablerepo=whtc-qmt-testing update
If you have White Horse repos in your yum configuration.

CentOS7:
rpm -Uvh 
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/7/testing/x86_64/spamdyke-5.0.1-0.qt.el7.x86_64.rpm

or
# yum --enablerepo=whtc-qmt-testing update
If you have White Horse repos in your yum configuration.

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com





-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: 
qmailtoaster-list-h...@qmailtoaster.com





-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com






-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64

[Eric]

Helmut,

I'm not sure what's in your current spamdyke.conf file, but there are 
three different ways to proceed.

1) Remove and reinstall spamdyke.
 I'm not sure, but your original spamdyke.conf may be lost when you 
remove spamdyke. So, if there's anything special in the conf file I'd 
opt for 2). On reinstall the qmail standard conf file with   
  necessary 5.0.1 updates (below, *b) is installed.

2) Upgrade and run my script (*a).
Please make sure that spamdyke is running correctly and that you 
are able to send and receive email.
3) Upgrade and manually change spamdyke.conf (with configuration from my 
previous post to the list), or paste the updated spamdyke.conf(*b) 
provided in this email.
The conf file below is simply the original qmail version with the 
necessary 5.0.1 updates.


(*a)

#!/bin/sh
sed -i \
-e 's/reject-missing-sender-mx/reject-sender=no-mx/g' \
-e 's/rejection-text-missing-sender-mx/rejection-text-sender-no-mx/g' \
-e 's/reject-identical-sender-recipient/reject-recipient=same-as-sender/g' \
-e 
's/rejection-text-identical-sender-recipient/rejection-text-recipient-same-as-sender/g' 
\

-e 's/local-domains-file/qmail-rcpthosts-file/g' \
-e 's/local-domains-entry=/#local-domains-entry=(Add these entries to 
qmail-rcpthosts-file)/g' \

-e 's/morercpthosts/qmail-morercpthosts-cdb/'g spamdyke.conf


(*b)

#dns-blacklist-entry=zombie.dnsbl.sorbs.net
#dns-blacklist-entry=dul.dnsbl.sorbs.net
#dns-blacklist-entry=bogons.cymru.com
dns-blacklist-entry=zen.spamhaus.org
dns-blacklist-entry=bl.spamcop.net
graylist-dir=/var/spamdyke/graylist
graylist-level=none
graylist-max-secs=2678400
graylist-min-secs=180
greeting-delay-secs=6
header-blacklist-entry=From:*>,*<*
idle-timeout-secs=60
ip-blacklist-file=/etc/spamdyke/blacklist_ip
ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords
ip-in-rdns-keyword-whitelist-file=/etc/spamdyke/whitelist_keywords
ip-whitelist-file=/etc/spamdyke/whitelist_ip
qmail-rcpthosts-file=/var/qmail/control/rcpthosts
#qmail-rcpthosts-file=/var/qmail/control/qmail-morercpthosts-cdb
log-level=info
max-recipients=50
#policy-url=http://my.policy.explanation.url/
rdns-blacklist-file=/etc/spamdyke/blacklist_rdns
rdns-whitelist-file=/etc/spamdyke/whitelist_rdns
recipient-blacklist-file=/etc/spamdyke/blacklist_recipients
recipient-whitelist-file=/etc/spamdyke/whitelist_recipients
reject-empty-rdns
#reject-ip-in-cc-rdns
reject-sender=no-mx
reject-unresolvable-rdns
sender-blacklist-file=/etc/spamdyke/blacklist_senders
sender-whitelist-file=/etc/spamdyke/whitelist_senders
tls-certificate-file=/var/qmail/control/servercert.pem
tls-level=smtp


As always, if you run into issues PLEASE let me know.

EricB.


On 3/6/2016 9:39 PM, Helmut Fritz wrote:

Thx Eric.  The below helps a lot.  Is there a recommended method?  Remove and 
install anew or upgrade?

-Original Message-
From: Eric [mailto:ebr...@whitehorsetc.com]
Sent: Sunday, March 06, 2016 2:49 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64

Helmut,

Eventually it will be in general release unless you want it there sooner, it is 
in the testing tree presently (per previous posts), though; and I've already 
implemented 5.0.1-0 on my business production server. Be mindful that if you're 
upgrading (NOT A FRESH INSTALL) spamdyke from the testing tree you'll have to 
address the below 7 options in your server's spamdyke.conf file as an upgrade 
does not overwrite existing conf file. Without the adjustments below mail will 
not be delivered.

1)  If the "reject-missing-sender-mx" option is given, it should be changed 
to
"reject-sender" with a value of "no-mx".
2) If the "rejection-text-missing-sender-mx" option is given, it should be
renamed to "rejection-text-sender-no-mx".
3) If the "reject-identical-sender-recipient" option is given, it should be
changed to "reject-recipient" with a value of "same-as-sender".
4) If the "rejection-text-identical-sender-recipient" option is given, it 
should
be renamed to "rejection-text-recipient-same-as-sender".
5) If the option "local-domains-file" is given, it should be renamed to
"qmail-rcpthosts-file".
6) If the option "local-domains-entry" is given, it should be removed.  Any
domains given with this option should be added to the file given with
"qmail-rcpthosts-file".
7) If qmail's "morercpthosts" file is provided to spamdyke with the
"qmail-rcpthosts-file" option (formerly "lcoal-domains-file"), the CDB file
should be provided instead with the "qmail-morercpthosts-cdb" option.

EricB


On 3/6/2016 2:00 PM, Helmut Fritz wrote:

Will this get rolled into the general rpms/release?

-Original Message-
From: Eric [mailto:ebr...@whitehorsetc.com]

Re: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64

[Tony White]

Hi Eric,
   Looks good except I am still on CentOS5.
How do I add your repo to my repos please?

best wishes
  Tony White

On 7/03/2016 06:09, Eric wrote:

I was a bit hasty in my creation of the rpm's as the old spamdyke.conf file should be replaced. I'll get on that and have 
the rpms up by end of day.


On 3/6/2016 9:55 AM, Eric wrote:

Be mindful that some of the setting in the old spamdyke.conf will mess with 
mail delivery.
I had to comment out 2 lines

#local-domains-file=/var/qmail/control/rcpthosts
#reject-missing-sender-mx

Eric

On 3/6/2016 9:32 AM, Eric wrote:

CentOS 6:
rpm -Uvh 
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/6/testing/x86_64/spamdyke-5.0.1-0.qt.el6.x86_64.rpm
or
# yum --enablerepo=whtc-qmt-testing update
If you have White Horse repos in your yum configuration.

CentOS7:
rpm -Uvh 
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/7/testing/x86_64/spamdyke-5.0.1-0.qt.el7.x86_64.rpm
or
# yum --enablerepo=whtc-qmt-testing update
If you have White Horse repos in your yum configuration.

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com






-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

RE: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64

[Helmut Fritz]

Thx Eric.  The below helps a lot.  Is there a recommended method?  Remove and 
install anew or upgrade?

-Original Message-
From: Eric [mailto:ebr...@whitehorsetc.com] 
Sent: Sunday, March 06, 2016 2:49 PM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64

Helmut,

Eventually it will be in general release unless you want it there sooner, it is 
in the testing tree presently (per previous posts), though; and I've already 
implemented 5.0.1-0 on my business production server. Be mindful that if you're 
upgrading (NOT A FRESH INSTALL) spamdyke from the testing tree you'll have to 
address the below 7 options in your server's spamdyke.conf file as an upgrade 
does not overwrite existing conf file. Without the adjustments below mail will 
not be delivered.

   1)  If the "reject-missing-sender-mx" option is given, it should be changed 
to
   "reject-sender" with a value of "no-mx".
   2) If the "rejection-text-missing-sender-mx" option is given, it should be
   renamed to "rejection-text-sender-no-mx".
   3) If the "reject-identical-sender-recipient" option is given, it should be
   changed to "reject-recipient" with a value of "same-as-sender".
   4) If the "rejection-text-identical-sender-recipient" option is given, it 
should
   be renamed to "rejection-text-recipient-same-as-sender".
   5) If the option "local-domains-file" is given, it should be renamed to
   "qmail-rcpthosts-file".
   6) If the option "local-domains-entry" is given, it should be removed.  Any
   domains given with this option should be added to the file given with
   "qmail-rcpthosts-file".
   7) If qmail's "morercpthosts" file is provided to spamdyke with the
   "qmail-rcpthosts-file" option (formerly "lcoal-domains-file"), the CDB file
   should be provided instead with the "qmail-morercpthosts-cdb" option.

EricB


On 3/6/2016 2:00 PM, Helmut Fritz wrote:
> Will this get rolled into the general rpms/release?
>
> -----Original Message-
> From: Eric [mailto:ebr...@whitehorsetc.com]
> Sent: Sunday, March 06, 2016 11:10 AM
> To: qmailtoaster-list@qmailtoaster.com
> Subject: Re: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64
>
> I was a bit hasty in my creation of the rpm's as the old spamdyke.conf file 
> should be replaced. I'll get on that and have the rpms up by end of day.
>
> On 3/6/2016 9:55 AM, Eric wrote:
>> Be mindful that some of the setting in the old spamdyke.conf will mess
>> with mail delivery.
>> I had to comment out 2 lines
>>
>> #local-domains-file=/var/qmail/control/rcpthosts
>> #reject-missing-sender-mx
>>
>> Eric
>>
>> On 3/6/2016 9:32 AM, Eric wrote:
>>> CentOS 6:
>>> rpm -Uvh
>>> ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/6/testing/x86_64/spamd
>>> yke-5.0.1-0.qt.el6.x86_64.rpm
>>> or
>>> # yum --enablerepo=whtc-qmt-testing update If you have White Horse
>>> repos in your yum configuration.
>>>
>>> CentOS7:
>>> rpm -Uvh
>>> ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/7/testing/x86_64/spamd
>>> yke-5.0.1-0.qt.el7.x86_64.rpm
>>>
>>> or
>>> # yum --enablerepo=whtc-qmt-testing update If you have White Horse
>>> repos in your yum configuration.
>>>
>>> -
>>> To unsubscribe, e-mail:
>>> qmailtoaster-list-unsubscr...@qmailtoaster.com
>>> For additional commands, e-mail:
>>> qmailtoaster-list-h...@qmailtoaster.com
>>>
>>
>> -
>> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
>> For additional commands, e-mail:
>> qmailtoaster-list-h...@qmailtoaster.com
>>
>
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>
>
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com
>


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64

[Eric]

Helmut,

Eventually it will be in general release unless you want it there 
sooner, it is in the testing tree presently (per previous posts), 
though; and I've already implemented 5.0.1-0 on my business production 
server. Be mindful that if you're upgrading (NOT A FRESH INSTALL) 
spamdyke from the testing tree you'll have to address the below 7 
options in your server's spamdyke.conf file as an upgrade does not 
overwrite existing conf file. Without the adjustments below mail will 
not be delivered.


  1)  If the "reject-missing-sender-mx" option is given, it should be 
changed to

  "reject-sender" with a value of "no-mx".
  2) If the "rejection-text-missing-sender-mx" option is given, it 
should be

  renamed to "rejection-text-sender-no-mx".
  3) If the "reject-identical-sender-recipient" option is given, it 
should be

  changed to "reject-recipient" with a value of "same-as-sender".
  4) If the "rejection-text-identical-sender-recipient" option is 
given, it should

  be renamed to "rejection-text-recipient-same-as-sender".
  5) If the option "local-domains-file" is given, it should be renamed to
  "qmail-rcpthosts-file".
  6) If the option "local-domains-entry" is given, it should be 
removed.  Any

  domains given with this option should be added to the file given with
  "qmail-rcpthosts-file".
  7) If qmail's "morercpthosts" file is provided to spamdyke with the
  "qmail-rcpthosts-file" option (formerly "lcoal-domains-file"), the 
CDB file

  should be provided instead with the "qmail-morercpthosts-cdb" option.

EricB


On 3/6/2016 2:00 PM, Helmut Fritz wrote:

Will this get rolled into the general rpms/release?

-Original Message-
From: Eric [mailto:ebr...@whitehorsetc.com]
Sent: Sunday, March 06, 2016 11:10 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64

I was a bit hasty in my creation of the rpm's as the old spamdyke.conf file 
should be replaced. I'll get on that and have the rpms up by end of day.

On 3/6/2016 9:55 AM, Eric wrote:

Be mindful that some of the setting in the old spamdyke.conf will mess
with mail delivery.
I had to comment out 2 lines

#local-domains-file=/var/qmail/control/rcpthosts
#reject-missing-sender-mx

Eric

On 3/6/2016 9:32 AM, Eric wrote:

CentOS 6:
rpm -Uvh
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/6/testing/x86_64/spamd
yke-5.0.1-0.qt.el6.x86_64.rpm
or
# yum --enablerepo=whtc-qmt-testing update If you have White Horse
repos in your yum configuration.

CentOS7:
rpm -Uvh
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/7/testing/x86_64/spamd
yke-5.0.1-0.qt.el7.x86_64.rpm

or
# yum --enablerepo=whtc-qmt-testing update If you have White Horse
repos in your yum configuration.

-
To unsubscribe, e-mail:
qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail:
qmailtoaster-list-h...@qmailtoaster.com



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

RE: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64

[Helmut Fritz]

Will this get rolled into the general rpms/release?

-Original Message-
From: Eric [mailto:ebr...@whitehorsetc.com] 
Sent: Sunday, March 06, 2016 11:10 AM
To: qmailtoaster-list@qmailtoaster.com
Subject: Re: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64

I was a bit hasty in my creation of the rpm's as the old spamdyke.conf file 
should be replaced. I'll get on that and have the rpms up by end of day.

On 3/6/2016 9:55 AM, Eric wrote:
> Be mindful that some of the setting in the old spamdyke.conf will mess 
> with mail delivery.
> I had to comment out 2 lines
>
> #local-domains-file=/var/qmail/control/rcpthosts
> #reject-missing-sender-mx
>
> Eric
>
> On 3/6/2016 9:32 AM, Eric wrote:
>> CentOS 6:
>> rpm -Uvh
>> ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/6/testing/x86_64/spamd
>> yke-5.0.1-0.qt.el6.x86_64.rpm
>> or
>> # yum --enablerepo=whtc-qmt-testing update If you have White Horse 
>> repos in your yum configuration.
>>
>> CentOS7:
>> rpm -Uvh
>> ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/7/testing/x86_64/spamd
>> yke-5.0.1-0.qt.el7.x86_64.rpm
>>
>> or
>> # yum --enablerepo=whtc-qmt-testing update If you have White Horse 
>> repos in your yum configuration.
>>
>> -
>> To unsubscribe, e-mail: 
>> qmailtoaster-list-unsubscr...@qmailtoaster.com
>> For additional commands, e-mail: 
>> qmailtoaster-list-h...@qmailtoaster.com
>>
>
>
> -
> To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
> For additional commands, e-mail: 
> qmailtoaster-list-h...@qmailtoaster.com
>


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64

[Eric]

I was a bit hasty in my creation of the rpm's as the old spamdyke.conf 
file should be replaced. I'll get on that and have the rpms up by end of 
day.


On 3/6/2016 9:55 AM, Eric wrote:
Be mindful that some of the setting in the old spamdyke.conf will mess 
with mail delivery.

I had to comment out 2 lines

#local-domains-file=/var/qmail/control/rcpthosts
#reject-missing-sender-mx

Eric

On 3/6/2016 9:32 AM, Eric wrote:

CentOS 6:
rpm -Uvh 
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/6/testing/x86_64/spamdyke-5.0.1-0.qt.el6.x86_64.rpm

or
# yum --enablerepo=whtc-qmt-testing update
If you have White Horse repos in your yum configuration.

CentOS7:
rpm -Uvh 
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/7/testing/x86_64/spamdyke-5.0.1-0.qt.el7.x86_64.rpm 


or
# yum --enablerepo=whtc-qmt-testing update
If you have White Horse repos in your yum configuration.

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64

[Eric]

Be mindful that some of the setting in the old spamdyke.conf will mess 
with mail delivery.

I had to comment out 2 lines

#local-domains-file=/var/qmail/control/rcpthosts
#reject-missing-sender-mx

Eric

On 3/6/2016 9:32 AM, Eric wrote:

CentOS 6:
rpm -Uvh 
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/6/testing/x86_64/spamdyke-5.0.1-0.qt.el6.x86_64.rpm

or
# yum --enablerepo=whtc-qmt-testing update
If you have White Horse repos in your yum configuration.

CentOS7:
rpm -Uvh 
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/7/testing/x86_64/spamdyke-5.0.1-0.qt.el7.x86_64.rpm 


or
# yum --enablerepo=whtc-qmt-testing update
If you have White Horse repos in your yum configuration.

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] spamdyke 5.0.1-0 CentOS 6/7 x86_64

[Eric]

CentOS 6:
rpm -Uvh 
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/6/testing/x86_64/spamdyke-5.0.1-0.qt.el6.x86_64.rpm

or
# yum --enablerepo=whtc-qmt-testing update
If you have White Horse repos in your yum configuration.

CentOS7:
rpm -Uvh 
ftp://ftp.whitehorsetc.com/pub/repo/qmt/CentOS/7/testing/x86_64/spamdyke-5.0.1-0.qt.el7.x86_64.rpm 


or
# yum --enablerepo=whtc-qmt-testing update
If you have White Horse repos in your yum configuration.

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Spamdyke 4 to 5 upgrade question

[Tony White]

Hi Eric,
  Thank you for that I appreciate your effort...
The latest version is 5 and has a couple of nice benefits.

best wishes
  Tony White

Yea Computing Services
http://www.ycs.com.au
4 The Crescent
Yea
Victoria
Australia 3717

Telephone No's
VIC : 03 9008 5614
FAX : 03 9008 5610 (FAX2Email)

Be aware: All calls to and from YCS landlines and mobiles are recorded

IMPORTANT NOTICE

This communication including any file attachments is intended solely for
the use of the individual or entity to whom it is addressed. If you are
not the intended recipient, or the person responsible for delivering
this communication to the intended recipient, please immediately notify
the sender by email and delete the original transmission and its
contents. Any unauthorised use, dissemination, forwarding, printing or
copying of this communication including file attachments is prohibited.
It is your responsibility to scan this communication including any file
attachments for viruses and other defects. To the extent permitted by
law, Yea Computing Services and its associates will not be liable for
any loss or damage arising in any way from this communication including
any file attachments.
You may not disclose this information to a third party without written
permission from the Author.

On 7/03/2016 02:02, Eric wrote:

Hi Tony,

I would think so as it sits in front of qmail and shouldn't affect it. Someone 
please correct me if I'm wrong.

I'll download the latest sources and roll an rpm. I should have done this a 
while ago.

EricB.

On 3/6/2016 12:27 AM, Tony White wrote:

Hi folks,
  Can I just download the latest spamdyke and install it?
There is no update for my QMT.




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com






-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] Spamdyke 4 to 5 upgrade question

[Tony White]

Hi folks,
  Can I just download the latest spamdyke and install it?
There is no update for my QMT.

--
best wishes
  Tony White


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke reason LOG

[Ridwan Firmansyah]

that's how i do it right now :) ,
thank's


rgds
Ridwanfi



On 09/02/2015 12:15, Eric Broch wrote:
You could go over to mxtoolbox.com and punch in the blacklisted domain 
and run a blacklist check. This could possibly reveal the BL reporter.


On 2/8/2015 8:36 PM, Ridwan Firmansyah wrote:
one of my server with spamdyke installed, did'not show reason what 
caused incoming connection being Blocked.
for example, below is right log that i need. it's show that mail 
blocked by bl.spamcop.net


spamdyke[21054]: DENIED_RBL_MATCH from: misa...@bebidaseafins.com.br 
to: m...@x.xxx origin_ip: 201.200.197.70 origin_rdns: (unknown) 
auth: (unknown) encryption: (none) _/reason: bl.spamcop.net


/_in the other hand, this is log which reason not shown,

spamdyke[7442]: DENIED_RBL_MATCH from: ces...@megared.net.mx to: 
c...@xxx. origin_ip: 177.240.67.71 origin_rdns: 
customer-gdl-67-71.megared.net.mx auth: (unknown) encryption: (none)



i have match and set all spamdyke confiq on both server but still no 
reason came up..

any Idea why this happen.

for your ref, here's my spamdyke conf
=
#dns-blacklist-entry=zombie.dnsbl.sorbs.net
dns-blacklist-entry=b.barracudacentral.org
dns-blacklist-entry=dnsbl.sorbs.net
dns-blacklist-entry=cbl.abuseat.org
dns-blacklist-entry=zen.spamhaus.org
dns-blacklist-entry=bl.spamcop.net
graylist-dir=/var/spamdyke/graylist
dns-whitelist-entry=dnswl.rpxholding.com
#graylist-level=always
graylist-max-secs=2678400
graylist-min-secs=180
greeting-delay-secs=10
idle-timeout-secs=300
ip-blacklist-file=/etc/spamdyke/blacklist_ip
ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords
ip-in-rdns-keyword-whitelist-file=/etc/spamdyke/whitelist_keywords
ip-whitelist-file=/etc/spamdyke/whitelist_ip
local-domains-file=/var/qmail/control/rcpthosts
log-level=info
log-target=stderr
max-recipients=50
#policy-url=http://my.policy.explanation.url/
rdns-blacklist-file=/etc/spamdyke/blacklist_rdns
rdns-whitelist-file=/etc/spamdyke/whitelist_rdns
recipient-blacklist-file=/etc/spamdyke/blacklist_recipients
recipient-whitelist-file=/etc/spamdyke/whitelist_recipients
#reject-empty-rdns
#reject-ip-in-cc-rdns
reject-missing-sender-mx
#reject-unresolvable-rdns
sender-blacklist-file=/etc/spamdyke/blacklist_senders
sender-whitelist-file=/etc/spamdyke/whitelist_senders
tls-certificate-file=/var/qmail/control/servercert.pem
#tls-level=smtp
==

thank's
Ridwanfi

Re: [qmailtoaster] spamdyke reason LOG

[Eric Broch]

You could go over to mxtoolbox.com and punch in the blacklisted domain
and run a blacklist check. This could possibly reveal the BL reporter.

On 2/8/2015 8:36 PM, Ridwan Firmansyah wrote:
 one of my server with spamdyke installed, did'not show reason what
 caused incoming connection being Blocked.
 for example, below is right log that i need. it's show that mail
 blocked by bl.spamcop.net

 spamdyke[21054]: DENIED_RBL_MATCH from: misa...@bebidaseafins.com.br
 to: m...@x.xxx origin_ip: 201.200.197.70 origin_rdns: (unknown)
 auth: (unknown) encryption: (none) _/reason: bl.spamcop.net

 /_in the other hand, this is log which reason not shown,

 spamdyke[7442]: DENIED_RBL_MATCH from: ces...@megared.net.mx to:
 c...@xxx. origin_ip: 177.240.67.71 origin_rdns:
 customer-gdl-67-71.megared.net.mx auth: (unknown) encryption: (none)


 i have match and set all spamdyke confiq on both server but still no
 reason came up..
 any Idea why this happen.

 for your ref, here's my spamdyke conf
 =
 #dns-blacklist-entry=zombie.dnsbl.sorbs.net
 dns-blacklist-entry=b.barracudacentral.org
 dns-blacklist-entry=dnsbl.sorbs.net
 dns-blacklist-entry=cbl.abuseat.org
 dns-blacklist-entry=zen.spamhaus.org
 dns-blacklist-entry=bl.spamcop.net
 graylist-dir=/var/spamdyke/graylist
 dns-whitelist-entry=dnswl.rpxholding.com
 #graylist-level=always
 graylist-max-secs=2678400
 graylist-min-secs=180
 greeting-delay-secs=10
 idle-timeout-secs=300
 ip-blacklist-file=/etc/spamdyke/blacklist_ip
 ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords
 ip-in-rdns-keyword-whitelist-file=/etc/spamdyke/whitelist_keywords
 ip-whitelist-file=/etc/spamdyke/whitelist_ip
 local-domains-file=/var/qmail/control/rcpthosts
 log-level=info
 log-target=stderr
 max-recipients=50
 #policy-url=http://my.policy.explanation.url/
 rdns-blacklist-file=/etc/spamdyke/blacklist_rdns
 rdns-whitelist-file=/etc/spamdyke/whitelist_rdns
 recipient-blacklist-file=/etc/spamdyke/blacklist_recipients
 recipient-whitelist-file=/etc/spamdyke/whitelist_recipients
 #reject-empty-rdns
 #reject-ip-in-cc-rdns
 reject-missing-sender-mx
 #reject-unresolvable-rdns
 sender-blacklist-file=/etc/spamdyke/blacklist_senders
 sender-whitelist-file=/etc/spamdyke/whitelist_senders
 tls-certificate-file=/var/qmail/control/servercert.pem
 #tls-level=smtp
 ==

 thank's
 Ridwanfi

[qmailtoaster] spamdyke reason LOG

[Ridwan Firmansyah]

one of my server with spamdyke installed, did'not show reason what 
caused incoming connection being Blocked.
for example, below is right log that i need. it's show that mail blocked 
by bl.spamcop.net


spamdyke[21054]: DENIED_RBL_MATCH from: misa...@bebidaseafins.com.br to: 
m...@x.xxx origin_ip: 201.200.197.70 origin_rdns: (unknown) auth: 
(unknown) encryption: (none) _/reason: bl.spamcop.net


/_in the other hand, this is log which reason not shown,

spamdyke[7442]: DENIED_RBL_MATCH from: ces...@megared.net.mx to: 
c...@xxx. origin_ip: 177.240.67.71 origin_rdns: 
customer-gdl-67-71.megared.net.mx auth: (unknown) encryption: (none)



i have match and set all spamdyke confiq on both server but still no 
reason came up..

any Idea why this happen.

for your ref, here's my spamdyke conf
=
#dns-blacklist-entry=zombie.dnsbl.sorbs.net
dns-blacklist-entry=b.barracudacentral.org
dns-blacklist-entry=dnsbl.sorbs.net
dns-blacklist-entry=cbl.abuseat.org
dns-blacklist-entry=zen.spamhaus.org
dns-blacklist-entry=bl.spamcop.net
graylist-dir=/var/spamdyke/graylist
dns-whitelist-entry=dnswl.rpxholding.com
#graylist-level=always
graylist-max-secs=2678400
graylist-min-secs=180
greeting-delay-secs=10
idle-timeout-secs=300
ip-blacklist-file=/etc/spamdyke/blacklist_ip
ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords
ip-in-rdns-keyword-whitelist-file=/etc/spamdyke/whitelist_keywords
ip-whitelist-file=/etc/spamdyke/whitelist_ip
local-domains-file=/var/qmail/control/rcpthosts
log-level=info
log-target=stderr
max-recipients=50
#policy-url=http://my.policy.explanation.url/
rdns-blacklist-file=/etc/spamdyke/blacklist_rdns
rdns-whitelist-file=/etc/spamdyke/whitelist_rdns
recipient-blacklist-file=/etc/spamdyke/blacklist_recipients
recipient-whitelist-file=/etc/spamdyke/whitelist_recipients
#reject-empty-rdns
#reject-ip-in-cc-rdns
reject-missing-sender-mx
#reject-unresolvable-rdns
sender-blacklist-file=/etc/spamdyke/blacklist_senders
sender-whitelist-file=/etc/spamdyke/whitelist_senders
tls-certificate-file=/var/qmail/control/servercert.pem
#tls-level=smtp
==

thank's
Ridwanfi

[qmailtoaster] Spamdyke-stats

[Finn Buhelt]

Hi Eric.

Am I correct that Spamdyke-stats-report.pl needs to be altered to read
the mighty maillog log file now in order to compile other than 0's in
the report ? ;-)

Cheers
Finn

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke logging switch

[Finn Buhelt]

Hi Eric.

Maybe You should put in a litle remark that users who uses fail2ban
(like me ;-))  may have to make some changes to their jail.conf file,
due to the changes of logging ?

Cheers and thanks for all Your work to make QMT what it is.

Finn


Den 10-07-2014 00:22, Eric Shubert skrev:
 In the next release of spamdyke, the configuration will be such that log
 messages will go to syslog (/var/log/maillog).
 
 The release for this change is in the testing repo, but it requires a
 manual change to the spamdyke.conf file even with an updated package.
 
 So in preparation for this, you can make this change whenever you like.
 Updating the packing from the repo isn't necessary at this time. Simply
 remove (or comment out) the
 log-target=stderr
 line in the spamdyke.conf file. The default setting is syslog, which
 will become effective immediately. You don't need to restart anything
 when changes are made to spamdyke's configuration.
 
 I've found that having all the mail messages together in a single log
 file is really quite nice. This change is in preparation for
 implementing the ELK stack for log analysis, which might be available as
 soon as early next year. In the meantime, QMT services are being
 migrated to using syslog (stock) instead of multilog (daemontools).
 
 Note, this does not apply to legacy (*-toaster) hosts (there is no
 spamdyke-toaster package).
 
 Thanks.
 

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke logging switch

[Finn Buhelt]

Hi Eric.

Maybe You should put in a litle remark that users who uses fail2ban
(like me ;-))  may have to make some changes to their jail.conf file,
due to the changes of logging ?

Cheers and thanks for all Your work to make QMT what it is.

Finn


Den 10-07-2014 00:22, Eric Shubert skrev:
 In the next release of spamdyke, the configuration will be such that log
 messages will go to syslog (/var/log/maillog).
 
 The release for this change is in the testing repo, but it requires a
 manual change to the spamdyke.conf file even with an updated package.
 
 So in preparation for this, you can make this change whenever you like.
 Updating the packing from the repo isn't necessary at this time. Simply
 remove (or comment out) the
 log-target=stderr
 line in the spamdyke.conf file. The default setting is syslog, which
 will become effective immediately. You don't need to restart anything
 when changes are made to spamdyke's configuration.
 
 I've found that having all the mail messages together in a single log
 file is really quite nice. This change is in preparation for
 implementing the ELK stack for log analysis, which might be available as
 soon as early next year. In the meantime, QMT services are being
 migrated to using syslog (stock) instead of multilog (daemontools).
 
 Note, this does not apply to legacy (*-toaster) hosts (there is no
 spamdyke-toaster package).
 
 Thanks.
 

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke logging switch

[Finn Buhelt]

Hi Eric.

Maybe You should put in a litle remark that users who uses fail2ban
(like me ;-))  may have to make some changes to their jail.conf file,
due to the changes of logging ?

Cheers and thanks for all Your work to make QMT what it is.

Finn


Den 10-07-2014 00:22, Eric Shubert skrev:
 In the next release of spamdyke, the configuration will be such that log
 messages will go to syslog (/var/log/maillog).
 
 The release for this change is in the testing repo, but it requires a
 manual change to the spamdyke.conf file even with an updated package.
 
 So in preparation for this, you can make this change whenever you like.
 Updating the packing from the repo isn't necessary at this time. Simply
 remove (or comment out) the
 log-target=stderr
 line in the spamdyke.conf file. The default setting is syslog, which
 will become effective immediately. You don't need to restart anything
 when changes are made to spamdyke's configuration.
 
 I've found that having all the mail messages together in a single log
 file is really quite nice. This change is in preparation for
 implementing the ELK stack for log analysis, which might be available as
 soon as early next year. In the meantime, QMT services are being
 migrated to using syslog (stock) instead of multilog (daemontools).
 
 Note, this does not apply to legacy (*-toaster) hosts (there is no
 spamdyke-toaster package).
 
 Thanks.
 

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] spamdyke logging switch

[Eric Shubert]

In the next release of spamdyke, the configuration will be such that log 
messages will go to syslog (/var/log/maillog).


The release for this change is in the testing repo, but it requires a 
manual change to the spamdyke.conf file even with an updated package.


So in preparation for this, you can make this change whenever you like. 
Updating the packing from the repo isn't necessary at this time. Simply 
remove (or comment out) the

log-target=stderr
line in the spamdyke.conf file. The default setting is syslog, which 
will become effective immediately. You don't need to restart anything 
when changes are made to spamdyke's configuration.


I've found that having all the mail messages together in a single log 
file is really quite nice. This change is in preparation for 
implementing the ELK stack for log analysis, which might be available as 
soon as early next year. In the meantime, QMT services are being 
migrated to using syslog (stock) instead of multilog (daemontools).


Note, this does not apply to legacy (*-toaster) hosts (there is no 
spamdyke-toaster package).


Thanks.

--
-Eric 'shubes'


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] spamdyke

[Eric Broch]

Hello list,

I am getting the following error when a local QMT user tries to send an
email to a remote hotmail account. Can anyone tell me why I would be
getting such a message in the SMTP log?

spamdyke[28592]: DENIED_OTHER from: myu...@mydomain.org to: 
remoteaddr...@hotmail.com origin_ip: some.local.ip.address origin_rdns: 
(unknown) auth: myu...@mydomain.org encryption: (none) reason: 
451_DNS_temporary_failure_(#4.5.1_-_chkuser)

EricB.


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] Spamdyke doesnt stop any spam/backscatter/entries in the blacklist_IP

[ole . johansen]

Hello,

Anyone got an idea why not the spamdyke not stopping any incoming
connection and backscatter emailing?


10-14 15:55:05 tcpserver: status: 1/100
10-14 15:55:09 CHKUSER accepted sender: from
my.em...@adress.no:my.em...@adress.no: remote
localhost:unknown:46.185.44.90 rcpt  : sender accepted
10-14 15:55:09 CHKUSER relaying rcpt: from
my.em...@adress.no:my.em...@adress.no: remote
localhost:unknown:46.185.44.90 rcpt ana.sua...@bestbuy.com : client
allowed to relay
10-14 15:55:09 policy_check: local my.em...@adress.no - remote
ana.sua...@bestbuy.com (AUTHENTICATED SENDER)
10-14 15:55:09 policy_check: policy allows transmission
10-14 15:55:09 spamdyke[2492]: ALLOWED from: my.em...@adress.no to:
ana.sua...@bestbuy.com origin_ip: 46.185.44.90 origin_rdns:
46-185-44-90-ntsn.broadband.kyivstar.net auth: my.em...@adress.no
encryption: (none) reason: 250_ok_1381758909_qp_2513
10-14 15:55:10 tcpserver: end 2492 status 0

IP: 46.185.44.90 is added to blacklist_ip
My local domain is added to blacklist_senders (my.em...@adress.no)
It is the same for host missing rdns, spamdyke doesnt stop anything

Thanks in advance for input.
B/R
Ole J



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] SpamDyke MBL_349876.UNOFFICIAL

[Dan McAllister]

Greetings all:

I have a large mailserver that just today decided that all messages with 
attachments are infected with MBL_349876.UNOFFICIAL


I have temporarily bypassed SpamDyke processing on outbound mail, but 
would prefer to put it back in.


Has anyone else run into this? If so, how did you remove it?

Thanks,

Dan McAllister

--

PLEASE TAKE NOTE OF OUR NEW ADDRESS
===
IT4SOHO, LLC
33 - 4th Street N, Suite 211
St. Petersburg, FL 33701-3806

CALL TOLL FREE:
  877-IT4SOHO

877-484-7646 Phone
727-647-7646 Local
727-490-4394 Fax

We have support plans for QMail!


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] SpamDyke does not filter relayed messages

[Amir Abbasi]

Hi,

I've insalled and configured SpamDyke recently, but it is not working on 
relayed messages. (/etc/tcprules.d/tcp.smtp is as below)

xx.xx.xx.xx:allow,RELAYCLIENT=,SENDER_NOCHECK=1,QMAILQUEUE=/var/qmail/bin/simscan,NOP0FCHECK=1

shall I configure anything else? (Like Spamassassin).

[qmailtoaster] SpamDyke configuration issue

[Amir Abbasi]

Hi,

I just use this qmail toaster server as mail server relay from a few known 
hosts, I just need sender/recipient blacklist feature and content filtering 
(header-blacklist-entry) for now, but it still does not work. Could you please 
take a look at the following configuration and help me in troubleshooting:

#dns-blacklist-entry=zombie.dnsbl.sorbs.net
#dns-blacklist-entry=dul.dnsbl.sorbs.net
#dns-blacklist-entry=bogons.cymru.com
#dns-blacklist-entry=zen.spamhaus.org
#dns-blacklist-entry=bl.spamcop.net
#graylist-dir=/var/spamdyke/graylist
#graylist-level=none
#graylist-max-secs=2678400
#graylist-min-secs=180
#greeting-delay-secs=6
#idle-timeout-secs=60
ip-blacklist-file=/etc/spamdyke/blacklist_ip
#ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords
#ip-in-rdns-keyword-whitelist-file=/etc/spamdyke/whitelist_keywords
ip-whitelist-file=/etc/spamdyke/whitelist_ip
local-domains-file=/var/qmail/control/rcpthosts
log-level=info
log-target=stderr
max-recipients=50
#policy-url=http://my.policy.explanation.url/
#rdns-blacklist-file=/etc/spamdyke/blacklist_rdns
#rdns-whitelist-file=/etc/spamdyke/whitelist_rdns
recipient-blacklist-file=/etc/spamdyke/blacklist_recipients
recipient-whitelist-file=/etc/spamdyke/whitelist_recipients
#reject-empty-rdns
#reject-ip-in-cc-rdns
#reject-missing-sender-mx
#reject-unresolvable-rdns
sender-blacklist-file=/etc/spamdyke/blacklist_senders
sender-whitelist-file=/etc/spamdyke/whitelist_senders
#tls-certificate-file=/var/qmail/control/servercert.pem
#tls-level=smtp
header-blacklist-entry=Subject: Cialis

[qmailtoaster] Spamdyke - Denied other is actually SPAM count of 5+

[Tony White]

Hi folks,
  I have an issue that I thought I had fixed for a customer.
An email is sent from one of his software providers and
makes it all the way to SIMSCAN which rejects is with a
hard reject.
  No problem I thought, I will whitelist_sender that address
but nope it still gets simscan rejected.
  Can someone suggest how I might let this one email
through without opening the floodgates to the other 97.8%
spam please?

--
best wishes
  Tony White


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] Spamdyke RDNS problem

[Fernando Endangan]

Happy New year everyone!

I hope you guys can help me fix this issue. I am not familiar with 
spamdyke but I followed the installation a few months ago. But there is 
a problem with one of our client domain and from the SMTP logs it says 
below:


@400050ef9f7c00b45604 spamdyke[14586]: DENIED_RDNS_MISSING from: 
j...@.xxto: carol@XXX.XXXorigin_ip: XXX.160.XXX.3 origin_rdns: 
(unknown) auth: (unknown) encryption: (none) reason: (empty)


I already did added John's domain from the whitelist and rcphosts and 
also the IP of their mail server but still mails from their domain could 
not get thru.


Thanks in advance. :)


Yours,
Butch


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Spamdyke Statistics error

[Brent Gardner]

On 12/19/2012 12:56 AM, Giuseppe Perna wrote:

Hello,
thanks for you replay.

@400050d172131ddcbcbc tcpserver: ok 8032
mail.server.it:192.168.xx.xx:25 :176.28.51.172::44551
@400050d17214148dbddc tcpserver: status: 26/100
@400050d17214148dc5ac tcpserver: pid 8033 from 88.135.xx.xx
@400050d17214148dc5ac tcpserver: ok 8033
mail.server.it:192.168.xx.xx:25 :88.135.155.180::39332
@400050d172153b18325c CHKUSER accepted sender: from
i...@poste.it::  remote
xtrahost.picadorltd.eu:unknown:82.113.145.166  rcpt  : sender
accepted
@400050d172153b183644 DENIED_GRAYLISTED from: i...@poste.it to:
aff...@dominio.it origin_ip: 82.113.145.166 origin_rdns:
xtrahost.picadorltd.eu auth: (unknown)
@400050d17216091ed0e4 tcpserver: end 7687 status 0
@400050d17216091ed8b4 tcpserver: status: 25/100
@400050d1721632cbe60c DENIED_RDNS_RESOLVE from: uffi...@bper.it
to: webmas...@comune.it origin_ip: 72.245.192.117 origin_rdns:
h-72-245-192-117.snfccasy.static.covad.net auth: (unknown)
@400050d1721709685d04 tcpserver: status: 26/100
@400050d1721709698db4 tcpserver: pid 8038 from 151.1.244.162
@400050d17217096a35ac tcpserver: ok 8038
mail.server.it:192.168.xx.xx:25 :151.1.244.162::40328
@400050d172170eb9a164 tcpserver: end 7903 status 0
@400050d172170eb9a54c tcpserver: status: 25/100






@400050d1722c180fe3a4 DENIED_RDNS_MISSING from:
formazi...@dirittoitalia.it to: bradamantepicare...@diominio.it
origin_ip: 151.13.210.218 origin_rdns: (unknown) auth: (unknown)
@400050d1722c1feb034c tcpserver: end 8132 status 0
@400050d1722c1feb0b1c tcpserver: status: 31/100
@400050d1722c24d5c57c tcpserver: status: 32/100
@400050d1722c24d5c964 tcpserver: pid 8134 from 151.13.210.218
@400050d1722c24d5cd4c tcpserver: ok 8134
mail.server.it:192.168.xx.xx:25 :151.13.210.218::52216
@400050d1722c2b4f68f4 DENIED_RDNS_RESOLVE from:
vir...@grupocuina.com to: ute...@dominio.it origin_ip: 122.143.143.199
origin_rdns: 199.143.143.122.adsl-pool.jlccptt.net.cn auth: (unknown)
@400050d1722d00e170e4 DENIED_RDNS_MISSING from:
formazi...@dirittoitalia.it to: ute...@dominio.it origin_ip:
151.13.210.218 origin_rdns: (unknown) auth: (unknown)
@400050d1722d0948de84 tcpserver: end 8134 status 0
@400050d1722d0948e26c tcpserver: status: 31/100
@400050d1722d0edd03fc tcpserver: status: 32/100
@400050d1722d0edd07e4 tcpserver: pid 8136 from 151.13.210.218
@400050d1722d0edd0bcc tcpserver: ok 8136
mail.server.it:192.168.70.198:25 :151.13.210.218::52217
@400050d1722d1ffb1494 tcpserver: end 8109 status 0
@400050d1722d1ffb187c tcpserver: status: 31/100
@400050d1722d26513a1c DENIED_RDNS_MISSING from:
formazi...@dirittoitalia.it to: ute...@comune.it origin_ip:
151.13.210.218 origin_rdns: (unknown) auth: (unknown)



rpm -qa |grep qmail

qmail-toaster-1.03-1.3.15
qmailadmin-toaster-1.2.11-1.3.4
qmailtoaster-plus-0.3.0-1.4.4
qmail-pop3d-toaster-1.03-1.3.15
qmailmrtg-toaster-4.2-1.3.3



qmailctl stat

authlib: up (pid 23868) 2296 seconds
clamd: up (pid 23869) 2296 seconds
imap4: up (pid 23916) 2296 seconds
imap4-ssl: up (pid 23871) 2296 seconds
pop3: up (pid 23855) 2297 seconds
pop3-ssl: up (pid 23888) 2296 seconds
send: up (pid 23889) 2296 seconds
smtp: up (pid 23854) 2296 seconds
spamd: up (pid 23890) 2296 seconds
submission: up (pid 23899) 2296 seconds
authlib/log: up (pid 23862) 2297 seconds
clamd/log: up (pid 23870) 2296 seconds
imap4/log: up (pid 23917) 2296 seconds
imap4-ssl/log: up (pid 23872) 2296 seconds
pop3/log: up (pid 23853) 2297 seconds
pop3-ssl/log: up (pid 23882) 2296 seconds
send/log: up (pid 23895) 2296 seconds
smtp/log: up (pid 23867) 2296 seconds
spamd/log: up (pid 23877) 2296 seconds
submission/log: up (pid 23887) 2296 seconds




Interesting.

These lines appear to be Spamdyke log entries:

@400050d172153b183644 DENIED_GRAYLISTED from: i...@poste.it to: 
aff...@dominio.it origin_ip: 82.113.145.166 origin_rdns: 
xtrahost.picadorltd.eu auth: (unknown)
@400050d1721632cbe60c DENIED_RDNS_RESOLVE from: uffi...@bper.it to: 
webmas...@comune.it origin_ip: 72.245.192.117 origin_rdns: 
h-72-245-192-117.snfccasy.static.covad.net auth: (unknown)
@400050d1722c180fe3a4 DENIED_RDNS_MISSING from: 
formazi...@dirittoitalia.it to: bradamantepicare...@diominio.it 
origin_ip: 151.13.210.218 origin_rdns: (unknown) auth: (unknown)
@400050d1722c2b4f68f4 DENIED_RDNS_RESOLVE from: 
vir...@grupocuina.com to: ute...@dominio.it origin_ip: 122.143.143.199 
origin_rdns: 199.143.143.122.adsl-pool.jlccptt.net.cn auth: (unknown)
@400050d1722d00e170e4 DENIED_RDNS_MISSING from: 
formazi...@dirittoitalia.it to: ute...@dominio.it origin_ip: 
151.13.210.218 origin_rdns: (unknown) auth: (unknown)
@400050d1722d26513a1c DENIED_RDNS_MISSING from: 
formazi...@dirittoitalia.it to: ute...@comune.it origin_ip: 
151.13.210.218 origin_rdns: (unknown) auth: (unknown)



But they're missing the spamdyke[pid]: component.

Here's some examples from one of my machines:

Re: [qmailtoaster] Spamdyke Statistics error

[Giuseppe Perna]

thank for you replay,
my version spamdyke is :
spamdyke 3.1.8+TLS
not support

 log-level=verbose
log-target=stderr

please help me

thanks


2012/12/19 Brent Gardner bgardnermailingli...@gmail.com:
 On 12/19/2012 12:56 AM, Giuseppe Perna wrote:

 Hello,
 thanks for you replay.

 @400050d172131ddcbcbc tcpserver: ok 8032
 mail.server.it:192.168.xx.xx:25 :176.28.51.172::44551
 @400050d17214148dbddc tcpserver: status: 26/100
 @400050d17214148dc5ac tcpserver: pid 8033 from 88.135.xx.xx
 @400050d17214148dc5ac tcpserver: ok 8033
 mail.server.it:192.168.xx.xx:25 :88.135.155.180::39332
 @400050d172153b18325c CHKUSER accepted sender: from
 i...@poste.it::  remote
 xtrahost.picadorltd.eu:unknown:82.113.145.166  rcpt  : sender
 accepted
 @400050d172153b183644 DENIED_GRAYLISTED from: i...@poste.it to:
 aff...@dominio.it origin_ip: 82.113.145.166 origin_rdns:
 xtrahost.picadorltd.eu auth: (unknown)
 @400050d17216091ed0e4 tcpserver: end 7687 status 0
 @400050d17216091ed8b4 tcpserver: status: 25/100
 @400050d1721632cbe60c DENIED_RDNS_RESOLVE from: uffi...@bper.it
 to: webmas...@comune.it origin_ip: 72.245.192.117 origin_rdns:
 h-72-245-192-117.snfccasy.static.covad.net auth: (unknown)
 @400050d1721709685d04 tcpserver: status: 26/100
 @400050d1721709698db4 tcpserver: pid 8038 from 151.1.244.162
 @400050d17217096a35ac tcpserver: ok 8038
 mail.server.it:192.168.xx.xx:25 :151.1.244.162::40328
 @400050d172170eb9a164 tcpserver: end 7903 status 0
 @400050d172170eb9a54c tcpserver: status: 25/100






 @400050d1722c180fe3a4 DENIED_RDNS_MISSING from:
 formazi...@dirittoitalia.it to: bradamantepicare...@diominio.it
 origin_ip: 151.13.210.218 origin_rdns: (unknown) auth: (unknown)
 @400050d1722c1feb034c tcpserver: end 8132 status 0
 @400050d1722c1feb0b1c tcpserver: status: 31/100
 @400050d1722c24d5c57c tcpserver: status: 32/100
 @400050d1722c24d5c964 tcpserver: pid 8134 from 151.13.210.218
 @400050d1722c24d5cd4c tcpserver: ok 8134
 mail.server.it:192.168.xx.xx:25 :151.13.210.218::52216
 @400050d1722c2b4f68f4 DENIED_RDNS_RESOLVE from:
 vir...@grupocuina.com to: ute...@dominio.it origin_ip: 122.143.143.199
 origin_rdns: 199.143.143.122.adsl-pool.jlccptt.net.cn auth: (unknown)
 @400050d1722d00e170e4 DENIED_RDNS_MISSING from:
 formazi...@dirittoitalia.it to: ute...@dominio.it origin_ip:
 151.13.210.218 origin_rdns: (unknown) auth: (unknown)
 @400050d1722d0948de84 tcpserver: end 8134 status 0
 @400050d1722d0948e26c tcpserver: status: 31/100
 @400050d1722d0edd03fc tcpserver: status: 32/100
 @400050d1722d0edd07e4 tcpserver: pid 8136 from 151.13.210.218
 @400050d1722d0edd0bcc tcpserver: ok 8136
 mail.server.it:192.168.70.198:25 :151.13.210.218::52217
 @400050d1722d1ffb1494 tcpserver: end 8109 status 0
 @400050d1722d1ffb187c tcpserver: status: 31/100
 @400050d1722d26513a1c DENIED_RDNS_MISSING from:
 formazi...@dirittoitalia.it to: ute...@comune.it origin_ip:
 151.13.210.218 origin_rdns: (unknown) auth: (unknown)



 rpm -qa |grep qmail

 qmail-toaster-1.03-1.3.15
 qmailadmin-toaster-1.2.11-1.3.4
 qmailtoaster-plus-0.3.0-1.4.4
 qmail-pop3d-toaster-1.03-1.3.15
 qmailmrtg-toaster-4.2-1.3.3



 qmailctl stat

 authlib: up (pid 23868) 2296 seconds
 clamd: up (pid 23869) 2296 seconds
 imap4: up (pid 23916) 2296 seconds
 imap4-ssl: up (pid 23871) 2296 seconds
 pop3: up (pid 23855) 2297 seconds
 pop3-ssl: up (pid 23888) 2296 seconds
 send: up (pid 23889) 2296 seconds
 smtp: up (pid 23854) 2296 seconds
 spamd: up (pid 23890) 2296 seconds
 submission: up (pid 23899) 2296 seconds
 authlib/log: up (pid 23862) 2297 seconds
 clamd/log: up (pid 23870) 2296 seconds
 imap4/log: up (pid 23917) 2296 seconds
 imap4-ssl/log: up (pid 23872) 2296 seconds
 pop3/log: up (pid 23853) 2297 seconds
 pop3-ssl/log: up (pid 23882) 2296 seconds
 send/log: up (pid 23895) 2296 seconds
 smtp/log: up (pid 23867) 2296 seconds
 spamd/log: up (pid 23877) 2296 seconds
 submission/log: up (pid 23887) 2296 seconds



 Interesting.

 These lines appear to be Spamdyke log entries:


 @400050d172153b183644 DENIED_GRAYLISTED from: i...@poste.it to:
 aff...@dominio.it origin_ip: 82.113.145.166 origin_rdns:
 xtrahost.picadorltd.eu auth: (unknown)
 @400050d1721632cbe60c DENIED_RDNS_RESOLVE from: uffi...@bper.it to:
 webmas...@comune.it origin_ip: 72.245.192.117 origin_rdns:
 h-72-245-192-117.snfccasy.static.covad.net auth: (unknown)
 @400050d1722c180fe3a4 DENIED_RDNS_MISSING from:
 formazi...@dirittoitalia.it to: bradamantepicare...@diominio.it origin_ip:
 151.13.210.218 origin_rdns: (unknown) auth: (unknown)
 @400050d1722c2b4f68f4 DENIED_RDNS_RESOLVE from: vir...@grupocuina.com
 to: ute...@dominio.it origin_ip: 122.143.143.199 origin_rdns:
 199.143.143.122.adsl-pool.jlccptt.net.cn auth: (unknown)
 @400050d1722d00e170e4 DENIED_RDNS_MISSING from:
 formazi...@dirittoitalia.it to: ute...@dominio.it origin_ip: 151.13.210.218
 origin_rdns: (unknown) auth: 

Re: [qmailtoaster] Spamdyke Statistics error

[Brent Gardner]

On 12/19/2012 10:21 AM, Giuseppe Perna wrote:

thank for you replay,
my version spamdyke is :
spamdyke 3.1.8+TLS
not support

  log-level=verbose
log-target=stderr

please help me

thanks





You should probably upgrade Spamdyke.  Version 4.3.1 is available.


Brent Gardner



-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Spamdyke Statistics error

[Brent Gardner]

On 12/17/2012 06:43 AM, Giuseppe Perna wrote:

Hi all,
I enabled statistics according to these directions,
http://wiki.qmailtoaster.com/index.php/Spamdyke#Statistics
  but when I run the command cat / var / log / qmail / smtp / current
| / usr / share / QMT / scripts / spamdyke-stats I get this error:



cat /var/log/qmail/smtp/current | /usr/share/qmt/scripts/spamdyke-stats

 Summary 
Allowed:00.00%
Timeout:00.00%
Errors :00.00%
Denied :00.00%
Total  :00.00%


i run this command whit root user.

Thanks


Guiseppe-

Will you show us some lines from /var/log/qmail/smtp/current?  Perhaps 
using pastebin?



Brent Gardneer





-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Spamdyke Statistics error

[Giuseppe Perna]

Hello,
thanks for you replay.

@400050d172131ddcbcbc tcpserver: ok 8032
mail.server.it:192.168.xx.xx:25 :176.28.51.172::44551
@400050d17214148dbddc tcpserver: status: 26/100
@400050d17214148dc5ac tcpserver: pid 8033 from 88.135.xx.xx
@400050d17214148dc5ac tcpserver: ok 8033
mail.server.it:192.168.xx.xx:25 :88.135.155.180::39332
@400050d172153b18325c CHKUSER accepted sender: from
i...@poste.it:: remote
xtrahost.picadorltd.eu:unknown:82.113.145.166 rcpt  : sender
accepted
@400050d172153b183644 DENIED_GRAYLISTED from: i...@poste.it to:
aff...@dominio.it origin_ip: 82.113.145.166 origin_rdns:
xtrahost.picadorltd.eu auth: (unknown)
@400050d17216091ed0e4 tcpserver: end 7687 status 0
@400050d17216091ed8b4 tcpserver: status: 25/100
@400050d1721632cbe60c DENIED_RDNS_RESOLVE from: uffi...@bper.it
to: webmas...@comune.it origin_ip: 72.245.192.117 origin_rdns:
h-72-245-192-117.snfccasy.static.covad.net auth: (unknown)
@400050d1721709685d04 tcpserver: status: 26/100
@400050d1721709698db4 tcpserver: pid 8038 from 151.1.244.162
@400050d17217096a35ac tcpserver: ok 8038
mail.server.it:192.168.xx.xx:25 :151.1.244.162::40328
@400050d172170eb9a164 tcpserver: end 7903 status 0
@400050d172170eb9a54c tcpserver: status: 25/100






@400050d1722c180fe3a4 DENIED_RDNS_MISSING from:
formazi...@dirittoitalia.it to: bradamantepicare...@diominio.it
origin_ip: 151.13.210.218 origin_rdns: (unknown) auth: (unknown)
@400050d1722c1feb034c tcpserver: end 8132 status 0
@400050d1722c1feb0b1c tcpserver: status: 31/100
@400050d1722c24d5c57c tcpserver: status: 32/100
@400050d1722c24d5c964 tcpserver: pid 8134 from 151.13.210.218
@400050d1722c24d5cd4c tcpserver: ok 8134
mail.server.it:192.168.xx.xx:25 :151.13.210.218::52216
@400050d1722c2b4f68f4 DENIED_RDNS_RESOLVE from:
vir...@grupocuina.com to: ute...@dominio.it origin_ip: 122.143.143.199
origin_rdns: 199.143.143.122.adsl-pool.jlccptt.net.cn auth: (unknown)
@400050d1722d00e170e4 DENIED_RDNS_MISSING from:
formazi...@dirittoitalia.it to: ute...@dominio.it origin_ip:
151.13.210.218 origin_rdns: (unknown) auth: (unknown)
@400050d1722d0948de84 tcpserver: end 8134 status 0
@400050d1722d0948e26c tcpserver: status: 31/100
@400050d1722d0edd03fc tcpserver: status: 32/100
@400050d1722d0edd07e4 tcpserver: pid 8136 from 151.13.210.218
@400050d1722d0edd0bcc tcpserver: ok 8136
mail.server.it:192.168.70.198:25 :151.13.210.218::52217
@400050d1722d1ffb1494 tcpserver: end 8109 status 0
@400050d1722d1ffb187c tcpserver: status: 31/100
@400050d1722d26513a1c DENIED_RDNS_MISSING from:
formazi...@dirittoitalia.it to: ute...@comune.it origin_ip:
151.13.210.218 origin_rdns: (unknown) auth: (unknown)



rpm -qa |grep qmail

qmail-toaster-1.03-1.3.15
qmailadmin-toaster-1.2.11-1.3.4
qmailtoaster-plus-0.3.0-1.4.4
qmail-pop3d-toaster-1.03-1.3.15
qmailmrtg-toaster-4.2-1.3.3



qmailctl stat

authlib: up (pid 23868) 2296 seconds
clamd: up (pid 23869) 2296 seconds
imap4: up (pid 23916) 2296 seconds
imap4-ssl: up (pid 23871) 2296 seconds
pop3: up (pid 23855) 2297 seconds
pop3-ssl: up (pid 23888) 2296 seconds
send: up (pid 23889) 2296 seconds
smtp: up (pid 23854) 2296 seconds
spamd: up (pid 23890) 2296 seconds
submission: up (pid 23899) 2296 seconds
authlib/log: up (pid 23862) 2297 seconds
clamd/log: up (pid 23870) 2296 seconds
imap4/log: up (pid 23917) 2296 seconds
imap4-ssl/log: up (pid 23872) 2296 seconds
pop3/log: up (pid 23853) 2297 seconds
pop3-ssl/log: up (pid 23882) 2296 seconds
send/log: up (pid 23895) 2296 seconds
smtp/log: up (pid 23867) 2296 seconds
spamd/log: up (pid 23877) 2296 seconds
submission/log: up (pid 23887) 2296 seconds

2012/12/19 Brent Gardner bgardnermailingli...@gmail.com:
 On 12/17/2012 06:43 AM, Giuseppe Perna wrote:

 Hi all,
 I enabled statistics according to these directions,
 http://wiki.qmailtoaster.com/index.php/Spamdyke#Statistics
   but when I run the command cat / var / log / qmail / smtp / current
 | / usr / share / QMT / scripts / spamdyke-stats I get this error:



 cat /var/log/qmail/smtp/current | /usr/share/qmt/scripts/spamdyke-stats

  Summary 
 Allowed:00.00%
 Timeout:00.00%
 Errors :00.00%
 Denied :00.00%
 Total  :00.00%


 i run this command whit root user.

 Thanks


 Guiseppe-

 Will you show us some lines from /var/log/qmail/smtp/current?  Perhaps using
 pastebin?


 Brent Gardneer





 -
 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] Spamdyke Statistics error

[Giuseppe Perna]

Hi all,
I enabled statistics according to these directions,
http://wiki.qmailtoaster.com/index.php/Spamdyke#Statistics
 but when I run the command cat / var / log / qmail / smtp / current
| / usr / share / QMT / scripts / spamdyke-stats I get this error:



cat /var/log/qmail/smtp/current | /usr/share/qmt/scripts/spamdyke-stats

 Summary 
Allowed:00.00%
Timeout:00.00%
Errors :00.00%
Denied :00.00%
Total  :00.00%


i run this command whit root user.

Thanks

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] spamdyke configuration

[Giuseppe Perna]

Hi all,
I would like to decrease the sensitivity and spam filter because, in
my opinion, it blocks too much email.
You think about what parameters I need to change?
Below the configuration of spamdyke,
the reports of blocked email
configure spamassassin

thanks



spamdyke.conf

#dns-blacklist-entry=zombie.dnsbl.sorbs.net
#dns-blacklist-entry=dul.dnsbl.sorbs.net
#dns-blacklist-entry=bogons.cymru.com
dns-blacklist-entry=zen.spamhaus.org
dns-blacklist-entry=bl.spamcop.net
graylist-dir=/var/spamdyke/graylist
graylist-level=always
graylist-max-secs=2678400
graylist-min-secs=180
greeting-delay-secs=6
idle-timeout-secs=60
ip-blacklist-file=/etc/spamdyke/blacklist_ip
ip-in-rdns-keyword-blacklist-file=/etc/spamdyke/blacklist_keywords
ip-in-rdns-keyword-whitelist-file=/etc/spamdyke/whitelist_keywords
ip-whitelist-file=/etc/spamdyke/whitelist_ip
local-domains-file=/var/qmail/control/rcpthosts
log-level=info
log-target=stderr
max-recipients=50
#policy-url=http://my.policy.explanation.url/
rdns-blacklist-file=/etc/spamdyke/blacklist_rdns
rdns-whitelist-file=/etc/spamdyke/whitelist_rdns
recipient-blacklist-file=/etc/spamdyke/blacklist_recipients
recipient-whitelist-file=/etc/spamdyke/whitelist_recipients
reject-empty-rdns
#reject-ip-in-cc-rdns
reject-missing-sender-mx
reject-unresolvable-rdns
sender-blacklist-file=/etc/spamdyke/blacklist_senders
sender-whitelist-file=/etc/spamdyke/whitelist_senders
tls-certificate-file=/var/qmail/control/servercert.pem
tls-level=smtp


This report was generated Mon Nov 26 11:28:56 2012


 999   36.00%  DENIED_RDNS_MISSING
 763   27.49%  DENIED_RDNS_RESOLVE
 751   27.06%  DENIED_RBL_MATCH
--- Breakdown ---
-
 1174.21%  DENIED_OTHER
  953.42%  ALLOWED
  230.82%  DENIED_EARLYTALKER
  170.61%  DENIED_SENDER_NO_MX
  100.36%  TIMEOUT

 Summary 
Allowed:   953.42%
Timeout:   100.36%
Errors :00.00%
Denied : 2670   96.21%
Total  : 2775  100.00%


/etc/mail/spamassassin/local.cf

ok_locales all
skip_rbl_checks 1

required_score 5
report_safe 0
rewrite_header Subject ***SPAM***

use_pyzor 1

use_auto_whitelist 1

use_bayes 1
use_bayes_rules 1
bayes_auto_learn 1



thanks

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke configuration

[Alessio Cecchi]

Il 27/11/2012 15:07, Giuseppe Perna ha scritto:

Hi all,
I would like to decrease the sensitivity and spam filter because, in
my opinion, it blocks too much email.
You think about what parameters I need to change?
Below the configuration of spamdyke,
the reports of blocked email
configure spamassassin

thanks



spamdyke.conf

#dns-blacklist-entry=zombie.dnsbl.sorbs.net
#dns-blacklist-entry=dul.dnsbl.sorbs.net
#dns-blacklist-entry=bogons.cymru.com
dns-blacklist-entry=zen.spamhaus.org
dns-blacklist-entry=bl.spamcop.net



Remove bl.spamcop.net, many italian ISP (Libero, Fastweb, TelecomItalia) 
are often in this list.


Ciao

--
Alessio Cecchi is:
@ ILS - http://www.linux.it/~alessice/
on LinkedIn - http://www.linkedin.com/in/alessice
Assistenza Sistemi GNU/Linux - http://www.cecchi.biz/
@ PLUG - ex-Presidente, adesso senatore a vita, http://www.prato.linux.it


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke configuration

[Giuseppe Perna]

Thanks Alessio,
my problem is this many italian ISP (Libero, Fastweb, TelecomItalia) are
often in this list.
What are your dns-blacklist-entry?
you're just using zen.spamhaus.org?
thanks


2012/11/27 Alessio Cecchi ales...@skye.it:
 Il 27/11/2012 15:07, Giuseppe Perna ha scritto:

 Hi all,
 I would like to decrease the sensitivity and spam filter because, in
 my opinion, it blocks too much email.
 You think about what parameters I need to change?
 Below the configuration of spamdyke,
 the reports of blocked email
 configure spamassassin

 thanks



 spamdyke.conf

 #dns-blacklist-entry=zombie.dnsbl.sorbs.net
 #dns-blacklist-entry=dul.dnsbl.sorbs.net
 #dns-blacklist-entry=bogons.cymru.com
 dns-blacklist-entry=zen.spamhaus.org
 dns-blacklist-entry=bl.spamcop.net


 Remove bl.spamcop.net, many italian ISP (Libero, Fastweb, TelecomItalia) are
 often in this list.

 Ciao

 --
 Alessio Cecchi is:
 @ ILS - http://www.linux.it/~alessice/
 on LinkedIn - http://www.linkedin.com/in/alessice
 Assistenza Sistemi GNU/Linux - http://www.cecchi.biz/
 @ PLUG - ex-Presidente, adesso senatore a vita, http://www.prato.linux.it



 -
 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke configuration

[Aleksander Podsiadły]

Dnia 2012-11-27, wto o godzinie 16:18 +0100, Alessio Cecchi pisze:
 Remove bl.spamcop.net, many italian ISP (Libero, Fastweb,
 TelecomItalia) 
 are often in this list. 

Don't do it. It's not the problem to remove from this list a proper
configured mail server.
You can add:
rhs-blacklist-entry=dsn.rfc-ignorant.org


-- 
Pozdrawiam/Regards,
mgr inż. Aleksander Podsiadły
st. informatyk gminy
Urząd Gminy w Mniowie
ul. Centralna 9
26-080 Mniów
tel: +48 413737002
fax: +48 413737024
mail: a...@mniow.pl
jid: a...@jabber.mniow.pl
gg: 9150578


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] spamdyke - spamassassin

[Giuseppe Perna]

Good morning to all,
I read a lot of documentation on spamdyke and spamassassin but I did
not understand a few things:

1) I have installed on my system (qnmailtoaster up date ) spamdyke
from this time spamassassin is uninstalled or work together?

2) spamdyke merely accept or reject, if a message is blocked, the
message is not saved in the spam folder of server?

3) spamassassin blocks a message, where the message can be saved?

4) the configuration file spamdyke are here: / etc / spamdyke /
to increase or decrease the sensitivity of spamdyke I can only change
these entries?
dns-blacklist-entry = zen.spamhaus.org
dns-blacklist-entry = bl.spamcop.net

5) the configuration files of spamassassin are here: / etc / mail /
spamassassin /
to increase or decrease the sensitivity of spamassassin I can only
change these entries?
required_score

thanks

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke - spamassassin

[Maxwell Smart]

On 11/18/2012 02:16 AM, Giuseppe Perna wrote:

Good morning to all,
I read a lot of documentation on spamdyke and spamassassin but I did
not understand a few things:

I'll post my understanding which is by no means gospel.


1) I have installed on my system (qnmailtoaster up date ) spamdyke
from this time spamassassin is uninstalled or work together?

They work independently.  Spamdyke blocks e mails based on it's rDNS


2) spamdyke merely accept or reject, if a message is blocked, the
message is not saved in the spam folder of server?

It's not saved, it's rejected before it ever reaches the mail server.


3) spamassassin blocks a message, where the message can be saved?
Spamassassin scans a message to determine if it's SPAM based on a score, 
then delivers the message with an appended Subject line. Default is 
***SPAM***


4) the configuration file spamdyke are here: / etc / spamdyke /
to increase or decrease the sensitivity of spamdyke I can only change
these entries?
dns-blacklist-entry = zen.spamhaus.org
dns-blacklist-entry = bl.spamcop.net

or add another dns list


5) the configuration files of spamassassin are here: / etc / mail /
spamassassin /
to increase or decrease the sensitivity of spamassassin I can only
change these entries?
required_score

Changing the score is one way.  I believe you can also us spam lists


thanks

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com




-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Spamdyke

[David Good]

On 10/29/2012 12:38 PM, Dave MacDonald wrote:

Hi List
for testing, how do I disable spamdyke?


http://wiki.qmailtoaster.com/index.php/Spamdyke

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Spamdyke

[Dave MacDonald]

Thanks for the reply.

My problem is now my mail queue willnot send,
remote queue currently 88 an going up
tried qmHandle -a

waited a bit, the qmHandle -l, still more not going out.

This is a complete rebuild, using Centos ISO, all yum and qtp-menu updates,
re-added all domains and users, tested some at random, no errors.
Now its live, email not going out of box,
Commented all out in spamdyke config. Restarted email server etc.

Please help


On Mon, Oct 29, 2012 at 11:05 AM, David Good dav...@ntcb.com wrote:

 On 10/29/2012 12:38 PM, Dave MacDonald wrote:

 Hi List
 for testing, how do I disable spamdyke?

  
 http://wiki.qmailtoaster.com/**index.php/Spamdykehttp://wiki.qmailtoaster.com/index.php/Spamdyke

 --**--**-
 To unsubscribe, e-mail: 
 qmailtoaster-list-unsubscribe@**qmailtoaster.comqmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: 
 qmailtoaster-list-help@**qmailtoaster.comqmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Spamdyke

[Cecil Yother, Jr.]

  
  
On 10/29/2012 11:19 AM, Dave MacDonald
  wrote:

Thanks for the reply.
  
  
  My problem is now my mail queue willnot send,
  remote queue currently 88 an going up
  triedqmHandle -a
  
  
  waited a bit, theqmHandle -l, still more not going out.
  
  
  This is a complete rebuild, using Centos ISO, all yum and
qtp-menu updates, re-added all domains and users, tested some at
random, no errors.
  Now its live, email not going out of box,
  
Commented all out in spamdyke config. Restarted email server
etc.
  
  
  Please help
  
  
  
On Mon, Oct 29, 2012 at 11:05 AM, David
  Good dav...@ntcb.com
  wrote:
  
On 10/29/2012 12:38 PM, Dave MacDonald
  wrote:
  
Hi List
for testing, how do I disable spamdyke?

  

http://wiki.qmailtoaster.com/index.php/Spamdyke

-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

  


  

Firewall?

-- 
  
  

Re: [qmailtoaster] Spamdyke

[Aleksander Podsiadły]

Dnia 2012-10-29, pon o godzinie 10:38 -0700, Dave MacDonald pisze:
 for testing, how do I disable spamdyke?
Go to the directory: /var/qmail/supervise/smtp
and change the symbolic link run from run.spamdyke to run.dist.

-- 
Pozdrawiam/Regards,
mgr inż. Aleksander Podsiadły
st. informatyk gminy
Urząd Gminy w Mniowie
ul. Centralna 9
26-080 Mniów
tel: +48 413737002
fax: +48 413737024
mail: a...@mniow.pl
jid: a...@jabber.mniow.pl
gg: 9150578


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Spamdyke

[Dave MacDonald]

Standard as setup with qmail iso, will drop firewall to test, and restarted
queue

am I doing the correct command to restart queue?

 qmHandle -a

Thanks all

On Mon, Oct 29, 2012 at 11:32 AM, Cecil Yother, Jr. c...@yother.com wrote:

  On 10/29/2012 11:19 AM, Dave MacDonald wrote:

 Thanks for the reply.

  My problem is now my mail queue willnot send,
 remote queue currently 88 an going up
 tried qmHandle -a

  waited a bit, the qmHandle -l, still more not going out.

  This is a complete rebuild, using Centos ISO, all yum and qtp-menu
 updates, re-added all domains and users, tested some at random, no errors.
 Now its live, email not going out of box,
  Commented all out in spamdyke config. Restarted email server etc.

  Please help


 On Mon, Oct 29, 2012 at 11:05 AM, David Good dav...@ntcb.com wrote:

 On 10/29/2012 12:38 PM, Dave MacDonald wrote:

 Hi List
 for testing, how do I disable spamdyke?

  http://wiki.qmailtoaster.com/index.php/Spamdyke

 -
 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com


  Firewall?

 --

cj's_sig.png

Re: [qmailtoaster] Spamdyke

[Dave MacDonald]

Okay, now remote mail staying at 88, but not going out,
firewall is down .
qmHandle -l
Messages in local queue: 0
Messages in remote queue: 88

Thanks


On Mon, Oct 29, 2012 at 11:36 AM, Dave MacDonald dmacd6...@gmail.comwrote:

 Standard as setup with qmail iso, will drop firewall to test, and
 restarted queue

 am I doing the correct command to restart queue?

  qmHandle -a

 Thanks all

 On Mon, Oct 29, 2012 at 11:32 AM, Cecil Yother, Jr. c...@yother.com wrote:

  On 10/29/2012 11:19 AM, Dave MacDonald wrote:

 Thanks for the reply.

  My problem is now my mail queue willnot send,
 remote queue currently 88 an going up
 tried qmHandle -a

  waited a bit, the qmHandle -l, still more not going out.

  This is a complete rebuild, using Centos ISO, all yum and qtp-menu
 updates, re-added all domains and users, tested some at random, no errors.
 Now its live, email not going out of box,
  Commented all out in spamdyke config. Restarted email server etc.

  Please help


 On Mon, Oct 29, 2012 at 11:05 AM, David Good dav...@ntcb.com wrote:

 On 10/29/2012 12:38 PM, Dave MacDonald wrote:

 Hi List
 for testing, how do I disable spamdyke?

  http://wiki.qmailtoaster.com/index.php/Spamdyke

 -
 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com


  Firewall?

 --



cj's_sig.png

Re: [qmailtoaster] Spamdyke

[Kalil Costa]

Hey,


troubleshootingsee the logs os SMTP , antispam and clamavsometimes 
spamassassin may have a problem and lock the queue.

Check your DNS too

Cecil Yother, Jr. c...@yother.com escreveu:

On 10/29/2012 11:19 AM, Dave MacDonald wrote:
 Thanks for the reply.

 My problem is now my mail queue willnot send,
 remote queue currently 88 an going up
 tried qmHandle -a

 waited a bit, the qmHandle -l, still more not going out.

 This is a complete rebuild, using Centos ISO, all yum and qtp-menu 
 updates, re-added all domains and users, tested some at random, no errors.
 Now its live, email not going out of box,
 Commented all out in spamdyke config. Restarted email server etc.

 Please help


 On Mon, Oct 29, 2012 at 11:05 AM, David Good dav...@ntcb.com 
 mailto:dav...@ntcb.com wrote:

 On 10/29/2012 12:38 PM, Dave MacDonald wrote:

 Hi List
 for testing, how do I disable spamdyke?

 http://wiki.qmailtoaster.com/index.php/Spamdyke

 -
 To unsubscribe, e-mail:
 qmailtoaster-list-unsubscr...@qmailtoaster.com
 mailto:qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail:
 qmailtoaster-list-h...@qmailtoaster.com
 mailto:qmailtoaster-list-h...@qmailtoaster.com


Firewall?

-- 

Re: [qmailtoaster] Spamdyke

[Dave MacDonald]

smtp logs show lots of  qq write error or disk full Dying due to write
operation error (disk full?).
but df -h show 134Gb free


On Mon, Oct 29, 2012 at 12:03 PM, Kalil Costa ka...@brasilsite.com.brwrote:

 Hey,


 troubleshootingsee the logs os SMTP , antispam and clamavsometimes
 spamassassin may have a problem and lock the queue.

 Check your DNS too

 Cecil Yother, Jr. c...@yother.com escreveu:


 On 10/29/2012 11:19 AM, Dave MacDonald wrote:

 Thanks for the reply.

  My problem is now my mail queue willnot send,
 remote queue currently 88 an going up
 tried qmHandle -a

  waited a bit, the qmHandle -l, still more not going out.

  This is a complete rebuild, using Centos ISO, all yum and qtp-menu
 updates, re-added all domains and users, tested some at random, no errors.
 Now its live, email not going out of box,
  Commented all out in spamdyke config. Restarted email server etc.

  Please help


 On Mon, Oct 29, 2012 at 11:05 AM, David Good dav...@ntcb.com wrote:

 On 10/29/2012 12:38 PM, Dave MacDonald wrote:

 Hi List
 for testing, how do I disable spamdyke?

  http://wiki.qmailtoaster.com/index.php/Spamdyke

 -
 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com


  Firewall?

 --

Re: [qmailtoaster] Spamdyke

[Dave MacDonald]

 Also client getting error 451 qq trouble creating files in queue ( #4.3.0 )

Re: [qmailtoaster] Spamdyke

[Dave MacDonald]

this is gonna cost me my job,

anyone do email hosting?

Re: [qmailtoaster] Spamdyke

[Postmaster]

Please post /var/qmail/queue permissions here



On 29/10/2012 20:24, Dave MacDonald wrote:


Also client getting error 451 qq trouble creating files in queue (
#4.3.0 )

Re: [qmailtoaster] Spamdyke

[Kalil Costa]

Copy and paste these errors for us

Dave MacDonald dmacd6...@gmail.com escreveu:

smtp logs show lots of  qq write error or disk full Dying due to write
operation error (disk full?).
but df -h show 134Gb free


On Mon, Oct 29, 2012 at 12:03 PM, Kalil Costa ka...@brasilsite.com.brwrote:

 Hey,


 troubleshootingsee the logs os SMTP , antispam and clamavsometimes
 spamassassin may have a problem and lock the queue.

 Check your DNS too

 Cecil Yother, Jr. c...@yother.com escreveu:


 On 10/29/2012 11:19 AM, Dave MacDonald wrote:

 Thanks for the reply.

  My problem is now my mail queue willnot send,
 remote queue currently 88 an going up
 tried qmHandle -a

  waited a bit, the qmHandle -l, still more not going out.

  This is a complete rebuild, using Centos ISO, all yum and qtp-menu
 updates, re-added all domains and users, tested some at random, no errors.
 Now its live, email not going out of box,
  Commented all out in spamdyke config. Restarted email server etc.

  Please help


 On Mon, Oct 29, 2012 at 11:05 AM, David Good dav...@ntcb.com wrote:

 On 10/29/2012 12:38 PM, Dave MacDonald wrote:

 Hi List
 for testing, how do I disable spamdyke?

  http://wiki.qmailtoaster.com/index.php/Spamdyke

 -
 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com


  Firewall?

 --

Re: [qmailtoaster] Spamdyke

[Dave MacDonald]

@4000508eda9f3977dc54 tcpserver: end 5233 status 0
@4000508eda9f3977e424 tcpserver: status: 10/100
@4000508edaa01b6a5d2c tcpserver: end 5253 status 0
@4000508edaa01b6a9f94 tcpserver: status: 9/100
@4000508edaa01db73f14 qmail-dk:[5239]: Dying due to write operation
error (disk full?).
@4000508edaa01dbaf064 qmail-smtpd: qq soft reject (qq write error or
disk full (#4.3.0)): MAILFROM:

tons more:

On Mon, Oct 29, 2012 at 12:39 PM, Kalil Costa ka...@brasilsite.com.brwrote:

 Copy and paste these errors for us

 Dave MacDonald dmacd6...@gmail.com escreveu:


 smtp logs show lots of  qq write error or disk full Dying due to write
 operation error (disk full?).
 but df -h show 134Gb free


 On Mon, Oct 29, 2012 at 12:03 PM, Kalil Costa ka...@brasilsite.com.brwrote:

 Hey,


 troubleshootingsee the logs os SMTP , antispam and
 clamavsometimes spamassassin may have a problem and lock the queue.

 Check your DNS too

 Cecil Yother, Jr. c...@yother.com escreveu:


 On 10/29/2012 11:19 AM, Dave MacDonald wrote:

 Thanks for the reply.

  My problem is now my mail queue willnot send,
 remote queue currently 88 an going up
 tried qmHandle -a

  waited a bit, the qmHandle -l, still more not going out.

  This is a complete rebuild, using Centos ISO, all yum and qtp-menu
 updates, re-added all domains and users, tested some at random, no errors.
 Now its live, email not going out of box,
  Commented all out in spamdyke config. Restarted email server etc.

  Please help


 On Mon, Oct 29, 2012 at 11:05 AM, David Good dav...@ntcb.com wrote:

 On 10/29/2012 12:38 PM, Dave MacDonald wrote:

 Hi List
 for testing, how do I disable spamdyke?

  http://wiki.qmailtoaster.com/index.php/Spamdyke

 -
 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com


  Firewall?

 --

Re: [qmailtoaster] Spamdyke

[Kalil Costa]

See permission in var queue and user maildir.

Dave MacDonald dmacd6...@gmail.com escreveu:

@4000508eda9f3977dc54 tcpserver: end 5233 status 0
@4000508eda9f3977e424 tcpserver: status: 10/100
@4000508edaa01b6a5d2c tcpserver: end 5253 status 0
@4000508edaa01b6a9f94 tcpserver: status: 9/100
@4000508edaa01db73f14 qmail-dk:[5239]: Dying due to write operation
error (disk full?).
@4000508edaa01dbaf064 qmail-smtpd: qq soft reject (qq write error or
disk full (#4.3.0)): MAILFROM:

tons more:

On Mon, Oct 29, 2012 at 12:39 PM, Kalil Costa ka...@brasilsite.com.brwrote:

 Copy and paste these errors for us

 Dave MacDonald dmacd6...@gmail.com escreveu:


 smtp logs show lots of  qq write error or disk full Dying due to write
 operation error (disk full?).
 but df -h show 134Gb free


 On Mon, Oct 29, 2012 at 12:03 PM, Kalil Costa ka...@brasilsite.com.brwrote:

 Hey,


 troubleshootingsee the logs os SMTP , antispam and
 clamavsometimes spamassassin may have a problem and lock the queue.

 Check your DNS too

 Cecil Yother, Jr. c...@yother.com escreveu:


 On 10/29/2012 11:19 AM, Dave MacDonald wrote:

 Thanks for the reply.

  My problem is now my mail queue willnot send,
 remote queue currently 88 an going up
 tried qmHandle -a

  waited a bit, the qmHandle -l, still more not going out.

  This is a complete rebuild, using Centos ISO, all yum and qtp-menu
 updates, re-added all domains and users, tested some at random, no errors.
 Now its live, email not going out of box,
  Commented all out in spamdyke config. Restarted email server etc.

  Please help


 On Mon, Oct 29, 2012 at 11:05 AM, David Good dav...@ntcb.com wrote:

 On 10/29/2012 12:38 PM, Dave MacDonald wrote:

 Hi List
 for testing, how do I disable spamdyke?

  http://wiki.qmailtoaster.com/index.php/Spamdyke

 -
 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com


  Firewall?

 --

Re: [qmailtoaster] Spamdyke

[Dave MacDonald]

See permission in var queue and user maildir

/var/queue 777 qmail:qmails
Maildir 700 vchkpw:vpopmail 700

Thanks

Re: [qmailtoaster] Spamdyke

[Postmaster]

Are you sure this is the correct queue folder?

Normally queue is in /var/qmail with the following permissions:
drwxr-x--- 11 qmailq qmail 4096 Apr 22  2012 queue

By the way, the maildir is:
-rw--- 1 vpopmail vchkpw



On 29/10/2012 20:55, Dave MacDonald wrote:

See permission in var queue and user maildir

/var/queue 777 qmail:qmails
Maildir 700 vchkpw:vpopmail 700

Thanks





-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Fwd: Re: [qmailtoaster] Spamdyke

[Postmaster]

The permission in /var/qmail/queue look alright to me


Check /var/qmail/bin/ permissions:
lrwxrwxrwx 1 root root 16 Apr 1 20:22 qmail-queue -qmail-queue.orig
-rws--x--x 1 qmailq qmail 24776 Mar 29 10:19 qmail-queue.orig


Check the user/group id problem please.
Vpopmail  -89
vchkuser  - 89


Let us know.
Rgds
Alex



On 29/10/2012 20:40, Dave MacDonald wrote:



On Mon, Oct 29, 2012 at 12:37 PM, Postmaster 
postmas...@seawise-chartering.co.uk 
mailto:postmas...@seawise-chartering.co.uk wrote:


Please post /var/qmail/queue permissions here

 ls -al /var/qmail

drwxrwxrwx 11 qmailq qmail 4096 Oct 26 10:39 queue

and inside: ls -al  /var/qmail/queue

drwxr-xr-x 12 root   qmail 4096 Oct 26 10:52 ..
drwx--  2 qmails qmail 4096 Oct 29 12:51 bounce
drwx-- 25 qmails qmail 4096 Oct 26 10:39 info
drwx--  2 qmailq qmail 4096 Oct 29 12:08 intd
drwx-- 25 qmails qmail 4096 Oct 26 10:39 local
drwxr-x---  2 qmailq qmail 4096 Oct 26 10:57 lock
drwxr-x--- 25 qmailq qmail 4096 Oct 26 10:39 mess
drwx--  2 qmailq qmail 4096 Oct 29 12:08 pid
drwx-- 25 qmails qmail 4096 Oct 26 10:39 remote
drwxr-x---  2 qmailq qmail 4096 Oct 29 12:08 todo


On 29/10/2012 20:24, Dave MacDonald wrote:


Also client getting error 451 qq trouble creating files in
queue ( #4.3.0 )

Re: [qmailtoaster] Spamdyke

[Dave MacDonald]

Sorry typo:

it is /var/qmail/ and I reset to 777 to test


And Maildirs are:
drwx--  9 vpopmail vchkpw

Thanks

On Mon, Oct 29, 2012 at 1:00 PM, Postmaster 
postmas...@seawise-chartering.co.uk wrote:

 Are you sure this is the correct queue folder?

 Normally queue is in /var/qmail with the following permissions:
 drwxr-x--- 11 qmailq qmail 4096 Apr 22  2012 queue

 By the way, the maildir is:
 -rw--- 1 vpopmail vchkpw




 On 29/10/2012 20:55, Dave MacDonald wrote:

 See permission in var queue and user maildir

 /var/queue 777 qmail:qmails
 Maildir 700 vchkpw:vpopmail 700

 Thanks




 --**--**-
 To unsubscribe, e-mail: 
 qmailtoaster-list-unsubscribe@**qmailtoaster.comqmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: 
 qmailtoaster-list-help@**qmailtoaster.comqmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] spamdyke-stats.pl giving zero's again

[Tony White]

Hi folks,
  Sorry about this, I am sure we discussed this issue before but I am unable to
find out how to fix it again.

[root@myserver scripts]# cat /var/log/qmail/smtp/current | ./spamdyke-stats

 Summary 
Allowed:00.00%
Timeout:00.00%
Errors :00.00%
Denied :00.00%
Total  :00.00%

  Is the result and nothing more. Can someone please illuminate the darkness 
again please?
This happened after the last update using qtp-newmodel.

--
best wishes
  Tony White

Yea Computing Services
http://www.ycs.com.au
4 The Crescent
Yea
Victoria
Australia 3717

Telephone No's
VIC : 03 9008 5614
FAX : 03 9008 5610 (FAX2Email)



IMPORTANT NOTICE

This communication including any file attachments is intended solely for
the use of the individual or entity to whom it is addressed. If you are
not the intended recipient, or the person responsible for delivering
this communication to the intended recipient, please immediately notify
the sender by email and delete the original transmission and its
contents. Any unauthorised use, dissemination, forwarding, printing or
copying of this communication including file attachments is prohibited.
It is your responsibility to scan this communication including any file
attachments for viruses and other defects. To the extent permitted by
law, Yea Computing Services and its associates will not be liable for
any loss or damage arising in any way from this communication including
any file attachments.
You may not disclose this information to a third party without written
permission from the Author.


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke-stats.pl giving zero's again

[Aleksander Podsiadły]

Dnia 2012-08-26, nie o godzinie 02:24 +1000, Tony White pisze:
 This happened after the last update using qtp-newmodel.

8--
cd /var/qmail/supervise/smtp
rm run
ln -s run.spamdyke run.spamdyke
service qmail restart
8-- EOT

-- 
Pozdrawiam/Regards,
mgr inż. Aleksander Podsiadły
st. informatyk gminy
Urząd Gminy w Mniowie
ul. Centralna 9
26-080 Mniów
tel: +48 413737002
fax: +48 413737024
mail: a...@mniow.pl
jid: a...@jabber.mniow.pl
gg: 9150578


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] spamdyke-stats.pl giving zero's again

[Aleksander Podsiadły]

Dnia 2012-08-25, sob o godzinie 19:11 +0200, Aleksander Podsiadły pisze:
 ln -s run.spamdyke run.spamdyke

My mistake:
ln -s run.spamdyke run
sorry!

-- 
Pozdrawiam/Regards,
mgr inż. Aleksander Podsiadły
st. informatyk gminy
Urząd Gminy w Mniowie
ul. Centralna 9
26-080 Mniów
tel: +48 413737002
fax: +48 413737024
mail: a...@mniow.pl
jid: a...@jabber.mniow.pl
gg: 9150578


-
To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] Spamdyke rdns filter

[Sylco S.r.l. - Alberto Maffini]

Dear all, I set up a filter only qmailtoaster server to put in front of an 
exchange server (sigh) following the Jake's video on youtube. Now my situation 
is the following

I ofcourse enabled spamdyke.

I have an hylafax server in internal network that want to send notification at 
the internal exchange server but it's refused ..

@4000500674dc07e5dbb4 tcpserver: pid 23213 from 192.168.1.253
@4000500674dc07e5df9c tcpserver: ok 23213 
mailfront.sylco.local:192.168.1.90:25 :192.168.1.253::40774
@4000500674e70d8ddb34 CHKUSER accepted sender: from 
f...@fax.sylcomed.com:: remote fax.sylcomed.com:unknown:192.168.1.253 rcpt 
 : sender accepted
@4000500674e70da74704 spamdyke[23213]: DENIED_RDNS_MISSING from: 
f...@fax.sylcomed.com to: na...@sylcomed.com origin_ip: 192.168.1.253 
origin_rdns: (unknown) auth: (unknown) encryption: TLS reason: (empty)
@4000500674e70db4cfdc tcpserver: end 23213 status 0

but if I dig the faxserver at the local dns server I get the correct answer 
(the faxserver is only listed in the internal dns not on the external public 
dns)

[root@mailfront ~]# dig -x 192.168.1.251

;  DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el5_8.1  -x 192.168.1.251
;; global options:  printcmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NOERROR, id: 32081
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;251.1.168.192.in-addr.arpa.IN  PTR

;; ANSWER SECTION:
251.1.168.192.in-addr.arpa. 3600 IN PTR fax.sylcomed.com.

;; Query time: 1 msec
;; SERVER: 192.168.1.203#53(192.168.1.203)
;; WHEN: Wed Jul 18 11:08:19 2012
;; MSG SIZE  rcvd: 74

Am I missing something, can you put me in the right direction ?

Is there a way to let the internal faxserver send mail throught without 
spamdyke check ? I tried to add the following lines in the spamdyke.conf 
without success

local-domains-entry=sylcomed.com
local-domains-entry=fax.sylcomed.com


Thanks in advance

Alberto Maffini

CHIUSURA PER FERIE ESTIVE:

Dal 10/08/2012 al 17/08/2012 compresi.

Dal 20 /08/2012 al 24/08/2012 apertura solo al mattino dalle 9.00 alle 13.00

Nei mesi di luglio ed agosto il venerdì apertura solo al mattino dalle 9.00 
alle 13.00

Le informazioni contenute nel presente documento sono riservate, soggette al 
segreto professionale e destinate all'uso esclusivo del destinatario sopra 
indicato. Qualora, per errore di invio o trasmissione, pervenisse a persona 
diversa, preghiamo di contattarci immediatamente, avvertendo che la ritenzione, 
l'uso indebito e la diffusione non espressamente autorizzata del documento e 
delle informazioni in esso contenute potranno comportare la violazione degli 
art. 616 e seguenti del codice penale, nonche' ai sensi del D.Lgs. 196/2003. 
Per l'informativa sulla tutela dei dati e per ogni comunicazione relativa al 
D.Lgs. 196/2003 Codice della Privacy collegarsi al sito 
webhttps://remote.sylcomed.com/OWA/redir.aspx?C=2ad283a6ff644d189b4eab8150a3d13bURL=http%3a%2f%2fwww.parlamento.it%2fparlam%2fleggi%2fdeleghe%2f03196dl.htm.

According to Italian law (D.Lgs. 30.06.2003 n. 196) this message may contain 
confidential information and is intended solely for the use by the addressee. 
It may contain privileged and confidential information. If you are not the 
person or organisation to whom it is addressed, it is prohibited for you to 
copy, distribute or take any action in reliance upon it. If you have received 
this email in error, please notify us immediately by telephone, fax or email 
and return the original message to us. Please note that email communication is 
not completely secure and whilst we will endeavour to maintain security we 
cannot be responsible for any breach of confidentiality that may result from 
such a communication.

P Before printing this message please consider it's effect to our environment.

[qmailtoaster] Spamdyke/SpamAssassin blacklisting

[Casey Price]

Is the blacklisting function used by spamdyke  spamassassin case 
sensitive? For example, would blacklisting j...@domain.com effectively 
blacklist j...@domain.com as well?


Thanks,

--
Casey Price

Smile Global Technical Support
Submit or check trouble tickets http://billing.smileglobal.com
www.smileglobal.com http://www.smileglobal.com

Follow us on Twitter https://twitter.com/#%21/SmileInternet
Find us on Facebook https://www.facebook.com/smileglobal

Re: [qmailtoaster] Spamdyke-Stats-Report script no longer working

[Brent Gardner]

On 03/06/2012 08:25 PM, Tony White wrote:

Hello again,
  Thanks to Eric and to Brent but neither seem to be the issue.
I have updated spamdyke and check the script at the command
line and still only gets zeros for results! Also no errors reported at
the command line.
Do you run the script as root or as an unprivileged user?  By default, 
unprivileged users don't have read rights to the qmail logs.  If you had 
changed rights on the qmail log directories to allow access to 
unprivileged users, the qtp-newmodel process appears to reset the rights 
back to the stricter defaults.



Brent Gardner

-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.

 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Spamdyke-Stats-Report script no longer working

[Brent Gardner]

On 03/06/2012 01:58 PM, Tony White wrote:

Hello all,
  Since the last qtp-newmodel the spamdyke report generator
only reports zeros.
  I have looked through the list but can only find a few comments
on historical reasons. I am sure I made no changes to the server
that might have caused this issue.
  Does anyone else have this issue please? Can anyone think
of a reason it might have stopped working? All the permissions
appear to be the same!


Tony-

Try running it from command line:

# cat /var/log/qmail/smtp/current | /usr/share/qmt/scripts/spamdyke-stats


See if it returns any errors.

Also, if your spamdyke is set to log to /var/log/maillog, cat that file 
instead of /var/log/qmail/smtp/current.



Brent Gardner



-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.

 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Spamdyke-Stats-Report script no longer working

[Tony White]

Hello again,
  Thanks to Eric and to Brent but neither seem to be the issue.
I have updated spamdyke and check the script at the command
line and still only gets zeros for results! Also no errors reported at
the command line.
  I have noticed getting more spam through since the update though!

best wishes
  Tony White



On 07/03/2012 08:18, Brent Gardner wrote:

On 03/06/2012 01:58 PM, Tony White wrote:

Hello all,
  Since the last qtp-newmodel the spamdyke report generator
only reports zeros.
  I have looked through the list but can only find a few comments
on historical reasons. I am sure I made no changes to the server
that might have caused this issue.
  Does anyone else have this issue please? Can anyone think
of a reason it might have stopped working? All the permissions
appear to be the same!


Tony-

Try running it from command line:

# cat /var/log/qmail/smtp/current | /usr/share/qmt/scripts/spamdyke-stats


See if it returns any errors.

Also, if your spamdyke is set to log to /var/log/maillog, cat that file instead 
of /var/log/qmail/smtp/current.


Brent Gardner



-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.
 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com






-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.

 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

[qmailtoaster] spamdyke disabled after update

[Peter Peltonen]

Hi,

I recently updated my box using qtp-newmodel. After that I noticed an
increased number of spam.

I found out that the symlink /var/qmail/supervise/smtp/run pointing to
/var/qmail/supervise/smtp/run.spamdyke had been replaced with the
default run file.

Restoring the symlink and restarting qmail solved the issue,  but I
don't think this is the wanted behaviour, and it should have been
created as /var/qmail/supervise/smtp/run.rpmnew instead?

Best,
Peter

-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
  If you need professional help with your setup, contact them today!
-
 Please visit qmailtoaster.com for the latest news, updates, and packages.
 
  To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com
 For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com

Re: [qmailtoaster] Spamdyke-Stats-Report script no longer working

[Brent Gardner]

Casey Price wrote:
I'm having a problems on one of my toasters...just updated with 
qtp-newmodel and now I'm having trouble with the 
Spamdyke-Stats-Report.pl script. It runs without error, but the email 
that it sends out an email without any stats:


 Summary 
Allowed:00.00%
Timeout:00.00%
Errors :00.00%
Denied :00.00%
Total  :00.00%

However, when I run the following command: cat 
/var/log/qmail/smtp/current | ./spamdyke-stats


I get the following:

6998   46.77%  DENIED_GRAYLISTED
5780   38.63%  DENIED_RDNS_MISSING
11867.92%  ALLOWED
 6904.61%  DENIED_RBL_MATCH
--- Breakdown ---
-
 1541.02%  DENIED_SENDER_NO_MX
 1511.00%  TIMEOUT
   10.00%  DENIED_OTHER

 Summary 
Allowed: 11867.92%
Timeout:  1511.00%
Errors :00.00%
Denied :13623   91.06%
Total  :14960  100.00%

Any idea why? I was having a few issues with perl modules installed 
from CPAN, so I went through and made sure everything was up to date. 
It was working fine up until a few days ago, and I'm fairly certain 
the only the I've changed on my end was updating QMT.


Any ideas?

Thanks!

Casey Price

Smile Global Technical Support
Submit or check trouble tickets http://billing.smileglobal.com
www.smileglobal.com http://www.smileglobal.com

Follow us on Twitter https://twitter.com/#%21/SmileInternet
Like us on Facebook https://www.facebook.com/smileglobal
In the Spamdyke-Stats-Report.pl script, there's $ScriptRoot, $TempFile 
and $SMTPLogRoot.  Check the rights on these to make sure they weren't 
changed.


I updated clam the other day using qtp-newmodel and I had to fix rights 
on /var/log/qmail/smtp.  Some of my scripts I was running interactively 
weren't working right because of this.  I fixed the rights issue before 
the daily report jobs ran, so I don't know if they would have been affected.



Brent Gardner



-
Qmailtoaster is sponsored by Vickers Consulting Group 
(www.vickersconsulting.com)
   Vickers Consulting Group offers Qmailtoaster support and installations.
 If you need professional help with your setup, contact them today!
-
Please visit qmailtoaster.com for the latest news, updates, and packages.

 To unsubscribe, e-mail: qmailtoaster-list-unsubscr...@qmailtoaster.com

For additional commands, e-mail: qmailtoaster-list-h...@qmailtoaster.com