554 Failed: Malformed MIME field

Discussion in 'Mail Chat' started by Mike91TT, May 30, 2011.

  1. Mike91TT

    Mike91TT VIP

    Joined:
    Apr 29, 2011
    Messages:
    300
    Likes Received:
    17
    Trophy Points:
    18
    Location:
    Los Angeles,CA
    Getting a lot of this today when reviewing bounces. Anyone able to chime in on what is causing this?
     
  2. mx10

    mx10 VIP

    Joined:
    Mar 30, 2011
    Messages:
    535
    Likes Received:
    18
    Trophy Points:
    18
    paste examples of the entire message in with all the surrounding text
     
  3. PushSend

    PushSend VIP

    Joined:
    Apr 12, 2011
    Messages:
    1,927
    Likes Received:
    141
    Trophy Points:
    63
    Location:
    Paradise
    If everything is exactly the same as a previous message to the same list, check your headers for any malformed fields. If you have none, then it could be ISP's not allowing mail to be redirected (possibly you're seeing this because of new data). Send yourself a test and check it out, it could be a bug in your platform.
     
  4. Mike91TT

    Mike91TT VIP

    Joined:
    Apr 29, 2011
    Messages:
    300
    Likes Received:
    17
    Trophy Points:
    18
    Location:
    Los Angeles,CA
    What would be considered "malformed"?
     
  5. Mike91TT

    Mike91TT VIP

    Joined:
    Apr 29, 2011
    Messages:
    300
    Likes Received:
    17
    Trophy Points:
    18
    Location:
    Los Angeles,CA
    Is it any symbols like a " - " or something in the subject line?
     
  6. PushSend

    PushSend VIP

    Joined:
    Apr 12, 2011
    Messages:
    1,927
    Likes Received:
    141
    Trophy Points:
    63
    Location:
    Paradise
    Mike, do you always send tests to yourself at seed accounts you've set up? If so, pull an email from a send that was NOT returning this code...then pull one that DID return the code. Compare the headers side by side and look for differences. What you'll be looking for is the stuff added by your platform, not input by you. A malformed time/date stamp would do it (check for strange characters in that line), stuff like that.

    If you don't send tests to yourself (and you SHOULD!) then you've got a problem on your hands. Also, I asked about the data you're sending to. Did you simply start mailing new data with a proven creative? Or did you do something to a creative and send it without testing?
     
  7. Mike91TT

    Mike91TT VIP

    Joined:
    Apr 29, 2011
    Messages:
    300
    Likes Received:
    17
    Trophy Points:
    18
    Location:
    Los Angeles,CA
    Just in case anyone who was helping me or following this thread cares, it was an @ symbol in the subject line that I stupidly didn't notice. Removed it and we're good. Thanks for the help!
     
  8. DKPMO

    DKPMO VIP

    Joined:
    Mar 31, 2011
    Messages:
    1,452
    Likes Received:
    68
    Trophy Points:
    48
    Location:
    Elaborate Underground Base
    I am not sure '@' symbol is even forbidden in your subject line, but you might have to escape it.

    Just ran a quick test sending myself a message with '@' in subject (gmail-to-gmail) and it worked fine, gmail did not even escape it.

    What domains have been giving you this error?
     
  9. Mike91TT

    Mike91TT VIP

    Joined:
    Apr 29, 2011
    Messages:
    300
    Likes Received:
    17
    Trophy Points:
    18
    Location:
    Los Angeles,CA
    Some ISPs I believe. I didn't dig too far into it, but once I removed the @ symbol, I stopped getting this error. Could it be specific to my platform?
     
  10. DKPMO

    DKPMO VIP

    Joined:
    Mar 31, 2011
    Messages:
    1,452
    Likes Received:
    68
    Trophy Points:
    48
    Location:
    Elaborate Underground Base
    Can you post any headers for the original message that was causing problems?
     

Share This Page