I am using Thunderbird mac 17.0.7, it always send "return receipts" even I have set the "Never send a return receipt". It did act as expected, but i don't know when and why it become so.
I have check the global setting and the account setting, it does be "Never send a return receipt".
Any ideas?
Thanks!
If your server is Exchange, it's a feature.
Related
I really want to know why does sent email cant be unsend
Is it because after mail reach the recipient MTA our Mail Server does not have control/permission to that MTA so it is not possible to unsend it?
Or is it because in the recipient SMTP Server has downloaded the sender mail, so it will always available in the recipient SMTP Server after get sent?
or what cause that ?
and if the cause is point number 1, my question what if the Mail Server is the same as mine or in other words for example me and the recipient use gmail
thank you for helping me
The reason might surprise you but it's rather simple. Because time is linear and you can't travel back in time.
Now, if both you(the sender) and someone else(the receiver) have Microsoft Outlook AND your email accounts are hosted in a Microsoft Exchange Server, then:
Open the Sent Items folder, and double-click to open the email you want to recall.
In the Message window, please click Message > Actions > Recall This Message. See screenshot:
In the popping out Recall This Message dialog box, please check the Delete unread copies of this message option, and click the OK button. See screenshot:
Note: It’s optional to check the Tell me if recall succeeds or fails for each recipient option.
If your recipients have not read the specified email yet, this email will be deleted from their Outlook automatically.
I have a need to "bounce" email from a specific email address. Meaning, when this person emails me I would like them to receive the MAILER_DAEMON message saying that the email address is no longer valid or some other "official looking" message that would make them believe that the email address (mine) is no longer valid.
Is it possible? I have Gmail but I am also a programmer so I would not be afraid to get my hands dirty with some kind of "server" that takes forwarded emails and then re-routes them or anything creative like that.
Any suggestions?
Apple used to include this feature in their mail app. There was a menu item
labeled "bounce" If you integrated into say, Thunderbird, you should be able to send the bounce. Alternatively, google has gmail API's that can read and send from your gmail account.
A Delivery Status Notification message is not hard to create on your own. You might have to tweak something to properly set an empty envelope sender (so as to produce an empty Return-Path:), but other than that, just write a reply with the desired text, and invoke it from your .procmailrc or whatever.
If you have direct access to the delivery machine, you might get away with just returning a particular error code, and the MTA will bounce the message for you, but the exit code depends on the MTA. Many implementations use Sendmail's conventions, but e.g. qmail has its own. http://www.eden.net.nz/7/20011101pairprocmail.html explains this from a Procmail perspective in some detail, and has the pertinent exit codes for both Sendmail-compatibles (which includes Postfix) and Qmail.
:0
* ^From: Annoying Perp <troll#example\.com>
{ EXITCODE=67 HOST= } # Exit with Sendmail code for "no such user"
The Postfix document http://www.postfix.org/FILTER_README.html explains the processing model in much more detail -- some of it is specific to Postfix, but as with all the Postfix documentation, it is understandable and helpful to the technically adept reader.
If you want to roll your own, your first stop would be RFC 3464; it's not a very tough read.
The Postfix bounce(5) manual page is very hands-on.
I am working with MFMailComposeViewController and all seems good. The class indicates the mail was sent, but I have never setup email on the simulator and don't know how. So if its sent, what email server did it send it to?
The [mailClass canSendMail] also returns YES so it thinks its all ok.
Does anyone know how to setup the simulator for testing this 100%
No, the simulator does not actually support email accounts or allow you to really send mail.
[MFMailComposeViewController canSendMail] returns YES to allow you to fully test your mail generation and compose code paths. As far as your app should be concerned, it behaves exactly like a real device (since the user can choose to cancel out anyways on the real thing), although you cannot inspect the actual contents of the resulting email without testing on a real device.
I'm working on an iPhone app that, at a certain point, will try to send an email message. If the user has an email set up, great, if not, I need to change some actions accordingly. My question is how do I check to see if the user's iPhone has an email account setup? I've looked everywhere but I can't seem to find an answer.
I'm using MFMailViewController to send the message, but I don't want to create an instance of it unless I can actually send something. Any ideas?
MFMailComposeViewController class has +canSendMail method which
Returns a Boolean indicating whether
the current device is able to send
email. (YES if the device is configured for sending email or NO if it is not.)
I know how to launch the Mail app to write a new email (using mailto). But I have a facility for users who have forgotten their password to get it sent to their email, and when they submit the request I would like to launch the Mail app, preferably in their Inbox.
Is there a way to do this?
Not possible. Confirmed by Apple.
If it is possible, it might be outside the public APIs. That said, here's an idea that might work, but I don't have all the details for you. The way you get Mail to open up when you want to send e-mail is that the APIs handle a URL request for mailto: by passing it to Mail. Maybe you can find another URL type that you can request to have opened, Mail will try to open it, but then have nothing there for Mail to open. If all goes in your favor, Mail will open and not show anything to the user (even an error from the bogus request you sent it).
Hell if I know what type of URL you'd need a pass, and there's no guarantee that something like this wouldn't break in a future iPhone OS version.