Follow-up: Resolving rDNS with CNAME

Hi all,

I've started using spamdyke recently and ran into the same problem
described in the thread from Oct. 23rd with the same subject.

AFAI can see the rejection is based on the rDNS being determined as
<hostname>. without the domain part.
This <hostname>. itself does not resolve to an ip-address hence the
rejection.

The thread ends with a private message request with additional (real)
information.

Has this led to a resolution for the problem?

Thanks.

Kind regards,

Ton

Re: Follow-up: Resolving rDNS with CNAME

Hi,

I've been doing some testing using the util 'dnsptr'. This sample
returns, in its original form, the correct answer for the following ip:
217.110.117.8   (profi-1.wetteronline.de)

I've copied the following lines (280 - 290) from spamdyke/dns.c into
dnsptr.c and modified the usage of structures to single variables:

---- dns.c -----
                tmp_ptr = answer_ptr;
                while (((tmp_ptr - answer_ptr) < size) &&
                       ((txt_length = tmp_ptr[0]) > 0))
                  {
                  tmp_ptr[0] = '.';
                  tmp_ptr += txt_length + 1;
                  }

                current_settings->strlen_server_name = MINVAL(MAX_BUF,
size - 2);
                for (i = 0; i < current_settings->strlen_server_name; i++)
                  current_settings->server_name[i] =
tolower((int)(answer_ptr + 1)[i]);
--------------

Now the dnsptr program issues a servername of 'profi-1.wetteronline.'.

The difference seems to be in the usage of the dn_expand function in the
original whereby the correct domainname is determined.
I've been reading up on "domain name compression" and as far as I can

Re: graylisting

_______________________________________________
spamdyke-users mailing list
spamdyke-users@...
http://www.spamdyke.org/mailman/listinfo/spamdyke-users

New version: spamdyke 3.1.0

After much work, spamdyke 3.1.0 is ready:
	http://www.spamdyke.org/

NEW FEATURES:
   Rewritten/refactored DNS query code now allows much faster lookups
and timeouts.  Testing shows 10x speed improvement in some situations 
(your mileage may vary).
   Data reading and writing now moves as much data as possible in each
system call (up to 4K), not one byte at a time.  This greatly improves 
performance and reduces system load!
   Faster option processing -- reduced startup time.
   The "graylist-dir" and "no-graylist-dir" options can now be used
multiple times to search multiple graylist folders for a domain folder.
   The "ip-in-rdns-keyword-file" now allows top-level domains to be
listed.  This will allow blocking _some_ country code domains instead of
blocking them all with "reject-ip-in-cc-rdns".
   Log messages can now be sent to stderr instead of syslog.

NEW CONFIG-TEST FEATURES:
   spamdyke will now test its own binary and complain if its permissions
are incorrect.
   spamdyke will now test qmail for SMTP AUTH support (and recommend 
correct options).
   spamdyke will now test SMTP AUTH command for encryption support (and 
recommend correct options).
   The new "config-test-user" option will change user identities so the 
tests will run as the mailserver's user (filesystem permission checks 
will be correct).
   File types are now correctly reported, even on uncooperative
filesystems (XFS on Linux) or uncooperative operating systems (Solaris).

MAJOR BUG FIXES:
   Now compiles on 64 bit Linux and Solaris.
   Invalid qmail or SMTP AUTH commands (typos) will now fail with an
error message instead of failing silently.
   Frozen/locked/blocked/hung qmail or SMTP AUTH commands will now
timeout and be terminated by spamdyke instead of blocking forever.
   spamdyke will no longer crash if a qmail or SMTP AUTH command exits
while spamdyke is sending data.

MINOR BUG FIXES:
   Too numerous to list here -- see the Changelog file for details.

Version 3.1.0 is backwards-compatible with version 3.0.1; simply
replacing the old binary with the new one should be safe.

-- Sam Clippinger

Re: Follow-up: Resolving rDNS with CNAME

You're exactly right -- attempting to expand the name without using 
dn_expand() was the problem.  Thanks for doing so much research on it!

I've fixed this code in version 3.1.0 (just released).

-- Sam Clippinger

