Failed e-mail continuosly being tried to send

[zenbubbles]

I sent a message a week ago w/ an attachment that is still being tried to be
re-sent, Over 70 error messages has caused lag and has slow down any computer
application that is open. I've tried to delete the original message but still
the error keeps being sent to both the recipient and I. If there is a quick
way to solve this problem it will be greatly appreciated.

Copy of the error messages:


This is the Spam Firewall at lexluther0.pns.networktel.net.

I'm sorry to inform you that the message below could not be delivered.
When delivery was attempted, the following error was returned.


<[email protected]>: host ib.mail.pns.networktel.net[216.83.236.250] said:
552
sorry, that message size exceeds my databytes limit (#5.3.4) (in reply to
end of DATA command)

 

[OrlandoTommy]

Doesn't look like a "Outlook" issue, this looks like a firewall issue to me...

 

[Brian Tillman]

I sent a message a week ago w/ an attachment that is still being
tried to be re-sent, Over 70 error messages has caused lag and has
slow down any computer application that is open. I've tried to delete
the original message but still the error keeps being sent to both the
recipient and I. If there is a quick way to solve this problem it
will be greatly appreciated.

Copy of the error messages:


This is the Spam Firewall at lexluther0.pns.networktel.net.

I'm sorry to inform you that the message below could not be delivered.
When delivery was attempted, the following error was returned.


<[email protected]>: host ib.mail.pns.networktel.net[216.83.236.250]
said: 552
sorry, that message size exceeds my databytes limit (#5.3.4) (in
reply to end of DATA command)

This is a server-side message. Your server accepted the message and is
trying to forward it on to the recipient's mail server (I hope that's not
youre recipient's real address there. S/he'll not thank you for publishing
the address in a public forum, thereby guaranteeing viruses and spam). That
server won't accept it because it's too large. Eventually, the sending
server should give up. The default retry time is five days, so I'm unsure
why it hasn't given up yet.