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, Ithink
it is a spam blocking problem, but do not know how to fix it.
Mike
20090403 22:11:14 (07D4) MAIL FROM: <xxxxxxx@yahoo.com>... Sender
validation pending. Continue.
20090403 22:11:16 (07D4) RCPT: Return Path not verifiable: <xxxxxxx@yahoo.com> (Rejected by WCSAP CBV)!
Mike Roberts wrote:I do
I am able to send out internet email, but when I try sending to my BBS,
not get the mail. Here is what I am seeing in my logs, How can I fix it, I
Senderit is a spam blocking problem, but do not know how to fix it.
Mike
20090403 22:11:14 (07D4) MAIL FROM: <xxxxxxx@yahoo.com>...
validation pending. Continue.
20090403 22:11:16 (07D4) RCPT: Return Path not verifiable: <xxxxxxx@yahoo.com> (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: <francis02_invest@yahoo.com>
20050121 10:08:30 0001ea94 S: 250 recipient
<francis02_invest@yahoo.com> ok
20050121 10:08:30 0001ea94 C: RCPT TO: <wcsap-openrelay-test-123sxa23@alqwejad.com>
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: <xxxxxxxxxx@yahoo.com>
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: <wcsap-openrelay-test-123sxa23@alqwejad.com>
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
Hello Hector, thanks for Your response. Here is a copy from my Log. Even If I
totally understood, I would not know how to fix this problem with mail from Yahoo.
Mike
20090403 21:11:42 00000043 -------------------------------------
20090403 21:11:42 00000043 version : 2.10 / 1.63
20090403 21:11:42 00000043 calltype : SMTP
20090403 21:11:42 00000043 state : rcpt
20090403 21:11:42 00000043 cip : 98.136.44.48
20090403 21:11:42 00000043 cdn : n76.bullet.mail.sp1.yahoo.com 20090403 21:11:42 00000043 from : tnel003@yahoo.com
20090403 21:11:42 00000043 hdn : n76.bullet.mail.sp1.yahoo.com 20090403 21:11:42 00000043 rcpt : mike.roberts@holodeck.myip.us 20090403 21:11:42 00000043 ruid : 1
20090403 21:11:43 00000043 sapfilter : pass (time:31)
20090403 21:11:43 00000043 saprbl : pass (time:47)
20090403 21:11:43 00000043 sapspf : none (time:16)
20090403 21:11:43 00000043 sapcep : disabled
20090403 21:11:45 00000043 DNS Error : 10061
20090403 21:11:45 00000043 sapcbv : rejected - can not resolve
yahoo.com
20090403 21:11:45 00000043 result : reject (0)
20090403 21:11:45 00000043 smtp code : 452
20090403 21:11:45 00000043 wcsap finish (2141 msecs)
20090403 21:14:12 00000044 -------------------------------------
On 2009-04-04 11:06 AM, HECTOR SANTOS wrote to Mike Roberts:I
Mike Roberts wrote:I do
I am able to send out internet email, but when I try sending to my BBS,
not get the mail. Here is what I am seeing in my logs, How can I fix it,
think
it is a spam blocking problem, but do not know how to fix it.
Mike
Sender20090403 22:11:14 (07D4) MAIL FROM: <xxxxxxx@yahoo.com>...
validation pending. Continue.
20090403 22:11:16 (07D4) RCPT: Return Path not verifiable: <xxxxxxx@yahoo.com> (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: <francis02_invest@yahoo.com> 20050121 10:08:30 0001ea94 S: 250 recipient
<francis02_invest@yahoo.com> ok
20050121 10:08:30 0001ea94 C: RCPT TO: <wcsap-openrelay-test-123sxa23@alqwejad.com>
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: <xxxxxxxxxx@yahoo.com>
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: <wcsap-openrelay-test-123sxa23@alqwejad.com>
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
This appears to be a DNS (Domain Name Server) lookup issue.
sapcbv : rejected - can not resolve yahoo.com
In other words, its doing something like this:
NSLOOKUP -query=mx yahoo.com
which you can type from the dos command and it could not be resolved.
If I type that command above now, I get this:
Server: dns.mia.bellsouth.net
Address: 205.152.144.23
Non-authoritative answer:
yahoo.com MX preference = 1, mail exchanger = b.mx.mail.yahoo.com
yahoo.com MX preference = 1, mail exchanger = c.mx.mail.yahoo.com
yahoo.com MX preference = 1, mail exchanger = d.mx.mail.yahoo.com
yahoo.com MX preference = 1, mail exchanger = e.mx.mail.yahoo.com
yahoo.com MX preference = 1, mail exchanger = f.mx.mail.yahoo.com
yahoo.com MX preference = 1, mail exchanger = g.mx.mail.yahoo.com
yahoo.com MX preference = 1, mail exchanger = a.mx.mail.yahoo.com
which are the servers to send mail too. What happen is that this
didn't work for you.
It generally means your connection with ISP has a DNS setup issue or
they were down or their DNS servers were down or there is a firewall,
etc, who knows.
But before you can use WCSAP or send mail with WCSMTP, you must be
able to do NSLOOKUP commands from the PC wcSMTP is running. Do it for other domains too:
NSLOOKUP -query=mx gmail.com
NSLOOKUP -query=mx santronics.com
NSLOOKUP -query=mx microsoft.com
NSLOOKUP -query=mx live.com
When these return valid MX records, then you know your DNS resolution
is working with the ISP connection.
etc.
Mike Roberts wrote:Even If I
Hello Hector, thanks for Your response. Here is a copy from my Log.
fromtotally understood, I would not know how to fix this problem with mail
Yahoo.
Mike
20090403 21:11:42 00000043 -------------------------------------
20090403 21:11:42 00000043 version : 2.10 / 1.63
20090403 21:11:42 00000043 calltype : SMTP
20090403 21:11:42 00000043 state : rcpt
20090403 21:11:42 00000043 cip : 98.136.44.48
20090403 21:11:42 00000043 cdn : n76.bullet.mail.sp1.yahoo.com 20090403 21:11:42 00000043 from : tnel003@yahoo.com
20090403 21:11:42 00000043 hdn : n76.bullet.mail.sp1.yahoo.com 20090403 21:11:42 00000043 rcpt : mike.roberts@holodeck.myip.us 20090403 21:11:42 00000043 ruid : 1
20090403 21:11:43 00000043 sapfilter : pass (time:31)
20090403 21:11:43 00000043 saprbl : pass (time:47)
20090403 21:11:43 00000043 sapspf : none (time:16)
20090403 21:11:43 00000043 sapcep : disabled
20090403 21:11:45 00000043 DNS Error : 10061
20090403 21:11:45 00000043 sapcbv : rejected - can not resolve yahoo.com
20090403 21:11:45 00000043 result : reject (0)
20090403 21:11:45 00000043 smtp code : 452
20090403 21:11:45 00000043 wcsap finish (2141 msecs)
20090403 21:14:12 00000044 -------------------------------------
my BBS,On 2009-04-04 11:06 AM, HECTOR SANTOS wrote to Mike Roberts:
Mike Roberts wrote:
I am able to send out internet email, but when I try sending to
fix it, II do
not get the mail. Here is what I am seeing in my logs, How can I
think
it is a spam blocking problem, but do not know how to fix it.
Mike
Sender20090403 22:11:14 (07D4) MAIL FROM: <xxxxxxx@yahoo.com>...
validation pending. Continue.
20090403 22:11:16 (07D4) RCPT: Return Path not verifiable: <xxxxxxx@yahoo.com> (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: <francis02_invest@yahoo.com> 20050121 10:08:30 0001ea94 S: 250 recipient <francis02_invest@yahoo.com> ok
20050121 10:08:30 0001ea94 C: RCPT TO: <wcsap-openrelay-test-123sxa23@alqwejad.com>
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: <xxxxxxxxxx@yahoo.com>
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: <wcsap-openrelay-test-123sxa23@alqwejad.com>
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
--
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
Mike
20090403 21:11:42 00000043 ------------------------------------- 20090403 21:11:42 00000043 version : 2.10 / 1.63
20090403 21:11:42 00000043 calltype : SMTP
20090403 21:11:42 00000043 state : rcpt
20090403 21:11:42 00000043 cip : 98.136.44.48
20090403 21:11:42 00000043 cdn : n76.bullet.mail.sp1.yahoo.com 20090403 21:11:42 00000043 from : tnel003@yahoo.com
20090403 21:11:42 00000043 hdn : n76.bullet.mail.sp1.yahoo.com 20090403 21:11:42 00000043 rcpt : mike.roberts@holodeck.myip.us 20090403 21:11:42 00000043 ruid : 1
20090403 21:11:43 00000043 sapfilter : pass (time:31)
20090403 21:11:43 00000043 saprbl : pass (time:47)
20090403 21:11:43 00000043 sapspf : none (time:16)
20090403 21:11:43 00000043 sapcep : disabled
20090403 21:11:45 00000043 DNS Error : 10061
20090403 21:11:45 00000043 sapcbv : rejected - can not resolve yahoo.com
20090403 21:11:45 00000043 result : reject (0)
20090403 21:11:45 00000043 smtp code : 452
20090403 21:11:45 00000043 wcsap finish (2141 msecs)
20090403 21:14:12 00000044 -------------------------------------
But CBV does not allow me to get mail from yahoo.. It refuses it.. Any suggestions?
| Sysop: | Nelgin |
|---|---|
| Location: | Plano, TX |
| Users: | 577 |
| Nodes: | 10 (1 / 9) |
| Uptime: | 55:36:33 |
| Calls: | 9,294 |
| Calls today: | 2 |
| Files: | 16,016 |
| Messages: | 1,046,554 |