Ton van Rosmalen wrote:
> Hi,
> 
> I've been doing some testing using the util 'dnsptr'. This sample
> returns, in its original form, the correct answer for the following ip:
> 217.110.117.8   (profi-1.wetteronline.de)
> 
> I've copied the following lines (280 - 290) from spamdyke/dns.c into
> dnsptr.c and modified the usage of structures to single variables:
> 
> ---- dns.c -----
>                 tmp_ptr = answer_ptr;
>                 while (((tmp_ptr - answer_ptr) < size) &&
>                        ((txt_length = tmp_ptr[0]) > 0))
>                   {
>                   tmp_ptr[0] = '.';
>                   tmp_ptr += txt_length + 1;
>                   }
> 
>                 current_settings->strlen_server_name = MINVAL(MAX_BUF,
> size - 2);
>                 for (i = 0; i < current_settings->strlen_server_name; i++)
>                   current_settings->server_name[i] =
> tolower((int)(answer_ptr + 1)[i]);
> --------------
> 
> Now the dnsptr program issues a servername of 'profi-1.wetteronline.'.
> 
> The difference seems to be in the usage of the dn_expand function in the
> original whereby the correct domainname is determined.
> I've been reading up on "domain name compression" and as far as I can
> see the above code doesn't take these 'backreferences' into account.
> 
> Hope this helps in creating a solution.
> 
> Kind regards,
> 
> Ton
> 
> Ton van Rosmalen schreef:
>> Hi all,
>>
>> I've started using spamdyke recently and ran into the same problem
>> described in the thread from Oct. 23rd with the same subject.
>>
>> AFAI can see the rejection is based on the rDNS being determined as
>> <hostname>. without the domain part.
>> This <hostname>. itself does not resolve to an ip-address hence the
>> rejection.
>>
>> The thread ends with a private message request with additional (real)
>> information.
>>
>> Has this led to a resolution for the problem?
>>
>> Thanks.
>>
>> Kind regards,
>>
>> Ton
>> _______________________________________________
>> spamdyke-users mailing list
>> spamdyke-users@...
>> http://www.spamdyke.org/mailman/listinfo/spamdyke-users
>>   
> _______________________________________________
> spamdyke-users mailing list
> spamdyke-users@...
> http://www.spamdyke.org/mailman/listinfo/spamdyke-users

Re: graylisting

No.  You only need to create folders for the domains you host.

For example, if you host the domain "widgetcompany.com", you must create 
a folder for that domain:
	mkdir -p /tmp/graylist.d/widgetcompany.com
Then give spamdyke the graylist folder:
	spamdyke --graylist-dir /tmp/graylist.d

That's it.  spamdyke will do the rest.

-- Sam Clippinger

