I have changed my email address and now when I try to email invoices I get the following message:
"The email service you selected to use currently cannot be reached. Please ensure you are connected to the Internet before trying again. If the problem persists contact your email provider for help."
Any suggestions?
Thanks
Shane
If you go to the invoice is there a box down the bottom that says ‘to be emailed’?
Hello, thanks for responding to my original report and apologies that I overlooked it for so long! :-)
I can confirm that there is NOTHING that I can do to make the invoice send work as expected. No changes, or small adjustments will fix that problem.
Only remove and then re-create will allow me to send them again.
I have however discovered a way to find out whether an invoice is affected - that is to:
would be nice if t were fixed one day.
Mike.
Hi Mike,
Depending on how many emails are still currently in your 'to be emailed' list, remove those that you have identified to be an issue.
Then consider:
0) Make a backup of your data file
1) Export the Customer List as an IIF (tab-delimited text file)
2) Open that file in Excel as a TEXT file.
3) Add an email address (even your own or a dummy placeholder) for each one that does not have a valid email address set (example: "placeholderonly@notarealemailaddress.com")
4) Save the resulting Customer IIF file
5) Import the IIF file back to your data file
Hi,
I have had the same problem with Premier 2017. After much research, the problem appears to be that most email servers are upgrading security to include TLS1.2. Reckon has no plan to upgrade its email to this standard. I work around the problem by printing report to PDF then attaching thru my normal email program. This may now be academic as Reckon will now not reactivate and "read only" my software without annual subscription.
This is a known issue with some isps. You can use the webmail option in the recent versions.
It's only a matter of time before all isp's adopt TLS 1.2. They give the same "compliance" reason that Reckon give for non-reactivation. Email has been a persistent issue with Quickbooks / Reckon in the more than 20 years I have used the product. I am probably forced, reluctantly, to sign up to subscription with no confidence this issue will ever be resolved.
John that is very depressing.
That is nothing more than a dodgy work-around and does nothing to fix the actual problem - which is clearly a bug with reckon accounting.
Thanks for the suggestion though - at least you tried :-}
(and i think that process WILL avoid the problem recurring, but since it only happens when a NEW customer is entered, then that process will not prevent the same problem again if/when a new customer is added with the same flaw)
Regards, Mike.
don't know if you are replying to the original post to or someones later irrelevant reply, but the issue I am reporting is definitely not (100% certain) anything to do with any mail server. 🙄
I have been having this same issue for over 12 months.
I have issues sending remittances, payslips and invoices. It can take up to 10 attempts just to send a payslip. When you are charging customers by the hour it is wrong. You should not have to be saving a PDF when there is an option to email directly. So disappointing that this remains an ongoing issue.
I think it maybe time for a change.
You dont need to. I can fix this. Call me
0407744914
Thank you Zappy for your assistance.
It appears the problem has been solved, I should know for sure in the coming hours, looks the the issue lies with office 365 and not Reckon.☺️
Ros good evening. Thanks for the opportunity to help. You taught me something. I suspect this is what is happening with Optusnet as well. I'm delighted we were able to get this far. I complain about thesr email errors - a lot. Its great when we can find a solution. Let me know if you need anything else. And have a great weekend.
Hi. Could you please share details of your solution, as I have exactly the same issue with Reckon using Office365 to support the email processes. Cheers.
Mrossnay call me 0407744914
Thanks for your help Zappy.
For the interest of all who have this problem, if you are using Office365 Outlook, Reckon appears to have some incompatibilities, specifically regarding email security settings. Initially, check your Send Forms preferences, and ensure you are using an email provider of Outlook. Currently, you'll see that anytime an email send is attempted, you get a program busy dialog, asking you to either "Switch To..." or "Retry". What you should also note, is that a minimized Outlook warning dialog will also have appeared. Select it, and you'll see that Outlook is complaining about Reckon not having permission to send emails. You have an opportunity to "Allow" or "Deny" access. Currently if you choose "Allow", you must return to the Reckon dialog, and choose "Retry". At this point, the email should send correctly.
To get around the need to give permission for every Reckon sourced email you want to send, there is a Microsoft KB that details a solution where you add a DWORD regedit entry in location HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\16.0\Outlook\Security called ObjectModelGuard with a value of 2. You can check this has worked by looking in Outlook File - Options - Trust Center - Trust Center Settings - Programmatic Access and ensure that the "Never warn" option is selected.
At this point, you should be able to send emails from Reckon without a security prompt. Hope this helps...
the original bug report has been TOTALLY hijacked by latter entirely unrelated local system problems 🤦♂️
the original reported BUG still remains - still not addressed.
Mark good afternoon. Thanks for the kind words. This is what I do. Dux Tel or does it? Did you call me?
Dux thats not accurate. Do you have the answer? Have you looked at the help files?
if you bother to actually read the original post, you'll see that it is nothing like what has been claimed by others as "this happens to me too" - it's like you guys read the post subject and then jump on the 'me too' bandwagon :-D
a shame that a worked bug report, including repro steps, goes completely ignored by technical team....
<shrug>