Live data from Hacker News

Show HN: SESS – Simple Email Sending Service

sess.email

11–20 of 43 posts

Re: Show HN: SESS – Simple Email Sending Service

#11

My only concern with trying this as someone just starting out with email marketing is that I don't know my SBUR rate... in fact I would assume that the first ever email to a new population (even if legitimate) is bound to have a far higher rate given errors in data collection (say collected on paper, leading to bad email addresses and bounces) and keen unsubscribers. Then I'm successfully banned and have to go to ano…

Let me rephrase your query. If you send 2 emails and 1 bounces, then your SBUR would be 50% and so will you be banned?

NO.

We predicted this would happen. The SBUR doesn't kick in for the first few thousand mails. Over time your list gets cleaner (because we keep track of bounces, unsubscribes and dont send them emails from next time on.)

(I'm one of the engineers who developed SESS.)

Re: Show HN: SESS – Simple Email Sending Service

#12
post #7

This is going to become a spamming service in 3.. 2.. How will you be dealing with that inevitable problem?

From the about page: >You are not allowed to send unsolicited emails. If your SBUR (Spam + Bounce + Unsubscribe + Reject) rate is >=5% you are automatically banned without any prior intimation.

They will need to add machine learning based classification of mails before sending them. Spammers will just create the next account until they get detected again. Their servers will be faster on a blacklist than they can spell Spamhaus.

I recommend ULMFiT [1].

[1]: http://nlp.fast.ai/classification/2018/05/15/introducting-ul...

Re: Show HN: SESS – Simple Email Sending Service

#14
post #7

This is going to become a spamming service in 3.. 2.. How will you be dealing with that inevitable problem?

Hi, im one of the engineers that built SESS. I can't get into specifics but we have a nifty little algorithm that works at multiple levels right from checking whether you have a valid business email to email list scanning to match bounces from a master bounce list etc. etc. Finally if it deems the list is risky it triggers an automatic payment refund.

Re: Show HN: SESS – Simple Email Sending Service

#16
post #10

Hi, i'm one of the engineers that made SESS.EMAIL as a side project. AMA.

Is the website not mobile friendly? It acts really wonky on my side. Firefox Beta on Android.

I must agree that we have not given particular thought to making this work on mobile. We made the assumption that people composing newsletters would mostly be working on desktops than on mobiles.

Re: Show HN: SESS – Simple Email Sending Service

#17

Earlier quoted context omitted.

From the about page: >You are not allowed to send unsolicited emails. If your SBUR (Spam + Bounce + Unsubscribe + Reject) rate is >=5% you are automatically banned without any prior intimation.

They will need to add machine learning based classification of mails before sending them. Spammers will just create the next account until they get detected again. Their servers will be faster on a blacklist than they can spell Spamhaus. I recommend ULMFiT [1]. [1]: http://nlp.fast.ai/classification/2018/05/15/introducting-ul...

Like i mentioned in an earlier comment, we have a nifty little program that checks both the validity of the business email as well as the domain. Then a sampling of the list is done to weed out troublemakers. We do a little bit more. Unfortunately i can't get into specifics here :)

Re: Show HN: SESS – Simple Email Sending Service

#18
Looks great, but email composition is only half the battle.

The page is silent on what, if anything, is being done to help deliverability. Does the site have any kind of relationship with the big ESPs? How 'clean' are the IPs right now? What, if any, mitigation is in place for the sending IPs inevitable reputation degredation? Or is a EDS being used to actually send the emails?

Re: Show HN: SESS – Simple Email Sending Service

#20
post #15

I think this is a nightmare, even sending 1000 spam mails multiple times can ruin whole IPv4 prefixes. How do you deal with that?

Hi, im one of the engineers that built SESS.

We knew we could become a potential spam magnet. Like ive been mentioning in other comments here, we have an algorithm that does checks at multiple levels before a campaign is sent. If the algorithm deems the list as risky it triggers an automatic payment refund. The algorithm is also self learning. Over time its designed to assess the risk-function of an email list. (I'm from a data science background and SESS is a side project which uses learnings we get from elsewhere).

Post reply on HN