Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about programming within the scope defined in the help center.
Closed 9 years ago.
Improve this question
I'm getting following error message when I'm trying to add a new user to site and trying to send mails to him.
The Site is Intranet site as well exposed on internet via alternate URL mapping while adding users of local exchange group it does not give any errors but suppose that I add a user having gmail id expressed in his AD that throws following error:
The user or users have been added successfully, but there was an error in sending the e-mail message. The server may not be set up correctly to send e-mail. To verify that e-mail is configured correctly, contact your server administrator.
First verify that the user you just added has a valid email address in SharePoint - don't assume it was picked up correctly from A.D. (Site Setings > People and Groups)
Find out what you have set as the outgoing SMTP server (Central Administration > Operations > Outgoing Email Settings)
Install a tool like the SMTP Test tool on your server (or use Telnet to test manually) and use the same settings/email address. This will tell you if the problem is with SharePoint or your email infrastructure.
The problem was with the settings on the server our Infrastructure team resolved it
Related
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 1 year ago.
Improve this question
I'm developing an invoicing system using stripe.
I'm going to send invoice using stripe invoice API.
When I create an invoice, it is shown in stripe dashboard, but there is no email for the invoice. I used a function called 'sendInvoice'.
const stripe = require('stripe')('sk_test_4eC39HqLyjWDrjtT1zdp7dc');
const invoice = await stripe.invoices.sendInvoice(
'in_1J1Yqg2eZvKYlo..NtAx5Hl'
);
If I send manually in the dashboard, it works well.
Please help me, stripe experts.
enter image description here
enter image description here
No emails are automatically sent in test mode, this is expected. Using the Dashboard, you can manually send invoice/receipt emails to your own email address only. In live mode these would be sent automatically.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
I am trying to bind SSL certificate to my domain in Azure from the below blade:
When I do, it fails and I can see the following error message in my activity log:
"Failed to configure SSL Binding for www.testing.me with 'thumbprint' {'Code':'BadRequest','Message':'The name www.xn--testing-s4a6m.me is not valid.','Target':null,'Details':[{'Message':'The name www.xn--testing-s4a6m.me is not valid.'},{'Code':'BadRequest'},{'ErrorEntity':{'ExtendedCode':'01003','MessageTemplate':'The name {0} is not valid.','Parameters':['www.xn--testing-s4a6m.me'],'Code':'BadRequest','Message':'The name www.xn--testing-s4a6m.meis not valid.'}}],'Innererror':null}"
As per the error message, SSL binding for www.testing.me is failing, but the issue is related to the domain www.xn--testing-s4a6m.me. I have no idea why this other domain would throw the error when it is not the one to which I am trying to bind.
Based on the error message it appears like you have few invalid hostnames (www.xn--testing-s4a6m.me). As a first step please try and delete the invalid hostnames and retry the operation.
However, I have seen in the past that one of our customers had multiple invalid hostnames (Involved Puny Codes) in the Custom Domains page on portal, every time they tried deleting an invalid domain, the error message shows a different invalid domain, and it goes on a loop. Hence, our product team deleted the invalid domain names in the backend. Once they are deleted, the customer is unblocked, and he was able to secure his custom domains successfully. PFB example for better understanding:
Example: Two custom domains are added to Web App: xn--hello.com and xn--hello2.com. Both of these are invalid.
When trying to delete xn--hello.com, error message returns: "The name www.xn--hello2.com is not valid".
When trying to delete xn--hello2.com, error message returns: "The name www.xn--hello.com is not valid".
Hence, it gets stuck in a loop and neither can be deleted.
Note: Main root cause of the issue was that puny code (xn-) is not supported in Azure from 2015. It should have thrown an error when you tried to add the Puny code custom domain.
If this is the case with you, please raise a support request with in portal so our team can help unblock you.
References:
https://en.wikipedia.org/wiki/Punycode
Closed. This question needs details or clarity. It is not currently accepting answers.
Want to improve this question? Add details and clarify the problem by editing this post.
Closed 3 years ago.
Improve this question
As it my ordering app , orders should be sorted and sent to admin panel or just I shall be able to retrieve order from bots chat history . How to retrieve chat or an order list and Name ,address, etc from google dialogflow and send to admin panel or a database
I dont think it is possible to download the History, you can enable 'Log interactions to Google Cloud' in the Settings, then you can acces (also download) the events that occur during the conversation.
The best option is however to build a Webhook, so all user interactions are sent to your backend where you can store data into DB or apply some custom logic.
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
So i'm learning Swift and i'm trying to validate user inputs on IOS app for a class project but i'm not sure if i'm following the right steps. Can you give me some feedbacks ?
Here's how it goes:
User enters phone number, check if it's valid.
Send twilio code notification if user phone number doesn't exist in db to set phoneVerified = true
User proceed to next screen to enter email & password
then send link to set user.status = true
Datas are sent in JSON format to Couchbase via NodeJs route.
I'm not sure if datas should be validated on client-side or server-side or both. I've been told never trust user input but i was working on websites at the time. I'm really confused, Does it apply for phone apps also ?
I'll say you have two choices so far:
1 - create the random verification code (usually 6 digits) from the client (meaning the user's phone), then send it to your api along the user's phone number so that twillio can send the code within the twillio's message body.
2 - create the random verification code from your api and repeat the end steps of option 1
Client Side (let's use option 1, and think of the following as psuedo-code)
verify the input phone number, and if not valid, tell the user to do fix it.
create the random code and save it to UserDefault. (we save it because if something happen while your app is being used, of course you'll also add a logic for request another code)
create the request body dictionary that contains the code and phone number i.e [phone: 182822939, code: 83920]
using either URLSession or Alamofire you do a POST request to your nodejs api along the body that you've created from the previous step.
NodeJS API
here, you get the phone number from your request object like const phoneNumber = req.body.phonenumber, and the code like const code = req.body.code.
you create the twillio sending object using the phone, and you add the code within the message body and you send it.
if the message was successfully sent, return 200 Ok from the response, else you return the error with a 404 code
Client Side Again
As of now, the user gets the code, now with need to check if the input code and the code from UserDefault are identical. if valid you continue with your login process, otherwise you notify the user with an alert (so that's why is important to also add the request another code in case the user never receive the code.)
Voila, also this is not the only way to approach your problem.
Server side should always have the validation. You can't trust user input. Your phone app also will use some APIs to communicate with the server right? What if I don't use your app and just send request to those APIs?
Also, your design looks like it has some flaws.
What if a user verifies a phone but exits the app (user phone is verified in the database right?). But another user requests your API for email and password?
Do you have anything in place that, the person who verified the phone is registering with the email and password?
Please specify more details.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
How to find my limitations and methods to not get blacklisted, trash/spam moved for sending emails?
I have growing number of like 10000 e-mail adressess and e-mails that I have to send on daily basis regarding:
user registration
reminders
confirmations
news
I want to send mailing to my community but am afraid of beeing blacklisted. It happend few times when years back then was sending mailings from virtual server.
Now I own my dedicated server and want come back to sending lare ammount of e-mails (all sort of reasons listed above).
Don't send junk and you should be fine. If your server is configured to let them go out, then the rest is out of your control. The best you can do is to ensure you have "good looking" email content.
Spam filters are usually set up to flag certain words too, like: $%&^, %£!$ and or course $*%^. So you need to avoid the obvious ones, if your email sounds unprofessional, or looks like you are trying to market a Sex Toy Scam (for example) then you are more likely to be spam flagged.
Also, I have found providing both a HTML and Plain Text version of each email body can make a big difference in your spam scores at the other end.
Here is something that might provide some other ideas for you.
Other than ensuring that the people you are sending email to actually want to receive those emails by specifically opting-in for reminders/news/anything non-essential like registrations, you could try using a mass mailer like constant contact who has a RestAPI.
The email itself should be well formed. It shouldn't have any missing required headers (like Date: or To:) and the body should conform to the Content-Type header, either being all text if it's content is text, or if there is HTML, to use multipart-mime and include a text version in one part, and html in the other. Also, don't include links to shady places that could be blacklisted.
Make sure your mailing list is opt-in or provide an easy way for your community members to opt-out.
Provide the opt-in/out link directly in every email message.
Make it highly visible!
Send only to your community members.
Don't annoy them everyday with meaningless crap.
Even being careful and providing opt-in/out for your members you can't force them to use it.
Realize that email clients make it easier to just flag it as spam.