I talked to Justin and he is not aware of a SurfNet machine. They are a
targeted sponsor who has helped us. I've sent one email seeing if I can
dig anything up but I must concur.
Dave's research shows that "trap-proc.spamassassin.org and
spam-upload.spamassassin.org both resolve to
Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY
http://sa-update.dnswl.org/ (78.47.167.123): UP (CURRENT)
http://www.sa-update.pccc.com/ (69.171.29.39): UP (CURRENT)
http://sa-update.secnap.net/ (204.89.241.6): UP (CURRENT)
http://sa-update.space-pro.be/
+ promote_active_rules
+ pwd
+ /usr/bin/perl build/mkupdates/listpromotable
/usr/local/spamassassin/automc/svn/trunk
HTTP get: http://ruleqa.spamassassin.org/1-days-ago?xml=1
HTTP get: http://ruleqa.spamassassin.org/2-days-ago?xml=1
HTTP get: http://ruleqa.spamassassin.org/3-days-ago?xml=1
+ mv
On 01/17/2018 08:13 AM, Kevin A. McGrail wrote:
> 2 - [Joe, can you help?] Find out what Sonic is trapping and where
> they are sending it.
Our setup was/is as follows:
- a server running qsmtpd and a customized version of sendmail is at
mailin.sonic.net (157.131.0.10)
- the messages that hit
Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY
http://sa-update.dnswl.org/ (78.47.167.123): UP (CURRENT)
http://www.sa-update.pccc.com/ (69.171.29.39): UP (CURRENT)
http://sa-update.secnap.net/ (204.89.241.6): UP (CURRENT)
http://sa-update.space-pro.be/
Fetching sa-update URLs from http://spamassassin.apache.org/updates/MIRRORED.BY
http://sa-update.dnswl.org/ (78.47.167.123): UP (CURRENT)
http://www.sa-update.pccc.com/ (69.171.29.39): UP (CURRENT)
http://sa-update.secnap.net/ (204.89.241.6): UP (CURRENT)
http://sa-update.space-pro.be/
