Re: [mailop] crippling gmail rate limit

2015-12-11 Thread John Levine
In article <01d13493$6df98140$49ec83c0$@iname.com> you write: >I'd recommend that rather than forward messages to Google that you have >those Google accounts POP the messages from smokva.net. What I do is to run them through spamassassin, forward the ones with a low spam score so they get ther

Re: [mailop] crippling gmail rate limit

2015-12-11 Thread frnkblk
I'd recommend that rather than forward messages to Google that you have those Google accounts POP the messages from smokva.net. Frank -Original Message- From: mailop [mailto:mailop-boun...@mailop.org] On Behalf Of Petar Bogdanovic Sent: Thursday, December 10, 2015 9:44 AM To: mailop@mailo

Re: [mailop] Delivery to gmail via IPv6

2015-12-11 Thread Franck Martin
On Fri, Dec 11, 2015 at 3:59 AM, David Hofstee wrote: > That’s why, in ESP parlance, there are two sorts of bounces, to keep it > simple: > > - Hardbounces: The recipient address does not work. Contact > through other means. > > - Softbounces: This email did not arrive. Try agai

Re: [mailop] Delivery to gmail via IPv6

2015-12-11 Thread Steve Atkins
> On Dec 11, 2015, at 6:06 AM, Ian Eiloart wrote: > > I wonder why they don’t use the terminology from the RFCs: "reject", "defer", > "non-delivery notification", "delay notification"? > > As it is, when you say "Hardbounce", I don’t know whether you’re referring to > an SMTP 5yz reply (a re

Re: [mailop] Delivery to gmail via IPv6

2015-12-11 Thread David Hofstee
Hi Ian, So ESP parlance, 'a particular manner of speaking', is not RFC parlance. That part is true. We have to explain our customers, who are not techies, what is going on with their mails. We either say that the mail is delivered or bounced (=did not arrive in ESP parlance). And if it bounced,

Re: [mailop] Delivery to gmail via IPv6

2015-12-11 Thread Ian Eiloart
I wonder why they don’t use the terminology from the RFCs: "reject", "defer", "non-delivery notification", "delay notification"? As it is, when you say "Hardbounce", I don’t know whether you’re referring to an SMTP 5yz reply (a rejection) by the receiving MTA or an rfc 3461 "failed" DSN sent t

Re: [mailop] Delivery to gmail via IPv6

2015-12-11 Thread David Hofstee
That’s why, in ESP parlance, there are two sorts of bounces, to keep it simple: - Hardbounces: The recipient address does not work. Contact through other means. - Softbounces: This email did not arrive. Try again later or contact through other means. If this keeps happening t

Re: [mailop] Delivery to gmail via IPv6

2015-12-11 Thread Ian Eiloart
> On 10 Dec 2015, at 18:43, Franck Martin wrote: > > It also has to do with people not understanding DSN. Seriously they are ugly > and hard to find the relevant information in them... Agreed, but if the recipient doesn’t understand the message, and doesn’t act on it, then it doesn’t matter w

Re: [mailop] Delivery to gmail via IPv6

2015-12-11 Thread Gil Bahat
Also bounce.io , but these are very bad services. They bounce to the reply to, not bounce address: former is likely monitored, latter is likely automated removal. On Dec 11, 2015 10:40 AM, "Franck Martin" wrote: > There a whole business, https://betterbounces.net, based on rewriting the > NDR int

Re: [mailop] Delivery to gmail via IPv6

2015-12-11 Thread Franck Martin
There a whole business, https://betterbounces.net, based on rewriting the NDR into something any user can read, with a meaningful call to action. I love the technical info too, but as Brandon said, it could be later in the email. On Thu, Dec 10, 2015 at 1:23 PM, Brandon Long wrote: > I was just