I'm using Typo3 powermail mail forms, after send the form is stored in backend but never send a copy to the recepient or user adress. how can i troubleshoot this issue ?
btw, Test emails from installtool works good.
Did you configure your form that it uses the email address of the visitor who fills in the form as sender address? That's not good practice anymore. Most mail servers check the SPF record and reject mails that don't pass that test.
You can configure the default sender name and address via TypoScript. And check if the SPF Record fits for that sender address.
Have you set a subject? I've been fooled more than once because I didn't set the subject.
There are different ways to do this:
in the Plugin/CE,
in TypoScript,
in the overrides in TypoScript.
The value must not be empty after applying this cascade.
(Applies to sender and receiver settings in the same way)
Related
I have a form on my portfolio that allows a user fill in a form with a question they have and send that to me by email.
When i try to use sendgrid it only allows me as a verified user to send emails from my own email address. but i want the 'from' field to be dynamically filled in by that user and then sent to me.
note: I also tried 'emailjs' but that works fine in development but fails in production.
Any suggestions on how to fix this or any other platforms i can use for that preferabally free since it is a hobby project.
Thanks
Twilio SendGrid developer evangelist here.
You do need to use a verified email address to send emails from SendGrid, this is to stop people using a form like you describe to spoof anyone's email address.
A better idea is to send emails created in your form from a verified email address and set the reply-to address as the submitted email. That way you can send with SendGrid and then when you reply in your email client it will return to the person that submitted the form.
I added more detail and example code (in Python) in this answer.
All of the contact forms on our website put the user's actual e-mail address in as the FROM address. The problem is that it appears our e-mail host is now checking DMARC headers and seeing that our SMTP server (Sendgrid) is not a permitted host to send FROM certain domains such as yahoo.com or gmail.com.
One hacky fix I found was to make the FROM address default to something control DNS for (user#ourdomain.com) and then put the user's actual address into the REPLY TO field, but this then causes problems with our ticketing system (Kayako) and it feels like there should be a better solution.
Any tips on dealing with this? I'd hate to get rid of all of our contact forms and switch them to simple e-mail addresses, but apparently we've been losing a bunch of contact requests that are simply blocked.
The best way to handle this would be to set the form to use a domain you control. Otherwise, the form submissions have the appearance of spoofed emails. You aren't a spoofer but your form submissions look exactly like them. There's not a good work around other than to send form results from a domain you control.
I'm trying to get a mailto link that would open a new outlook email window with a modified from field (i.e. to use a secondary account as it were). Is that possible?
No. Certainly not in most of the popular mail clients.
I assume you are wanting to do this just to save time in your own mail client. I would certainly be annoyed with a website that tried to change my from or reply-to address, so I'd expect my mail client to ignore it.
MAILTO is designed to facilitate a sender contacting an address that has been listed on a website. So there are very few things that the sender would expect to have dictated by the website. Even the standard options can be pretty annoying if handled badly by the website owner.
Your options are pretty much limited to
subject
body
cc
bcc
Even if a client were to support From (and I am not aware of any that do), there is no obvious way for them to handle edge-case scenarios such as a from address that has not been configured in the mail client.
What do you need this for? Perhaps you can use a script to send mails and dynamically set the From header. For example, PHP has a mail() function which would allow you to set a custom From address (and modify other headers).
We are developing a contact form for a SaaS application; each instance of our application will have a contact form to contact the instance owner.
Our first version sends email from a generic SaaS email address (i.e. contact#saas.com) to the owner of the instance (i.e. user#example.com).
This works, but of course if user#example.com replies to the email, the answer gets sent to contact#saas.com . I'm wondering what's the best practice here:
Setting the from: message to the email address filled out in the contact form would enable replies to be sent easily to the person who sent the contact form- but then, we cannot tell people to add contact#saas.com to their whitelist to avoid spam filtering
Setting the reply-to header seems better, but I'm wary that some clients will misinterpret reply-to
Including an explanatory text in the message seems inconvenient, but workable
Allowing instance owners to read contact forms through their admin panel seems too much work (but completely spamfilter-proof, albeit inconvenient)
I'm leaning towards 2. Thoughts?
Alex
I'd definitely go for option 2 . From-Header / Envelope-From should make it clear that the message originated at your service (and allow proper bounce handling etc) . I'm not aware of any current mail clients that cannot handle reply-to header correctly. to be on the safe side you could mix in option 3 and clearly state that the message was sent from address sender#example.net via your webform.
Proper whitelists should work if you put the real sender in Sender: and/or the envelope sender; but then again, in an ideal world there would be no Microsoft.
How do I create a contact form that will submit to an email address? The email account will be hard coded and grabbed from a form field to cc sender.
Thanks!!
You'll need the form to submit to a controller action on the server (I'm assuming ASP .NET MVC 2 based on the question's title) which will build and send the email.
There are plenty of tutorials on how to actually send the email. Basically, you use the mail objects from System.Net to construct a message and send it to an SMTP server. Naturally, this means you'll need an SMTP server you can use. Your email provider may or may not have a public one. If not, that's a whole other question.