spam blockers

[progman1010]

hello! i have a site which is being built to allow people to send emails through it. It actually connects to an external SMTP server for sending from the website, but i don't know that it should matter for this particular issue.

The main problem i'm having is that the SPF record for the sending domain and the rDNS is missing (more details below). The website is an online community and never used for spam, but i do need to allow anyone to send a message with their address at the top.

How can I get around these two issues? These seem to be the big ones getting the emails caught up in the spamblockers. The rest of the problems listed below I can address easily.

Details from SpamAssassin:

Content analysis details:   (5.3 points, 5.0 required)

 pts rule name              description
---- ---------------------- --------------------------------------------------
 0.0 MISSING_MID            Missing Message-Id: header
 0.7 SPF_SOFTFAIL           SPF: sender does not match SPF record (softfail)
 0.0 HTML_MESSAGE           BODY: HTML included in message
 1.7 MIME_HTML_ONLY         BODY: Message only has text/html MIME parts
 1.8 MIME_QP_LONG_LINE      RAW: Quoted-printable line longer than 76 chars
 1.1 HTML_MIME_NO_HTML_TAG  HTML-only message, but there is no HTML tag
 0.1 RDNS_NONE              Delivered to trusted network by a host with no rDNS

 

[smah]

allow anyone to send a message with their address at the top

I assume that by that statement you mean that it recipient should see the message as being from the user's e-mail adddress, not the server that's actually sending it?

This is interesting, because assuming that the 'sending' users could be from any domain name, there's no way you could correct the SPF records. However, this occurs all the time in the real world, usually without problems, so there must be a way to do it. What immediately comes to mind for me is job hunting sites where you can 'send this job to a friend'. A quick check of the headers of one of these messages, shows that the 'from' field is actually a generic e-mail address at the real sending mail server domain. The header also contains a specific 'reply to' address which is the correct 'user' address. So, sending from the real mail server domain instead of trying to spoof it, should resolve the SPF issue (assuming that it's configured correctly for that domain).

As for the reverse DNS thing, I guess that would have to be the rDNS for the sending mail server, which you can't do anything about. The mail server admin (or more likely thier ISP) will need to correct that.

 

[progman1010]

your posts helped. my issue was mainly with the SPF record. I've had fewer problems since I figured out how to use it.

It's not an easy issue to solve, but I think i'm making progress into the right direction.

Thanks!