While we're at it, why does your server re-run its mail queue every 3 seconds
when given a 451 tempfail?
Sep 8 16:53:48 xanadu milter-greylist: k88Krlk2014120: addr 24.62.224.60 from
<[EMAIL PROTECTED]> to <[EMAIL PROTECTED]> delayed for 00:00:39
Sep 8 16:53:50 xanadu milter-greylist: k88KrntH0
Forrest Aldrich wrote:
> No, and no.
No and no to what?
Does your system show 208.39.141.86 as being listed in sorbs, despite what SORBS
says?
If not, why does forrie.com issue 550's claiming a listing in SORBS?
I can't direct-link a check to SORBS's page, but here's one at dnsstuff.com
http:/
No, and no.
I'm on Comcast - of course the IP is listed, it's dynamic duh.
Matt Kettler wrote:
> Looks like forrie needs to fix his mailserver...
>
> My server is not currently, and to my knowledge never has been, listed in any
> SORBS list. so forrie.com's MX is errantly blocking mail for
Looks like forrie needs to fix his mailserver...
My server is not currently, and to my knowledge never has been, listed in any
SORBS list. so forrie.com's MX is errantly blocking mail for IPs not listed in
sorbs.
[208.39.141.86] was not found in the SORBS database
Verified via telnet from the
Forrest Aldrich wrote:
> I've been getting these errors, not sure what to make of it - as it's
> ambiguous to me, but I'm guessing a host is not responding... ?
Possibly, or your firewall isn't configured to allow outbound razor connections,
and is generating a reset.
Razor uses tcp port 2703, a
Jordan wrote:
> Hey folks,
> We really appreciate the effort from everyone. We now have
> email.txt and are adding it to the unit tests, plus are in the
> process of fixing the bug itself (permanently this time!). Please
> be patient, and we'll roll a new release shortly.
>
Hey folks,
We really appreciate the effort from everyone. We now have
email.txt and are adding it to the unit tests, plus are in the
process of fixing the bug itself (permanently this time!). Please
be patient, and we'll roll a new release shortly.
If there are any other pro
