Setting OE email to direct, we have the ability to email within the company. When testing an email address outside, ie: abc@gmail.com, we get "There was an error during the email test procedure".

I know all the server settings are correct, as well as the authentication settings.

We have tried the MAPI settings also and they do work. It's just not a preferred method.

Lastly, we are running on a terminal server, although MAPI works on all profiles as well as the direct method to internal addresses.

Any ideas? Am I missing something?

What port number is your ISP using for e-mail transmission? A user in San Jose just had their ISP change their SMTP port.

In the e-mail setup, does "verify e-mail" work properly? It sends a test e-mail to your "reply to" email address.

port 25

When I verify to an internal email address - it works.
When I verify to an external address - if fails.

Carefully - (very carefully - check the web address you are using to send to your ISP. Is it possible there is a typo?

By "fails", what symptoms are reported?

Hi Todd,

I have experienced a similar scenario to the one you describe. We use a hosted exchange server and were able to send to any other address also using this same host, but no others.

We have solved the problem (external emails now get through) by turning on the "Server requires authentication" option and adding the account information in the email setup in Adagio.

Hope that helps,

I have tried turning on 'the server requires authentication' and email still doesn't go through. I've tried user accounts, the administrator account and users accounts with administrative rights.

To Andrew's question above...Adagio returns "There was an error during the email test procedure".

Also, the Email method is set to direct, Server requires authentication is checked and account name and password are filled in.

Still, if I send to an internal address, it works fine. When I try sending to an external address, I get the error above.

For the account name, try including the "@domain.com". When I access webmail, my account name is simply "ryan". But in Adagio i need to use "ryan@stiefgroup.com".

Maybe you'll get lucky!

Thanks. Yes, I already have the domain included.
Doesn't work & returns the same error.

-Todd

Are you using an ISP or an internal mail server (such as exchange)? If it's an internal mail server, that may potentially not reach external email addresses.

Hi Todd,

You should also check that whatever firewall or anti-virus you have installed will let SMTP mail through. These product often block outbound SMTP traffic since it is unusual.

hmmmm, Yes, it's an internal mail server.
We are able to send email from the Terminal sessions through Outlook, as well as Adagio through MAPI. It's just the direct method that's not working. You still think it's a firewall issue?

That's what was suggested by our network manager when asked about your symptoms. You may need to let your firewall know that it's "OK" for Adagio to be sending this traffic.

Andrew-
I checked with AT&T, and they said port 25 or 465 should work - no problem. They also indicated that both ports are working correctly and no traffic is being blocked.

So, Which port does Adagio use? Is there a way to change this setting? As for my firewall, all traffic is open on 25 and 465.

Did you check the settings on your firewall?

Hello Todd,

We are using Gmail and their requirements to send emails by their smtp server include "Use Secure Connection" TLS which automatically requires port 587. At the present time it is not possible to set either of these necessary settings in Adagio email setup under the direct method so we use Eudora 7.1 to send the emails using Mapi. It is almost as fast as sending them direct.

Andrew-
I checked the firewall, and all seems OK.

Rick-
We use Outlook, so we could use MAPI, but direct is preferred. It should work, just not sure why it doesn't.

-Todd

Hi Todd,

While "all may seem OK" with your firewall, we're pretty certain here that it's been set to allow Outlook to talk to the SMTP ports but disallow other programs (like Adagio). They are usually set this way to prevent viruses from e-mailing themselves around.

OK, then what changes must I make?
I've allowed SMTP traffic on ports 25 and 465. Is there something else I'm missing? I;m sure the fix is an obvious one, I just can't put my finger on it.

Are there any diagnostics I can run from the server that hosts Adagio (like a ping test) to verify traffic is getting through?

Thanks-

Sorry Todd - we don't even know what firewall you're using. Seems like a good time for a visit from your favorite network technician.

There is a test email button on the e-mail setup dialog.

BTW - are you "talking" to your Exchange server, or directly to your ISP?

You should be directing Adagio to communicate directly with your ISP's SMTP server.

I have it going through my Exchange 2007 server.
Can I use gmail?
If so, is there a way to change the port Adagio uses? BTW, what port does Adagio use?

Thanks-

Great News!!!
http://clip2net.com/page/m0/400032

It worked. I created a new email address with my ISP. I asked them to change my smtp port from 465 to 25 (which they can & did).

I tested the email and it worked perfectly!!!

It would then appear to me that the problem was not my firewall, but rather my Exchange 2007 server. I suppose it doesn't matter which way it works, as long as it does.

Thank you all for your kind help.

-Todd

oops, perhaps I spoke too soon.
The 'test' worked to my att account.
I tried sending an order confirmation to an external address & it did not send. When sending from the que, it is immediate?

-Todd

OK, it appears that the only time it works is when the return address is the att.net account. I assume AT&T prevents us from sending from 'any' account, although I did verify customerservice@todds.com as a valid account.

http://clip2net.com/page/m0/401215

So now, anyone who replies to an email from adagio, will be sending the mail to my att.net account. hmmm.....

Any thoughts???

-Todd