There's a better way to do what you're thinking. If I were following the instructions on the link, I'd probably tweak the gmail filter so it would only forward mail sent "To: user@domain.com", give it a tag, and archive it.
In fact, there are several ways without being a mail server admin. You could set it up so gmail takes email for user@domain and forwards it to user+key@domain... and use two .forwards (regular ".forward" and a ".forward+key"), though I'm not sure about the precidence of the + operator and .forward files. I've seen people do something like that with spamassassin before.
You could also make procmail add a new header the first time it comes through, and if it's got the header it goes to your mailbox. Procmail is a wonderful thing. Hugely versitile.
There are several other ways of doing it, I'm sure. Geeks are generally good about sharing their ideas.
Daniel Miessler
· 3 years ago
I've actually already experimented with the headers method using maildrop and wasn't successful after trying a couple of different things. I may give that another shot, though.
The multiple user-side filter files isn't an approach I think I'd like to take, but it's an interesting idea.
All Comments
In fact, there are several ways without being a mail server admin. You could set it up so gmail takes email for user@domain and forwards it to user+key@domain... and use two .forwards (regular ".forward" and a ".forward+key"), though I'm not sure about the precidence of the + operator and .forward files. I've seen people do something like that with spamassassin before.
You could also make procmail add a new header the first time it comes through, and if it's got the header it goes to your mailbox. Procmail is a wonderful thing. Hugely versitile.
There are several other ways of doing it, I'm sure. Geeks are generally good about sharing their ideas.
The multiple user-side filter files isn't an approach I think I'd like to take, but it's an interesting idea.
Thanks for the comment.