Quote:
|
Originally Posted by goblin
Yes, that's the thing I am trying to get away from. I want for the most part reliability. I want to know that as soon as someone sends me an email I am going to get it. This of course (under the present circumstances) requires NTL to have absolutely no part in the process other than providing me with a connection. If possible, I don't want my mail to even touch NTL's mailserver. I imagine this must be possibly somehow, looks like I have some investigating to do  |
I don't care about incoming servers, because they are so easy to come by - heck, I run one on my own machine. Outgoing servers are more of an issue, because some servers do not accept mail directly from dynamic addresses.
My current setup is to send messages directly except when sending to a few preset fussy domains, where they get sent via the NTL outgoing SMTP servers. Because I don't trust these servers as far as I can throw them, I made a little program that monitors them, by sending an email every hour or so. Lots of messages just randomly go missing, take a week, etc. Even more interesting is when the outgoing server refuses to accept the message, but then delivers it anyway, resulting in messages being delivered multiple times when the client retries. I have been seeing quite a lot of that over the last day or two.