David,
As part of the initial installation, and any future SMTP mail server
changes, you will need to configure R:Mail to communicate with the
SMTP mail server(s) that you are using.
Use the "Test" button to perform a test for the host name and port
number. The process will test if a connection to the server can be
established using the parameters provided. Note that connecting to
the server is different from sending an email. The Login
Name/Password authentication values are not used to test the connection.
With the test, you will receive either "Connection Established" or
"Connection Failed" as return messages. If the connection is
established, you will receive a message from the SMTP server in the
"Response from SMTP Server" panel. If the connection fails, you will
need to correct the host and/or port values.
The following will assist in correcting the test:
. Verify the host and port from your Internet service provider. You
may ping your Host name at a command prompt to ensure you can reach the Host.
. To test connectivity out, perform a test using another Host name
and Port, for example "smtp.gmail.com" for the host, and "25" for the
port number.
. Ensure that your firewall is configured to allow RMailXSetup.exe
full in/out access.
. Use Telnet to test the SMTP server connectivity.
If the SMTP mail server that you are using requires authentication,
you must enable the "Server Requires Authentication" check box and
enter the Login Name and Password for the SMTP account. You must
verify the TLS and SSL settings from your Internet service provider.
Use TLS (Transport Layer Security)
----------------------------------
. No TLS Support - specifies data will be transmitted without encryption.
. Use Implicit TLS - specifies if server doesn't support SSL/TLS
then the connection is aborted. R:Mail connects to the server and
TLS/SSL encryption is switched on implicitly as soon as the channel
is established. R:Mail talks to the server using an encrypted
channel. The login name and password is sent as encrypted.
. Use Require TLS - R:Mail connects to the server which requires
the use of explicit TLS/SSL. R:Mail talks to the server using an
encrypted channel. The login name and password is sent as encrypted.
Some servers make sure that certain commands can only be executed by
clients over an already-secure SSL/TLS connection. If the connection
is not secure, those commands fail.
. Use Explicit TLS - specifies SSL/TLS is activated dynamically
only when the server supports it. R:Mail connects to the server and
explicitly requests TLS/SSL encryption to be switched on. R:Mail
talks to the server using an encrypted channel. The login name and
password is sent as encrypted.
SSL Version (Secure Sockets Layer)
-----------------------------------
The setting specifies the SSL version to use for the SMTP server. The
hosting provider will supply the correct values to use. With SSL Ver
2 or SSL Ver 3, you are explicitly telling R:Mail to use that
version. With SSL Ver 2.3, you are telling R:Mail to use whatever is
the highest version supported by the SSL library. In the image below
an example is displayed using the TLS and SSL settings.
. SSLV2
. SSLV23
. SSLV3
. TLSV1
. TLSV11
. TLSV12
If there is still an issue with sending email, within the R:Mail
setup configuration utility, enable logging and specify a folder
path. After sending a test R:Mail message, reference the log file
where file you may see a response from the hosting provider and URL
containing instructions to enable custom apps access to your account.
Follow the instructions in the web pages to enable the account access.
When using the configuration file method for storing SMTP
credentials, remember that the new configuration file must be
copied/moved again into the folder location where the R:Mail Plugin
resides, if any changes are made to your R:Mail SMTP server
credentials. Otherwise, R:Mail will not recognize the changes. It may
be ideal to copy the RMailXSetup.exe file into the R:BASE program
directory during testing. Important: After configuration file changes
are made, the R:BASE session must be restarted.
Very Best R:egards,
Razzak
At 08:04 PM 7/27/2021, [email protected] wrote:
We've been using R:Mail with R:Base X for 3 years or so. Same email
provider (comcast) and code for sending email without issues all
this time. Today our emails quit sending. A look at the R:Mail log
shows that the email provider says that authentication and TLS are
now required. We have always had authentication enabled along with
SSL. I see different options for TLS in the R:Mail configuration
app, but I don't really know what any of the options mean. I made
several changes to those check boxes and tried many different
combinations. I also changed the port to the one now listed as the
correct port to use with the provider. No matter what I tried, I
end up with a failure notice. Looking at the log again with
different TLS settings returns no error, but there is also no log of
communication with the smtp server. I also tried using a gmail smtp
that we had set up previously as a backup in case of issues with the
comcast server. Those attempts gave the same issues and failure to
send. Even tried with a Yahoo account with the same results. I
would appreciate any help or advice anyone may have that could get
me headed in the right direction for a solution. Thanks, David
Fowler Sent from my android device.
--
For group guidelines, visit
http://www.rbase.com/support/usersgroup_guidelines.php
---
You received this message because you are subscribed to the Google Groups "RBASE-L" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/rbase-l/0MAxJS-1mIfPZ0OeK-00A11I%40mrelay.perfora.net.
