From: Thomas E. <Tho...@th...> - 2011-07-25 17:13:33
|
Hi all, fixed in 2.0.2_3.2.04: - the orginating IP detection was broken since any of the last versions - some wrong outputs of the analyzer features - a memory leak on some anonymous arrays changed: - improved/enhanced information at the analyzer features - the GRIPLIST download is changed to run also at a changed download host added: - enhanced orginating IP address detection: ASSP parses the received header lines and some other common OIP lines for IP-addresses. The detected IP addresses are checked against the IP-Blocking features and DNSBL in the same way like an OIP address would be checked for an ISP-email. This will help to detect bots that are using different gateways or open SMTP-relay servers. This feature will also detect host that are abusing ISP-servers like AOL,gmal,hotmail ..... Simply add the source IP or any other 'IP on the way to you' to the IP-Blocking features . Thomas 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! ******************************************************* |
From: K P. <nnt...@gm...> - 2011-07-27 14:42:56
|
On the originating IP address detection, won't this cause problems with legitimate users who are sending email from dynamic IP addresses at home to their outbound server? For example, my home connection is with a cable company. Their ip address blocks that are handed out to consumers are on my dns blacklists as no email should be originating from that server. I connect via smtp to the ISP's smtp server to send mail. Will ASSP try to block mail that it gets from me because I started out on a dynamic address? For example, when I send SMTP mail, the first helo line shows a received from with my home ip address. That won't cause problems will it??? I've seen other antispam systems erroneously block like this. |
From: Thomas E. <Tho...@th...> - 2011-07-27 17:37:37
|
Yes I know that problem. I've redesingned that feature in the next release. IP addresses that are: in accepAll Mail in whiteListedIPs in noProcessingIPs in noDelay in noPB ISPIP's IP's that where connected to the ISP (OIP/cip) in a privat IP range will be ignored Thomas Von: K Post <nnt...@gm...> An: ASSP development mailing list <ass...@li...> Datum: 27.07.2011 16:43 Betreff: Re: [Assp-test] fixes and changes in assp 2.0.2_3.2.04 On the originating IP address detection, won't this cause problems with legitimate users who are sending email from dynamic IP addresses at home to their outbound server? For example, my home connection is with a cable company. Their ip address blocks that are handed out to consumers are on my dns blacklists as no email should be originating from that server. I connect via smtp to the ISP's smtp server to send mail. Will ASSP try to block mail that it gets from me because I started out on a dynamic address? For example, when I send SMTP mail, the first helo line shows a received from with my home ip address. That won't cause problems will it??? I've seen other antispam systems erroneously block like this. ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ Assp-test mailing list Ass...@li... 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! ******************************************************* |
From: K P. <nnt...@gm...> - 2011-07-28 15:29:27
|
Excellent. Can you explain: "IP's that where connected to the ISP (OIP/cip)" My real concern isn't the IP's that I know about, it's those that I don't. Does any of the recent changes reslolve this problem? For example, someone outside of our org emails us from a small ISP. That ISP hands out ip's to cable modems with hostnames like: 22.11.chicago-dsl.dhcp.isp.net which reverses to 64.33.22.11 or something. That ip address is in a dns blacklist since as a dynamic ip that is only handed out to residential customers of the ISP, it should never be running its own mail server. Instead, the mail should be sent as it really was, from the sender to the sender's ISP's smtp server (or a thrid party smtp server that isn't in a dnsbl). Thanks On Wed, Jul 27, 2011 at 1:37 PM, Thomas Eckardt <Tho...@th...>wrote: > Yes I know that problem. I've redesingned that feature in the next > release. > > IP addresses that are: > > in accepAll Mail > in whiteListedIPs > in noProcessingIPs > in noDelay > in noPB > ISPIP's > IP's that where connected to the ISP (OIP/cip) > in a privat IP range > > will be ignored > > Thomas > > > > > > Von: K Post <nnt...@gm...> > An: ASSP development mailing list <ass...@li...> > Datum: 27.07.2011 16:43 > Betreff: Re: [Assp-test] fixes and changes in assp 2.0.2_3.2.04 > > > > > On the originating IP address detection, won't this cause problems with > legitimate users who are sending email from dynamic IP addresses at home > to > their outbound server? For example, my home connection is with a cable > company. Their ip address blocks that are handed out to consumers are on > my > dns blacklists as no email should be originating from that server. I > connect via smtp to the ISP's smtp server to send mail. Will ASSP try to > block mail that it gets from me because I started out on a dynamic > address? > > For example, when I send SMTP mail, the first helo line shows a received > from with my home ip address. That won't cause problems will it??? > > I've seen other antispam systems erroneously block like this. > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > _______________________________________________ > Assp-test mailing list > Ass...@li... > 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! > ******************************************************* > > > > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > _______________________________________________ > Assp-test mailing list > Ass...@li... > https://lists.sourceforge.net/lists/listinfo/assp-test > > |
From: Thomas E. <Tho...@th...> - 2011-07-28 16:00:58
|
>Can you explain: >"IP's that where connected to the ISP (OIP/cip)" using 'ispip' and 'ispHostnames' assp will use the ip, from which your ISP has received (Received: header) the mail in the same way as this ip has connected to assp. Such IP's are signed as 'OIP' (orginated ip) in the maillog.txt - the internal code sign is {cip}. >That ip address is in a dns blacklist since as a dynamic ip An IP is never in any DNSBL because it is dynamic - the only check that is done on that by assp is the PTR check, which will fail on a dynamic IP. The PTR check is for this reason not done on any IP collected by the enhanced mail routing detection. How ever, if any IP in the mail route (in your case for example 64.33.22.11) is black listed - the IP and the message will possibly get the penalty and the mail will be blocked, if assp is configured to do so. The IP's on the mail route will only be checked for/against: denySMTPConnectionsFromAlways droplist PenaltyExtreme ValidateRBL PenaltyBox These checks are done in the same way, like the IP's where directly connected to assp. Thomas Von: K Post <nnt...@gm...> An: ASSP development mailing list <ass...@li...> Datum: 28.07.2011 17:32 Betreff: Re: [Assp-test] Antwort: Re: fixes and changes in assp 2.0.2_3.2.04 Excellent. Can you explain: "IP's that where connected to the ISP (OIP/cip)" My real concern isn't the IP's that I know about, it's those that I don't. Does any of the recent changes reslolve this problem? For example, someone outside of our org emails us from a small ISP. That ISP hands out ip's to cable modems with hostnames like: 22.11.chicago-dsl.dhcp.isp.net which reverses to 64.33.22.11 or something. That ip address is in a dns blacklist since as a dynamic ip that is only handed out to residential customers of the ISP, it should never be running its own mail server. Instead, the mail should be sent as it really was, from the sender to the sender's ISP's smtp server (or a thrid party smtp server that isn't in a dnsbl). Thanks On Wed, Jul 27, 2011 at 1:37 PM, Thomas Eckardt <Tho...@th...>wrote: > Yes I know that problem. I've redesingned that feature in the next > release. > > IP addresses that are: > > in accepAll Mail > in whiteListedIPs > in noProcessingIPs > in noDelay > in noPB > ISPIP's > IP's that where connected to the ISP (OIP/cip) > in a privat IP range > > will be ignored > > Thomas > > > > > > Von: K Post <nnt...@gm...> > An: ASSP development mailing list <ass...@li...> > Datum: 27.07.2011 16:43 > Betreff: Re: [Assp-test] fixes and changes in assp 2.0.2_3.2.04 > > > > > On the originating IP address detection, won't this cause problems with > legitimate users who are sending email from dynamic IP addresses at home > to > their outbound server? For example, my home connection is with a cable > company. Their ip address blocks that are handed out to consumers are on > my > dns blacklists as no email should be originating from that server. I > connect via smtp to the ISP's smtp server to send mail. Will ASSP try to > block mail that it gets from me because I started out on a dynamic > address? > > For example, when I send SMTP mail, the first helo line shows a received > from with my home ip address. That won't cause problems will it??? > > I've seen other antispam systems erroneously block like this. > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > _______________________________________________ > Assp-test mailing list > Ass...@li... > 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! > ******************************************************* > > > > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > _______________________________________________ > Assp-test mailing list > Ass...@li... > https://lists.sourceforge.net/lists/listinfo/assp-test > > ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ Assp-test mailing list Ass...@li... 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! ******************************************************* |
From: K P. <nnt...@gm...> - 2011-07-28 17:35:33
|
Doesn't zen.spamhaus.org, which is a default of ASSP, include the the PBL, which includes known dynamic ISP addresses? http://www.spamhaus.org/pbl/ On Thu, Jul 28, 2011 at 12:00 PM, Thomas Eckardt <Tho...@th... > wrote: > >Can you explain: > >"IP's that where connected to the ISP (OIP/cip)" > > using 'ispip' and 'ispHostnames' assp will use the ip, from which your ISP > has received (Received: header) the mail in the same way as this ip has > connected to assp. > Such IP's are signed as 'OIP' (orginated ip) in the maillog.txt - the > internal code sign is {cip}. > > >That ip address is in a dns blacklist since as a dynamic ip > > An IP is never in any DNSBL because it is dynamic - the only check that is > done on that by assp is the PTR check, which will fail on a dynamic IP. > The PTR check is for this reason not done on any IP collected by the > enhanced mail routing detection. > > How ever, if any IP in the mail route (in your case for example > 64.33.22.11) is black listed - the IP and the message will possibly get > the penalty and the mail will be blocked, if assp is configured to do so. > > The IP's on the mail route will only be checked for/against: > > denySMTPConnectionsFromAlways > droplist > PenaltyExtreme > ValidateRBL > PenaltyBox > > These checks are done in the same way, like the IP's where directly > connected to assp. > > > Thomas > > > > > > Von: K Post <nnt...@gm...> > An: ASSP development mailing list <ass...@li...> > Datum: 28.07.2011 17:32 > Betreff: Re: [Assp-test] Antwort: Re: fixes and changes in assp > 2.0.2_3.2.04 > > > > > Excellent. > > Can you explain: > "IP's that where connected to the ISP (OIP/cip)" > > My real concern isn't the IP's that I know about, it's those that I don't. > Does any of the recent changes reslolve this problem? > > For example, someone outside of our org emails us from a small ISP. That > ISP hands out ip's to cable modems with hostnames like: > 22.11.chicago-dsl.dhcp.isp.net which reverses to 64.33.22.11 or something. > That ip address is in a dns blacklist since as a dynamic ip that is only > handed out to residential customers of the ISP, it should never be running > its own mail server. Instead, the mail should be sent as it really was, > from the sender to the sender's ISP's smtp server (or a thrid party smtp > server that isn't in a dnsbl). > > Thanks > On Wed, Jul 27, 2011 at 1:37 PM, Thomas Eckardt > <Tho...@th...>wrote: > > > Yes I know that problem. I've redesingned that feature in the next > > release. > > > > IP addresses that are: > > > > in accepAll Mail > > in whiteListedIPs > > in noProcessingIPs > > in noDelay > > in noPB > > ISPIP's > > IP's that where connected to the ISP (OIP/cip) > > in a privat IP range > > > > will be ignored > > > > Thomas > > > > > > > > > > > > Von: K Post <nnt...@gm...> > > An: ASSP development mailing list <ass...@li...> > > Datum: 27.07.2011 16:43 > > Betreff: Re: [Assp-test] fixes and changes in assp 2.0.2_3.2.04 > > > > > > > > > > On the originating IP address detection, won't this cause problems with > > legitimate users who are sending email from dynamic IP addresses at home > > to > > their outbound server? For example, my home connection is with a cable > > company. Their ip address blocks that are handed out to consumers are > on > > my > > dns blacklists as no email should be originating from that server. I > > connect via smtp to the ISP's smtp server to send mail. Will ASSP try > to > > block mail that it gets from me because I started out on a dynamic > > address? > > > > For example, when I send SMTP mail, the first helo line shows a received > > from with my home ip address. That won't cause problems will it??? > > > > I've seen other antispam systems erroneously block like this. > > > > > > ------------------------------------------------------------------------------ > > Got Input? Slashdot Needs You. > > Take our quick survey online. Come on, we don't ask for help often. > > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > > http://p.sf.net/sfu/slashdot-survey > > _______________________________________________ > > Assp-test mailing list > > Ass...@li... > > 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! > > ******************************************************* > > > > > > > > > > > > ------------------------------------------------------------------------------ > > Got Input? Slashdot Needs You. > > Take our quick survey online. Come on, we don't ask for help often. > > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > > http://p.sf.net/sfu/slashdot-survey > > _______________________________________________ > > Assp-test mailing list > > Ass...@li... > > https://lists.sourceforge.net/lists/listinfo/assp-test > > > > > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > _______________________________________________ > Assp-test mailing list > Ass...@li... > 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! > ******************************************************* > > > > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > _______________________________________________ > Assp-test mailing list > Ass...@li... > https://lists.sourceforge.net/lists/listinfo/assp-test > > |
From: Thomas E. <Tho...@th...> - 2011-07-29 05:08:54
|
>Doesn't zen.spamhaus.org, which is a default of ASSP, include the the PBL, >which includes known dynamic ISP addresses? >http://www.spamhaus.org/pbl/ Ken, you are right. The next release will consider this. Thomas Von: K Post <nnt...@gm...> An: ASSP development mailing list <ass...@li...> Datum: 28.07.2011 19:37 Betreff: Re: [Assp-test] Antwort: Re: Antwort: Re: fixes and changes in assp 2.0.2_3.2.04 Doesn't zen.spamhaus.org, which is a default of ASSP, include the the PBL, which includes known dynamic ISP addresses? http://www.spamhaus.org/pbl/ On Thu, Jul 28, 2011 at 12:00 PM, Thomas Eckardt <Tho...@th... > wrote: > >Can you explain: > >"IP's that where connected to the ISP (OIP/cip)" > > using 'ispip' and 'ispHostnames' assp will use the ip, from which your ISP > has received (Received: header) the mail in the same way as this ip has > connected to assp. > Such IP's are signed as 'OIP' (orginated ip) in the maillog.txt - the > internal code sign is {cip}. > > >That ip address is in a dns blacklist since as a dynamic ip > > An IP is never in any DNSBL because it is dynamic - the only check that is > done on that by assp is the PTR check, which will fail on a dynamic IP. > The PTR check is for this reason not done on any IP collected by the > enhanced mail routing detection. > > How ever, if any IP in the mail route (in your case for example > 64.33.22.11) is black listed - the IP and the message will possibly get > the penalty and the mail will be blocked, if assp is configured to do so. > > The IP's on the mail route will only be checked for/against: > > denySMTPConnectionsFromAlways > droplist > PenaltyExtreme > ValidateRBL > PenaltyBox > > These checks are done in the same way, like the IP's where directly > connected to assp. > > > Thomas > > > > > > Von: K Post <nnt...@gm...> > An: ASSP development mailing list <ass...@li...> > Datum: 28.07.2011 17:32 > Betreff: Re: [Assp-test] Antwort: Re: fixes and changes in assp > 2.0.2_3.2.04 > > > > > Excellent. > > Can you explain: > "IP's that where connected to the ISP (OIP/cip)" > > My real concern isn't the IP's that I know about, it's those that I don't. > Does any of the recent changes reslolve this problem? > > For example, someone outside of our org emails us from a small ISP. That > ISP hands out ip's to cable modems with hostnames like: > 22.11.chicago-dsl.dhcp.isp.net which reverses to 64.33.22.11 or something. > That ip address is in a dns blacklist since as a dynamic ip that is only > handed out to residential customers of the ISP, it should never be running > its own mail server. Instead, the mail should be sent as it really was, > from the sender to the sender's ISP's smtp server (or a thrid party smtp > server that isn't in a dnsbl). > > Thanks > On Wed, Jul 27, 2011 at 1:37 PM, Thomas Eckardt > <Tho...@th...>wrote: > > > Yes I know that problem. I've redesingned that feature in the next > > release. > > > > IP addresses that are: > > > > in accepAll Mail > > in whiteListedIPs > > in noProcessingIPs > > in noDelay > > in noPB > > ISPIP's > > IP's that where connected to the ISP (OIP/cip) > > in a privat IP range > > > > will be ignored > > > > Thomas > > > > > > > > > > > > Von: K Post <nnt...@gm...> > > An: ASSP development mailing list <ass...@li...> > > Datum: 27.07.2011 16:43 > > Betreff: Re: [Assp-test] fixes and changes in assp 2.0.2_3.2.04 > > > > > > > > > > On the originating IP address detection, won't this cause problems with > > legitimate users who are sending email from dynamic IP addresses at home > > to > > their outbound server? For example, my home connection is with a cable > > company. Their ip address blocks that are handed out to consumers are > on > > my > > dns blacklists as no email should be originating from that server. I > > connect via smtp to the ISP's smtp server to send mail. Will ASSP try > to > > block mail that it gets from me because I started out on a dynamic > > address? > > > > For example, when I send SMTP mail, the first helo line shows a received > > from with my home ip address. That won't cause problems will it??? > > > > I've seen other antispam systems erroneously block like this. > > > > > > ------------------------------------------------------------------------------ > > Got Input? Slashdot Needs You. > > Take our quick survey online. Come on, we don't ask for help often. > > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > > http://p.sf.net/sfu/slashdot-survey > > _______________________________________________ > > Assp-test mailing list > > Ass...@li... > > 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! > > ******************************************************* > > > > > > > > > > > > ------------------------------------------------------------------------------ > > Got Input? Slashdot Needs You. > > Take our quick survey online. Come on, we don't ask for help often. > > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > > http://p.sf.net/sfu/slashdot-survey > > _______________________________________________ > > Assp-test mailing list > > Ass...@li... > > https://lists.sourceforge.net/lists/listinfo/assp-test > > > > > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > _______________________________________________ > Assp-test mailing list > Ass...@li... > 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! > ******************************************************* > > > > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > _______________________________________________ > Assp-test mailing list > Ass...@li... > https://lists.sourceforge.net/lists/listinfo/assp-test > > ------------------------------------------------------------------------------ Got Input? Slashdot Needs You. Take our quick survey online. Come on, we don't ask for help often. Plus, you'll get a chance to win $100 to spend on ThinkGeek. http://p.sf.net/sfu/slashdot-survey _______________________________________________ Assp-test mailing list Ass...@li... 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! ******************************************************* |
From: K P. <nnt...@gm...> - 2011-07-30 01:22:37
|
I have printed out that reply banner sized and will be making walpaper out of it. I haven't heard that I'm right in years.... On Fri, Jul 29, 2011 at 1:08 AM, Thomas Eckardt <Tho...@th...>wrote: > >Doesn't zen.spamhaus.org, which is a default of ASSP, include the the > PBL, > >which includes known dynamic ISP addresses? > >http://www.spamhaus.org/pbl/ > > Ken, you are right. The next release will consider this. > > Thomas > > > > Von: K Post <nnt...@gm...> > An: ASSP development mailing list <ass...@li...> > Datum: 28.07.2011 19:37 > Betreff: Re: [Assp-test] Antwort: Re: Antwort: Re: fixes and > changes in assp 2.0.2_3.2.04 > > > > Doesn't zen.spamhaus.org, which is a default of ASSP, include the the PBL, > which includes known dynamic ISP addresses? > http://www.spamhaus.org/pbl/ > > > > > > On Thu, Jul 28, 2011 at 12:00 PM, Thomas Eckardt > <Tho...@th... > > wrote: > > > >Can you explain: > > >"IP's that where connected to the ISP (OIP/cip)" > > > > using 'ispip' and 'ispHostnames' assp will use the ip, from which your > ISP > > has received (Received: header) the mail in the same way as this ip has > > connected to assp. > > Such IP's are signed as 'OIP' (orginated ip) in the maillog.txt - the > > internal code sign is {cip}. > > > > >That ip address is in a dns blacklist since as a dynamic ip > > > > An IP is never in any DNSBL because it is dynamic - the only check that > is > > done on that by assp is the PTR check, which will fail on a dynamic IP. > > The PTR check is for this reason not done on any IP collected by the > > enhanced mail routing detection. > > > > How ever, if any IP in the mail route (in your case for example > > 64.33.22.11) is black listed - the IP and the message will possibly get > > the penalty and the mail will be blocked, if assp is configured to do > so. > > > > The IP's on the mail route will only be checked for/against: > > > > denySMTPConnectionsFromAlways > > droplist > > PenaltyExtreme > > ValidateRBL > > PenaltyBox > > > > These checks are done in the same way, like the IP's where directly > > connected to assp. > > > > > > Thomas > > > > > > > > > > > > Von: K Post <nnt...@gm...> > > An: ASSP development mailing list <ass...@li...> > > Datum: 28.07.2011 17:32 > > Betreff: Re: [Assp-test] Antwort: Re: fixes and changes in assp > > 2.0.2_3.2.04 > > > > > > > > > > Excellent. > > > > Can you explain: > > "IP's that where connected to the ISP (OIP/cip)" > > > > My real concern isn't the IP's that I know about, it's those that I > don't. > > Does any of the recent changes reslolve this problem? > > > > For example, someone outside of our org emails us from a small ISP. That > > ISP hands out ip's to cable modems with hostnames like: > > 22.11.chicago-dsl.dhcp.isp.net which reverses to 64.33.22.11 or > something. > > That ip address is in a dns blacklist since as a dynamic ip that is only > > handed out to residential customers of the ISP, it should never be > running > > its own mail server. Instead, the mail should be sent as it really was, > > from the sender to the sender's ISP's smtp server (or a thrid party smtp > > server that isn't in a dnsbl). > > > > Thanks > > On Wed, Jul 27, 2011 at 1:37 PM, Thomas Eckardt > > <Tho...@th...>wrote: > > > > > Yes I know that problem. I've redesingned that feature in the next > > > release. > > > > > > IP addresses that are: > > > > > > in accepAll Mail > > > in whiteListedIPs > > > in noProcessingIPs > > > in noDelay > > > in noPB > > > ISPIP's > > > IP's that where connected to the ISP (OIP/cip) > > > in a privat IP range > > > > > > will be ignored > > > > > > Thomas > > > > > > > > > > > > > > > > > > Von: K Post <nnt...@gm...> > > > An: ASSP development mailing list > <ass...@li...> > > > Datum: 27.07.2011 16:43 > > > Betreff: Re: [Assp-test] fixes and changes in assp 2.0.2_3.2.04 > > > > > > > > > > > > > > > On the originating IP address detection, won't this cause problems > with > > > legitimate users who are sending email from dynamic IP addresses at > home > > > to > > > their outbound server? For example, my home connection is with a > cable > > > company. Their ip address blocks that are handed out to consumers are > > on > > > my > > > dns blacklists as no email should be originating from that server. I > > > connect via smtp to the ISP's smtp server to send mail. Will ASSP try > > to > > > block mail that it gets from me because I started out on a dynamic > > > address? > > > > > > For example, when I send SMTP mail, the first helo line shows a > received > > > from with my home ip address. That won't cause problems will it??? > > > > > > I've seen other antispam systems erroneously block like this. > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > Got Input? Slashdot Needs You. > > > Take our quick survey online. Come on, we don't ask for help often. > > > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > > > http://p.sf.net/sfu/slashdot-survey > > > _______________________________________________ > > > Assp-test mailing list > > > Ass...@li... > > > 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! > > > ******************************************************* > > > > > > > > > > > > > > > > > > > > > ------------------------------------------------------------------------------ > > > Got Input? Slashdot Needs You. > > > Take our quick survey online. Come on, we don't ask for help often. > > > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > > > http://p.sf.net/sfu/slashdot-survey > > > _______________________________________________ > > > Assp-test mailing list > > > Ass...@li... > > > https://lists.sourceforge.net/lists/listinfo/assp-test > > > > > > > > > > > > ------------------------------------------------------------------------------ > > Got Input? Slashdot Needs You. > > Take our quick survey online. Come on, we don't ask for help often. > > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > > http://p.sf.net/sfu/slashdot-survey > > _______________________________________________ > > Assp-test mailing list > > Ass...@li... > > 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! > > ******************************************************* > > > > > > > > > > > > ------------------------------------------------------------------------------ > > Got Input? Slashdot Needs You. > > Take our quick survey online. Come on, we don't ask for help often. > > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > > http://p.sf.net/sfu/slashdot-survey > > _______________________________________________ > > Assp-test mailing list > > Ass...@li... > > https://lists.sourceforge.net/lists/listinfo/assp-test > > > > > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > _______________________________________________ > Assp-test mailing list > Ass...@li... > 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! > ******************************************************* > > > > > ------------------------------------------------------------------------------ > Got Input? Slashdot Needs You. > Take our quick survey online. Come on, we don't ask for help often. > Plus, you'll get a chance to win $100 to spend on ThinkGeek. > http://p.sf.net/sfu/slashdot-survey > _______________________________________________ > Assp-test mailing list > Ass...@li... > https://lists.sourceforge.net/lists/listinfo/assp-test > > |