Sendblaster Login

[Thomasina Norse]

SendBlasteris an email software that provides bulk email solutions to manage mailing lists and set up email marketing campaigns. It provides templates for writing emails and newsletters as well as analytics for you to track your email campaigns.

Today, most email marketing software is hosted in the cloud. In fact, at SocketLabs we even built our our own email marketing tools, which are a great sendblaster alternative. Unlike most cloud-based email platforms like SocketLabs, Sendblaster is downloaded right to your computer.

Your money is worth the investment for a cloud-based server. Using a open source SMTP server is more time consuming as you have to build and maintain your email infrastructure. This may also be more costly.

Microsoft recently announced that it may begin to delete accounts under its branded services division if those accounts have seen no login activity for 270 consecutive days. This change affects Hotmail accounts, as well as Windows Live and Outlook.

Microsoft has put its current users on notice, notifying them of the new policy on its website. The notice states:

While this is similar to the earlier move by Yahoo!, there is an important difference. Unlike Yahoo!, Microsoft has not yet announced that it will recycle those old addresses and make them available to new users. But even though there has been no formal announcement, a Microsoft spokesperson told PC World that the company does eventually plan to make those old addresses available.

This new move by Microsoft should also spur email marketers to do some spring cleaning of their own. Now is the perfect time to sort through your lists and remove those old inactive addresses. This simple move can reduce bounce rates, increase open rates and boost sales.

As always, email marketers need to stay on top of changes by the major players in the free email arena. Any moves by Yahoo!, Microsoft and Google can have a profound impact on marketers, and those marketers need to understand what is happening, why it is happening and how they can best react. Even so, this latest move by tech giant Microsoft should actually be good news for the email marketing community. No one wants a mailing list filled with dead and inactive addresses.

The cleanup Microsoft is planning should make building good lists that much easier.

To change your outgoing SMTP server settings away from outMail simply follow the setup guide above and where asked to enter the outgoing SMTP mail server address and login credentials please use those provided to you for the service provider you are moving to.

The Origin of this information may be internal or external to Prolateral Consulting Ltd. Prolateral makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Prolateral makes no explicit or implied claims to the validity of this information. Any trademarks referenced in this document are the property of their respective owners.

