4 ms·
Our company is the owner of kamer.nl (kamer=room/chamber) and our government in the Netherlands has a first and second chamber (eerstekamer and tweedekamer) as
by bartkappenburg 5y ago
Our company is the owner of kamer.nl (kamer=room/chamber) and our government in the Netherlands has a first and second chamber (eerstekamer and tweedekamer) as a parallel to Congress/House of Commons.
We're getting a lot of emails (due to a catch-all) because politicians type foo@tweede.kamer.nl, foo@eerste.kamer.nl or just plain foo@kamer.nl instead the correct foo@tweedekamer.nl or foo@eerstekamer.nl.
It does sometimes contain some privacy-sensitive information and we always reply and point them to the mistake. We do this because hopefully they learn (most do...) and they can get the information to the right person.
- gnyman 5y agoout of curiosity, why do you maintain a catch all? would it not be easier (and less of a privacy issue) to just reject them outright?
- bartkappenburg 5y agoIt has a business reason: we let customers email each other on an anonymized email address ($hash@kamer.nl) to keep their info private. I know the structure of the hash (length etc) but no clue how to filter on the mail-server side using this characteristic, that’s why a catch-all. We’re thinking of sunsetting the feature and that would mean that a catch-all won’t be necessary anymore :-)