>> Agreed - all those addresses are local addresses. I guess maybe I am >> still >> confused about the difference between IspIP and AcceptAllMail. > > The difference is in their descriptions. ispip allows for certain > functionality bypasses. AcceptAllMail is a whitelisted IP - performing > the same as if the email address was on the whitelist..
Right - that was exactly my understanding of it as well. >> So, in >> that case, why shouldn't I be able to put a local address on the IspIP >> address list, expecting the email to be accepted but still go through the >> content checks? >> > > You can do either, but I think the better question is that if these are > internal IP addresses, why wouldn't you want them whitelisted? That is > the default nature of ASSP - that internal sourced email gets > whitelisted and added to the corpus. You would think so, but if I try to put the server's address on the IspIp list, then I get "relay attempt blocked" error msgs for any domains that aren't on my local domains list. Which makes me wonder if either there is a bug, or if I am misunderstanding the idea / concept of these addresses. Indeed, the "correct" solution is to put them on the AcceptAllMail list, but I had originally put them on the IspIP list and ran across this issue. So now I'm trying to figure out if this is actually a bug that needs to be corrected, or if it is working as intended, in which case the description needs to be updated, as does the FAQ I wrote on it yesterday. :) > ispip is mainly to not force any sessions delays or scrutiny - to allow > the connection to take place as fast as possible - and still be able to > perform other types of filtering against the content of the message. A > listing in ispip is to imply that the connecting server is a trusted > source for e-mail (such as your ISPs mail server), but the content might > not be. Aha. I think I finally clued in on your last paragraph here. Thanks. The key sentence is "still be able to perform other types of filtering against the content of the message". In my original understanding, this included only the actual body of the message, but not the sender/receiver as well. I am guessing that if I dig further, I'll see that email sent from IsPIP performs all Local Address Validation checks as well. In my mind, I had understood that given that email was coming in from a trusted source, that LAV was not being performed. This would now explain why I was getting Relay rejected for all non-local domains. I think I'll update the Wiki FAQ to futher clarify this as well. I'll also put it on my list of things to clarify when looking over the interface... Thanks! Eric ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
