Andy Lyttle wrote:
Meanwhile, I'm figuring out how to strip X-UID headers. I use MIMEDefang, which is designed for cleaning up these sorts of things, but apparently it doesn't strip X-UID by default, so I'll have to add that. While I'm at it, are there any other nasty headers you can think of that I should be stripping?
I've seen spam with bogus X-UID headers creating such problems. We filter those bogus headers out with procmail/formail :0 fw * ^(X-UID|X-IMAPbase|X-IMAP|X-Status|Status|X-Keywords): | formail -IX-UID: -IX-IMAPbase: ... etc ...
Once I get that taken care of, how can I get imapd to go back to using smaller values? You mentioned "the UID regime"; what is that?
If you are using unix format, you could "sed" the X-UID headers out, imapd would regenerate them. IMAP users would see their clients re-indexing the mailbox, which should not be a problem, but POP3 clients with keep messages on server would re-download every message, creating duplicates, you might want to warn them. _______________________________________________ Imap-uw mailing list Imap-uw@u.washington.edu https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
