Unixfy

No, it doesn't.

Hi, A user of mine is attempting to register via the product order form (while ordering a service). However, when the "Submit" button is pressed, nothing happens. All of the input fields grey out for a second and then come back. In my Nginx logs, there is a POST request occurring every time the form is submitted, but no client is created. However, when I attempt to use a "Client Registration" form to register a user with debug mode on, I get an error after clicking submit: Undefined index: first_name Why is this happening? Are there any logs I can check? Thanks. EDIT: Forgot to note, I am able to successfully create a client via the admin interface.

Here's a paste of the (relevant) exim logs that they provided for me (emails and IP addresses are all anonymised): https://paste.ee/p/GhRPr#f1J0xUE7zzgbmteWWwTDsmf7kt757I98 /var/log/exim_mainlog:2017-07-17 16:25:02 H=([127.0.0.1]) [Blesta_IP_Address]:36188 X=TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128 CV=no F=<billing@example.com> A=dovecot_login:smtp-username@domain.com rejected RCPT <recipientemail@domain.com>: Sender verify failed /var/log/exim_mainlog:2017-07-17 16:26:09 H=(my.example.com) [Blesta_IP_Address]:37270 X=TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128 CV=no F=<sales@example.com> A=dovecot_login:smtp-username@domain.com rejected RCPT <recipientemail@domain.com>: Sender verify failed /var/log/exim_mainlog:2017-07-17 16:26:40 H=(my.example.com) [Blesta_IP_Address]:37450 X=TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128 CV=no F=<sales@example.com> A=dovecot_login:smtp-username@domain.com rejected RCPT <recipientemail@domain.com>: Sender verify failed /var/log/exim_mainlog:2017-07-18 10:14:06 H=(my.example.com) [Blesta_IP_Address]:48182 X=TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128 CV=no F=<billing@example.com> A=dovecot_login:smtp-username@domain.com rejected RCPT <recipientemail@domain.com>: Sender verify failed /var/log/exim_mainlog:2017-07-18 10:16:08 H=(my.example.com) [Blesta_IP_Address]:49364 X=TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128 CV=no F=<billing@example.com> A=dovecot_login:smtp-username@domain.com rejected RCPT <recipientemail@domain.com>: Sender verify failed /var/log/exim_mainlog:2017-07-18 10:38:34 H=(my.example.com) [Blesta_IP_Address]:44890 F=<billing@example.com> A=dovecot_login:smtp-username@domain.com rejected RCPT <recipientemail@domain.com>: Sender verify failed /var/log/exim_mainlog:2017-07-18 10:43:03 H=(my.example.com) [Blesta_IP_Address]:48352 F=<billing@example.com> A=dovecot_login:smtp-username@domain.com rejected RCPT <recipientemail@domain.com>: Sender verify failed /var/log/exim_mainlog:2017-07-18 10:43:22 H=(my.example.com) [Blesta_IP_Address]:37954 X=TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128 CV=no F=<billing@example.com> A=dovecot_login:smtp-username@domain.com rejected RCPT <recipientemail@domain.com>: Sender verify failed /var/log/exim_mainlog:2017-07-18 10:44:07 H=(my.example.com) [Blesta_IP_Address]:38252 X=TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128 CV=no F=<billing@example.com> A=dovecot_login:smtp-username@domain.com rejected RCPT <recipientemail@domain.com>: Sender verify failed All of those "Sender Verify Failed" errors occur when sending from the root domain. On the other hand, on any subdomain, there is no such error: /var/log/exim_mainlog:2017-07-18 11:32:30 1dXVQE-00043Y-3g <= sales@my.example.com H=(my.example.com) [Blesta_IP_Address]:38178 P=esmtpsa X=TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128 CV=no A=dovecot_login:smtp-username@domain.com S=2027 id=cca1af60f07ba5bb530da86ad7c459c4@my.example.com T="Welcome to My Company" for recipientemail@domain.com / That is probably why the errors were occurring, the incoming mail server (at the same provider) was rejecting the mails from Blesta because it couldn't verify that my Blesta install actually sent them. EDIT: Yep, the above is the case. Their cPanel server requires the email address to be created in cPanel before you can send emails from it, otherwise, you'd end up with the sender verification errors.

I tried it with ElasticEmail (another hosted SMTP service) which I already had an account with. The email sends successfully for the root domain, a nonexistent subdomain, and the Blesta install URL. The same occurs with Sendgrid and Mailgun, so we can probably narrow it down to it being my mail provider's fault. I've asked them for a copy of their recent SMTP logs for my domain (I'll get back with what they say).

I'm using SMTP, but the same issue occurs with PHP. My email is hosted at MXroute, a reputable provider that I've never had problems with (on other applications, and on a different install of Blesta on a different domain). I'll go get DKIM and SPF setup - I only have an SPF record, no DKIM. As the mail is hosted at an external provider (MXroute uses cPanel and has mail log viewing disabled as far as I know), I'm not able to see the mail server logs.

Hi, I am having an issue with Blesta where emails will fail to send if the From address is specified as the root domain. For example (assuming that the Blesta installation URL is my.example.com): From address ends in my.example.com (Blesta Installation URL): Success From address ends in 1234587421abcdefg.example.com (nonexistent subdomain): Success From address ends in example.com (root domain): Fails with "The email failed to send due to a configuration issue." Why is this happening, and how can it be corrected? Thanks!