Hi Adrian
0.3 RM_hm_EmptyMsgid Message ID is empty, or just spaces - probable spamsign
This looks like a custom rule, but you're matching this rule because you're using an SMTP server to send rather than sendmail. It will be fixed in the next release.
Actually No Message-ID/Date part is used by Exim users to filter out Mydoom Worm mails. The ACL that is used in DATA part is:
# Reject on no message-id/date from remote hosts
deny condition = ${if !def:h_Message-ID: {1}}
message = Message SHOULD have Message-ID: but does not
deny condition = ${if !def:h_Date: {1}}
message = Message SHOULD have Date: but does not
Now this woule mean that Any Mailings from LSQL with a Missing Message ID (and all derivatives of GT::MAIL::send call being used in third party plugins) would get blocked at SMTP level if this scheck is built in...
Actually Mass Email has the drop down of sending mail as HTML.
Thanx...
HyTC
Quote:
As for the ones that have been reported: 0.3 RM_hm_EmptyMsgid Message ID is empty, or just spaces - probable spamsign
This looks like a custom rule, but you're matching this rule because you're using an SMTP server to send rather than sendmail. It will be fixed in the next release.
Actually No Message-ID/Date part is used by Exim users to filter out Mydoom Worm mails. The ACL that is used in DATA part is:
# Reject on no message-id/date from remote hosts
deny condition = ${if !def:h_Message-ID: {1}}
message = Message SHOULD have Message-ID: but does not
deny condition = ${if !def:h_Date: {1}}
message = Message SHOULD have Date: but does not
Now this woule mean that Any Mailings from LSQL with a Missing Message ID (and all derivatives of GT::MAIL::send call being used in third party plugins) would get blocked at SMTP level if this scheck is built in...
Quote:
These rules are due to you putting HTML in the email templates. They currently only support plain textThanx...
HyTC
