Quote:
Originally Posted by mavas
The point of why I wanted to see if it would forward when sending from comcast to the godaddy that would intern forward the email to freehostia is it still has parts of the comcast headers to make sure that there was no issue with the headers causing a filter or issue of some sort.
|
Good thinking, although in this case it's extremely unlikely to be a header problem.
Basically, headers aren't analyzed at the SMTP session level at all — they're just part of the message data stream. Based on what we're seeing here, the message transfer from Comcast isn't getting beyond the SMTP session — the very "best-case" scenario is that Freehostia is "hanging up" on Comcast's mail server, but based on what Freehostia claims it's seeing (or
not seeing) in its log files, we're not even getting that far — it sounds much more likely that Comcast either can't get to Freehostia's server or is unwilling to connect to it for some other reason.
If
Freehostia was receiving and bouncing the message, then it could quite possibly be the headers, but because the message isn't getting delivered to Freehostia's servers, there's no point at which Freehostia could be analyzing any headers.