| T O P I C R E V I E W |
| irpworks |
Posted - Sep 23 2009 : 19:37:16
MLK Business Edition v7.30R
Windows XP Pro, Service Pack 3
Contention: Sometime last week, around 18 Sept., AT&T possibly made a change which keeps MKL from being able to login with SSL. MLK can no longer login to the AT&T mail server while Outlook has no problem with identical settings.
All was working earlier in the week. Then, all emails sending through the ISP began failing: automated emails, acknowledgment emails, and sending to groups.
This condition has been verified by hours of testing. I've eliminated the possibility of any corruption of the MLK program on my computer by both installing the latest version again and, duplicated the same failure on a backup machine that is rarely used for MLK but was working with the same MLK version a month ago.
Using other non-AT&T email accounts work fine though none I use require SSL so I'm not able to determine if a problem is with MLK's SSL coding or is unique to AT&T.
AT&T will not confirm any changes. All settings are still the same according to AT&T support and their website: smtp.att.yahoo.com; outgoing port 465 with SSL checked, and; SMTP requires authentication.
Any test email with MLK fails immediately with a pop-up error indicating an SSL failure. This is the text in each log entry after each address attempted:
Commencing Send (4)
MailAgent: MailList King 7.3.0.724
Enabling SSL
Connecting to SMTP Server: smtp.att.yahoo.com
SMTP Connection Error: Error connecting with SSL.
SMTP Connection Error: Error connecting with SSL.
Disconnecting from SMTP Server
Obviously, I need this to work with AT&T as it is my primary high-speed ISP and is the only account without sending limits.
Again, sending to one or multiple addresses through the same account with Outlook works fine. Nothing changed from the time the MLK worked and stopped working that I'm aware of. No MLK upgrades or Outlook upgrades. XP Service Pack 3 was installed on the 10th and a completed email broadcast went out on 9/16 without error.
I've waited several days to ensure that this was not a temporary mail server problem. The problem has persisted with no change of symptoms.
Please advise.
|
| 20 L A T E S T R E P L I E S (Newest First) |
| xequte |
Posted - Sep 07 2018 : 16:38:42
Hi
V13 is now five years old and does not support the latest SSL standards.
Check whether your ISP supports a non-SSL sending method, or upgrade to the latest version at:
http://www.xequte.com/maillistking/upgrade.html
Nigel
Xequte Software
www.xequte.com
nigel@xequte.com
|
| adamd2 |
Posted - Sep 07 2018 : 16:05:50
I've switched providers are now I get:
Unable to connect to your SMTP Server: Error connecting to SSL(0).
I'm using v13. |
| xequte |
Posted - Oct 22 2009 : 12:21:59
Hi Elaine and Robert
Thanks for your reports. We've been testing SSL against our test accounts and will be changing the default option to SSL v3 for the next release.
Robert, I'll check the code regarding the toolbar issue and will email you if I cannot find a cause.
Nigel
Xequte Software
www.xequte.com
nigel@xequte.com
|
| emtenzer |
Posted - Oct 21 2009 : 11:22:32
Robert-
Thanks. I, too have swbell. I used to find that it stopped after 25 and then I would have to resend to the rest. I'm glad this works and I'm grateful (selfishly) that you had an issue so I didn't think I was doing something wrong. I found that especially with AOL customers the e-mails weren't ending up in spam folders if I used the swbell servers instead of the mail king servers.
Good luck to you.
Elaine
Elaine Tenzer |
| irpworks |
Posted - Oct 21 2009 : 11:01:21
Elaine,
Yes, the test is with the new version of MLK that Nigel provided - otherwise you'd have no way to set the SSL version which is the root of the problem. AT&T must have changed their SSL version when they upgraded.
The problem had nothing to do with the number of emails you could send - you were not able to send even one email through MLK with the SSL engaged. And if you want to send more than 25 at a time with AT&T, you must be using the SSL.
I only sent in batches of 100 but the SSL rejection problem is gone. I did not bother sending more at one time for other reasons (most of my subscribers are local and thus too many emails hitting mail servers at one time triggers ISP spam blockers and reduces delivery rates.)
The fix lets you send via AT&T (my account is old enough that it is an SWBell account) with SSL. According to the somewhat unhelpful AT&T support people, and past experience, there is no sending limit. I believe that to be correct. |
| emtenzer |
Posted - Oct 21 2009 : 10:44:08
Robert-
Thanks for doing the testing. Two questions: was the "test" exe (the download Nigel send)that you ran a new version of Mail King? and when you use the ATT/SBCglobal servers now are you limited on how many you can send?
Elaine
Elaine Tenzer |
| irpworks |
Posted - Oct 21 2009 : 10:21:59
Nigel, the test version works great for sending with AT&T as the ISP with SSL version 3.
One thing that did change after the update is that Outlook no longer keeps my MLK toolbar. I have to turn it on each time I load Outlook. I'm not sure what could have caused this but it is a behavior change you may need to know about.
Robert |
| irpworks |
Posted - Oct 21 2009 : 10:05:46
Elaine,
I've installed the new test version of MLK and it all works as Nigel advised. In my settings file, after installing the test version, the item is listed as SSLMethod=3. Search for SSLMethod and you'll find it.
The SSL version 3 setting is what worked after testing. I'm back up to full, regular sending use through AT&T with setting 3.
Note, be sure you close MLK before you change the SSLMethod=0 to SSLMethod=3 and save.
Robert |
| emtenzer |
Posted - Oct 21 2009 : 05:31:37
You suggested changing the SSLMethod in your email. In my settings.ini file I have "SendMethod=5". Is this the setting to change? I could not find a line with "SSLMethod".
Elaine Tenzer |
| xequte |
Posted - Oct 21 2009 : 01:00:35
Hi Robert and Elaine,
I've sent you a test version. Has that resolved the issue?
Nigel
Xequte Software
www.xequte.com
nigel@xequte.com
|
| emtenzer |
Posted - Oct 10 2009 : 16:08:15
I waited a half hour to chat with AT&T support and they finally came back and said that they didn't have a version of SSL.
Elaine Tenzer |
| xequte |
Posted - Oct 08 2009 : 14:42:43
Hi Robert and Elaine,
Can you confirm what type/version of SSL connection AT&T are expecting? Currently MLK defaults to SSL v2, but other options are available.
Nigel
Xequte Software
www.xequte.com
nigel@xequte.com
|
| irpworks |
Posted - Oct 05 2009 : 15:45:09
AT&T says there is no sending limit and that has been the case. They still claim no sending limit.
Because of other regular everyday problems with their SSL service, sometimes requiring Outlook to be closed and restarted to send regular email, I believe it is all rooted in their SSL service. But certainly they pretend ignorance on having any problems. |
| xequte |
Posted - Oct 05 2009 : 15:18:14
Hi
If it is due to a new sending limit regime by AT&T then your only resolution is to configure the ISP Limited sending in MLK (View > Options, Sending, Other Sending Settings) or sign up with an SMTP service such as AuthSMTP or TZO.
Nigel
Xequte Software
www.xequte.com
nigel@xequte.com
|
| irpworks |
Posted - Oct 05 2009 : 14:40:53
Update on sending. Testing with send-through-Outlook works fine with small test batches. But, when I did attempt a large send with 50 piece batches a few minutes apart, the SSL errors began showing up in Outlook.
The work around, to get the emails sent which were already dumped to Outlook from MLK, was to close the program (Outlook) at each error stop, then restart. It would then send another 25 to 50 emails.
It appears that they've put some sending limit in through the SSL. I changed the sending for the balance to send the the ISP (AT&T) without the SSL and through port 25. This works if the batches are at 25 emails and spaced out a few minutes apart.
I will provide you with other data requested in the separate email. |
| xequte |
Posted - Oct 05 2009 : 00:10:43
Hi Robert
Nothing has changed on our end with respect to SSL. AT&T appear to have made changes that are causing issues for Outlook users too:
http://groups.google.com/group/microsoft.public.outlook/browse_thread/thread/45882fa0e4cd3c00/05ae93ab4fa7458c?hl=en&lnk=st&q=#05ae93ab4fa7458c
http://groups.google.com/group/microsoft.public.outlook/browse_thread/thread/c5faad3138e4a4dd/9a7013577bf2109a?hl=en&lnk=st&q=#9a7013577bf2109a
It's possible that their changes require us to make modifications in our software to support it, but because they have not released any information (that i know of) about the changes, we are in the dark.
We don't have any AT&T accounts (it is not even in NZ), but SSL sending via GMail still works fine.
I'll send you some information to enable debug logging and possibly that will give some guidance.
Nigel
Xequte Software
www.xequte.com
nigel@xequte.com
|
| irpworks |
Posted - Oct 04 2009 : 17:28:52
I have again attempted, today, to send through the AT&T server with SSL and it still fails as before.
I have also tried the send-through-Outlook feature (using the exact same AT&T account and SSL settings in Outlook as they are set in MLK) and it appears to work with my test list.
Something appears to need updating or patching in MLK to now send through AT&T directly.
Please advise on any changes or updates.
Robert |
| xequte |
Posted - Sep 25 2009 : 20:15:56
Hi Elaine
When sending via MLK's servers did it report success or not. I expect if you look at the log you will find that MLK's server was blocked because of your firewall or ISP blocking port 25.
For more detail please email me the log file for the sending task:
1. Run MLK and click Ctrl+Shift+I.
2. Check the box to display your database folder and click "OK"
3. Browse to the subfolder named "SendLogs"
4. In that folder your log files are named "mail_sent_*.txt" with the date of the delivery included in the name. Find the files of the relevant date and send them to me
Nigel
Xequte Software
www.xequte.com
nigel@xequte.com
|
| irpworks |
Posted - Sep 25 2009 : 14:02:21
Outlook has no problem sending self-generated emails. But, I've not tried the send with Outlook feature. I can possible do so tonight in a test if that will help.
Robert
|
| emtenzer |
Posted - Sep 25 2009 : 13:32:10
Thanks, Nigel for looking into this. I also saw a few comments online about Thunderbird. I am using Outlook for the reply emails, but not for blasts. However I am using my client's web host servers and that didn't work yesterday, either. Also interesting was that I have used the MLK servers in the past quite often and yesterday used them for my "test" e-mails and I never received them. Until I saw Robert's post I thought it was my computer having issues.
Elaine Tenzer |
Search
