In my app, there is an email functionality which should send email from an id, which is not configured with mail app. From address will be like noreplyATgmail.com .. some thing like that.
How can I hard code the from address of an email ?
It's impossible to send email from account where user isn't authorised in.
For your aims it's better implement email functionality on server side that could be authorised to send emails from address that you specified.
As per my comment - you can't, you should use reply-to for that, or send a request to a server to send the email. The from gets set from the selected email address you eventually chose to send the email with.
For example:
mailto:email#email.com?subject=Subject&reply-to=noreply#something.com
I don't think there's anyway to do this using MFMailComposeViewController.
Related
I'm attempting to create Outlook emails that should be sent "from" someone other than the person actually sending the email. The idea is to prefill the email, display it in Outlook, allowing the end user to modify before sending. As a part of that process, I would like to use a different email address, which is a true email address, but is not an account in the end user's profile.
If this were SMTP, I could use the Net.Mail classes, which will accept any smtp address as the sender. Like this:
string from = "mytest#myorg.com";
System.Net.Mail.MailMessage mail = new System.Net.Mail.MailMessage(from, to);
My question then, is it possible to do this using Redemption? All the examples that I've been able to find talk about either accessing the "Sender" property, or the "SendUsingAccount" property. From what I can tell, these both require an Account in the user profile.
If you are sending using Exchange (as well as most SMTP servers), it will not let you spoof the sender. The user must actually have the right to send as that user.
Know a user can send a mail using he MFMailComposeViewControllerDelegate as mentioned here, but how to send a conformation mail to the user after the set of specific task has been done.
For some reason it feels like apple doesn't allow in sending background mails, without user conformation, which is fine.
The task is to send a conformation mail like after you buy productA, productB and pay, need to send a receipt to the said mail id.
Any guide in the said path would be greatly appericiated
You can't send an email from the user's email address without using an MFMailComposeViewController, and you can't send an email to the user without the use of a server.
What you should do is prompt the user to enter their email address, send that as part as their purchase, and then use a server-side mail app to send a confirmation email to the user-provided email address.
You can't send it directly from users device without email composer.
Only way to do this will be to prepare your own server that will handle those events and send proper emails from server side.
My website allow User A send email to User B through a form. Currently if User B want to reply, he need to login to my website and use the same form.
User A dont know the User B's email address and vice versa.
I would like to allow User B reply to User A directly using his mail client without need to login to my website (while still keep both email addresses confidentially). So User A send a message to User B using the form. User B can reply to user A using his email client, and user B can reply to user A using email client too without reveal their email address.
I was told this is possible with Mandrill Webhook. Is that correct? Can anybody please show me how?
Thanks a lot.
I think what you need to do is inbound email processing.
First, create an inbound domain in your Mandrill dashboard.
Set up routes / webhooks in your dashboard (for example, sending an email to pm#example.com will send a POST to http://example.com/email-processing/pm).
In your application, process the received message and decide if you have to send it to one of your user, and more important, which user.
To do so, you can add a unique ID inside your emails. So you just have to read this ID when you receive an email, and you know who is the sender and who should be the receiver. Of course, you should also check the sender's email address.
More informations about the first two steps: http://help.mandrill.com/entries/21699367-Inbound-Email-Processing-Overview
I'm working on a free iOS app; at the end of the registration (when the user has registered a good phone number and good email address) I want the user to enter a code which he has received on his phone or email.
But the problem is how to send automatically a SMS or an e-mail programmatically that contains the code?
I don't want the user to be redirected to a specific view controller to compose a message by himself (like with MFMessageComposeViewController or MFEmailComposeViewController)
just and only just the same appearance of SMS or email sent to users but with a different activation key (for the keys, I think about auto generated keys stored in a database).
And I think about the same way for forgotten identifiers, the user enter his email address or his phone number in a text field, and a message is automatically sent with the password and the username of the user, if the email address or the phone number entered is already existing in the database, if it is not, it shows an alert view with an error.
Does anyone have an idea for how to do this?
You can use the following services Parse.com + mailgun. Search on Parse.com for a tutorial using mailgun and it should accomplish what you are trying to do. On a side not, be careful when creating an app which does not allow the user to use it until they enter some access code, it is against the Apple rules and could lead to rejection.
I assume you have a server that generates this activation code that is sent to the user.
When the user enters the text field with the code he got it should be sent back to the server with an http request (use NSURLConnection ). The server should response to the http request with approval or error whether the code is right, or send the username and password and any other data the user needs to continue.
I am building an email app in ruby on rails and I had a basic version which just used to send emails using AWS SES but recently I received a mail from AWS team saying that most of the email which I have sent had bounced back and they will discontinue my account if I send emails to the bounced email ids.
Is there any way to verify before sending email to any address that whether that email exists or not and valid or not.
Any gem or work around will help me a lot
The general way to do this is purely from a system design point of view. If you are going to collect an email address from one of your users and send them email periodically, or as events happen etc, then you should first ask them to "verify their email address". This typically involves generating a unique token, putting that into your database, linked with the user, then sending an email containing a URL with that unique token in it. The user clicks the link, which goes to a controller in your Rails application that matches the token against the user. If they can't follow that link, they can't read your emails, so don't send further email to that address.
If you obtained the email addresses through "other means", you're down to setting a Return-Path address on the outgoing email (bounces will be sent here), then checking that mailbox for bounces. I'm also often suspicious of how people happen upon a list of email addresses that didn't come from users consenting to an agreement with your website.
You could use the Mail gem to do this, but you need to know how to set up an SMTP server that pipes the email into your Rails application, which is not straightforward without prior experience. You can also use a variable Return-Path address (VERP), such as <some unique hash>+bounces#your-domain.com, where <some unique hash> references the email address in your system. This takes away the pain of trying to parse and interpret the bounce email, since the address it is sent to tells you who the bounced recipient is.