(2) It appears webflow.io has been spammed ?? Or at least Barracuda thinks it’s spam.
We have a server rack that contains a Barracuda Firewall / Spam Filter server as well as one of our Microsoft Exchange servers.
Messages from webflow.io are sitting in our Quarantine folder. This tells us… Barracuda Central considers messages from webflow.io to be a potential spam. You might want to contact Barracuda and address this issue. For me… I’ve white listed the address - so hopefully I’ve solved this issue (for me). Other Barracuda users might still encounter this issue.
Why is this notice back in our messages. I thought it was removed a while ago… or at least I complained about it a while ago. Notice the webflow.com domain name.
(I was testing the site…) I wasn’t really testing the contact form. I did it by accident… forgetting that the contact form would be sent from the webflow server.
Normally… I export the site and let our mail servers handle it.
the email address that the email is coming from will always be “no-reply@webforms.io” . This is different that the “Reply-To” address.
The “Reply-To” address only takes effect when the user clicks on the reply button in their email client. If we allowed users to change the email address where the email is really coming from, they can spoof it and use it for malicious reasons.
Is there anyway to white-label webforms.io in your system?
I understand what spoofing is… apparently I mis-understood a prior statement Webflow made about this feature.
Having the webform.io domain name… kinda blows the white-label idea.
In fact… if you check the whois for webforms.io… you see Webflow as the owner of the domain.
I generally export… the only reason I caught this issue was I was in hurry and decided not to export and test. I was testing the website directly on the Webflow servers.
When I export… I change the mail features over to our servers… and the reply address is always the clients reply email address.