We have some issues related with AWS SES bounce and complain emails,
and we send send emails on these conditions. these conditions are as follows:
1) When new user registered, 2) When user forget his/her password and 3) When he/she purchased any video from ourplatform. To send email we have implemented AWS SES mail service and successfully managed to send email from AWS SES. But here I have some doubt to handle Bounced and Complaint email. According to this post on stackoverflow:
Handle hard bounces / complaints or just stick to suppression list?
We have managed list of emails in our database, when new user 1st time registered into our platform and getting notification for bounced and complaint notifications from AWS SNS. But here are some case I want to discuss with you:
Bounce: When user 1st time registered into our platform and his/her email does not exist i.e. jm123#gmail.com in that case we save his/her email into our bounced email list, but when 2nd time he creates a email with the same email id ( jim123#gmail.com ) and want to register with our platform again then how we will remove that email from list because we have already black listed that email in our platform.
Complaint: In 2nd case when user accidentally put our platforms email as spam when we send him/her a email and getting complaint notifications for that email and for complaint emails we have managed list of complaint emails and saved that email in this list so that same user can not get email from the next time but after some time that user white list us from spam and wants our email notifications.
Note: Is this necessary to handle all bounced or complaint email into our database because randomness of emails are infinite and for all random emails we have to handle into our database. and before send emails to any new registered user, 1st we have to process our bounced and complaint emails list then we will decide the user is eligible to receive our email or not.
Sorry for my bad English.
The StackOverflow Question you linked to covers this in the Answer.
Yes, you should maintain your own database table of at least some of the permanent bounced emails, something like:
record ID (auto increment), email address, bounce type: invalid mailbox | user complaint | rejected for content | rejected for spam blacklist
Bounce: "when 2nd time he creates a email with the same email id ...
how we will remove that email from list because we have already black
listed that email in our platform?"
When the user tries to add the email, you query the email address in your table, you see the type is "invalid mailbox", and then reject it as invalid. You could possibly also log the IP address to catch spammers trying to create fake accounts.
Complaint: "... but after some time that user white list us from spam
and wants our email notifications."
When the user tries to add the email, you query the email address in your table, you see the type is "user complaint", and maybe ask them "are you sure?" before adding them back to your mail list. You change the type of the email in your database to something like "user confirmed OK to send"
You could also just add one extra field to your existing mailing list table to hold the bounce type, with the default type being 0 / OK / not bounced. Then when sending email you skip sending emails where the type is not 0 / OK.
But in hard bounced if user will have valid email address after put
his email address in table and he/she wants our subscription then how
we could handle
You could allow them to re-add the address and set the type back to 0, but this might be a fake address like "fake#fakefake.com."
If you want to let them do this you could have a second field "times bounce was cleared" and add +1 each time the address is set back to 0 / OK / mail allowed. If this counter reaches 3-5 you never let them add the email again. They must use a different email.
what about soft bounce
"Transient" (soft) bounces should be ignored. SES will try again later and if it still fails then you will get a hard bounce.
Related
In Outlook 20xx there is no way to change From field automatically. There are ways to have multiple accounts and use a default one all the time, but not when you reply. This is anti-feature by design and I'm forced to use Outlook with Exchage server using user emails (so every user has his own storage) but sending as office accounts (and when recieving email a copy is forwarded to users which are in office group) [eg. robert#company.com is real account, but when sending/reply/forward it should be sales#company.com]. There are many examples on using macros for all sort of things but not this one.
I need 3 triggers that change From field without clicking some special custom button
when I click New Email
when I click Reply on some selected email
when I click Forward on some selected email
thnx.
added exchange user account, then added exchange office account, set office account as default, options -> mail -> send messages -> always use default account when composing new messages
This was the nearest goal but worked only for new messages, on reply it allways default to user account.
The email profiles are Exchange profiles/accounts and have the required permissions to send on behalf of another person (eg. office#company.com)
How do I configure an email address using cpanel to bounce back incoming emails after a certain date?
Our Organization wants to receive quotations from potential firms upto a certain defined date. After the date line, our organization wants the email account to automatically bounce back anyone sendind in late quotations.
I have a whitelisted Twitter app that can request and receive email address of a twitter account when the owner of the account accepts and logs in through my app.
Now, I plan to connect it to my already available "Sign-up/Login by email" flow seamlessly.
The problem is, logged in Twitter user may not have verified their email account. In that case they can hijack a user on my system who signed-up with that email.
Therefore, I have to be sure that they have verified their email address. Otherwise I have to automatically send a confirmation link to the email address of the just-signed-in twitter user.
Is there any way to detect if the user confirmed their email address on Twitter? If not, what is the general solution to this problem? At least, how do you solve it for yourselves?
I found out that if the user does not verify their email address, Twitter will not return the email address even though it is there. So, if you receive an email address from Twitter, that should mean that the email address of the user is verified.
If anyone finds that this is not correct, please leave your comment or your findings.
Twitter returns a 0 length string in field email if user didn't verify his email.
...
translator_type: 'none',
email:''}
I have pretty standard Qmail toaster installation. I'm using the dot files to set up mail forwarding for my account, so when I recieve an e-mail, this e-mail stays in my mailbox and is also forwarded to another email address. Easy, you say. And yes, it is, it is working fine ... except ... That this another email adress is actually a cell phone number, so I get an SMS notification about each email I recieve.
But, as our phone provider limits the size of an SMS, if I recieve an email with attachment, Qmail tries to forward it to my mobile phone, but this fails, the error message gets back to original email sender and he thinks the email was not delivered at all.
I haven't found any solution to this, but I came to an idea - if there is a possibility to LIMIT the Qmail, so he doesn't forward the specific type of emails (in my case, emails with attachments) ? Or somehow restrict him from sending back the error messages from these forwards ?
Stripmime
http://www.phred.org/~alex/stripmime.html
.qmail-default:
| /usr/local/bin/stripmime.pl | /home/vpopmail/bin/vdelivermail '' myphone#example.com
or
Demime
http://scifi.squawk.com/demime.html (link not working anymore)
.qmail-default:
|/var/qmail/bin/demime -8 myphone#example.com
My application sends mails containing an authentication token. The user which receives the mail clicks on a link and is directed to a webpage. The app recognizes him.
The problem is that sometimes the mail is sent to a mailing list instead of a personal address. Then several people come on the page and override each others' actions.
There are 2 ways I think I could solve this :
detect that the email address is a mailing list before I send the mail
include the final recipient address in the link in the email.
Is any of the 2 possible ?
No.
The recipient can tell if the message came from a mailing list (if the list follows the right guidlines), but the sender can't.
There is no way for the sender to modify the body of an email dynamically based on the final recipient.
David's answer is correct. Though, depending on your context you may find the following idea useful:
You might be able to record the number of clicks per email sent out using that token and just specify a threshold. If the number of times the auth token exceeds it, flag the recipient as a mailing list and exclude them from future mailings.