night duke wrote:
> Sorry i'm a little bit lost with graylisting...
> 
> I must add manually the domains from where i want to receive emails from?
> 
> Thanks a lot
> 
> Nightduke
> 
> */Filip RembiaÅ‚kowski <plk.zuber@...>/* escribió:
> 
>     2007/10/4, davide bozzelli :
>      > night duke ha scritto:
>      > > So i must add only my domains there.I must add the domains from
>     where
>      > > i want to receive?
>      > >
>      > Yes, more precisely the domain(s) you want to enable graylist for.
> 
>     hehe
>     "Yes, more precisely, no."
> 
> 
>     -- 
>     Filip Rembiałkowski
>     _______________________________________________
>     spamdyke-users mailing list
>     spamdyke-users@...
>     http://www.spamdyke.org/mailman/listinfo/spamdyke-users
> 
> 
> ------------------------------------------------------------------------
> 
> ¡Descubre una nueva forma de obtener respuestas a tus preguntas!
> Entra en Yahoo! Respuestas 
> <http://us.rd.yahoo.com/mail/es/tagline/answers/*http://es.answers.yahoo.com/;_ylc=X3oDMTEzNWwxbTZtBF9TAzIxMTQ3MTQxOTAEc2VjA01haWwEc2xrA3RhZ2xpbmVz>.
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> spamdyke-users mailing list
> spamdyke-users@...
> http://www.spamdyke.org/mailman/listinfo/spamdyke-users

Re: graylisting

spamdyke 3.1 - denied relaying

Hi all,

I have a problem with a new version of spamdyke (3.1.0): when the remote 
server sends me a message the response of my server is 
"DENIED_RELAYING". The previous version of spamdyke (3.0.1) has not this 
problem.

Thanks in advance.

Kind regards,

Walter

_______________________________________________
spamdyke-users mailing list
spamdyke-users@...
http://www.spamdyke.org/mailman/listinfo/spamdyke-users

Re: spamdyke 3.1 - denied relaying

If you can provide a few more details, I may be able to help.  What do 
your spamdyke configuration file and command line look like?  What is in 
your /etc/tcp.smtp file?  What is in your /var/qmail/control/rcpthosts 
and /var/qmail/control/morercpthosts files?  What is the entire log 
entry for the rejection?

-- Sam Clippinger

Walter Russo wrote:
> Hi all,
> 
> I have a problem with a new version of spamdyke (3.1.0): when the remote 
> server sends me a message the response of my server is 
> "DENIED_RELAYING". The previous version of spamdyke (3.0.1) has not this 
> problem.
> 
> Thanks in advance.
> 
> Kind regards,
> 
> Walter
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> spamdyke-users mailing list
> spamdyke-users@...
> http://www.spamdyke.org/mailman/listinfo/spamdyke-users

Re: spamdyke 3.1 - denied relaying

The configuration works for spamdyke 3.0.1 but not for 3.1.0.

Log file:

Nov  8 00:26:33 nodo1 spamdyke[28072]: INFO: found no records for 
191.17.42.217.dnsbl.njabl.org
Nov  8 00:26:33 nodo1 spamdyke[28072]: INFO: querying 
191.17.42.217.zen.spamhaus.org with DNS server 172.17.1.5:53 (attempt 1)
Nov  8 00:26:33 nodo1 spamdyke[28072]: INFO: received DNS packet: 481 bytes
Nov  8 00:26:33 nodo1 spamdyke[28072]: INFO: received DNS response: TXT
Nov  8 00:26:36 nodo1 spamdyke[16655]: INFO: querying bosy71.com with 
DNS server 172.17.1.5:53 (attempt 1)
Nov  8 00:26:36 nodo1 spamdyke[16655]: INFO: received DNS packet: 184 bytes
Nov  8 00:26:36 nodo1 spamdyke[16655]: INFO: received DNS response: MX
Nov  8 00:26:36 nodo1 spamdyke[16655]: INFO: found MX record for 
bosy71.com: 10 m1.bosy71.com
Nov  8 00:26:36 nodo1 spamdyke[16655]: INFO: querying m1.bosy71.com with 
DNS server 172.17.1.5:53 (attempt 1)
Nov  8 00:26:36 nodo1 spamdyke[16655]: INFO: received DNS packet: 94 bytes
Nov  8 00:26:36 nodo1 spamdyke[16655]: INFO: received DNS response: A
Nov  8 00:26:36 nodo1 spamdyke[16655]: INFO: found A record for 
m1.bosy71.com: 81.174.52.83
Nov  8 00:26:36 nodo1 spamdyke[16655]: DENIED_RELAYING from: 
xxx@... to: xxx@...
origin_ip: 81.174.52.83 origin_rdns: m1
.bosy71.com auth: (unknown)

The domain bardelli.biz is present in rcpthosts and my /etc/tcp.smtp is:

127.:allow,RELAYCLIENT=""
172.17.1.:allow,RELAYCLIENT=""

Thanks in advance.

Best regards

Walter

Sam Clippinger wrote:
> If you can provide a few more details, I may be able to help.  What do 
> your spamdyke configuration file and command line look like?  What is in 
> your /etc/tcp.smtp file?  What is in your /var/qmail/control/rcpthosts 
> and /var/qmail/control/morercpthosts files?  What is the entire log 
> entry for the rejection?
> 
> -- Sam Clippinger
> 
> Walter Russo wrote:
>> Hi all,
>>
>> I have a problem with a new version of spamdyke (3.1.0): when the remote 
>> server sends me a message the response of my server is 
>> "DENIED_RELAYING". The previous version of spamdyke (3.0.1) has not this 
>> problem.
>>
>> Thanks in advance.
>>
>> Kind regards,
>>
>> Walter
>>
>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> spamdyke-users mailing list
>> spamdyke-users@...
>> http://www.spamdyke.org/mailman/listinfo/spamdyke-users
> _______________________________________________
> spamdyke-users mailing list
> spamdyke-users@...
> http://www.spamdyke.org/mailman/listinfo/spamdyke-users
> 

_______________________________________________
spamdyke-users mailing list
spamdyke-users@...
http://www.spamdyke.org/mailman/listinfo/spamdyke-users