How to test RingCentral Fax API without sending to real fax machine? - fax

Is it possible to test sending a fax with the RingCentral Fax API without sending a fax to a real fax machine?

The RingCentral sandbox account let's you set up multiple phone numbers and users, like a production account. If you want to test sending a fax in the sandbox without sending to a real fax number, you can simply create two sandbox fax numbers and send from one number to the other.
A user can have multiple numbers but, for testing purposes, I like to use different users so it better simulates sending from one user to another.
Creating a User and Phone Number
You can create a user in RingCentral by following the instructions here for the Sandbox Online Account Portal (https://service.devtest.ringcentral.com). You will also be prompted to select a phone number for this user. For a phone, selecting the free soft phone is useful for testing purposes.
https://success.ringcentral.com/articles/RC_Knowledge_Article/5-10-Adding-Extensions-via-Web
Verifying the User and Phone Number
After this, you will see this user and phone number in the Online Account Portal. You can also verify numbers via the API. When you call the account extension endpoint, you should see at least 2 extensions (the original one and your new one).
GET https://platform.devtest.ringcentral.com/restapi/v1.0/account/~/extension
You can then login as the new user and verify the fax numbers by calling the endpoint below:
GET https://platform.devtest.ringcentral.com/restapi/v1.0/account/~/extension/~/phone-number
The phone number array will include a list of numbers with the following JSON property:
"type": "VoiceFax",
Sending the Fax
When you have two extensions, one of which can be your super user extension, you can send from one number to the other. Simply login as one user and send to the the VoiceFax number of the other user:
POST /restapi/v1.0/account/~/extension/~/fax HTTP/1.1
Content-Type: multipart/mixed; boundary=Boundary_1_14413901_1361871080888
--Boundary_1_14413901_1361871080888
Content-Type: application/json
{"to":[{"phoneNumber":"+16505550100"}],
"faxResolution":"High",
"country" : {
"isoCode" : "IE"
},
"sendTime":"2013-02-26T09:31:20.882Z"}
--Boundary_1_14413901_1361871080888
Content-Disposition: attachment; filename="fax.txt"
Hello, World!
--Boundary_1_14413901_1361871080888--
Verifying the Fax
You can verify receipt of the fax via the API, Online Account Portal or Softphone application.

Related

Firebase reset password not sending link to email in Firebase Console [duplicate]

I am new to firebase and I am trying to handle firebase user authentication in React.js. I did manage to create users with email and passwords. But, now I would like to send the user an Email link to reset their password.
My code currently look like this.
// This line of code belongs to the top
import { auth } from '../firebaseConfig'
//This part goes under the React component
<p onClick={async () => {
try{
await sendPasswordResetEmail(auth, // My Email Id)
alert('Password reset link has been sent to your email')
}
catch(err){
alert(err)
}
}}
>Forgot your Password ?</p>
However, I do not get any error messages and I do get the alert message that says "Password reset link has been sent to your email." Unfortunately, I didn't receive any email. Note that I have given my own email id as the parameter for testing purposes.
firebaser here
Did you check your spam folder? We recently see a lot of the emails from Firebase Authentication ending up in the user's spam folder or being marked as spam in a system along the way. This is being tracked in this status message on the Firebase dashboard and in public issue #253291461.
To reduce the chances of the messages getting marked as spam, consider taking more control of the email delivery yourself.
As a first step, consider using a custom domain with your project. Email that comes from a custom domain has less chance of being marked as span.
As a second step, consider setting up your own SMTP server.) for delivering the email, so that the emails are not being delivered from Firebase's shared infrastructure anymore.
While these steps are more involved, they typically will drastically reduce the cases where the messages from Firebase Authentication are marked as spam.
Full Guide Based on Frank's Answer
Firstly create a new email account you can use to relay the Firebase emails through the SMTP server with. I personally chose Gmail, but I tested with Outlook and it also works.
You can now find an SMTP server host that will work for your scenario. If you're sending less than 1000 emails per month you can find free and reliable hosts. I chose SMTP2GO's free option.
Now you've found the SMTP host, add the email address you've chosen as a single sender email (note that if you do own a domain, you can alternatively use that to send emails).
Note that you will have to verify the email, usually by your host sending a link to the email's inbox. Make sure to check spam.
Once verified, navigate to where you host allows you to add SMTP Users and add a new user. This will allocate an SMTP username and password.
Navigate to the Firebase console, and choose the Authentication option from the sidebar (within the Build product category).
Go to Templates → SMTP Settings and enter the details of your SMTP server. The username and password fields are to be filled with the SMTP user login you created in the step above.
It is better to use TLS, but I believe SSL should work too but it is untested.
Click save, and you're all set up - but there may still be steps to perform depending on your email provider.
Provider Specific Steps
If the emails are being sent to an account managed by Google you will have no issues with your emails being quarantined by anti-spam policies and it will work immediately.
If you are using Outlook, you will have a different problem on your hands. Outlook's built in defender will most likely have auto-quarantined your email under multiple policies - that bit is important.
These policies are likely to be both spam and phish policies. If you unblock one of them, the other will catch it and re-quarantine.
Unblock both policies for the email address, and test. You can see the status of quarantined messages in Microsoft 365 Defender app under Review → Quarantine. Please note that you will need to be an administrator to add global allow policies to your email accounts.
If this still doesn't work it is likely that your company has an additional external filter (as mine did), and you will have to add the IP's manually to the Tenant Allow/Block Lists spoofed senders tab.

Auth Email limits password reset in Firebase Free account

I'm setting up a new application using Angular with Firebase. I'm using only Auth system. But like said in the Firebase docs, only 150 emails/day can be sent for Password reset.
https://firebase.google.com/docs/auth/limits#email_limits
I have two questions:
1) If a user spam the recover password button (that use the function sendPasswordResetEmail() ) does it consume this email limit ? If yes how to prevent that ?
(Doc: https://firebase.google.com/docs/reference/js/firebase.auth.Auth.html#sendpasswordresetemail )
2) Does the SMTP parameters (own server or other mail service) from Firebase project settings use the email limits ?
The 150 emails per day for passwords resets limit applies to emails sent through Google's mail servers. If requests are identified as spam, and email doesn't get sent, they don't count. If spam requests are not identified and email is sent, it does get counted. If you're running into spam problems and hit this (or other limits) because of that, reach out to Firebase support for personalized help in troubleshooting
The limit is on emails sent through Google's mail servers, if you use your own mail server, the limit doesn't apply.

