I send email through cogeco and receive through my web host, but this is not something anyone can see, so how could it be confusing? The emails say they are from my domain and don't mention cogeco.
By "sending" via cogeco, cogeco's IP addresses are in the headers ... and this takes us right to your rejection notice;
bl.spamcop.net; Blocked - see http://www.spamcop.net/bl.shtml?220.127.116.11
Query bl.spamcop.net - 18.104.22.168
22.214.171.124 is smtp.cogeco.net
126.96.36.199 listed in bl.spamcop.net (127.0.0.2)
In the past week, this system has:
Been reported as a source of spam less than 10 times
Been detected sending mail to spam traps
In the past 7.8 days, it has been listed 5 times for a total of 24 hours
So please note, there is nothing there to say you or your "company" is involved in spamming, but your outgoing e-mail is going through a cogeco server that is "guilty" of sending out spam spew in addition to "your" e-mail. There is a bit of a math formula to handle the listing and delisting of an IP, and it certainly looks as if this server has been doing a bit of dancing around, apparently sending enough "non-reportable as spam" e-mail to keep dropping it off the list for a while, but sending enough bad stuff (especially note the spamtrap issues which carry a hih weighting factor in that formula) that it gets added back in every now and then.
Are these forums open so anyone can see what is written
Anyone can read, need to register to post in other than the Test Forum. But again, identifying an IP doesn't translate to "let's send this guy some spam" .... At this point, your issue seems to be cogeco's handling of their spam spew problem.
One other thing, I cannot send emails from my [myname]@cogeco.ca account either, I get the same response, so maybe it is a Cogeco thing.
As stated above, yes, a definite Cogeco issue ... but from the way you phrased that remark, does this imply that Cogeco is also hosting your web/e-mail server? If so, you've not been provided a "real" e-mail server, you're just using their resources and they're mapping your domain stuff to "your" account ... which would explain the above issues .. you're actually using a "shared" server, so your e-mail is mixed in with everyone else's ... this would explain your "no difference" statement, as it's actually the same server being used.