I'm seeing this as well and it is becoming a serious problem...
If SpamGourmet rejects an incoming email, it returns a message to the sender referring to
http://www.spamgourmet.com/dynamic.html. This may be OK for technical users but small businesses (which are more likely to be using email servers lacking a "proper" reverse DNS) are likely to have difficulties with it (one did in my case, though I was able to provide detailed guidance based on a previous email they sent).
However when an email is sent by an automated system, this response does no good whatsoever and the Spamgourmet user is powerless to do anything to identify, let alone fix, the cause.
I have so far not received multiple password resets from eBay (they say they sent 3 which I didn't receive - a fourth from mx30.sjc.ebay.com (mxpool14.ebay.com [66.135.197.20]) got through so it seems likely that SG blocked the others) and registration/password resets from 2 forums (
Hexus and
XtremeSystems, mail servers unknown since I've not received any email from them).
Given the choice between reliability and speed, I would vote for reliability, hands down. I know I have posted about slow deliveries in the past, but I would far prefer that to the current uncertainty of not knowing if a missing email was due to SG.
As such, I would ask that the existing filtering be revised to minimise the chance of blocking legitimate senders. There are clearly several ways of doing this (IP/subnet blocklists based on past abuse,
SpamHaus' PBL blocklist) but the existing method, for me, is harming SG's usability in a way that nothing else has.
The "dynamic.html" page could also be improved (for human senders) by placing the necessary "fix" at the top and leaving the explanation at the bottom, plus including a webform to allow a human sender to contact the SG user directly (for cases where they really don't know what to do - limiting it to existing SG aliases only and having a CAPTCHA should prevent spambot abuse).