spam

For the purpose of identifying [possible] bot-generated usernames. Suppose you have a username like "bilbomoothof" .. it may be nonsense, but it still contains pronouncable sounds and so appears human-generated. I accept that it could have been randomly generated from a dictionary of syllables, or word parts, but let's assume for a moment that the bot in question is a bit rubbish. Suppose you have a username like "sdfgbhm342r3f", to a human this is clearly a random string. But can this be identified programatically? Are there any algorithms available (similar to Soundex, etc..) that can

I searched this topic but there wasn't anything useful for me. CODE: public function sendActivation($name, $user, $pass, $activationKey) { $to = $user; $subject = 'Account Activation'; $headers = "From: noreply@domain.tld\r\n"; $headers .= "MIME-Version: 1.0\r\n"; $headers .= "Content-Type: text/html; charset=UTF-8\r\n"; $message = "<div id='mail' style='height: auto; width: 500px;background-color: #DDDDDD; font-family: Tahoma, Arial, sans-serif;'> <p>Hello dear $name and thanks for your choise!</p> <p>Your details:</p> <p>Username: $user</p> <p>Password: $pass</p> <p><br /></p> <p>Here there

I know that in first look many users mark this question as duplicate, but after reading more than 10 question I did not get any satisfactory answer, almost all question has answers having words like "There's not much you can do about it.", "I am not sure", "There is no sure shot trick" etc. that's why I am writing this question, and I think this is very generalized questions and every php developer faces it at least once, ok enough speech :) , now my question is.. I working on a project management application and am using phpmailer to send mail when any task is created or anybody comments on

I'm using the phpmailer class to send emails. Currently gmail and yahoo do not mark emails as spam, but hotmail always does. How can I prevent this? My code is below. require_once('../PHPMailer/class.phpmailer.php'); //include("class.smtp.php"); // optional, gets called from within class.phpmailer.php if not already loaded $mail = new PHPMailer(); $mail->IsSMTP(); // set mailer to use SMTP $mail->Host = "mail.example.com"; // specify main and backup server $mail->SMTPAuth = true; // turn on SMTP authentication $mail->Username = "xxx"; // SMTP username -- CHANGE -- $mail->Password = "xxx"; //

My website sends emails to users using the PHP mail function. Hotmail and Gmail users don't receive them, or they end up in SPAM-folder. Here is the header of a message marked as SPAM by Gmail. What to do? Delivered-To: koopter1982@gmail.com Received: by 10.216.213.222 with SMTP id a72cs207473wep; Sat, 2 Oct 2010 04:26:47 -0700 (PDT) Received: by 10.216.3.19 with SMTP id 19mr3099233weg.108.1286018806068; Sat, 02 Oct 2010 04:26:46 -0700 (PDT) Return-Path: <admin@drt01.dco.fusa.be> Received: from drt01.dco.fusa.be (drt01.dco.fusa.be [193.110.251.55]) by mx.google.com with ESMTP id

Is there any way to consistently detect PhantomJS/CasperJS? I've been dealing with a spat of malicious spambots built with it and have been able to mostly block them based on certain behaviours, but I'm curious if there's a rock-solid way to know if CasperJS is in use, as dealing with constant adaptations gets slightly annoying. I don't believe in using Captchas. They are a negative user experience and ReCaptcha has never worked to block spam on my MediaWiki installations. As our site has no user registrations (anonymous discussion board), we'd need to have a Captcha entry for every post. We

Suppose we have an application that acts as a middleman, allowing Company A to send reports to their customers. Company A --> Company B (me)--> Company A's customers After getting the report we send email notifications to the recipients, but they necessarily originate from our company notifications email address e.g. joe.bloggs@a.com --> notifications@b.com --> peter@c.com Now, customers tend to reply to those email notifications, wanting them to go back to whoever sent the report at Company A. Instead, they end up back at our address, notifications@b.com. A simple solution may be to change