Consider enabling internet session logging.  The log can be helpful in

pinpointing the point of failure.  I STRONGLY suggest reading the help file about internet session logging.  Don't forget to disable it.  Don't post content of the log with obfuscating your login credentials.

Also, this article shows inbound.att.net uses port 445 for SMTP and requires SSL so make sure you have those settings configured correctly.

http://www.att.com/esupport/article.jsp?sid=KB401570&cv=804

Technically, this isn't a Pegasus problem but I am not having too much success getting help elsewhere.

Two days ago I had ATT U-verse Fiber Optic service put in to my house to replace my older, slower DSL connection. Internet works and email will download mail but I cannot send mail. I went to the ATT help site to see what they had to say about it and they had some instructions on what to type into the POP3 and SMTP boxes for Outlook to make mail work. I figured Pegasus had the same boxes so it should work for Pegasus, too, no?

So I put "inbound.att.net" in POP3 and "outbound.att.net" in the SMTP boxes as shown and .... NO SENDING EMAIL. Oops. Try some different stuff but still no go. ATT said they'd help me if I signed up for a $15 a month plan for software help. I JUST NEED HELP THIS ONE TIME!  I don't want a lifelong contract. The Dell (it's a Dell computer) techs are still trying to find a fix so I figured I'd take a chance and see if any of the fine folks here might have some idea of how to make Pegasus work on webmail-type service instead of older dial-up and/or DSL systems.

 Any ideas? I appreciate any tips, ideas  or information you might have that can make Pegasus work on a webmail service. Thanks in advance!

[quote user="robhic"]So I put "inbound.att.net" in POP3 and "outbound.att.net" in the SMTP boxes as shown and .... NO SENDING EMAIL.[/quote]

Try the other way around: IMO "inbound.att.net" is for SMTP while "outbound.att.net" for POP3 access, or does ATT tell you explicitely to do it like you did?

I think he has that part right. 

att.net 

POP Server: inbound.att.net   Port: 995   SSL required

SMTP Server: outbound.att.net  Port: 465   SSL required

I

posted earlier but suspect it is delay pending moderator approval

because it contains a link to the att server matrix from which I pulled

this info.  My suggestions are to check the host configuration (port,

credentials & SSL enabled) and to turn on internet session logging

to try to identify where in the process the failure occurs.

Thank you two gentlemen for the replies. The way I had it is the way they depict it on the "help" page at ATT for use in Outlook email. At this point, I'll try anything and, so far, you two are giving me as much info as the ATT people have![:@]

 The interesting thing (or not :-) is that before, I used "mail.bellsouth.net" for email as I have a bellsouth email address. That still works to download my email!

 I'll go try reversing the "inbound"  and "outbound" positions in Pegasus right now.

Thanks so much for the info and help!

OK, I reversed the SMTP and POP3 settings as advised but no luck. I got this message upon hitting "send": 15: Peer connect failure (the host has refused the connection).

 I hope that means more to you than it does to me. The Dell tech guy called me meanwhile and wants to delete Pegasus and reinstall. I have my backup copies of PMAIL current so that should (hopefully!!!)  go all right.

Any other further idea how to turn Pegasus from a DSL/landline emailer to a digital/fiber-optic mailer? Does it make a difference?

The ATT service comes with Yahoo! mail which works so I am not completely hosed but I do NOT see why Pegasus cannot be made to function with this new setup! I don't want Yahoo!

Thanks, again, for any more ideas or information.

A reinstall of Pegasus won't help.  You really need to identify where the failure is occurring.  You can get this from an internet session log.  I suggest returning the servers to inbound.att.net for the POP3 host (port 995 via SSL) and outbound.att.net for the SMTP host (port 465 via SSL) then enable internet session logging.  Now attempt to retrieve mail.  A record of the communications between Pegasus Mail and the att server will be recorded in the log.  Read the help file on internet session logging as there is info there about what gets logged (eg: login credentials, so be careful what log content you post) and where to find the log files.  Don't forget to disable it when done troubleshooting.

The location where you enable internet session logging is on the General tab of Tools > Internet options. 

It is important to make sure you have configured with the correct ports and have SSL enabled.  Also, sometimes an SMTP server still works with legacy settings which are port 587 and STARTTLS so this is worth testing. 

I went and printed the text and graphics from the ATT HELP page. I then went over it with a bit more focus. What I found and what I think has now made Pegasus functional with the ATT U-Verse service:

"USERNAME" can be your username or can be the complete email address. "SSL" must be turned 'on' where it seems Pegasus has it set to 'never' as its default.

Once I changed the username boxes to complete email addresses (where needed) and turned SSL 'on', made a couple of other changes/adjustments, it seems to be finally working. Never have I sent myself so many "test" emails! I must have sent 20 with around 20 variations of settings in the POP3 and SMTP boxes! I started to get "sending mail" from Pegasus and then I fine-tuned it and it sent mail. I will make sure it is OK but I feel it is working.

Your tip about the SSL made the final difference, I think, and I thank you. I've NEVER  had to make so many changes to get Pegasus to work before whether on dial-up or on DSL so this had me completely baffled.

Thanks to the both of you for your time and help. This was making me crazy so I am very relieved to have it fixed.

 EDIT: I'm going to go out on a limb and say it is fixed. I've just sent a few replies and none have bounced back or been refused. Pegasus says mail sent successfully so I think (hope?) this is a done deal! If it changes I will be back to whine about it! [;)] Thanks again for the help!