Linux - SecurityThis forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It seems like the email labyrinth is never ending! I have a host on a subdomain: host.ohprs.org. I tried sending a test message from a user on this host to my gmail account. I got bounced the following rejection:
Code:
----- The following addresses had permanent fatal errors -----
<mercureytech@gmail.com>
(reason: 550-5.7.26 This mail has been blocked because the sender is unauthenticated.)
----- Transcript of session follows -----
... while talking to gmail-smtp-in.l.google.com.:
>>> DATA
<<< 550-5.7.26 This mail has been blocked because the sender is unauthenticated.
<<< 550-5.7.26 Gmail requires all senders to authenticate with either SPF or DKIM.
<<< 550-5.7.26
<<< 550-5.7.26 Authentication results:
<<< 550-5.7.26 DKIM = did not pass
<<< 550-5.7.26 SPF [ohprs.org] with ip: [24.142.169.13] = did not pass
<<< 550-5.7.26
<<< 550-5.7.26 To mitigate this issue, please visit Gmail's authentication guide
<<< 550-5.7.26 for instructions on setting up authentication:
<<< 550 5.7.26 https://support.google.com/mail/answer/81126#authentication g8-20020ac87f48000000b00419544d589bsi3213665qtk.743 - gsmtp
554 5.0.0 Service unavailable
This says specifically "SPF [ohprs.org] with ip: [24.142.169.13] = did not pass", yet the SPF record for ohprs.org is:
Doh! That did it! You're a life saver. I've used ip4: before, but for some reason I thought include: and ipv4: were synonyms, But no. Using ipv4: did the trick.
Doh! That did it! You're a life saver. I've used ip4: before, but for some reason I thought include: and ipv4: were synonyms, But no. Using ipv4: did the trick.
They are not the same.
You use include if you're going to use a third party to send out email for your domain. So for example in your case you include spf.protection.outlook.com meaning that any of the following IP addresses are allowed to send email for your domain:
They are not the same.
You use include if you're going to use a third party to send out email for your domain. So for example in your case you include spf.protection.outlook.com meaning that any of the following IP addresses are allowed to send email for your domain:
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.