We're an anti-spam company that combines a few tools for users:
whitelist/blacklist, some social-networking leveraging, spam filtering,
customization options, in-place IMAP filtering, integration with
Yahoo/GMail/domains hosted by Google Apps, etc. We do SPF checking on
all identities present in
9/7/6 :
>>
>>> Just wanted to say thanks for the jSPF release... We've deployed the
>>> update
>>> and it's been working smoothly. Thanks for the fix, -Casey
>>>
>>> [email protected] wrote:
>>>
>>>&g
wrote:
Hi - just checking in about JSPF-72... I understand it was fixed, or close
to being fixed, and folks had graciously stepped up to do a release with
that fix... I couldn't tell from the recent messages on this list if there
was still momentum for that, if the the recent commits ar
@caseyconnor.org wrote:
>>
>> Hi - just checking in about JSPF-72... I understand it was fixed, or close
>> to being fixed, and folks had graciously stepped up to do a release with
>> that fix... I couldn't tell from the recent messages on this list if there
>> was s
Just wanted to say thanks for the jSPF release... We've deployed the
update and it's been working smoothly. Thanks for the fix, -Casey
[email protected] wrote:
Hi - just checking in about JSPF-72... I understand it was fixed, or
close to being fixed, and folks had graciously
I will hopefully find some time this weekend to publish a RC.
Bye,
Norman
2009/6/12 Stefano Bagnara :
> [email protected] ha scritto:
>> Hi - just checking in about JSPF-72... I understand it was fixed, or
>> close to being fixed, and folks had graciously stepped up to do a
[email protected] ha scritto:
> Hi - just checking in about JSPF-72... I understand it was fixed, or
> close to being fixed, and folks had graciously stepped up to do a
> release with that fix... I couldn't tell from the recent messages on
> this list if there was still mome
Hi - just checking in about JSPF-72... I understand it was fixed, or
close to being fixed, and folks had graciously stepped up to do a
release with that fix... I couldn't tell from the recent messages on
this list if there was still momentum for that, if the the recent
commits are all bui
[
https://issues.apache.org/jira/browse/JSPF-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara updated JSPF-72:
Priority: Critical (was: Major)
> Parsing errors for TXT reco
[
https://issues.apache.org/jira/browse/JSPF-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara resolved JSPF-72.
-
Resolution: Fixed
I found that the issue was better solved in the xbill resolver and not in the
[
https://issues.apache.org/jira/browse/JSPF-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefano Bagnara reassigned JSPF-72:
---
Assignee: Stefano Bagnara
> Parsing errors for TXT reco
[
https://issues.apache.org/jira/browse/JSPF-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714386#action_12714386
]
Stefano Bagnara commented on JSPF-72:
-
The problematic code is in
resolver/src/main/
[
https://issues.apache.org/jira/browse/JSPF-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12714383#action_12714383
]
Stefano Bagnara commented on JSPF-72:
-
Confirmed as a bug. Here is the rele
Parsing errors for TXT records
--
Key: JSPF-72
URL: https://issues.apache.org/jira/browse/JSPF-72
Project: JAMES jSPF
Issue Type: Bug
Components: Parser
Affects Versions: 0.9.6, 0.9.7
14 matches
Mail list logo
