#24 disable/enable version functionality

v1.0.0
open
5
2008-10-07
2008-10-06
Noel
No

I am requesting there be included an option to disable senderID, or if you like to enable only SPF (v1)

The main reason for using SPF is to reject forgers, and SenderID protocol is incredibly broken when it comes to dealing with mailing lists, SPF v1 handles these fine, this would allow those of us wanting to do what SPF is intended to do, IOW, use r2 option etc to outright block, can do so without losing legitimate mail, after much google research, senderID recommends violating smtp RFCs to overcome this, this is very wrong, so a simple option allowing us control would be better, perhaps, for example it can do by default as it does now, unless we give a -1 indicating only do SPFv1, and -2 for only do SenderID.

EG- would overcome this :
This is the Postfix program at host outgoing3.securityfocus.com.I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.For further assistance, please send mail to <postmaster>If you do so, please include this problem report. You can delete your own text from the attached returned message.

The Postfix program <x@x.x>: host x.x.x[x.x.x.x] said: 550 5.7.1 Rejected due to Sender-ID policy for sender yyyy@y.y.y (in reply to end of DATA command)

Thanks
Noel

Discussion

  • Anonymous - 2008-10-07
    • milestone: --> v1.0.0
    • assigned_to: nobody --> sm-msk
     
  • Anonymous - 2008-10-16

    The attached patch adds a "-s" command line option which forces all Sender-ID test results to come back "neutral". You should, accordingly, be able to pick a "-r" setting that works for you.
    File Added: PATCH

     
  • Anonymous - 2008-10-16

    Proposed patch #1

     
  • Noel

    Noel - 2008-10-22

    Patch now in testing, thanks.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.





No, thanks