Dean Mumby wrote:
>
> I have reported this to bugs@e-smith.org
>
> Are you using essg 4.1.2 it seems that fetchmail is doing a
> dns lookup on all receipents listed in the headers and if it
> cant resolve all the domains it simply leaves the email on
> the isp server
>
> Apparently sme 5.1.2 does not do this as there is a no dns
> spec now.
Your problem isn't the same as mine. My situation is that one particular ISP has a very slow CHAP responder which fails to complete the authentication of the caller before the mailserver times out and says it couldn't find the multi-drop mailserver at all. On the other modem dial-up system I have running - my own - I get reliable connections at every mail call. When I swap the equipment over, so that I use the modem/router combination normally used on the slow-response ISP, but with my ISP, I again get good connections every time. My own equipment also fails to get quick enough authentication on the troublesome ISP. So it's not the equipment's fault, nor is it a bug in e-smith.
When the dialup is to browse the internet the authentication delay isn't a real problem. Internet explorer on the client PC gets tired of waiting and puts up error 404, but a few more seconds, and a quick F5, gets it going. The problem with the mailserver is serious because mail fails every time and always goes for a second dialup, and often a third, before it gets an authenticated connection within the timeout window - more phone bill escalation.
What I am looking for is some way to hold back the mail server for a bit longer after it triggers a dialup before it calls the mailserver for mail.
Anyone have any ideas?
Ed Form
3 Replies
824 Views