Dnia 19.08.2024 o godz. 12:23:54 John A via mailop pisze:
> My motto that I tell my senders is "Send mail people want to people who
> want it." This should cover your personal > personal bucket ;-)
No, it won't. If you read again my messages, you would understand.
I want to emphasize it again: EV
> On 18 Aug 2024, at 19:21, Kasper Peeters via mailop wrote:
>
>> Note that this behaviour is also the correct way to handle actual spam
>> from spammers ...
>
> It may be the correct way to handle actual spam from spammers. It is arguably
> not the correct way to handle non-spam email from n
; 5. Re: [E] Yahoo 'temporarily' deferred (Jaroslaw Rafa)
> 6. Re: [E] Yahoo 'temporarily' deferred (Richard Clayton)
> 7. Re: [E] Yahoo 'temporarily' deferred (Jaroslaw Rafa)
>
>
> ----------
>
> Message: 1
> Date: Sun, 18 Aug 2024 17:24:33 +0200
> From: Jaroslaw
Dnia 19.08.2024 o godz. 01:15:04 Richard Clayton via mailop pisze:
> perhaps Google and Yahoo don't work in exactly the same way ?
>
> also you should note that although anecdotes are interesting, what MBPs
> do does change over time
My message was not about how Google and Yahoo work, and what MB
In message <20240818173004.ga27...@rafa.eu.org>, Jaroslaw Rafa via
mailop writes
>> and thereafter (at
>> Yahoo anyway) further email from that sending address will go in the
>> inbox no matter what the machine learning system thinks overall.
>
>I had that exact problem with Google once. My mess
Dnia 18.08.2024 o godz. 20:21:08 Kasper Peeters via mailop pisze:
> > Someone well respected round here advises "send email people have asked
> > for" ... those people find that in the spam folder
>
> There is one class of emails to which this logic does not apply: real
> humans sending email to o
> Note that this behaviour is also the correct way to handle actual spam
> from spammers ...
It may be the correct way to handle actual spam from spammers. It is arguably
not the correct way to handle non-spam email from non-spammers.
> Someone well respected round here advises "send email peopl
Dnia 18.08.2024 o godz. 17:59:49 Richard Clayton via mailop pisze:
> Note that this behaviour is also the correct way to handle actual spam
> from spammers ... they have never sent anything that people wanted, yet
> their mail is not so awful to be rejected out of hand so it goes into
> the spam fo
In message <20240818152433.ga27...@rafa.eu.org>, Jaroslaw Rafa via
mailop writes
>Yeah, that's the typical "dead loop" problem of mistaken spam
>classifications. Your mail gets mistakenly classified as spam, so the
>recipient doesn't see it in inbox and doesn't know the mail has arrived
>(most us
Dnia 18.08.2024 o godz. 11:28:50 Kasper Peeters via mailop pisze:
> That test message eventually made its way out of the queue (the
> "temporary" aspect of the 421 error I guess) and then went straight to
> spam in my Yahoo account... So Yahoo decides by itself that it is spam
> and then uses that
> Have you set up a test account at Yahoo, sent yourself a message, clicked
> Junk, and seen that you got the
> report?
That test message eventually made its way out of the queue (the "temporary"
aspect of the 421 error I guess) and then went straight to spam in my Yahoo
account... So Yahoo d
It appears that Kasper Peeters via mailop said:
>I understand that. I have looked carefully for any abuse (monitoring postfix
>queues, monitoring outbound port 25 traffic at an upstream router
>and things like that) but do not see anything suspicious. I'm sure a
>sufficiently determined hacker w
> First, if you have never ever gotten a single FBL message from Yahoo, that
> probably means your
> FBL isn't set up correctly.
Or it means that the volume is sufficiently low, and the senders and recipients
are sufficiently familiar with each other, that no-one ever hits the spam
button. I un
It appears that Kasper Peeters via mailop said:
>-=-=-=-=-=-
>-=-=-=-=-=-
>
>> Yahoo's FBL works on DKIM signatures. Are you 100% sure that all the mail
>> you're sending has
>> signatures from domains you've signed up to get reports?
>
>Yes, we serve 6 domains, all have correct DKIM signatures
> Yahoo's FBL works on DKIM signatures. Are you 100% sure that all the mail
> you're sending has
> signatures from domains you've signed up to get reports?
Yes, we serve 6 domains, all have correct DKIM signatures and all are enrolled
in Yahoo's FBL. Have never received a single report from the
It appears that Kasper Peeters via mailop said:
>-=-=-=-=-=-
>-=-=-=-=-=-
>
>> I would suggest that you join the Yahoo complaint Feedback loop:
>>
>> https://senders.yahooinc.com/complaint-feedback-loop/
>
>We did, for all domains served from that IP, but have so far not received a
>single messa
It appears that Viktor Dukhovni via mailop said:
>On Tue, Aug 13, 2024 at 05:40:05PM -0700, incoming-mailop--- via mailop wrote:
>
>> In our case we had a client who was repeated flagging our mailings as
>> spam. We contacted the client and all was resolved.
>
>I have distant recollection of repo
I run a small mailing list with a little over 100 users and maybe 20
messages a day. I've gotten feedback multiple times when a user marks
all their mail and hits spam instead of delete in the web interface
which typically has both side by side. Also, the feedback loop is for
more than just yah
Does the Yahoo FBL work/have value even for the tiniest of senders?
Yes, sign up for it.
It helped me catch somebody entering garbage into my email newsletter
signup form a week or two ago.
A random complaint or two is quite unexpected for me, and it turned
out that I had accidentally forgotten to
> Two comments:
>
> 1: "deferred" is not the same as "blocked"
Fair enough. An email that was stuck yesterday finally made it out after 6h in
the queue. Whether that's because I asked the Yahoo team again or because the
deferred time had expired is unclear. I have seen emails from us to yahoo g
> I would suggest that you join the Yahoo complaint Feedback loop:
>
> https://senders.yahooinc.com/complaint-feedback-loop/
We did, for all domains served from that IP, but have so far not received a
single message through this loop. So either it is like Microsoft and Google and
doesn't do any
On Tue, Aug 13, 2024 at 05:40:05PM -0700, incoming-mailop--- via mailop wrote:
> In our case we had a client who was repeated flagging our mailings as
> spam. We contacted the client and all was resolved.
I have distant recollection of reports that some users don't understand
the difference betw
On 8/13/24 1:02 PM, Kasper Peeters via mailop wrote:
[TSS05] Messages from x.x.x.x temporarily deferred due to unexpected
volume or user complaints - 4.16.55.1; see
https://postmaster.yahooinc.com/error-codes
>>>
>>> Click that link. Read through it. Open a ticket with the suppo
On Tue, Aug 13, 2024 at 1:14 PM Kasper Peeters via mailop
wrote:
> Replying to the support email about this would then resolve the issue for
> another day or so, but eventually the IP always ends up being blocked again
> with the same error message "temporarily deferred due to unexpected volume
> > > [TSS05] Messages from x.x.x.x temporarily deferred due to unexpected
> > > volume or user complaints - 4.16.55.1; see
> > > https://postmaster.yahooinc.com/error-codes
> >
> >
> > Click that link. Read through it. Open a ticket with the support team.
>
> I did that, but it doesn't s
> > [TSS05] Messages from x.x.x.x temporarily deferred due to unexpected
> > volume or user complaints - 4.16.55.1; see
> > https://postmaster.yahooinc.com/error-codes
>
>
> Click that link. Read through it. Open a ticket with the support team.
I did that, but it doesn't seem to have had any
On Mon, Jul 8, 2024 at 8:24 AM Kasper Peeters via mailop
wrote:
Is there anyone on the list who can help me get our server off the
> 'temporarily deferred' Yahoo list?
>
> [TSS05] Messages from x.x.x.x temporarily deferred due to unexpected
> volume or user complaints - 4.16.55.1; see
> https://
27 matches
Mail list logo
