ShareOutlook

[starship001]

We run ShareOutlook, a bolt on to MS Outlook which is an alternative to MS Exchange Server. It works by frequently sending emails back and forth between all subscribers on the network with zip attachments containing relevant updates which are then automatically processed.

It now seems that SpamCop has taken it upon itself to label these messages as spam and blacklist most of the email addresses on our network.

Does anyone know how to get round this?

[Merlyn]

We run ShareOutlook, a bolt on to MS Outlook which is an alternative to MS Exchange Server. It works by frequently sending emails back and forth between all subscribers on the network with zip attachments containing relevant updates which are then automatically processed. 

It now seems that SpamCop has taken it upon itself to label these messages as spam and blacklist most of the email addresses on our network.

Does anyone know how to get round this?

Spamcop does not label or call anything spam. Spamcop is only a list of server IP's that have been reported for spamming.

You have not left anything that could be useful to assist you.

Please post the IP number or the Blocked/Reject text you received and someone will assist.

[Spambo]

We run ShareOutlook, a bolt on to MS Outlook which is an alternative to MS Exchange Server. It works by frequently sending emails back and forth between all subscribers on the network with zip attachments containing relevant updates which are then automatically processed. 

It now seems that SpamCop has taken it upon itself to label these messages as spam and blacklist most of the email addresses on our network.

The only way that the SCBL could possibly list your IP(s) is if recipients of the emails are reporting them as spam.

Does anyone know how to get round this?

1. Ask the people on your network not to report the emails as spam.
   
2. Have your postmaster whitelist your IPs.
   

[Wazoo]

We run ShareOutlook, a bolt on to MS Outlook which is an alternative to MS Exchange Server. It works by frequently sending emails back and forth between all subscribers on the network with zip attachments containing relevant updates which are then automatically processed.

You might want to characterize your statement of "subscribers on the network" a bit more / better. Is this totally an "internal" network? If so, it appears that someone needs to have some conversations with "your netork users" ...

It now seems that SpamCop has taken it upon itself to label these messages as spam and blacklist most of the email addresses on our network.

SpamCop makes no claims or labels on content. Only those that make the decision that the e-mail is spam and take the next step of reporting it can "label" the specific e-mail. And yet, even after that is accomplished, SamCop pays no mind to e-mail addresses, instead targetting on the IP address of the source of the spew. And next, SpamCop blocks nothing, so if there is an issue of being on the BL, one would have to ask whom that might be in your case. If it's the same internal network, that would state that your own network is using the SpamCopDNSbl and blocking off various IP addresses of your own network ... this sounds odd, so perhaps you're actually talking about seeing some rejection notices from other networks that are using the SpamCopDNSbl .. it'd would help greatly to provide the contents of one of these rejection messages, as that would reflect the IP in question, who's doing the blocking, etc ...

Does anyone know how to get round this?

Either stop spamming those that don't want your exciting internal fresh e-mail with zipped attachments that automatically execute .... or train those receiving it to believe that these things aren't spam ... or possibly check that e-mail list to see if in fact all addresses are actually valid (running the possibility that these e-mails are hitting spamtraps) ...."Getting round" shouldn't be the goal, one would think that you'd actually want to "fix" the problem.