On 12 Nov 2003 at 20:02, Brian Ipsen wrote: > I posted a message to the forum about this issue sunday, but haven't gotten > any response on it - so I'll try again.
Brian - Thanks for CCing me a copy of this post. I've haven't been keeping up with tmda-users lately. > I've been emailing with some SpamCop.net people, because one of my > submissions by mistake pointed my backup MX up as spam-relaying :-( > > The fuzz has been identified to be caused by the reporter.py script (which > actually also is present on SpamCop's own webpage) - because the script > masks the hostname/domain of the last mailserver, which is not allowed > according to the SpamCop-admin I was mailing with. The headers need to > remain intact - only the recipient name is allowed to be masked. <snipped> > The problem is what to do ? I think the script needs to be more or less > redesigned in order to meet the requirements I was told from > SpamCop.... I'm not a spamcop user and only added spamcop's script to tmda-cgi to appease the tmda-cgi users that do use spamcop. So I'm not real interested in mucking with their script to make sure it works correctly. If there is a bug, by all means fix it and mail me the new version to I can include it with tmda-cgi. I see that http://www.spamcop.net/reporter.py still has the same version I have, so clearly they haven't yet made any changes to prevent the situation you found. Feel free to e-mail me if they do change this. Gre7g. _____________________________________________ tmda-users mailing list ([EMAIL PROTECTED]) http://tmda.net/lists/listinfo/tmda-users
