Except that it's the misused version of 'begets', and not the actual concept of 'begs'. It's about as correct as 'wratched' being used currently in place of 'wretched', but it's never been about 'begging'.

It's easy to remember 20+ web passwords if they mean something to you:

I Use Gmail For Sending Email = IUGFSE.

My Money Is Safe At Toronto Dominion Bank = MMISATDB.

I Love To Eat Pizza At Joe's Pizzeria = ILTEPAJP. ...add a sequence or some other memorable number, perhaps a standard special character as the 2nd or 3rd character, and capitalize the even, odd, or 4th and last characters or whatever makes sense to you and you end up with:

iu@GfsE54
mm@IsatdB54
il@TepajP54

...easy to remember, and pretty strong passwords.

Same holds true for an unarmed populace.

+8

It's still British food.

Very rarely are static and dynamic IP's issued from the same subnet. If you can't get out of a blocked range and won't switch ISP's, then smart-host.

Really? From TFA: "We are singling out spammers on our network and blocking port 25," said Mitch Bowling, Comcast's vice president of operations. "We don't think it's the right approach to blanket port 25. The right approach is to seek out people who are spamming our network and others." ...so, any spammers they find, instead of terminating the account they block port 25. Of course everyone else they don't 'find' can still spam away...

If you aren't able to get a proper reverse DNS entry for your public outbound mail server then you probably shouldn't be running one. If you have a real static IP (as opposed to "my IP doesn't seem to change") - then it shouldn't be a problem getting the DNS setup correctly.

To answer the original question about "what should you do", the answer is simple - if the ISP won't issue a PTR record because of the type of connection being used then the customer should smart-host their mail through the ISP mail servers to ensure global reachability. As you say, often the edge device is a swiss-army knife and in many cases the admin isn't competent enough to properly secure/maintain it. This is exactly what blocking outbound SMTP from dynamic space is meant to accomplish and I'm pleasantly surprised to hear that Comcast/Verizon have finally started to implement what every other responsible ISP has been doing for a decade.

5) Stop trying to run a mail server from a dynamic IP address and wondering why the rest of the world doesn't want to accept your mail.

Thank you!

To play devil's advocate using your example it'd be the same as selling "child poison" and saying there are plenty of other things you could do with it. :) I don't disagree with you that tools can be abused for non-intended purposes, but this software is being promoted for its intended purpose. The fix is stronger security protocols of course, but I couldn't resist the analogy - sorry.

Interesting idea on the both hands....

Only in MDU's, otherwise Fibe 16 is the top end which is provisioned with ADSL2+.

Waves of Mass Destruction...

Visa doesn't do hex, and they certainly wouldn't convert spaces to binary. Most of the credit card import systems use formatted flat files. The problem is more likely an alignment issue and the credit card number itself was 4231 4885 5308 1845.