cronjob mailto - without SMTP?

SupermanInNY

Verified User
Joined
Sep 28, 2004
Messages
419
One of my users has set a cronjob and wants to get an email of the execution.

We have the MailTo text box, but when the user tried to get an email to their gmail, it got blocked.

0005ry-18 ** [email protected] F=<[email protected]> R=lookuphost T=remote_smtp H=gmail-smtp-in.l.google.com [108.177.15.27] X=TLS1.2:ECDHE-ECDSA-AES128-GCM-SHA256:128 CV=yes: SMTP error from remote mail server after end of data: 550-5.7.26 This mail is unauthenticated, which poses a security risk to the\n550-5.7.26 sender and Gmail users, and has been blocked. The sender must\n550-5.7.26 authenticate with at least one of SPF or DKIM. For this message,\n550-5.7.26 DKIM checks did not pass and SPF check for [server.com\n550-5.7.26 il] did not pass with ip: [1.2.3.4]. The sender should visit\n550-5.7.26 https://support.google.com/mail/answer/81126#authentication for\n550 5.7.26 instructions on setting up authentication. o13-20020adfcf0d000000b0030addea3869si1109817wrj.516 - gsmtp


I think we need to have an SMTP credential box for sending out emails at the User Level - per their own domain, so they can get their emails of cronjobs.
 
You don't reallyl need to use SMTP but the answer is in here:
he sender must\n550-5.7.26 authenticate with at least one of SPF or DKIM.
Normally DA creates SPF records by default for every domain.
So either it got deleted or something went wrong. If you have an SPF record on that domain and a correct PTR/rDNS record for the servers hostname, then Gmail will accept the mail.
It's wise to have an SPF record for the servers hostname too by the way.

Ofcourse... using SMTP is always better.
 
cronjob doesn't design for smtp authentication.
your customer can wrote script mail sender inside their application, if they want to use smtp.

but normally if you adjust spf and dkim correctly, Mail should sending.
 
cronjob doesn't design for smtp authentication.
your customer can wrote script mail sender inside their application, if they want to use smtp.

but normally if you adjust spf and dkim correctly, Mail should sending.
First, I think it would be a DA Feature to add SMTP credentials for the MailTo of the built-in DA Cronjob email notifier.
This will solve all conflicts and setups and it won't matter what SPF dkim are set incorrectly in the specific domain/server as the mail server who will send the email must be configured correctly (assuming they are not the same server).

Second, until this will be implemented,.. on this server, the client has few domains, all of them are now using CloudFlare or other DNS management outside of the DA server itself.
The client don't care for the server name, he uses it for some internal activity, yet he just wants to know when the cronjob fired (if it fired) and get notified about it.

So currently, if I understood it correctly, sadly, unless the client does a full correct configuration of the server and not a quick and dirty install, he cannot enjoy the quick testing for himself.
Is that correct?

How can we raise the option to ask DA to add this feature (with a radio button toggle to use the current setup or enable SMTP credentials fields to allow sending from external mail servers?
 
First, I think it would be a DA Feature to add SMTP credentials for the MailTo of the built-in DA Cronjob email notifier.
No that is not how cronjobs in OS work, neither any panel supports this. This would require an OS change.
Sending mailserver needs to have SPF present anyway.

So currently, if I understood it correctly, sadly, unless the client does a full correct configuration of the server and not a quick and dirty install, he cannot enjoy the quick testing for himself.
Is that correct?
To be able to send out mail, you have to obey some RFC's or your server's mail will just get blocked by many mail systems as there are too many spammers out there and protection became more important.

So yes he can do a quick and dirty install. But in that case he will not be able to send mail to Gmail, probably also not to Microsoft accounts (live, hotmail and outlook) for the same reason.

But he might get lucky and be able to get that mail send to another ISP.

I don't understand the issue. DA creates an SPF record on every domein creation by default, so 1 problem is in fact a non problem if you do a quick and dirty install. Where is that SPF record gone?
And if the server sends out mail, and you also want mail to arrive at most places, you need a valid hostname and rDNS/PTR record for it. If possible SPF too, very very very easy to do, under 5 minutes.
You can do without, but then your mail will not arrive at most places, it's as simple as that.

(with a radio button toggle to use the current setup or enable SMTP credentials fields to allow sending from external mail servers?
Check the MX page in the account, it's possible to have the server send all mail to some external party like Gmail or Office365 for example.
However... I'm not sure if that works for cronjobs too.

Or let them try and use their home isp address and see if cronjob mails get accepted there.
 
No that is not how cronjobs in OS work, neither any panel supports this. This would require an OS change.
Sending mailserver needs to have SPF present anyway.


To be able to send out mail, you have to obey some RFC's or your server's mail will just get blocked by many mail systems as there are too many spammers out there and protection became more important.

So yes he can do a quick and dirty install. But in that case he will not be able to send mail to Gmail, probably also not to Microsoft accounts (live, hotmail and outlook) for the same reason.

But he might get lucky and be able to get that mail send to another ISP.

I don't understand the issue. DA creates an SPF record on every domein creation by default, so 1 problem is in fact a non problem if you do a quick and dirty install. Where is that SPF record gone?
And if the server sends out mail, and you also want mail to arrive at most places, you need a valid hostname and rDNS/PTR record for it. If possible SPF too, very very very easy to do, under 5 minutes.
You can do without, but then your mail will not arrive at most places, it's as simple as that.


Check the MX page in the account, it's possible to have the server send all mail to some external party like Gmail or Office365 for example.
However... I'm not sure if that works for cronjobs too.

Or let them try and use their home isp address and see if cronjob mails get accepted there.
Well, here is a stupid thing.
The client reported this issue, had me running all over the place.. and now it turns out that the whole issue is due to.....

The domain he used for the host server name and namesevers..... expired.
Since he didn't use the nameservers in the server itself, it didn't affect his websites.
The domain name used for the hostname was used a long time ago,.. and he dropped it as it was of no use for him.
So this is the first time he tried to make use of the cronjob emails and that's the only time it failed to do what he needed.

Sorry for the confusion of things.
Once I tried to check his SPF records.. I found that that nothing is working on that (as the domain expired and already revoked long time ago).
 
Back
Top