The users of this Meteor app need to send email to their customers. The code to do that is simple:
Email.send({
to: customerEmailAddress,
from: userEmailAddress,
subject: 'someSubject',
html: html
});
However since each user has a different userEmailAddress, AWS is rejecting the sending:
554 Message rejected: Email address is not verified.
It is not easy to verify each and every user email on AWS, and not sure if all other smtp server would give the same response, Any suggestions on how to handle this error for current and future users, which could be few hundred of them, each uses own domain, and each has own clients? thx
Related
When someone signs up they receive an email with a link they need to click to verify their email. The email comes from no_reply#domain.com
So far all clients receive this email with the exception of clients using their own domain with Office365. With these clients it's not an issue of emails going to spam - they don't receive anything at all in either their spam or their inbox.
The email is sent from a domain that uses Google Business for email.
Any ideas how to solve this issue?
I should add that if the email is forwarded manually, it does come through, just not when automatically sent.
I keep getting these bounce backs, works on any other domain gmail, yahoo but not outlook/hotmail. is it me or them? I am using Smartermail with all possible settings setup ie DKIM SPF ii basically get a perfect score on https://www.mail-tester.com/web-zorml
Could not deliver message to the following recipient(s):
Failed Recipient: xxxxxxxxxxxxxxxxxxxxxx
Reason: Remote host said: 501 5.5.4 Invalid domain name [DB5EUR03FT018.eop-
EUR03.prod.protection.outlook.com]
prod.protection.outlook.com is Outlook/Microsoft's anti-snooping service. In case you didn't know, by viewing an email header, you can see the sender's IP. In order to circumvent this, Microsoft/Outlook sends your emails to prod.protection.outlook.com and then to the recipient, so if someone views the header, they get prod.protection.outlook.com's IP instead of yours. My guess is that your email provider doesn't recognise prod.protection.outlook.com as a valid domain name and thus can't send the email.
I host a mail server, where users log in via SMTP to send email.
The current config of postfix allows every authenticated user to send emails with any sender address.
My objective is to prevent users sending mail with an other FROM: address than the sender’s own SMTP login name.
For example: if you log in with the username bob, you’re only allowed to send emails with the sender address bob#example.com.
smtpd_sender_restrictions could be a solution, but this would reject clients, who entered any other address.
A more elegant way would be to automatically rewrite all from addresses to the username they logged in with. That's, what I'm trying to achieve.
Just like Gmail, if you use it as an SMTP service to send emails, the messages are sent with the address you logged in to Gmail.
Currently the SMTP authentication is done by dovecot:
smtpd_sasl_type = dovecot
The server itself is really simple, no fancy custom per-user based stuff or multi-domain setup, just users SMTPing in, and sending emails. :-)
I know that smtp_generic_maps and sender_canonical_maps exist, but I coudn't find the way to automatically rewrite the senders address.
By automatically I mean not one-by-one in a separate file.
Thank you for your help!
I am currently working with a client that allows users to generate emails, which are sent to the client's mail server, where they are parsed, content language is added, and they are resent to the recipient.
So, my server basically sends the following:
FROM: sender#myserver.com
TO: receiver#externalclient.com
SUBJECT: hello world
BODY:
|FROM:anyone#anyserver.com|TO:anyoneelse#anyotherserver.com|CC:anycc#anyserver.com|
Dear so-and-so.
Here is the information you were asking for.
Sincerely,
Anyone.
When these emails are sent from our production website (i.e. www.myserver.com) to our SMTP server, they go through without a hitch.
However, when I attempt to send one from our testing websites (i.e. test.myserver.com), they are rejected with the following information:
#5.0.0 smtp; 5.1.0 - Unknown address error 550-'rejecting spoofed message' (delivery attempts: 0)> #SMTP#
Is there any way on our end to get these emails to go through, or do we need to ask the external client to change their configuration to allow us to send emails from other sub-domains?
it has to be the recipient domain to cater the changes.
My goal is to create a canned email on my server and then send the email from client email addresses. To do this and not be marked as spam I understand it must come from a domain matching the from address.
There are many user email addresses I would need to send email from, all with the same domain. With cooperation from my client, could I set this up to work with one SMTP credential or would I need credentials for each and every individual user?
To clarify, if I get an SMTP server address with a un/pw from my client, would that be enough to send from:
george#example.com
martha#example.com
ted#example.com
Thanks!
It depends completely on the SMTP server you are using. Some servers will allow this, like Google's SMTP, but it will attach a Sender header to the outgoing message when the From header does not match the authenticated account.
Example:
You authenticate with joe#gmail.com
You send out with From: bill#gmail.com
The message will contain From: bill#gmail.com, but Google will attach
Sender: joe#gmail.com to the message headers.
So, it completely depends on the SMTP server and their policy.
Problem
You want to avoid joe-jobbing in your automated messages.
Your Options
It depends on how you're submitting jobs to the MTA.
If you're authenticating to a remote SMTP server for each message, then you need credentials for each user.
If you're injecting messages directly into an MTA (e.g. with the sendmail command) that is authorized to send mail for the domain, then you only need privileged access.