Email Goes to junk in Hotmail

Email is sent using Amazon simple Email service form my website. When an email is sent to any Yahoo or Gmail address, it is delivered to Inbox; but when it is sent to Hotmail,it is delivered to Junk.
Why only Hotmail Treats my email as junk?
When an external user sends email messages to an Outlook.com account,
SmartScreen® filter technology evaluates the content of the messages
and assigns each message a rating based on the probability that it is
a junk email. This rating is stored as a message property called a
spam confidence level (SCL) within the message itself. The SCL rating
stays with the message as it is sent to other anti-spam protection
layers within Outlook.com. Rules inside Outlook.com are set to handle
email messages with various SCL ratings. If a message has an SCL
rating lower than a certain threshold, it is considered to be spam,
and a rule then deletes the message rather than sending it to the
user's junk email folder. If the message has a higher SCL rating than
the threshold, the email is delivered to the user's junk email folder
rather than to the inbox.
https://mail.live.com/mail/junkemail.aspx
Not all the Anti-Spam system depends only on 3rd party blacklists. Major email service providers builds their own reputation table in addition with the use of major 3rd party blacklists like spamhaus, barracuda etc. In your case, you are using Amazon SES to send mails.
I, myself found enormous marketing mails coming from Amazon SES. If the reputation of your email service provider is bad in hotmail then it may trigger the suspicious level of your mail regardless of your email service provider reputation at other blacklist providers. In addition to this, if your subject, body content contains some suspicious words then your mail will end up in junk folder.
Most emails sent from third party applications such as Wordpress, Joomla, or Amazon get diverted to junk and sometimes they fail and get stuck behind a security layer. I know for a fact with Wordpress Contact Form 7, this is the case many times.
After so many years and finally attending a seminar for this particular issue, I finally was able to solve this problem specifically for Hotmail (Outlook.com).
Before you do anything ensure your SMTP settings in your web config file (ASP.NET) are written correctly or in case of plugins (Wordpress) make sure the fields are filled correctly. This means ensuring these are the settings you are using for Outlook:
From: your email ("asdf#outlook.com")
From Name: "Your name or company name"
Host: smtp.live.com
Type of Encryption: TLS
SMTP Port: 587
SMTP Authentication: Yes
Username: Same you use to login (usually the complete email address)
Password: Enough said there
IMPORTANT - Send a test email even if it fails. The point is to trigger an activity in Outlook and have them flag it as an
unauthorized connection
Now, to the fix:
Go to Outlook.com
Login
go to Account Settings
Choose Security & Privacy
Click on "See my recent activity"
The most recent activity should be the fail attempt. Authorize it as a trusted connection.
Done!
Re-test and you shall see your emails showing in the inbox as an authorized connection. Doing these steps let Outlook know that your emails from Amazon are legitimate connections and not Amazon trying to spam your account with solicitations etc.
Mostly it is a email service provider specific thing but you can do below checks
Ensure valid sender email address
Try not to use keywords like gift, prize etc. which are preferably spam activities
Try using https://litmus.com which may help on this/ rendering email in different email clients

