Is this problem the fault of the sender or the receiver???

[goombawaho]

I'm arguing it's the sender for sending an incorrect/unsupported format in the automated message. Since it's doesn't conform to one of the RFCs, our server is rightly rejecting it. Our mail is hosted by Network Solutions.
Names have been changed to protect the moronic and for comic effect

From: System Administrator
Sent: Monday, March 15, 2010 10:51 AM
To: Pimplyho, Cyncity
Subject: Undeliverable: Electronic Payment Notification

Your message did not reach some or all of the intended recipients.

Subject: Electronic Payment Notification

Sent: 3/15/2010 10:51 AM

The following recipient(s) cannot be reached:

slurpmedown@construction.com on 3/15/2010 10:51 AM

The message contains a content type that is not supported

<cle1smtpgw01.senderdomainname.enterprise.local #5.6.0 smtp;550 5.6.0 Lone CR or LF in body (see RFC2822 section 2.3)>

 

[58sniper]

Pimplyho - HA!

I'd say it's a sender problem. Not sure I'd bounce on it, but....

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[goombawaho]

Here's the problem, as usual. The sender thinks it's the receiver's fault for rejecting the message. The receiver is a small company using network solutions mail and Outlook. The sender is a bigger company that I don't have any info on yet in terms of mail system.

How do I approach this rather than finger-pointing? I'm trying to figure out whether to talk to Network Solutions first as a representative of the receiving party or talk to the IT department of the bigger company/sender.

Any advice appreciated. Actually, that "nickname" is close to the real name, but I didn't want to leave it there.

 

[58sniper]

Point at the RFC. You don't have to accept the message if it violates the RFC. Many companies would accept it, but you don't have to. You could really dig through some other RFCs and probably find more that they aren't adhering to.

Pat Richard MVP
Plan for performance, and capacity takes care of itself. Plan for capacity, and suffer poor performance.

http://www.ucblogs.net/blogs/exchange/

 

[goombawaho]

Yeah - that's the way I was approaching it: "It's not us, your server is sending something that we technically SHOULD REFUSE since it doesn't comply".

We'll see what they say. The main problem is that the small company has to pay me by the hour while the big company (sender) has IT staff. It's pretty crappy of the big company not to investigate this themselves since they have the (free) resources.

 

[tlcscousin]

Unfortunately the big company can afford to lose the business of the small company however the small company cant afford to lose the business of big company.
Which would almost force them to accept the email regardless of following proper RFC or not, if they want to do business with them.

 

[goombawaho]

How am I going to force Network Solutions email to accept that email if it is violating the RFC???? Do you think if I called them up on behalf of the small company that uses NetSol email that they would make a change????? I'm doubting it, but what do you think.

The message is an automated message sent by and account with a PDF attached, but there's nothing in the email when they send it SUCCESSFULLY" to my email. Interesting.

I'm pretty sure the fault lies with the sender, but how to make them act on it....................