It appears that the file extension filter on the POP3 proxy is simply grepping for the string that is the extension, and not parsing out the filename to be sure it's looking at extensions. I just had an email snagged by the proxy because it had a file attached named "recommendation.doc" and the filter grabbed it as violating the "com" extension. I tried forwarding the message to myself (the postmaster), extracted the file and made sure it was clean, then tried to resend it to the intended recipient--it got stuffed a second time.
When I renamed the file "recs.doc" it went right on through.
I thought maybe if I put the extension into the list as ".com" instead of simply "com" it'd work, but ASL won't accept an extension with a "." in it. That wouldn't be much better anyway, since the file "my.comments.txt" wouldn't pass muster with that version. The filter really needs to make sure it's looking at the end of the filename. . .
This thread was automatically locked due to age.