QR-encode email with recipient, subject and body?

I need to QR-encode an e-mail message with custom recipient, subject and body, so most mobile QR-Code scanner apps will automatically create an e-mail with the encoded recipient, subject and body. Of course this will depend from the features of the mobile QR-Scan app. But isn't there an international standard for such a purpose?
A Qr-code can contain many different types of information:
Contact information
Calendar event
E-mail address
Phone number
Geo location.
SMS
Text
Wifi network
URL
(from here)
The E-mail adress does'nt allow us to store body message.
The only information that could work is the URL, using the mailto scheme: http://en.wikipedia.org/wiki/Mailto
For example, encode mailto:someone#example.com?cc=someone_else#example.com&subject=This%20is%20the%20subject&body=This%20is%20the%20body
This generates the following QR-Code.
It doesn't open the mail app on my phone (Samsung Galaxy S2), but asks to add the email Adress to your contacts.
What you could probably do is to direct to one of your server, that will then redirect to the mailto URI. (I'm not sure that you can redirect to mailto , cf Django: how to redirect to mailto), howewer, you could create a big link on the page that mails to your adress.
The mailto: scheme is a pretty good choice, since it lets you specify a subject and body:
https://www.rfc-editor.org/rfc/rfc2368
It's not guaranteed that the scanner, or e-mail client, supports or honors it of course.
See also the old DoCoMo MATMSG format. Barcode Scanner supports this on Android for example, and has space for an email body.
https://code.google.com/p/zxing/wiki/BarcodeContents
http://www.nttdocomo.co.jp/english/service/developer/make/content/barcode/function/application/mail/

Check if mail sent is in recipient's inbox/junk in asp.net using C# ?

I am developing a software but for that I want to know as if i send an email then how can i check the sent email is in recipient's inbox/ Junk.
I am using AsP.net and c# technology for this
Please reply
You can't detect what is done with the email once it is delivered to the users inbox other than requesting a delivery receipt and a read receipt but the user can opt out of these.
The best way to avoid being marked as spam is to use a trusted third party service such as Campaign Monitor or MailChimp.
Failing that you should make sure that your email has a proper from address set, that you have set up SPF records to allow the sending IP official permission to send email on behalf of the from domain, keep your html to content ratio reasonable and if possible use an email address that your customers have already received an email from before so that there is a higher chance that the address is already in a whitelist.
You really can't because there are many different email spam solutions out there and they don't send a status back saying whether they delivered the email to the recipient or not. What you can do is send an email with a tracker to see if the receiver opened it.
http://www.aspnetemail.com/samples/emailtracker/default.aspx

Resources