View Single Post
  #16 (permalink)  
Old 21-09-2007, 12:19
247h's Avatar
247h 247h is offline
Premium Member
 
Join Date: Nov 2006
Location: Buckingham UK
Posts: 260
Send a message via AIM to 247h Send a message via MSN to 247h Send a message via Yahoo to 247h
Default

Quote:
Originally Posted by esnail View Post
...The problem I was finding with yahoo was that the message being sent wasn't arriving at the yahoo junk folder anyway.
I don't know if that's also true of my situation — all the messages I'm describing are held in the mail queue of my Dedicated Server and, after they are finally delivered (often forcefully), I'm not party to any information from the Yahoo account holders whether the messages arrived as Junk Mail and whether they have subsequently whitelisted those sender addresses or not ...

If you know your messages are never being delivered then it suggests they are staying in the mail queue until expiry, or they are being dumped by the server's own message filters (yes it happens), or worse still, your server has been blacklisted by Yahoo. Until you ask your server Admin if those are being held in the queue, or what the queue deferral messages contain, how can you know?

I have the impression that the eUKhost experiments were probably not done with mailing list or forwarded examples like my own, but regularly addressed mail which I don't seem to have a problem delivering to Yahoo addresses — either that or none of my clients are sending messages to Yahoo accounts other than in the ways I described! All I can confirm is that an eUKhost support person has logged into my Dedicated Server as root and successfully sent an email to their Yahoo test account, which is partly why I arrived at the conclusion that it's only affecting Mailman, apps and forwardees.

This prompts me to ask Mark, who in your organisation checks the mail queue on each Shared Hosting server and manages it like I do with mine?
__________________
Gadge

Too many nice toys — too little time to play with 'em!

Last edited by 247h; 21-10-2007 at 16:31. Reason: repair emdashes changed by database update to utf-8
Reply With Quote