----- Original Message ----- From: "Fritz Borgstedt" <[EMAIL PROTECTED]> To: "Questions and Answers for users of ASSP Anti-Spam SMTP Proxy" <[email protected]> Sent: Monday, October 15, 2007 8:34 Subject: Re: [Assp-user] Empty recipients
> >>Blank recipients must be allowed per an RFC that I cant recall off the >>top of my head. There are many types of notification emails that are >>sent with a NULL sender of '<>'. This is done intentionally to >>prevent >>mail loops. > > Yep, but the discussion here started with a blank "from" field. > I don't know how it got confused, but I was referring to the "to" field. I consider a "recipient" as the person receiving the email. What is the "Empty Recipient" in Penalty Box referring to? I look at our mail logs and it shows (The line is tab delimited, so I put each column on a separate line for easy reading): Column 1: 2007-10-15 02:43:07 Column 2: gbe.com Column 3: "" Column 4: [EMAIL PROTECTED] Column 5: "" Column 6: SNDR=ENODNS Column Description: 1: Date/Time 2: Client Domain 3: Destination Domain 4: Sender (Mail From) 5: Recipient (Rcpt To) 6: Status -- SNDR=ENODNS Sender domain has no DNS/MX entries ... ... As I was looking for the exact wording in ASSP for what I have selected, I can't believe I missed this one little important setting under "Validate Sender" ... Validate Sender Domain MX/A. Yes, it is now active. I bow my head in shame. One question that I have been meaning to ask, what is trying to be accomplished by not specifiying the receipient? Thanks! ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
