Re: [mailop] Microsoft Contact

I’d suggest either not repeating the email address twice, or wrapping the first instance in quotes? Aloha, Michael. -- Michael J Wise Microsoft Corporation| Spam Analysis "Your Spam Specimen Has Been Processed." Got the Junk Mail Reporting

Re: [mailop] Microsoft Contact

> On Apr 30, 2018, at 2:28 PM, Rob Heilman via mailop wrote: > > We appear to be having issues with the way Microsoft’s systems are parsing > headers. In particular headers using display-name strings containing the @ > symbol. For example: > > From: sen...@domain.net

Re: [mailop] Microsoft Contact

We appear to be having issues with the way Microsoft’s systems are parsing headers. In particular headers using display-name strings containing the @ symbol. For example: From: sen...@domain.net To: recipie...@gmail.com , recipie...@hotmail.com

Re: [mailop] CheetahMail for Allegiant Airlines marketing, badly formed messages.

I think the complaining about excessive X-headers is overblown. It's not harming anything. Google adds more meat than that nowadays with ARC, multiple DKIM signatures, authentication results, etc. Message headers ain't going to get any smaller, best to learn how to deal with them. Be liberal in

Re: [mailop] CheetahMail for Allegiant Airlines marketing, badly formed messages.

From what I recall (and I may be wrong) isn't it more along the lines of only one SHOULD be added?And, if you see Envelope From headers in inbound mail streams for which you are the final destination then you MAY replace/rewrite them. Apologies if I have misunderstood what you are saying. Ken. 

Re: [mailop] CheetahMail for Allegiant Airlines marketing, badly formed messages.

Hi, Michael, Thanks for the heads up, we'll take a look at the points you've brought up. I'll pm you w/ anything further. Thanks John On Mon, Apr 30, 2018 at 2:02 PM, Michael Peddemors wrote: > For the record, and a reminder to others.. > > RFC says that the

[mailop] CheetahMail for Allegiant Airlines marketing, badly formed messages.

For the record, and a reminder to others.. RFC says that the 'Return-Path', eg EnvelopeFrom should ONLY be added at the final destination.. Emails are being sent with existing Return-Path headers.. meaning they are added incorrectly for the mailing lists. It should be pointed out that a

Re: [mailop] Migrating to new IPs?

Hi Rob, On Mon, 2018-04-30 at 09:35 -0600, Rob Nagler wrote: > Is there a way to "pre-register" IPs in preparation for a data center > move? There's been some discussion this list, but I didn't get a sense of > a definitive answer.  Not really. There's no definitive central source for recording

[mailop] Migrating to new IPs?

Is there a way to "pre-register" IPs in preparation for a data center move? There's been some discussion this list, but I didn't get a sense of a definitive answer. We have held the new IPs (216.17.132.32/27) for many months. The old IPs have been in use by us for two decades for a handful of

Re: [mailop] Hotmail ticket/help for senders link down?

Smells like an internet routing issue to me. If you're on your work VPN, I'd try turning it off for a minute (or trying the URL from your non-work computer). Or vise-versa if you're not on a VPN. On Mon, Apr 30, 2018 at 10:00 AM, Annalivia Ford wrote: > That's

Re: [mailop] Hotmail ticket/help for senders link down?

That's interestingfor me it's 100% down, doesn't matter what browser I use. My colleague was able to load it and submit a ticket once, today, but not since. The rest of my team is not able to load it either. (45 mins later) It's coming and going now. Thanks for getting back to me, I just

Re: [mailop] Hotmail ticket/help for senders link down?

It is loading for me, as well. Cheers, Al Iverson On Mon, Apr 30, 2018 at 9:04 AM, Benjamin BILLON wrote: > Right now it's ok for me > > > > -- > > Benjamin Billon > > > > From: mailop On Behalf Of Annalivia Ford > Sent: Monday, 30 April, 2018