Oh, I'm sorry - the default download page on SF got the update (at 
21.01.2016) but not the CVS repo.

CVS -> Done.

Thomas





Von:    Colin Waring <co...@dolphinict.co.uk>
An:     ASSP development mailing list <assp-test@lists.sourceforge.net>
Datum:  09.09.2016 10:18
Betreff:        Re: [Assp-test] invalidFormatHeloRe



Hi Thomas,

Thanks for the reply. That was actually a typo in my email, I did mean 
validFormatHeloRe not invalidFormatHeloRe.

The file on SourceForge is out of date. It hasn't been updated in nearly 
three years and still has w{2,6} in it - I checked this prior to posting 
as my way of keeping things up to date is comparing them with 
http://assp.cvs.sourceforge.net/viewvc/assp/assp2

All the best,
Colin Waring.

-----Original Message-----
From: Thomas Eckardt [mailto:thomas.ecka...@thockar.com] 
Sent: 09 September 2016 08:38
To: ASSP development mailing list <assp-test@lists.sourceforge.net>
Subject: Re: [Assp-test] invalidFormatHeloRe

>invalidFormatHeloRe

No - 'validFormatHeloRe' makes this rule.

This regex was change at the begin of this year (I think) - the default is

file:files/validhelo.txt

validhelo.txt:

^(?:\w[\w\.\-]*\.\w{2,64})$
^[a-fA-F0-9]{1,4}:([a-fA-F0-9:]{1,4}){1,}(?:(?:\.\d+){3})?$


Thomas




Von:    cw <colin.war...@gmail.com>
An:     ASSP development mailing list <assp-test@lists.sourceforge.net>
Datum:  08.09.2016 13:26
Betreff:        [Assp-test] invalidFormatHeloRe



Hi,



I’m not an expert at Regexs otherwise I’d look at this myself.



I’ve had someone emailing me about problems getting mail through and at 
first glance it was due to an invalid HELO. At second glance, the HELO is 
actually valid and points to a domain that has a valid DNS record. The 
HELO is server.kalo.digital



This fails the default regex for invalidFormatHeloRe because the regex
stipulates that the last part of the HELO has to be between 2 and 6
characters long. This doesn’t take into account the more recent TLDs that
have been forced on the Internet of which .digital is one being 7
characters.



I can’t find anything in RFC1123 that specifically states the number of
characters for the TLD so is this a problem with the Regex rather than the
usage of TLDs with more than 6 characters?



All the best,

Colin Waring.
------------------------------------------------------------------------------
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test




DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 


individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************


------------------------------------------------------------------------------
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test




DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally 
privileged and protected in law and are intended solely for the use of the 

individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no 
known virus in this email!
*******************************************************


------------------------------------------------------------------------------
_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to