if i take an order manually in Magento Backend without depositing an e-mail adress for the customer, Magento is creating a random one for this order.
But where does it come from or what is the sense of that? My problem here is that i'm recieving an error by mailerdemon because that e-mail does not exist.
Check http://yourdomain.com/index.php/admin/system_config/edit/section/customer/ under "Options for creating new customer". There you can set the custom domain used for new customers. Setting that to, for example, the free catch all email service mailinator.com should get rid of your errors.
Related
I have a G Suite account for, let's say, domain.com. I have a user with email address me#domain.com. Today I added a new domain to the account new-domain.com and set up an email alias for my user, which is me#new-domain.com.
Since "New Domain" is my new company name, I want to transition to the new email address and eventually get rid of the old one. To help avoid confusion during this transition, I want anyone who emails the old address (me#domain.com) to get an auto-response like "Please use my new email address in the future...".
What I've Tried
The most obvious thing would be to setup a Vacation Responder, but Gmail doesn't let you specify which address it's for. So there's no way for me to easily specify that responses should only be going to senders emailing me#domain.com. G Suite does have an advanced setting in Gmail where you can quarantine messages. I've tried to use that to quarantine Vacation Responders coming from the new address, but that's not working either because the new address is now the default one, and thus emails coming in to me#domain.com get a Vacation Responder from me#new-domain.com.
To me, this seems like a pretty common situation - transitioning users from one domain to another - and using an alias so users can just have one inbox to check. Does anyone know how to get this to work, or is there some other best practice I could be following?
From my knowledge, your options are to use the Gmail Routing to block incoming mail to specific users or groups and to set it to 'reject message' and add a message informing them of this change.
-a little crude but workable.
Alternatively ensure users reply use their new primary email and ensure there is a long enough transition period for people for external responders to change over.
I have 10 customer group in my website. I would send the order admin notification email to different address, based on user customer group.
For example.
User from customer_group_a take order will send admin notification to order1#website.com. Then user from customer_group_b take order will send admin notification to order2#website.com
Also, how can i get the customer data in order email? I try this, but not working in email/sales/order_new.html:
{{var customer.name}}
To send to different people, the best is to add the needed email adressess via system.xml to be able to edit in your back-office the emails then you will need to override app/code/core/Mage/Sales/Model/Order.php to fit with your logic. The lines that interest you are in queueNewOrderEmail() function.
Try to use the constant for the path to your config.
For the name in your template, you can normally use {{var order.customer_name}} if my memory is good or {{var order.customer.name}}. The functions getCustomer() and getCustomerName() exist in the precited class.
Need help - my prestashop sometimes not sending new order admin emails. They are not in the email logs in backoffice, and not in the spam folder in email.
I also noticed a pattern, that for new orders with just numbers in reference email are generating, but i'm not receiving admin emails for orders with random letters in reference, like this:
Other emails, such as order confirmation and payment confirmation are generating for every order and they are received by customers.
Is there any way to change this order reference to just numbers or any other way to deal with email problem?
Have you tried installing module named "Email Alerts". You can install this module and you can setup notification accordingly.
Hope this helps you !!! :)
Here is the module links:
https://www.dropbox.com/s/is666weeq6qhcug/mailalerts.zip?dl=0
https://github.com/PrestaShop/mailalerts
My company have a website on which, at some point, users are asked to register.
Until a few weeks ago, we used to verify the mail adress by sending an email.
The user had to log into their mail account and click on a link in order to validate their account.
Problem is, we had many users having difficulties (email not received...) or simply leaving the website at this step. Moreover, our support team had to deal with many call about those difficulties.
We decided to remove this verification and it had many positive effects, the first being less ticket for our support team.
However from this point, we had many "fake" emails and I would like to know, what can I do to limit those fake emails without the verification described above? Is there any non-intrusive methods to verify an email adress ?
An exemple of (probably) fake email is hyuiuyhajsdv#gmail.com
Here are what we're already doing to prevent fake emails :
We're using PHP filter_var to validate the format
I know it's not perfect but we didn't found anything better
We're doing a DNS verification of the domain name (with gethostbyname)
This prevents something like superemail#test1245.com
Finally, we're checking if the domains name match a disposable email service.
Note: we don't have any problem with bots creating fake accounts, so a captcha won't help.
Given there is a "FAILTO=''" option for cfmail, triggering an email to be sent to that email if the email didn't get delivered...
Is there a way to somehow assign an ID or tracking # to an email, store it in a database with that ID... then update the status of that email if it fails?
I'd like to track bouncebacks... preferably WITHOUT sending the FAILTO to a POP3 or IMAP and then checking it with cfimap...
Is there any alternate way of handling this?
Maybe an event gateway that is triggered upon email failure?
UPDATE: I've decided to take a different approach, utilizing the sendgrid API.
I'm hoping that lends me with a few more tools than CF offers.
The short answer to your question is unfortunately no.
A longer version with a possible solution:
The failTo email address populates the return-path in the email header, this then 'should' be used by mail servers for bounce backs (however see - http://www.bennadel.com/blog/1899-GMail-Seems-To-Ignore-The-Return-Path-Header-Defined-By-The-CFMail-FailTo-Attribute.htm for an example where it doesn't)
So you are going to need to monitor an Imap or pop account to see your mails, however you can set up an event gateway to monitor this, with detailed instructions here - http://www.alagad.com/documentation/imapGateway/ImapWatcher%20Gateway%20Documentation.pdf
What you're left with is needing to identify which mail matches which bounceback, when I've done something similar in the past I used unique id's for the failTo email addresses at a domain I owned. If you set that up and then use your listener cfc to look for the id in the return-path.
So your sending code would work along the lines of:
Generate unique id
Send mail
Add row to database with unique id
Your listener.cfc would then need to inspect the email returned and if it finds the unique id update the row with whatever information that you're after.
Hope that that at least helps even if you'll need to set up some other bits.
You could use a directly watcher on the undelivr folder to log the failed emails, only really a solution if its own server and not a shared server though.
As far as I know once it leave the spool and is off to your SMTP server CF assume it's been sent correctly.
The email will trickle down the chain of SMTP servers/relays and if anything happen the only instruction they have is to bounce it back to the from address or failto address if present. CF isn't listening at this point so it can't respond.
We use an external tool called Glock email processor to handle exceptions. It's not free, but works pretty well. You can find it here: http://www.glocksoft.com/email-processor/
You need to configure it to check the failto address and from there you can take many actions. I got it setup as a three strikes system.
Email address bounce, I increment a counter in my email table, at 3 I deactivate that email from the system.
Nothing you can't do yourself with cfpop though.