Post by @andyc

I have conquered today's mission of getting #LittleFedi to send email notifications. Took another 3 hours and I couldn't possibly document the process or hope to reproduce it in a clean environment but still.

Replying to @andyc
Paul Wilde
@paul @paulwilde.uk

@andyc@yakshaving.social
What sort of barriers did you come across? Out of interest. I've heard of a few people having issues here.

Admittedly I have my own mail server, and I've just configured littleFedi to send to that, and it's only sending internally to that server so the whole thing was a breeze. Though that server itself can send publicly via a relayhost (which I also run) if I need it to, so that would work also.

Replying to @paul@paulwilde.uk
andyc
@andyc
Unlisted en edited

@paul@paulwilde.uk How long have you got ? :-)

I was trying to lazily and quickly relay to Gmail's SMTP server (which is what my NAS does). That had a load of security related problems so then I used msmtp which worked standalone (also to perform the same relay). That also had a load of different issues - permissions on the local/global msmtp configuration file, accessing the logs etc etc. Rinse and repeat.

Plus I used Gemini so clearly my endless hours of frustration and irritation was perhaps a right and fitting punishment but I'm a persistent old git !

Replying to @andyc
Paul Wilde
@paul @paulwilde.uk

@andyc@yakshaving.social
Ah, I see how that can be tricky.
I too am an old git, a pedantic one though and generally of the opinion that we should let mail servers be mail servers and anything else I.e. webservers, should hand over to them before exiting to the wider internet. Sadly things like google and Microsoft etc. have made this more of a hassle than it needs to be with their additional authentication processes.