Chris Norman wrote: >> If implemented, I would vote for defining a time unit, 0 being >> disabled. >> >> In this manner, if the user wanted to allow a 72 hour "window", ASSP >> could accommodate them. >> >> Just my two cents.
I was thinking more along the lines of the standard/popular MTA retry schedules- this could be upto 6 weeks in the past. Is sending email with the date wrong by months\years wrong acceptable? I don't thinks so. If the date was checked against the first received header (to allow for delays) then this time could be much shorter- 2 or 3 days. How far in the future is can email be sent and considered valid? Most clients are sycronised against a time server and have a slop of less then 10 minutes- 30 minutes should be more than enough. Plus I was only thinking of this as another Penalty Box check like 'Failed relay' or 'Invalid Recipient'- if you don't like it just zero the score. Bro ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
