Richard,

I use bellsouth.net which is ATT (ATT merged with them little while back).

I have been using 2.6 R:mail to send SMS messages via email and email
invoices since August 2007.

Example of what I have set up

SMTP Server Name: mail.bellsouth.net
Port: 25
Display progress should be checked

When test is run I get a response - <250 isp.att.net>. 
Also I get the response dialog connection good!

Your router should not be an issue because port 25 is a standard port for
smtp mail and if your client email is working on your test PC then R:Mail
should work too!

What router are you using!

What AV are you using and is it monitoring and filtering your email?


Best Regards,


Oma Cox
O.C. Services Inc.
P.O. Box 5485
Brandon, MS 39047

662.820.7599
601.992.6785

www.ocservicesinc.com

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Doug
Hamilton
Sent: Sunday, March 29, 2009 11:23 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: R:Mail Help -- Please

Richard, I think I ran into something like this a year or two ago (so 
forgive me if it's a little sketchy - precede every sentence with "I 
think", "Maybe", etc.)  We were trying to email about 70 newsletters 
through SBC using RB 7.6 & R:Mail 2.6 and I ran into the same problem 
you did.  I called SBC and they require Secure Socket Layer (SSL) which 
isn't supported in R:Mail 2.6.  Our workaround was to email the 
newsletters through our web hosting site.  Fortunately, they didn't 
require SSL but, as an aside, had a limit on the number emails that 
could be sent - max of 50 in 5 minutes or 200 per hour, so I had to put 
appropriate timers in the code.
More recently I was setting up email for another client on AT&T DSL (not 
R:Base related) and I believe AT&T required SSL to be set on in Outlook 
Express email.
So tying those two setups together, AT&T may require SSL which, AFAIK, 
isn't supported in 2.6, it is in 3.0.
Best bet is to call AT&T to confirm.
Hope that helps,
Doug


Richard Croy wrote:

> Okay, I give up! <G>
>
> I have tried every possible configuration that I can think of, both 
> with the
> firewall turned on and turned off, to configure R:Mail (Ver. 2.6 for 
> R:Base 7.6) to work with my STMP
> (AT&T) and all that I get is repeated "Connection failed" messages.
>
> I have been trying the same settings -- same server name, port, 
> log-in, and
> password -- as I use for my e-mail account on AT&T (which works 
> great), but
> these don't seem to work with R:Mail. Nor does anything else I have 
> tried.
>
> So I'm stumped (or, okay, maybe stupid). I seem to recall some 
> exchanges on the
> R:Base List from others who had a similar problem, but because I 
> wasn't into
> R:Mail at the time, I did not save them. Duh!
>
> Now I'm trying to build R:Mail into a meeting registration 
> application, but
> I'm going nowhere fast (or slow). Anything which will help me stop 
> spinning my wheels will be gratefully appreciated.
>
>
> Richard S. Croy
> [email protected]
>
> ====================================
> This message has been checked with an up-to-date
> version of Norton Antivirus before sending,
> ====================================
>
>

--- RBASE-L
================================================
TO POST A MESSAGE TO ALL MEMBERS:
Send a plain text email to [email protected]

(Don't use any of these words as your Subject:
INTRO, SUBSCRIBE, UNSUBSCRIBE, SEARCH,
REMOVE, SUSPEND, RESUME, DIGEST, RESEND, HELP)
================================================
TO SEE MESSAGE POSTING GUIDELINES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: INTRO
================================================
TO UNSUBSCRIBE: 
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: UNSUBSCRIBE
================================================
TO SEARCH ARCHIVES:
Send a plain text email to [email protected]
In the message SUBJECT, put just one word: SEARCH-n
(where n is the number of days). In the message body, 
place any 
text to search for.
================================================


Reply via email to