> > Do any of you use spamassassin with a gmail account, and if so, how are > people doing it? The reason to do this is gmail's spam filtering isn't > perfect
You can add to this, that gmail actually is also losing email and annoying is that you can't send zip files. I am constantly asking people to give me a different email address. > We built some plumbing to do this using gmail's API, and also IMAP which > can work with other services such as yahoo or outlook. I'm wondering if > this is of any use to anyone other than myself. I don't like any daemon connecting to my mail storage. Can you imagine if your solution gets hacked, how much data would be compromised? I prefer messages being scanned/marked before stored. I wonder if this is even gdpr compliant, because you can access private data constantly. > Essentially, it's a daemon that connects to the account and acts as a > mail client (an MUA). When messages arrive in a mailbox (could be any > folder really), sucks out the message, runs it through spamassassin, and > puts the result either into the Spam folder or Inbox. Why not just forward messages? Register a domain put some mx servers in front of gmails mx. I recently was testing with such relay/forward, works perfectly, I am only changing the envelope nothing else. DKIM, spf everyting perfectly working. > I'm just wondering what to do with this plumbing software, if it should > be open sourced or run as a service. Running it as a service couldn't be > free as I don't have access to free servers. So for the whole of Europe you need data processing agreement for accessing the mail storage as a 3rd party. > The daemon in it's current > state is a bit complicated to set up on it's own but it could definitely > be cleaned up, especially if there was sufficient interest. I think this design is just wrong from the start. I have sometimes that we see that clients mailboxes are accessed from the digitalocean cloud because they granted access via their phone. Especially IOS is really insecure/bad with such privacy. It is just crazy giving access to your whole mailbox for maybe a 1 time action on a incoming email. > I bet this could also be put together using getmail5 instead of this > special built daemon but that would imply polling instead of push. > Several ways to do this. > Maybe forget about this? ;)
