Re: [mailop] Transparency is key... Here is a perfect example.. M3AAWG is coming.. time to take a st

On 2023-05-30 at 15:13 -0700, Michael Peddemors wrote: > At least mailgun.us has transparent whois.. >(oops, careful, they might have forgotten to hide that one) .us tld does not allow the use of anonymous whois services. Still, it's possible that their registrar enabled the anonymous option

[mailop] Yahoo placement feeds?

Hi all, I've been having a really hard time getting any information on whether or not gaining access to the yahoo performance feeds they claim to offer. Is anybody from Yahoo on here that can help, or does anybody have any advice on how to get access? https://senders.yahooinc.com/email-delivera

Re: [mailop] MIME multipart/related & type argument

Dňa 11. júna 2023 11:56:00 UTC používateľ Julian Bradfield via mailop napísal: >I have valid ham messages with type="multipart/alternative" . >multipart/related type="multipart/alternative" > multipart/alternative > multipart/text plain version > multipart/html flashy version > image/... >

Re: [mailop] MIME multipart/related & type argument

On 2023-06-11, Slavko via mailop wrote: > Now i did search in both, the my MX's SPAM archive and > my own maildir. I found really small amount of multipart/related > with type= argument in my maildir, all was pointing to text/html. > I found relative many multipart/related nessages in SPAM > archi

Re: [mailop] MIME multipart/related & type argument

Dňa 11. júna 2023 9:57:25 UTC používateľ Julian Bradfield via mailop napísal: >Try reading RFC2387. Yes, your guess is right. Thanks, that was what i miss. Now i did search in both, the my MX's SPAM archive and my own maildir. I found really small amount of multipart/related with type= argumen

Re: [mailop] MIME multipart/related & type argument

On 2023-06-11, Slavko via mailop wrote: > from time to time i get SPAM with Content-Type with extra > type= argument, eg.: > > Content-Type: multipart/related; type="multipart/alternative"; ... > > I spend a lot of time to find where that type= argument is > defined. I guess, that they try do

[mailop] MIME multipart/related & type argument

Hi all, from time to time i get SPAM with Content-Type with extra type= argument, eg.: Content-Type: multipart/related; type="multipart/alternative"; ... I spend a lot of time to find where that type= argument is defined. I guess, that they try do define which nested part is "main". I creat