SanfordWhiteman

It's Sanford Whiteman actually. ("... 2" is one of my secondary accounts.)As you've discovered, even end-to-end SMTP success from one sending server (i.e. Outlook/Exchange) to the remote mailbox doesn't mean that you won't get an SMTP error from another sending server (Marketo), since servers vary...

With the upfront warnings that...[a] changing an address from an apparent typo should only be done for leads who aren't engaged; and[b] if you "fix up" user-provided input incorrectly, you may end up spamming another person... then this is quite easily automated using FlowBoost:var domainMisspelling...

Completely​ agree, Leanne... this policy shouldn't be enforced without consulting real engagement numbers. Guessing whether leads are legit can be fraught with errors.

That's a way to do it, Raymond. But you can do the same thing from the destination LP itself. (And you don't necessarily need to refresh the page after clearing the cookie, you can delete and reinsert the form. Though it's easier to refresh you should then skip the Visit Web Page for the second page...

It's certainly possible to void the cookie and create a new association based on the URL token. How are you trying to do this?

Has to be supported, otherwise the endpoint doesn't make a whole lot of sense.I'm on a plane right now so can't verify, but try lookupField:email and pass cookie: in the lead record.

"lookupField" : "cookie"No?

Yes, the cookie value is one of the possible associators (as it also is with the older syncLead/associateLead methods). It's the mkt_tok that's a newer option.

Benjamin Ortiz this may not be the best place to follow up (especially since there's no syntax highlighting here, as opposed to on Products threads).But while I wouldn't do it this way, the 10 and 336 represent, respectively, the Calendar class field HOUR (this is just a unique integer constant that...