Webmail delivery problem - SPAM/blacklist issue???
Jeff Funk
J.
#############################################################
This message is sent to you because you are subscribed to
the mailing list <CGat...@mail.stalker.com>.
To unsubscribe, E-mail to: <CGateP...@mail.stalker.com>
To switch to the DIGEST mode, E-mail to <CGatePr...@mail.stalker.com>
To switch to the INDEX mode, E-mail to <CGatePr...@mail.stalker.com>
Send administrative queries to <CGatePro...@mail.stalker.com>
Jeff Funk
Bueller?? Bueller?? But seriously . . . anyone else run into this???
Jeffrey J Funk
Chief Technology Officer
Farin & Associates, Inc.
608.661.4240
jf...@farin.com
Mark Jones
On Sun, 16 May 2004 11:35:10 -0500
"Jeff Funk" <jf...@farin.com> wrote:
> So is anyone else having issues with mail sent via the webmail interface not being delivered to some major ISP's?? I believe the problem is caused by the Received From:x.x.x.x header. It shows the mail coming from whatever the ip address of your local machine is. This, of course, lands in dynablocks a lot of times. I'm assuming that spam filters are picking up on that address and dumping mail as we've received tons of complaints about mail from the webmail interface not being delivered. We can fix the problem locally, but not on the remote end. Anyone know of a way to get that Received From header to be the address of the mail server rather than the address of the users computer????
When I compose and send mail via CGP webmail, the Received headers look
pretty much the same as mail sent from any other client...
The lower-most Received header shows my personal IP submitting the email
to my mailserver, the Received header above that shows my mailserver IP
submitting the email to the recipient's mailserver.
I run a CGP mailserver for a mid-size ISP, we've had no problems with
delivery of email composed in webmail. Most of our customers use IPs
that are in dynamic block lists.
Do you have a sample of a reject message that your users are seeing?
Mark
Bret Miller
that someone's spam filter is a little overagressive. The only big
difference I saw was that Hotmail was adding X-Originating-IP in
addition to the received header.
Bret
> -----Original Message-----
> From: CommuniGate Pro Discussions
> [mailto:CGat...@mail.stalker.com] On Behalf Of Mark Jones
> Sent: Monday, May 17, 2004 9:06 AM
> To: CommuniGate Pro Discussions
Jeff Funk
sent to his own domain from the webmail interface that was disappearing.
Coincidentally, he sent me one and I noticed it scored just below the
spam assassin threshold and it scored the majority of points for being
in a dynablock. I fixed the problem locally by adding a custom spam
assassin rule. I'm only assuming the same thing is happening on the far
end, which of course, we have not control over. There is no message
that's returned. The mail just disappears.....
Jeffrey J Funk
Chief Technology Officer
Farin & Associates, Inc.
608.661.4240
jf...@farin.com
Bret Miller
> sent to his own domain from the webmail interface that was
> disappearing.
> Coincidentally, he sent me one and I noticed it scored just below the
> spam assassin threshold and it scored the majority of points for being
> in a dynablock. I fixed the problem locally by adding a custom spam
> assassin rule. I'm only assuming the same thing is happening
> on the far
> end, which of course, we have not control over. There is no message
> that's returned. The mail just disappears.....
SpamAssassin processes the "last hop" differently than the rest of the
received headers. If the user is on a dial-up, DSL, or cable connection,
and the last hop is the only hop (i.e., it didn't go through another
server before arriving on yours) then you get a RCVD_IN_DYNABLOCK hit
which ups the score a lot. This won't happen on someone else's server
since the DYNABLOCK check would be done against your server instead of
the original webmail client IP.
Bret