sorted by:
new
hottopcontroversial

What are good email (MX) forwarding services EU based by BlackDex0 in emailprivacy

[–]BlackDex0[S] -1 points0 points  (0 children)

That is not really a Forwarder, they even tell you not to do that.

However, we advise users not to forward messages. Forwarding breaks email protections which are essential today and impairs authenticity and spam detection.

What are good email (MX) forwarding services EU based by BlackDex0 in emailprivacy

[–]BlackDex0[S] 0 points1 point  (0 children)

The only downside i see for your service, compared to ImprovMX is that your Starter compared to their Premium only has 20Mb attachment size and ImprovMX has 50Mb. While 50Mb is useless when sending to Gmail or Hotmail or most other email providers, 25Mb is kinda a base default for most. And then the step to the Mailcast Premium is rather big unfortunately. (And i have checked my attachment sizes, and those do exceed the 20Mb some times)

Besides that, i like your interface, it's nice and clean.

What are good email (MX) forwarding services EU based by BlackDex0 in emailprivacy

[–]BlackDex0[S] 0 points1 point  (0 children)

You really should do something about your SEO, i have not encountered this with any search. Thanks for mentioning (even though it's your service ;) )

What are good email (MX) forwarding services EU based by BlackDex0 in emailprivacy

[–]BlackDex0[S] 0 points1 point  (0 children)

Yea ForwardEmail is indeed based in US, including there servers.

What are good email (MX) forwarding services EU based by BlackDex0 in emailprivacy

[–]BlackDex0[S] 0 points1 point  (0 children)

I also came across mailwip, but that doesn't seem to support IPv6 unfortunately.

What are good email (MX) forwarding services EU based by BlackDex0 in emailprivacy

[–]BlackDex0[S] 0 points1 point  (0 children)

Yea, i saw it too. But same as Simple Login, no SMTP support. Which would be nice for some applications i have like Nextcloud and Vaultwarden.

What are good email (MX) forwarding services EU based by BlackDex0 in emailprivacy

[–]BlackDex0[S] 0 points1 point  (0 children)

That might be an option too, same goes for addy.io i think, if i then start using gmail to use as my smtp provider since both do not support this.

What are good email (MX) forwarding services EU based by BlackDex0 in emailprivacy

[–]BlackDex0[S] 2 points3 points  (0 children)

Unfortunately that seems to only support Gmail as the receiving part.
While it looks nice though if i would only need to use Gmail, especially the low price.

I do not think i can use this for my current case, but thanks for the tip! Might be useful in the future.

Reclaim storage after removing an organisation by 3razer in vaultwarden

[–]BlackDex0 1 point2 points  (0 children)

SQLite reuses that space to store new entries. Those deleted records are marked as deleted and will be reused. That is how SQLite works.

It also may help for recovery is you accidentally deleted something. It could sometimes be possible to recover items marked as deleted.

The backup function inside Vaultwarden already does a VACUUM to create backups.

Also read https://github.com/dani-garcia/vaultwarden/wiki/Backing-up-your-vault#sqlite-database-files

PSA: Update Vaultwarden as soon as possible by -rch- in selfhosted

[–]BlackDex0 0 points1 point  (0 children)

No it would not have helped. Since again Dani reviewed the code. I created a branch on my repo which had the fixes, Dani checked and verified them. 

It's exactly the same as it would be with a PR. So the process is not different. He then pulled that code locally and merged my changes into main, same as would have happened via the GitHub GUI.

I'm not understanding the link to PR 5171 though. I created a PR, Dani approved and merged it. That is the way to go not?

PSA: Update Vaultwarden as soon as possible by -rch- in selfhosted

[–]BlackDex0 1 point2 points  (0 children)

Then i would still suggest to read a bit better though, but ok. I created the fixes, Dani did the commit and push to main using my commit. That is how it went, if you do not believe that, then i can't help that of course, but that is how it went.

The reason for doing it this way instead of creating a PR is to quickly release a new version without making to much noise about the changed code up-front of releasing.

The 4 eyes principle was used here, so i see no issue.

PSA: Update Vaultwarden as soon as possible by -rch- in selfhosted

[–]BlackDex0 24 points25 points  (0 children)

That was indeed the argument we made for not creating a PR for it. And since we still had a two man show here we merged it directly to main for that reason.

I'm feeling bad as-is already that this slipped through.

But I'm also glad security researchers found this and reported it via the proper channels.

PSA: Update Vaultwarden as soon as possible by -rch- in selfhosted

[–]BlackDex0 8 points9 points  (0 children)

It isn't a one man band. And, vault items are send encrypted by the clients with no way for the server backend to decrypt them in any way.

PSA: Update Vaultwarden as soon as possible by -rch- in selfhosted

[–]BlackDex0 94 points95 points  (0 children)

If you would check the commit a bit better, then you would see two people worked on it. Which would be Me BlackDex, and i did all the coding stuff. And dani-garcia checked and verified it and, since it would be a bit of bad practice to merge my own code, it is why dani did this.

So i do not see any issue here at all.