Hi all,

I'm running RHE3 / PSA 7.14 and seem to be having a heck of a time sending out emails through my web server from my laptop using Outlook Express.

Either:

a) connection to my mail server is extremely slow, and mail finally gets delivered -- or

b) connection to my mail server is extremely slow and I get a message stating, " The server you are connected to is using a certificate that could not be verified. A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider. Do you want to continue using this server? "

When I first got the server, I couldn't send out emails *at all* because I would get the error message, "553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1) " ... so I changed my Plesk CP email settings to allow email relaying (restricted / depending on password).

After that, the *only* way I could get Outlook Express to send emails out through the web server was to set:

a) My server requires authentication (Tools -> Accounts -> my web server -> Servers tab), and

b) Outgoing SMTP / server requires a secure SSL connection (Tools -> Accounts -> my web server -> advanced tab)

If I do not have any of these options turned on, I cannot send out any emails. Period.


Can someone please tell me what I need to do to speed up my email connections and / or properly configure Outlook Express / Plesk?


Thanks ;-)

That one could well be causing the problem if the server doesn't have a valid SSL cert installed on the root domain.

Personally I tell folks to set up their Outlook to Requires Authorization but not not an SSL connection for authoization. Then I can use a self-signed cert for the main domain on the server since that domain isn't used for anything other than control panel access.

RE: Personally I tell folks to set up their Outlook to Require Authorization but not an SSL connection for authorization.

Wish I could do that -- but for whatever reason, I can't squeeze out an email if I don't have outgoing SSL turned on. I'm completely baffled.

RE: Then I can use a self-signed cert for the main domain on the server since that domain isn't used for anything other than control panel access.

I don't suppose you have step-by-step instructions that I can refer to so that I can give this a try?

I can suggest try it...
Repair Outlook Express and Windows Address Book tools. - Repair and recovery Outlook Express folders and emails. Undelete Outlook Express messages. Recovering and repairing Windows Address Book.
and
Easy Outlook Express repair tools. - Repairing a damaged or corrupted Outlook Express folders ands messages.

Thanks for all the suggestions, however, the problem with the password not being accepted (intermittently) was resolved by formatting my box ;-)

I'm not sure if I mentioned this in the original post, but Up2date died half way through and I believe this was responsible for messing up a number of things.

However --

Even after the box was formatted, it still took 30 seconds to send an email or login to FTP.

After some digging, I was able to find a page via an SWSoft Forum to fix this, and now I can send emails blazing fast and login to FTP without any delay.

If you own Plesk and have delays sending emails or logging into FTP, check this out:

http://forum.plesk.com/showthread.php?thre...ghlight=smtppsa

... and the official FAQ

http://faq.sw-soft.com/index.php?ToDo=view...Id=322&catId=61

The problem (as far as I understand) has to do with DNS not being resolved, Outlook Express + Windows XP Service Pack 2.

may be this software will solve ur problem guys..
Repair Outlook Express and Windows Address Book tools. - Repair and recovery Outlook Express folders and emails. Undelete Outlook Express messages. Recovering and repairing Windows Address Book.
and
Easy Outlook Express repair tools. - Repairing a damaged or corrupted Outlook Express folders ands messages.

Hi,

My users just started complaining about the delay in sending emails. They've been experiencing this since I moved them over (as have I) but now that they're complaining I have to do something about it!

I've read the Plesk FAQ on this problem (http://faq.sw-soft.com/article_22_298_en.html), and understand what to do to fix it, but don't quite understand *what* I'm doing by following those directions. So my questions are:

#1 What nameservers should I have in my resolv.conf file? I currently have two Ev1 servers in there and they seem to be valid. Should I have my own nameservers in there instead?

#2 Why does the server require that the sender be "reverse resolvable" as a default? Is this a security setting? My guess is that resolving the reverse DNS of a sender reduces the likelihood of spammers being allowed to send. If my understanding is correct, don't I reduce my security by turning this off?

Thanks!

Elle

Ok, figured out most of it on my own so thought I'd post to add to the wealth of information on this board (hopefully not subtract from the wealth)!

#1 I put my own nameservers in the resolv.conf file. Still not sure what this file does but I figured it was better to have my own nameservers that Ev1's.

#2 Still don't know why exactly the server does this (ask for TCPREMOTEINFO) but figured out what "-Rt0" means from reading another thread and getting directed to the man page for tcp-env (http://forums.ev1servers.net/showthread.php?t=41458 fascinating read). I put "-t5" in my file.
I also learned that if you've set up another SMTP port to deal with ISP's blocking port 25 you have to remember to edit both the standard smtp_psa file and the one you set up for the alternate port.

That's it! Now on to upgrading PostGreSQL!!!

Elle