----- Original Message ----- From: "Douglas Otis" <[EMAIL PROTECTED]>
>> But for the time-shifted application, if the message reception time >> (Received: header) is used, then it shouldn't matter. > > When verification occurs at the MUA, the key must remain available > _beyond_ the SMTP transport period. Agreed. Of course, the further away you are from real time, the higher the potential for failure. This is par for the course with time-shifted applications for DKIM. Unless it has help from the backend server, offline mail systems will not work very reliably when keys are being changed. The only way I see to reduced this is to increase the frequency of your pickup times so that is closer to real time. At pickup, the DKIM plug-ins do their work. So even if you are away on vacation, your computer is still on and doing its mail pickup. But the more you shift/delay your verification time, the more you get away from the real time dynamics of the system and you have more potential failure. -- Hector Santos, Santronics Software, Inc. http://www.santronics.com _______________________________________________ NOTE WELL: This list operates according to http://mipassoc.org/dkim/ietf-list-rules.html
