GSoC project - Implement module to process ARC headers
Hi!
I'm sorry that I haven't responded before, it's been very busy catching up to $DAYJOB since getting back.
I don't understand what you're worried about. Of course if you change all the names, especially with some sort of automatic process, there's a pretty good chance of introducing typos. We fix them as we find them, that's all.
The way I can think of doing this is to grep all files and change the names and then clear all the cache files.
Do you mean __pycache__? That will happen automatically for all files with updated API calls. If you haven't updated the source to use the changed API, the calls will break anyway. The only time this is a worry is if you repurpose an existing name to different semantics, and the answer there is "don't do that," because it's problematic anyway. But these will be new names, so shouldn't cause that kind of problem.
Re interop:
I have a server with a fixed IP which could just pipe mail to a Python script that reads it and passes the message to the ARC module for processing. Then the script can send it back out if necessary.
Yes, I went ahead and made the changes. I have a separate module 'arcpy' installed in my python dist-packages now which is basically the refactored 'dkimpy' package. I don't think its the best of names since it doesn't give the idea of presence of DKIM signing/verifying features. Any ideas for the same?
I have a server with a fixed IP which could just pipe mail to a Python
script that reads it and passes the message to the ARC module for processing. Then the script can send it back out if necessary.
That should work for us! Also we would need to have a DMARC and DKIM record set up though for the signing domain. The procedures for that are easy, and are outlined in detail on the net. So if we have a domain name associated with the ip, I'll go ahead and make the TXT records. Else, we'll have to create a new one. I'm not aware of any way to avoid this. Let me know if you are aware of any :)
Aditya
Yes, I went ahead and made the changes. I have a separate module 'arcpy' installed in my python dist-packages now which is basically the refactored 'dkimpy' package. I don't think its the best of names since it doesn't give the idea of presence of DKIM signing/verifying features. Any ideas for the same?
I have a server with a fixed IP which could just pipe mail to a Python
script that reads it and passes the message to the ARC module for processing. Then the script can send it back out if necessary.
That should work for us! Also we would need to have a DMARC and DKIM record set up though for the signing domain. The procedures for that are easy, and are outlined in detail on the net. So if we have a domain name associated with the ip, I'll go ahead and make the TXT records. Else, we'll have to create a new one. I'm not aware of any way to avoid this. Let me know if you are aware of any :)
Aditya
participants (2)
-
Aditya Divekar -
Stephen J. Turnbull