;; QUESTION SECTION: ;google.cm. IN A ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6369 ;; ANSWER SECTION:
google.cm. 518 IN A 72.51.27.58 zone "cm" IN { type delegation-only; }; ;; QUESTION SECTION: ;google.cm. IN A ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12264
The last 64 bits are for auto-negotiation, so your/64 does one LAN. A/48 should be assigned to end users, who can then use as many/64s as needed (up to 65536). So a/32 is just 65536/48s, which isn't much.
The bounces you're getting are from other spam using you as the From address. Spam sent from your machine would have random addresses not necessarily your own. But you might still have a trojan running that could be used to send spam so you should check.
I get random pings on my 56k dial-up, on an adsl connection, on another 56k dial-up, on a cable connection, I had someone on another dial-up isp run tcpdump and they get it too.
It's extremely annoying, and has caused me to block the response.
I think ISPs should block certain ports like 135-139. Too many people have these ports wide open. Once I was given a broadcast ip... and a few hundred windows boxes destroyed my available bandwidth.
If you add up all the accesses to port 135, I'm sure it comes to a lot of wasted bandwidth.
Of course certain ports should not be blocked if the user wishes - like port 25. Several ISPs want you to pay EXTRA for a static ip just to have such ports unblocked.
And then did not complain about unofficial clients using it. It's probably just a trick to get people using other clients to require using Messenger so much that they have to switch to MSN's client where they can see advertising.
It probably would work with a bellsouth.net destination address, my point is if you run a mailserver and an email needs to be bounced, you send an email from <>, if you're not allowed to connect to your destination's mailserver, and the only mailserver you have access to is your isp's which refuses to relay the email for you then you can't send out bounced emails properly.
It's all very well saying "residential users should use their isp's mailserver", but what about when that mailserver doesn't appear to know what an RFC is:
Connected to mail.bellsouth.net. Escape character is '^]'. 220 mail.bellsouth.net ESMTP server (InterMail vM.5.01.04.25 201-253-122-122-125-20020815) ready Sun, 13 Apr 2003 19:17:26 -0400 MAIL FROM:<> 250 Sender <> Ok RCPT TO:<slashdot@slashdot.org> 550.net 022: Your current IP address is not allowed to relay to slashdot.org Solution: Connect using BellSouth Internet Service. QUIT 221 imf35bis.bellsouth.net ESMTP server closing connection
<> is an important from address - it's used by the mailserver when it bounces a message, so that the bounce can't be bounced back and forth in a loop
For that particular server I used to test that, I had to arrange to send email via someone else's mailserver using smtp auth >:|
Slashdot Mirror
The Kindle isn't off when displaying the screensaver, so people already leave them on.
Buying a single copy of each issue by creating a new account each time would bypass this form of protection.
The online version would need to host every page for on demand access instead of providing downloads.
You may hide your master DNS servers but your slaves are probably still master for "localhost".
;; QUESTION SECTION:
;google.cm. IN A
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6369
;; ANSWER SECTION:
;; QUESTION SECTION:
;google.cm. IN A
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12264
google.cm. 518 IN A 72.51.27.58
zone "cm" IN { type delegation-only; };
The last 64 bits are for auto-negotiation, so your /64 does one LAN. /48 should be assigned to end users, who can then use as many /64s as needed (up to 65536). /32 is just 65536 /48s, which isn't much.
A
So a
The bounces you're getting are from other spam using you as the From address. Spam sent from your machine would have random addresses not necessarily your own. But you might still have a trojan running that could be used to send spam so you should check.
I "unsubscribed" a unique spam trap email address and it started recieving spam a few months later.
Looking at my mailboxes, Habeas headers are being used legitimately in mailing lists (gentoo and the lkml)
They give out free licences to individuals.
"Habeas has begun systematically adding the IP addresses of the hundreds of compromised PCs sending this spam to the Habeas Infringers List (HIL)."
All bounces are sent from , they can't loop.
Then the sending relay would bounce it.
Interesting index.museum doesn't exist except as a *.museum record, which I found out when I blocked wildcard records on that domain :|
I get random pings on my 56k dial-up, on an adsl connection, on another 56k dial-up, on a cable connection, I had someone on another dial-up isp run tcpdump and they get it too.
It's extremely annoying, and has caused me to block the response.
How can you prove that you own the domain (if needed) if the contact information is invalid?
What would you do if your registrar goes bust?
All of this information doesn't need to be exposed in the WHOIS database though.
I think ISPs should block certain ports like 135-139. Too many people have these ports wide open. Once I was given a broadcast ip... and a few hundred windows boxes destroyed my available bandwidth.
If you add up all the accesses to port 135, I'm sure it comes to a lot of wasted bandwidth.
Of course certain ports should not be blocked if the user wishes - like port 25. Several ISPs want you to pay EXTRA for a static ip just to have such ports unblocked.
Except Microsoft originally released their protocol for Messenger: http://www.hypothetic.org/docs/msn/ietf_draft.txt.
And then did not complain about unofficial clients using it. It's probably just a trick to get people using other clients to require using Messenger so much that they have to switch to MSN's client where they can see advertising.
Except it won't play in QuickTime either...
Thankyou. Unfortunately I deleted the two files I had downloaded before I read your comment :(
What's wrong with using jikes to compile your programs? It's not even 1 mb, it just needs rt.jar from the JRE.
jikes website
The JRE includes the same huge libraries that the JDK has, so there isn't much point in downloading the JRE on its own anyway
It probably would work with a bellsouth.net destination address, my point is if you run a mailserver and an email needs to be bounced, you send an email from <>, if you're not allowed to connect to your destination's mailserver, and the only mailserver you have access to is your isp's which refuses to relay the email for you then you can't send out bounced emails properly.
It's all very well saying "residential users should use their isp's mailserver", but what about when that mailserver doesn't appear to know what an RFC is:
.net 022: Your current IP address is not allowed to relay to slashdot.org Solution: Connect using BellSouth Internet Service.
Connected to mail.bellsouth.net.
Escape character is '^]'.
220 mail.bellsouth.net ESMTP server (InterMail vM.5.01.04.25 201-253-122-122-125-20020815) ready Sun, 13 Apr 2003 19:17:26 -0400
MAIL FROM:<>
250 Sender <> Ok
RCPT TO:<slashdot@slashdot.org>
550
QUIT
221 imf35bis.bellsouth.net ESMTP server closing connection
<> is an important from address - it's used by the mailserver when it bounces a message, so that the bounce can't be bounced back and forth in a loop
For that particular server I used to test that, I had to arrange to send email via someone else's mailserver using smtp auth >:|
I have 70 floppy disks right now that work fine - I format them on a 486 in dos, and use them fine in nt and 2k, on multiple pcs
But those users can't disable identd so its still possible to ban such users