I need to send a PDF to person B through person A, without person A being able to access it and i can not contact person B. Currently i only have person B's email address.
so the email will go from me -> A -> B
You can not disguise or impose and send email from someone else email address, IF that mail server does not allow sending emails without credentials (username, password) . Example: if you want to send mail from xyz.gmail.com, then you need xyz, credentials.
Copying text from comments so that this doesn't get down voted as non related answer.
Based on your latest edit,
One possible solution is to password protect your PDF and send it to A and ask him to send it to B. The password should be some thing like a pin that only B will know without you sending it to B
Related
i have an email domain but i want to create an email server using that email domain but these server should be able to recieve emails and handle them without existing user accounts.
I mean, if someone send an email like "aaa#mydomain.com" or "bbb#mydomain.com" the server should be able to recieve those emails and handled them but those user accounts (aaa or bbb or other any "users") don't really exist in my email server.
I don't know if i have to program from zero an email server that should be able to do that (I use Java) or if there's email servers out there that can do what i want to do.
Thanks in advance.
Right now I have a really simple mailer:
class ExampleMailer < ActionMailer::Base
default from: "info#example.com"
def weekly(email)
mail to: email, subject: "500 Points for liquid.radio!"
end
end
What I really want to do is send an email to all Users. The problem is that, a while back, there was a problem getting the email addresses from the facebook users, so as a temporary solution I generated a generic "xxxxxxx#facebook.com" email address for each user that wasn't able to get it from omni-auth.
So now what I would like to do is email all users EXCEPT for the ones with the "#facebook.com" email address.
Once that's setup I usually send the emails from the console like this:
ExampleMailer.weekly("example#gmail.com").deliver
I would imagine I'll have to find a different way to do that if I'm going to email all the users (except for the facebook ones.)
I m with a doubt with email, i have two objects an object call request where which request is related with an account.In the accounti have the email information, and in the"request" i have the fields that i need to write my email, so i create an email template where i bring the info from the object request, and now i want to send this email to contact in the account object.
And how do do a fluxe where it will send the email to my account with the information that i have in que other object.
Correct me if I'm wrong, the Email Address to which you want to send to is in the Account record and not in a Contact record associated to the Account, yes?
If so, using Standard Workflows, you only need to:
Create an Email field on your 'Request' object
Create a workflow that populates this new Email field equal to the Account Email Address upon creation/modification
Use this Email field to send an email.
Caveat: If the Email Address on the Account has changed, this won't fire off the workflow you created. You would need an Apex Trigger to achieve this.
When sending an email, is there a way to find out:
User has received the email (displayed in user's inbox).
User has read (and at what time) the email.
If it's not possible, what prevents it from finding out? What is the route an email message follows from sender to receiver.
When you send an email, the email is transferred through a series of servers using SMTP (Simple Mail Transfer Protocol). Once the email reaches it's destination it is stored into the recipients directory. To retrieve and read the email, the recipient uses and email client like Outlook to that connects to the server via IMAP/POP3 which tells them how many new emails they have and delivers each message to the client. In order to get this information, the user must provide their credentials.
So, in order to get this information you would need to know the imap/pop3 server(s) for the recipient's domain, as well as the recipient's login credentials (which would give you full access to the recipients email account). Basically, this is not possible.
This article gives a nice simple overview of how email gets sent over the internet.
You can, and you do not need the credentials as mentioned in the selected answer.
Lets imagine you are using apache and php + mysql.
You send person x an email,
In the email you have an embedded image (your logo) which resides on your server.
the url of the logo in the email, points to a file on your server:
example.com/logo.png?userRelatedId which is a php file.
with an htaccess (apache) you can state that logo.png gets executed with php and in fact forwards a real image and correct mimetype but before that identifies userRelatedId, and saves in your database with the time the file was accessed,
Meaning the email was read by person x and the time which the logo was accessed (email was looked at).
I'm building a system that allows people to submit text and photos via email in addition to standard access on the website. I'm trying to weight the security advantages of two strategies in particular for verifying submissions from a user. Here they are as follows:
To based auth: Create a secret email address per user and present this to the user for submission. This strategy has the advantage that people can send from multiple devices that might be setup with different mail accounts
From based auth: Only accept emails from addresses that are registered in the user database. The idea being that it is impractical/difficult to impersonate registered users based on the sending address.
Can you think of other possible solutions? Which strategy of the ones proposed makes the most sense to you?
I would suggest that you not use From based authentication, at least not without some additional credentials (a passphrase, etc)
It's way too easy to forge, and certainly not difficult if you know someone's email address.
If you echo the email back to the user for confirmation, you can make things a little more difficult, but realize that your service can end up being used as a sort of spamming relay. (I could send 100 upload requests to you, with a forged FROM address, and you'd go ahead and spam the real person with 100 confirmation requests)
The better option is to check the registered email address but add the need for a code within the email subject known to the user. This way if they forge the email from address, they would still need a key to authenticate the incoming email.
I would go with "from" + confirmation, to avoid forging.
I.e. receive the email, but send a response with auth token in the subject line (or in the body) back to the "from" address. The user either will need reply, or click a link to confirm the submission.
And you post the content only after confirmation.