Subj : Re: Not able to recieve mail To : All From : HECTOR SANTOS Date : Thu Jan 31 2019 19:18:38 Date: Sat, 04 Apr 2009 11:06:57 -0400 From: HECTOR SANTOS To: Mike Roberts Subject: Re: Not able to recieve mail Newsgroups: win.server.smtp.&.avs Message-ID: <1238864843.46.1238817288@winserver.com> References: <1238817288.46.0@winserver.com> X-WcMsg-Attr: Rcvd X-Mailer: Wildcat! Interactive Net Server v7.0.454.5 Lines: 93 Mike Roberts wrote: > I am able to send out internet email, but when I try sending to my BBS, I do > not get the mail. Here is what I am seeing in my logs, How can I fix it, I think > it is a spam blocking problem, but do not know how to fix it. > > Mike > > 20090403 22:11:14 (07D4) MAIL FROM: ... Sender > validation pending. Continue. > 20090403 22:11:16 (07D4) RCPT: Return Path not verifiable: > (Rejected by WCSAP CBV)! The WCSAP*.LOG file will tell you the details. But it was CBV - Callback Verification. WCSAP tried to call back the xxxxxxxxx@yahoo.com and YAHOO didn't like it. Why? The WCSAP*.LOG session log for this will tell ya. It may be hard to follow but on a busy system the log lines will mixed with all current SMTP sessions. So you need to make sure you group the right lines together and thats done by the connection ID, column #3 in the log: date time connection_id string You will be looking for the SAPCBV attempts. Here is an 2005 log example I have on hand for yahoo: 20050121 10:08:30 0001ea94 sapcbv : total mx records: 5 20050121 10:08:30 0001ea94 try mx : mx1.mail.yahoo.com ip: 67.28.113.11 20050121 10:08:30 0001ea94 # connecting to 67.28.113.11 20050121 10:08:30 0001ea94 S: 220 YSmtp mta154.mail.re2.yahoo.com ESMTP service ready 20050121 10:08:30 0001ea94 C: NOOP WCSAP v2.01 Wildcat! Sender Authentication Protocol http://www.santronics.com 20050121 10:08:30 0001ea94 S: 250 OK 20050121 10:08:30 0001ea94 C: HELO mail.winserver.com 20050121 10:08:30 0001ea94 S: 250 mta154.mail.re2.yahoo.com 20050121 10:08:30 0001ea94 C: MAIL FROM: <> 20050121 10:08:30 0001ea94 S: 250 null sender <> ok 20050121 10:08:30 0001ea94 C: RCPT TO: 20050121 10:08:30 0001ea94 S: 250 recipient ok 20050121 10:08:30 0001ea94 C: RCPT TO: 20050121 10:08:30 0001ea94 S: 452 Too many recipients 20050121 10:08:30 0001ea94 C: QUIT 20050121 10:08:30 0001ea94 sapcbv : 250 The idea of CBV is when someone is sending you mail (from yahoo.com), the theory that you should be able to write back to them. If you can't, then its probably a bad address. So CBV tries to act like its going to send mail, but only goes as far to issueing the: RCPT TO: if yahoo response with a 45x or 55x number, its bad. If 250, its good. But WCSAP goes one step further and ask the question: "ok, if yahoo says this address is ok, then lets try a fake address to see if its accepts any thing!" That would be the line above: RCPT TO: where wcsap tries to see if YAHOO accepts any junk. If no, then its WCSAP says: "Ok, we done the best we can. Yahoo is not accepting junk but it did accept the first address of interest. So its ok." If Yahoo had accepted the junk address, wcSAP assumes the site is a open relay and thats normally bad. So check for the same activity in your logs. The above was 2005. Yahoo might have changed policies and have a different result. -- Hector, Engineering & Technical Support Santronics Software, Inc. http://www.santronics.com (sales) http://www.winserver.com (support) http://www.winserver.com/AupInfo (Online AUP Help) Office: 305-248-3204 --- Platinum Xpress/Win/WINServer v3.1 * Origin: Prison Board BBS Mesquite Tx //telnet.RDFIG.NET www. (1:124/5013) .