Hello Mark,
Friday, July 6, 2012, 9:41:20 PM, you wrote:
MF It does this by connecting to the sender's MX and attempting to send a
message to the sender
And if the response is something like Greylist please try later?
--
Best regards,
Niamh
I had the same problem -- because someone from China is brute-forcing
all info@... accounts.. Once they find an easy password, they abuse
it with millions of spam..
- wrote code to check everyone's passwords for easyness (?) and forced
ppl to change their passwords -- or I changed it for
On 7/8/2012 11:00 AM, spamdyke-users-requ...@spamdyke.org wrote:
I think that the simplest way of matching up messages would be if the
log messages contained the Message-ID field from the email headers. I
checked the TODO.txt file, and Frank beat me to the request:
Log the Message-ID field so
Hi,
Am 07.07.2012 um 21:01 schrieb Eric Shubert:
Looking at the log messages, I see from: (unknown) in some cases. I
presume that this is the envelope sender, while the message/internal
sender is used for the graylist entries.
Hopefully not. I haven't had a look at the code recently, but
