I have an issue with a Prestashop 1.6.1.6 where the "eshop" doesn't receive any order email, but the customer receives them properly. The Prestashop is hosted on a shared hosting server with cPanel, running PHP 5.5.
I have checked the above so far:
Under Preferences->Store Contacts->Shop email, the email is correct.
After a successful order as a customer, in cPanel->Mail->Mail Trace, i can see the delivery attempts to customer's email but not to "eshop" email.
Have installed, enabled and configured properly the module "Mail Alerts", entered 1 and more emails in E-mail addresses, but didn't receive any email as the "eshop".
Tried the option: Advanced Parameters->E-mail->TEST YOUR EMAIL CONFIGURATION->Send a test email, with the "eshop's" email address and it worked, bot with PHP mail() and with SMTP.
I have sent an email via the contact form (as a test customer) to Webmaster and to Customer Service and both the client and the "eshop" received the mail.
Sent a test email via thunderbird to the "eshop's" email address and it worked.
Made a new registration as a test customer with a valid email address. The test customer received the "Welcome" email, but the "eshop" didn't receive anything. (i am not really sure if the "eshop" should get any notification mail in this case to be sure, but i tried it).
What i understood so far, is that the mail functionality works for contact forms, test emails via Prestashop, test emails via thunderbird, but not for any kind of orders.
I don't know if there is something else to try to find the problem.
Is there any other option in Prestashop, which prevents the order emails to be sent to the "eshop"?
Is this a bug in Order Functionality?
Any idea would be useful since i don't know what else i can do. Thank you in advance.
if in "eshop" you meant merchant, by default Prestashop does not send these notifications to "admin",
install the Mail alerts module, and there are options to send different types of emails to provided addresses.
It would look that you have the email template in "modules / mailalerts / mail / in / new_order.html"
Regards,
Related
I have a website with a webform which users can use to contact a company. The webform internally creates an email in PHP using PHPMailer and is sending this email via SMTP to the company.
The company has a customer-management-system which identifies the user by looking at the sender of the email. Which means I couldn't send the email from the form from "form#example.com" to "customer-relations#example.com", but need to send it from "customeremail#customerdomain.com" to "customer-relations#example.com".
This worked for some years now, but since some time, we get the error-message:
"envelope sender not allowed customeremail#customerdomain.com"
for example from emails from #gmail.com. Other domains still work.
I understand that it is not good practice to "fake" the sender of the email to make the identification of the customer-management-system work. The developer of the customer-management-systems are not able to offer a solution yet (no comment on that...), so perhaps there are any ideas here which we could try to make this work?
I'm running a wiki based on mediawiki 1.21.11. Because I can't prevent users to change their e-mail address, I want to get informed (e.g. by mail) about this change.
My question: is there any possibility to send e. g. a copy of the notification mail or another notification including the old or new e-mail address to a specified recipient when users change their e-mail address?
You can prevent users from changing their email address with an auth plugin, although it seems like a horrible thing to do. You can use some hook to send you notifications - PrefsEmailAudit or UserSetEmail if you don't require confirmations, ConfirmEmailComplete if you do.
I'm building a service for a company. The users of the service will send survey links to a list of email addresses. I'm going to use Mandrill as an email engine for this. The service is built using Laravel.
The users will feed a list of email addresses to the service that will generate emails (unique for every email address) and send them through the Mandrill API.
BUT, of course there will be errors made by the users. They will feed some bad email addresses in and emails will bounce. I need to find of way of notifying the users of the service that some emails have bounced.
Is there a way to get Mandrill to send a list of bounced emails to the sender or reply address?
Me as a developer has the Mandrill account of course, but I'm not interested in the bounce information - that has to go to the users of the system. So they can take action and correct the errors.
Thank you.
I see from Mandrill API that it is possible to get the status of sent e-mails with call /exports/activity.json as described in https://mandrillapp.com/api/docs/exports.JSON.html#method-activity
If you get any bounced e-mails from there then you can manually send the corresponding messages to the users who you want to.
I'm using the wordpress theme classipress and i've installed the plugin easysignup. The plugin works but the problem is once the user has received the email, they can reply. When i sign up to emails, they normally have a way to prevent the user from replying.
How do i accomplish this?
Do i have to create a #noreply email and change a setting so replies are bounced back?
This plugin required me to type in an Automated Reply Email, i used the website contact address just to test if the plugin worked.
Is there a host email address that is outgoing only?
You can't make it so users can't reply - that is up to their client. All you can do is send it from another email address and discard the emails it receives.
I have a Magento store that apparently sends too many confirmations emails on an order. My theory is that the emails are resent all over again to the store admin when the customer tries to shop entering an inexistent email address.
How can I debug and/or fix this?
Thanks
Is the customer's email getting returned to sender? If so try setting the sender address to a blackhole, a mailbox that drops all messages. It's not uncommon for sites to have a "noreply#" address for this purpose.