I think there were (as this was my previous employer) 2 or 3 support crew
per 1000 accounts.
And sure there were questions. But this would only escalate to me if the
technical dept. did not agree to the settings that were prefilled (e.g.
some customers simply demand 2048 bit DKIM). The advantage of this form is
that the link could be forwarded to the people "who did their website" or
"their hosting company". They could implement and verify DKIM/SPF settings
themselves (which was a huge win; most hosting service desks are not that
DKIM/SPF savvy or make tiny mistakes).
We would also let you send without the modifications. But we pushed for
strong authentication. This made the push easier and faster.
On 19 February 2018 at 13:08, Stefano Bagnara <mai...@bago.org> wrote:
> On 19 February 2018 at 12:24, David Hofstee <opentext.dhofs...@gmail.com>
> >>Using a return-path in the domain of your customer can be easy when
> >>you have a multi-thousands-dollars contract for each customer. But
> >>when you have "free" users or "few dollars per year" customers, you
> >>can't afford manually helping people to configure their domains so
> >>that you can use that in the return-path and then deal with major
> >>issues when the domain is "misconfigured" during a send
> > Why would you need to "manually help" people? SPF and DKIM can
> > be automated. Customers only need instructions for 3 DNS records.
> > Verification of those settings can be automated.
> > In MailPlus you can request this SPF/DKIM setting verification page:
> > https://drive.google.com/open?id=0B3Pxi9-uQ2MtbUdNeDByR3hqcTRHY2NyMk4zU
> Are you telling me that none of your customers needed help with that?
> Your customers probably have an IQ above average! How many
> customer-support people do you have for every 1000 users of the
> My users have issues identifying a button when there is only one
> button in the whole page, so we are very dedicated to UX. They don't
> even know who/where to go to alter DNS of their own domain, and there
> are plenty of providers with their own tool to deal with DNS entries.
> We work a lot on helpdesk and for every step you add, even the most
> trivial, we will get more requests.
> Last time I checked most big freemium ESP let you do this
> configuration as an option, but they also let you send without
> altering your DNS: maybe they shared my concern.
> > It checks if your DNS settings are ok, validate if DMARC settings are not
> > too restrictive and will setup SPF/DKIM automatically if they are.
> > is done in Java (and not on the mta). No hands needed anymore.
> Then maybe you use my opensource Apache jDKIM library? ;-)
> > Yours,
> > David
> > On 18 February 2018 at 00:53, Dave Warren <d...@thedave.ca> wrote:
> >> On 2018-02-17 03:48, Stefano Bagnara wrote:
> >>> Unfortunately there are still some server accepting everything and
> >>> sending bounces without headers or malformed bounces.
> >> This is not a small group. Every few months I get massive floods of
> >> bounces from some spambot that decided forging my domain is a good idea.
> >> I didn't even realize this was still a thing when I was running my own
> >> mail server as I've used something similar to BATV for years. But after
> >> switching my personal to a host that doesn't use this technique I have
> >> to realize just how much garbage goes flying by out there.
> >> _______________________________________________
> >> mailop mailing list
> >> email@example.com
> >> https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
> > --
> > --
> > My opinion is mine.
> > _______________________________________________
> > mailop mailing list
> > firstname.lastname@example.org
> > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
> mailop mailing list
My opinion is mine.
mailop mailing list