|
|
|
|
|
|
by ivberrOg
1074 days ago
|
|
|
I don't do it daily, but it's still often enough usage for me that having to set each one up individually would grind my gears. My own domains setup with catchalls and many custom name@ across services. I might be unusual though! |
|
|
For each organisation, project or person I interact with over email I issue a unique ${RANDOM}.${ORG}@mydomain.org across many separate domains.
Combined with procmail rules on my email server I can more easily:
1. efficiently filter and file emails into per-org, per-topic or per-project sub-directories 2. have all IMAP4 clients see the same view since filtering/filing is done server-side 3. block any addresses that receive spam without accidentally binning other email 4. know for certain there has been some kind of breach if emails arrive from another source 5. have some clients subscribed and sync-ing to only a (small) sub-set of IMAP4 folders 6. find emails related to specific orgs, projects, or people
I use Qmail's Maildir format (one file per email) on both server and Thunderbird which makes even manual 'grepping' for obscure or complex search parameters an easily scriptable operation.
I have a simple script accessible via SSH or web that adds the new entry to postfix's virtual table so unknown addresses are rejected - avoids needing to operate a catch-all policy and filter after reception since the SMTP daemon refuses delivery as soon as it sees the RCPT TO:
On the Postfix side using postgrey for grey-listing of unknown SMTP clients cuts almost all spam as well - in fact today I was surprised to see (for the first time in years) Thunderbird marking a project mail-list email as possible spam. I cannot recall the last time Thunderbird did that which I think shows how effective grey-listing on the mail server can be combined with other postfix filtering like reverse MX, SPF, DMARC, etc.