PS56k wrote:
> Precedence: bulk
That is a client added header. Your "friend" is a spammer? Some
newsletters and bulk mailers will add that header as notice that it was
sent to many recipients (even if only a single recipient was specified
in each sent copy of the bulk mail).
Just HOW did your friend send this e-mail? What client did he use? Did
he use some bulk mailing service to send many copies to a list of his
recipients? Is he using some forum that lets him, as the owner of that
forum, send out notices to his subscribers (Yahoo Groups is like that)?
I've never bothered to investigate Google Groups to know if those forums
have a similar bulk mailing aka newsletter service. (Google Groups is
both Google's own privately-owned forums along with Usenet - yeah,
Google confused the two services by using a common name.)
> Content-Disposition: inline
The sender specified to include an attachment but put it inline.
Attachments can have a disposition of "inline" (inserted within the body
of the message) or "attached" (encoded into a long string to put within
a MIME part which the receiving client should have some means of
notifying the user of an attachment). The encoding is exactly the same
for either disposition but "inline" tells the receiving client to render
the attachment within the body while "attached" tells the receiving
client to show some flag or notice about the attachment (that attachment
is not inserted into the body).
Looks like your sender tried to attach (inline) some external file
perhaps called "ltr" but it failed. Your sender was sending a bulk mail
(the Precedence header) to many recipients and using some bulk mailer
program or service that failed to insert the template file ("ltr") into
the body of the message. If the sender was not using a bulk mailing
program or a bulk mailing service, maybe he was trying to use a
mailmerge feature of Word or another application. Mailmerge is a bulk
mailing feature but not very robust (they typically spew out a copy of
each message to each recipient to deluge the SMTP server and often smack
into anti-spam quotas at the e-mail provider).
Tis also possible you sent an e-mail to someone who configured their
account to automatically reply, like a vacation responder option. The
"X-Autoreply: yes" header usually identifies an auto-responder. You
sent them an e-mail and their auto-responder sends back something like
"On vacation, back after October", or "This account no longer monitored.
Resend your e-mail to my Gmail account", or "This person no longer
employed here" (although at businesses they really should be redirecting
e-mails to another employee that assumes the duties of the ex-employee).
RFC 3834 defines the Auto-Submitted header.
https://tools.ietf.org/html/rfc3834
So it looks like you e-mailed your friend and they use an auto-responder
that screwed up by not inserting their canned response string into the
message the auto-responder sent to you.
I'm not familiar with setting up auto-responders. Since they respond to
one sender at a time (you send them an e-mail, the auto-responder sends
just *one* copy of the canned response to only you), it doesn't seem a
bulk mailing service to warrant including the "Precedence: bulk" header.
Does your friend operate or manage a bulk mailing service, like
newsletters, and you sent his account a request to opt in or opt out?
If this is just a "vacation reply" auto-responder feature of the
sender's Gmail account, I would think Google wouldn't allow enabling
their auto-responder while leaving the response string empty. I just
tried to do that in my Gmail account: enable the vacation responder
option but leave blank the response string. I got a popup saying, "You
have enabled the vacation responder but you have not provided a response
message". I was able to trick their check, however, by enabling their
auto-responder, specify a string in the Subject and response message
(body) fields, save that setup, and then go back to empty out both the
Subjec the response message fields. The auto-responder was still
enabled but it had nothing to return (the fields were blank).
Tell your friend to check the auto-responder in their Google mail
account (gmail or googlemail). However, you sent a message to your
friend that triggered getting back the blank auto-response but maybe you
didn't review your e-mails until long after you had sent an e-mail to
your friend so there was a disconnect between you sending and then
getting back the auto-response.