SMTP setting is as follow:smtp.office365.comport 587STARTTLSOAuth (this is correct setting, all others shows errors, including outlook.partner.cn & smtp.office365.cn, which is completely normal since I'm not in China).

The first thing that jump out is that my password is not OK, which is not correct. Password is OK. Click on "Retry" or "Enter new password" do nothing, just return the same pop up. If "Cancel", then receiving message with "unknown error 80004005" and all other blablabla about unknown reasons, with instruction to check my SMTP settings.

I've tried all variations available, but nothing works. Sometimes, at some moment after click on Cancel, it said "Message sent" and I can see it in my Sent Items folder, but it's fake because I never receive that test message to my personal Gmail address.

I have already tried all suggestions I could find (deleting passwords, resetting all, restarting, deleting and adding account again, changes in Config editor related to security.tls), but nothing worked for me.

2. Download the second Configuration (The Exchange Online PowerShell Module supports multi-factor authentication. Download the module to manage Exchange Online more securely.), then Install this module on affected computer (module's name: Microsoft.Online.CSE.PSModule.Client.application)

3. Run installed module as administrator from Desktop (if wont start, go to Start, in the search field type Exchange, than choose Microsoft Exchange Online PowerShell Module and Run as administrator).

4. Once the PowerShell panel is opened enter the following command (for your...@your.domain enter affected e-mail address): Set-CASMailbox -Identity your...@your.domain -SmtpClientAuthenticationDisabled $false

So, the main problem is related to O365 Basic security. This must be disabled in O365 Admin center and Advanced Security must be activated for all users. This is for those who use MFA and OAuth2. My Windows version: 10 Pro x64, build 2004TB version: 78.4

Steps to solve this:1. Activate Advanced Security and by that automatically disable Basic Security in O365 Admin center2. Sign-out affected user from all devices via Admin center3. Disable MFA for affected user (if enabled or enforced), then just Enable it back (nothing else) 4. Upgrade TB to the latest version 78.4.05. Remove previously added O365 email account from TB6. Delete Saved passwords for that account and close TB7. Go to Windows firewall and add TB as allowed into Inbound and Outbound rules8. Open PowerShell as admin and force TLS 1.1 and TLS 1.2 by these syntax: 8.1. [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls11 (enter to execute)8.2. [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 (enter to execute)9. Open Command prompt and test ping for smtp.office365.com (if get replies, it's OK)10. Open TB and set new email account with following (enter all requested data, including to check "Remember password"), then click Continue. If account was found, click on Manual settings and there check/set as follows:IMAP data: outlook.office365.com; SSL/TLS; Port 993; OAuth2; full email address as usernameSMTP data: smtp.office365.com; STARTTLS; Port 587; OAuth2; full email address as username Click on "Re-test". If no errors, click "Done". Restart TB.

11. Open TB again and login using Authentication.12. Try to send email. If work (for me this procedure worked for 10 computers) - great! If not - firstly wait a little bit because re=setting in Admin panel need some time to become active again, sometimes more then 30 min.

12. If not work even after 30 min., try with previously mentioned Hybrid module where will enter following syntax: Connect-EXOPSSession -UserPrincipalName yo...@email.com (yo...@email.com replace with affected email address).Restart computer and try to send email again.

You must be an Office 365 admin. Open the Microsoft 365 Admin Center (web page) and go to Users > Active users. Select the user, in the properties of the user panel click Mail. In the Email apps section, click Manage email apps.

FYI: For me enabling the SMTP-authentification by setting option -SmtpClientAuthenticationDisabled to false wasn't enough. It seems I also had to change weak initial-password for exchange-mailbox to a new strong password (imap access was not affected by this problem).

I can't say for sure, but it's possible that accounts with initial-passwords or weak passwords are excluded from using smtp-auth (at least in some exchange-server configurations). Maybe you should take it into consideration when you're facing this issue.

FWIW, here is what I have found. I went into the docker image and started monkeying around with the lib/tasks/emails.rake script and the config/discourse.conf file. Several hours later, after trying every possible combination of smtp.office365.com and .mail.protection.outlook.com AUTH login and AUTH plain I uncommented the block above the STMP start.

I use socketlabs.com as my email delivery service, and had a similar issue. In my case the solution was to edit lib/tasks/emails.rake as follows:

Change the line:

Net::SMTP.start(smtp[:address], smtp[:port], 'localhost', smtp[:user_name], smtp[:password])

to

Net::SMTP.start(smtp[:address], smtp[:port], 'localhost', smtp[:user_name], smtp[:password], smtp[:authentication])

Brother says:

Testergebnis der E-Mail-Konfiguration

Konfiguration des E-Mail-Versands

Die Test-E-Mail ist fehlgeschlagen. Der E-Mail-Server hat wie folgt geantwortet:

504 5.7.4 Unrecognized authentication type [xxxxxxxx0.eop-deu01.prod.protection.outlook.com]

Prfen Sie Ihre Einstellungen und versuchen Sie es erneut.

discovered on:

-everything-using-office-365-smtp-authentication-is-broken-wont-authenticate

After some digging around I found that I could go in to the Azure side of our tenant > azure ad > sign ins, add a column for client app and under legacy auth options for that filter choose SMTP. This displays all the failed SMTP login attempts on our backup@ mailbox that we use for our in-house backup solution to send backup reports.

That's cool, glad to know that your issue is resolved and thanks so much for providing your solution here! Since our forum has the policy that The question author cannot accept their own answer. They can only accept answers by others, and according to the scenario introduced here: Answering your own questions on Microsoft Q&A

You could "Accept Answer" for this summary to close this thread, and your action would be helpful to other users who encounter the same issue and read this thread. Thanks for your understanding!

To send email out, first you must have an email account to send email. Account to send email may be any email that you have, Ex : Yahoo Mail, Gmail, Hotmail, or your outgoing email server (SMTP) and other SMTP provider like SMTP.com, SendGrid.com, Amazonaws... If you're using free email service such as Gmail and Yahoo, you could only allowed to send about 500 emails out per day dependent on their term of service. To be free with your sending volume, you need to buy a SMTP Server. It's great with Amazon SES SMTP because it's take only 0,1$/1000 emails and pay only for what you use.

3a8082e126