#swaks — Public Fediverse posts

Warum kannte ich bis heute #swaks nicht? Das SWiss Army Knife for Smtp? Das ist mal ein Output, mit dem man Fehler suchen kann:

root@brick ~ [28]# swaks --from [email protected] --to [email protected] --server mx.hardbeerpunk.de: --auth --auth-user [email protected] --auth-password stregngeheim --port 587 -tls
=== Trying mx.hardbeerpunk.de::587...
=== Connected to mx.hardbeerpunk.de:.
<- 220 mx.hardbeerpunk.de ESMTP OpenSMTPD
-> EHLO brick
<- 250-mx.hardbeerpunk.de Hello brick [116.203.65.161], pleased to meet you
<- 250-8BITMIME
<- 250-ENHANCEDSTATUSCODES
<- 250-SIZE 36700160
<- 250-DSN
<- 250-STARTTLS
<- 250 HELP
-> STARTTLS
<- 220 2.0.0 Ready to start TLS
=== TLS started with cipher TLSv1.3:TLS_AES_256_GCM_SHA384:256
=== TLS client certificate not requested and not sent
=== TLS no client certificate set
=== TLS peer[0] subject=[/CN=mx.hardbeerpunk.de]
=== commonName=[mx.hardbeerpunk.de], subjectAltName=[DNS:imap.hardbeerpunk.de, DNS:mail.hardbeerpunk.de, DNS:mx.hardbeerpunk.de, DNS:smtp.hardbeerpunk.de] notAfter=[2026-01-14T10:21:11Z]
=== TLS peer[1] subject=[/C=US/O=Let's Encrypt/CN=E7]
=== commonName=[E7], subjectAltName=[] notAfter=[2027-03-12T23:59:59Z]
=== TLS peer certificate passed CA verification, failed host verification (using host mx.hardbeerpunk.de: to verify)
~> EHLO brick
<~ 250-mx.hardbeerpunk.de Hello brick [116.203.65.161], pleased to meet you
<~ 250-8BITMIME
<~ 250-ENHANCEDSTATUSCODES
<~ 250-SIZE 36700160
<~ 250-DSN
<~ 250-AUTH PLAIN LOGIN
<~ 250 HELP
~> AUTH LOGIN
<~ 334 VXNlcm5hbWU6
~> c3ZlbkBoYXJkYmVlcnB1bmsuZGU=
<~ 334 UGFzc3dvcmQ6
~> dGVzdDIzYXQ=
<~* 535 Authentication failed
~> AUTH PLAIN AHN2ZW5AaGFyZGJlZXJwdc5rLmRlAHRlc3AyM2F0
<~* 535 Authentication failed
*** No authentication type succeeded
~> QUIT
<~ 221 2.0.0 Bye
=== Connection closed with remote host.

Ever need to send a quick test email from the command line? Check out our guide to using Swaks, the Swiss Army Knife for SMTP - super handy for devs and email nerds.

https://www.sendamatic.net/blog/sending-test-emails-with-swaks

#EmailTesting #Swaks #DevLife

Nice, my #Brsk ISP's #CGNAT #IPv4 address is blacklisted by Spamhaus as I found out trying to test a new domain with #swaks. But delivery over #IPv6 is fine, because that's not shared with others.

Nice, my #Brsk ISP's #CGNAT #IPv4 address is blacklisted by Spamhaus as I found out trying to test a new domain with #swaks. But delivery over #IPv6 is fine, because that's not shared with others.

Nice, my #Brsk ISP's #CGNAT #IPv4 address is blacklisted by Spamhaus as I found out trying to test a new domain with #swaks. But delivery over #IPv6 is fine, because that's not shared with others.

Nice, my #Brsk ISP's #CGNAT #IPv4 address is blacklisted by Spamhaus as I found out trying to test a new domain with #swaks. But delivery over #IPv6 is fine, because that's not shared with others.

Nice, my #Brsk ISP's #CGNAT #IPv4 address is blacklisted by Spamhaus as I found out trying to test a new domain with #swaks. But delivery over #IPv6 is fine, because that's not shared with others.

Just got #tripwire set up to email me, too. What's nice is you can check your #cron files by running them as a shell script.

#selfhosting #selfhosted #exim4 #swaks (using both for this)

I've finally gotten emails to be sent from my server to myself via #exim4, a smarthost configuration, and #swaks. This page worked for me on #Mailjet, but Outlook is moving my emails to junk. I've said it's not junk, but it hasn't caught on yet. Did have to have logwatch's cron.daily thing run swaks since I can't seem to get #logwatch to email myself with my own email address properly. I had to think a lot on what to do, but this link should mostly help.

https://michael.franzl.name/blog/posts/2021-02-06-system-monitoring-using-e-mail

#Selfhosted