SOLVED How to make my VM and Fax to Email work

C

cporantes

Member
Joined
Jun 23, 2020
Messages
83
Reaction score
8
I searched Google, Voip-info, and Nerdvittles, but cannot find step by step instructions about how to make my VM and Fax to Email work.

I tried to get it to work with Gmail. No luck, Gmail rejects the login even though I set it for less-secure login. I get a Google Security Alert when a VM or FAX come in.

I would even like to try back with my webhost email.

But I need step by step instructions.
 
What platform are you using?

If Incredible PBX 2021 Ubuntu use these instructions. http://nerdvittles.com/?p=34195

Scroll down to: "Next Steps with Incredible PBX 2021" Look at the second paragraph.
 
Jake said:
What platform are you using?

If Incredible PBX 2021 Ubuntu use these instructions. http://nerdvittles.com/?p=34195

Scroll down to: "Next Steps with Incredible PBX 2021" Look at the second paragraph.
Click to expand...
I followed the instructions when I set up the system. Sendmail is there and there is a swapfile.

Gmail rejects the login even though I set it for less-secure login. I get a Google Security Alert sent to me but Google does not accept or relay the VM or FAX when my PBX receives a VM or FAX.

I have a Google Apps for Business account.

Anyone have any ideas to fix this or can you point me to a tutorial?
 
Last edited:
try a basic gmail email address with less-secure app turned on. Then open a commandline(e.g. Putty) on PBX and run this:

echo "test" | mail -s testmessage [email protected]

and see if you get the email...
 
what does /var/log/maillog say? It should tell you if it sent and if there is an error from gamil
 
Brianmac said:
what does /var/log/maillog say? It should tell you if it sent and if there is an error from gamil
Click to expand...
May 2 07:02:56 pbx1 sendmail[14026]: 142B2uVU014026: Authentication-Warning: pbx1.wildly-successful.com: asterisk set sender to [email protected] using -f
May 2 07:02:56 pbx1 sendmail[14026]: 142B2uVU014026: from=[email protected], size=28603, class=0, nrcpts=1, msgid=<[email protected]>, relay=asterisk@localhost
May 2 07:02:57 pbx1 sm-mta[14027]: 142B2uuk014027: from=<[email protected]>, size=28889, class=0, nrcpts=1, msgid=<[email protected]>, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
May 2 07:02:57 pbx1 sendmail[14026]: 142B2uVU014026: to=[email protected], ctladdr=[email protected] (998/1001), delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=58603, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (142B2uuk014027 Message accepted for delivery)
May 2 07:02:57 pbx1 sm-mta[14029]: STARTTLS=client, relay=smtp.gmail.com., version=TLSv1.3, verify=FAIL, cipher=TLS_AES_256_GCM_SHA384, bits=256/256
May 2 07:02:58 pbx1 sm-mta[14029]: 142B2uuk014027: to=<[email protected]>, delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=148889, relay=smtp.gmail.com. [173.194.219.109], dsn=5.0.0, stat=Service unavailable
May 2 07:02:58 pbx1 sm-mta[14029]: 142B2uuk014027: 142B2wuk014029: DSN: Service unavailable
May 2 07:02:58 pbx1 sm-mta[14029]: 142B2wuk014029: to=<[email protected]>, delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=60121, relay=smtp.gmail.com., dsn=5.0.0, stat=Service unavailable
May 2 07:02:58 pbx1 sm-mta[14029]: 142B2wuk014029: to=MAILER-DAEMON, delay=00:00:00, mailer=local, pri=60121, dsn=5.1.1, stat=User unknown
May 2 07:02:58 pbx1 sm-mta[14029]: 142B2wuk014029: to=postmaster, delay=00:00:00, mailer=local, pri=60121, dsn=5.1.1, stat=User unknown
May 2 07:02:58 pbx1 sm-mta[14029]: 142B2wuk014029: 142B2wul014029: return to sender: User unknown
May 2 07:02:58 pbx1 sm-mta[14029]: 142B2wul014029: to=MAILER-DAEMON, delay=00:00:00, mailer=local, pri=31145, dsn=5.1.1, stat=User unknown
May 2 07:02:58 pbx1 sm-mta[14029]: 142B2wuk014029: Losing ./qf142B2wuk014029: savemail panic
May 2 07:02:58 pbx1 sm-mta[14029]: 142B2wuk014029: SYSERR(root): savemail: cannot save rejected email anywhere
May 2 07:10:06 pbx1 sendmail[14777]: 142BA6xK014777: from=[email protected]-successful.com, size=90, class=0, nrcpts=1, msgid=<[email protected]-successful.com>, relay=root@localhost
May 2 07:10:06 pbx1 sm-mta[14778]: 142BA6aK014778: from=<[email protected]-successful.com>, size=378, class=0, nrcpts=1, msgid=<[email protected]-successful.com>, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
May 2 07:10:06 pbx1 sendmail[14777]: 142BA6xK014777: to=<[email protected]>, ctladdr=[email protected]-successful.com (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30090, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (142BA6aK014778 Message accepted for delivery)
May 2 07:10:06 pbx1 sm-mta[14780]: STARTTLS=client, relay=smtp.gmail.com., version=TLSv1.3, verify=FAIL, cipher=TLS_AES_256_GCM_SHA384, bits=256/256
May 2 07:10:07 pbx1 sm-mta[14780]: 142BA6aK014778: to=<[email protected]>, ctladdr=<[email protected]-successful.com> (0/0), delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=120378, relay=smtp.gmail.com. [173.194.219.108], dsn=5.0.0, stat=Service unavailable
May 2 07:10:07 pbx1 sm-mta[14780]: 142BA6aK014778: 142BA7aK014780: DSN: Service unavailable
May 2 07:10:07 pbx1 sm-mta[14780]: 142BA7aK014780: to=<[email protected]-successful.com>, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=31630, dsn=2.0.0, stat=Sent
 
Here is the previous days' mail log:

Apr 30 21:25:56 pbx1 sendmail[1382]: 1411Pu6L001382: from=asterisk, size=617, class=0, nrcpts=0, msgid=<[email protected]-successful.com>, relay=asterisk@localhost
Apr 30 21:25:56 pbx1 sendmail[1368]: 1411PuAo001368: from=asterisk, size=2398, class=0, nrcpts=1, msgid=<[email protected]-successful.com>, relay=asterisk@localhost
Apr 30 21:25:56 pbx1 sm-mta[1384]: 1411Puwl001384: from=<[email protected]-successful.com>, size=2540, class=0, nrcpts=1, msgid=<[email protected]-successful.com>, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
Apr 30 21:25:56 pbx1 sendmail[1368]: 1411PuAo001368: to="SUCCESSFUL ENTERPRISES" <[email protected]>, ctladdr=asterisk (998/1001), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=32398, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (1411Puwl001384 Message accepted for delivery)
Apr 30 21:25:56 pbx1 sm-mta[1386]: STARTTLS=client, relay=smtp.gmail.com., version=TLSv1.3, verify=FAIL, cipher=TLS_AES_256_GCM_SHA384, bits=256/256
Apr 30 21:25:57 pbx1 sm-mta[1386]: 1411Puwl001384: to=<[email protected]>, ctladdr=<[email protected]-successful.com> (998/1001), delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=122540, relay=smtp.gmail.com. [], dsn=5.0.0, stat=Service unavailable
Apr 30 21:25:57 pbx1 sm-mta[1386]: 1411Puwl001384: 1411Pvwl001386: DSN: Service unavailable
Apr 30 21:25:57 pbx1 sm-mta[1386]: 1411Pvwl001386: to=<[email protected]-successful.com>, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=33776, dsn=2.0.0, stat=Sent
May 1 04:27:25 pbx1 sendmail[3272]: 1418RPe1003272: from=[email protected]-successful.com, size=1263, class=0, nrcpts=1, msgid=<[email protected]-successful.com>, relay=asterisk@localhost
May 1 04:27:25 pbx1 sm-mta[3275]: 1418RPt5003275: from=<[email protected]-successful.com>, size=1390, class=0, nrcpts=1, msgid=<[email protected]-successful.com>, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
May 1 04:27:25 pbx1 sendmail[3272]: 1418RPe1003272: to=[email protected], ctladdr=[email protected]-successful.com (998/1001), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=31263, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (1418RPt5003275 Message accepted for delivery)
May 1 04:27:26 pbx1 sm-mta[3278]: STARTTLS=client, relay=smtp.gmail.com., version=TLSv1.3, verify=FAIL, cipher=TLS_AES_256_GCM_SHA384, bits=256/256
May 1 04:27:26 pbx1 sm-mta[3278]: 1418RPt5003275: to=<[email protected]>, ctladdr=<[email protected]-successful.com> (998/1001), delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=121390, relay=smtp.gmail.com. [108.177.122.108], dsn=5.0.0, stat=Service unavailable
May 1 04:27:26 pbx1 sm-mta[3278]: 1418RPt5003275: 1418RQt5003278: DSN: Service unavailable
May 1 04:27:26 pbx1 sm-mta[3278]: 1418RQt5003278: to=<[email protected]-successful.com>, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=32614, dsn=2.0.0, stat=Sent
May 1 06:27:39 pbx1 sendmail[14320]: 141ARdWP014320: from=[email protected]-successful.com, size=824, class=0, nrcpts=1, msgid=<[email protected]-successful.com>, relay=asterisk@localhost
May 1 06:27:40 pbx1 sm-mta[14324]: 141ARegl014324: from=<[email protected]-successful.com>, size=951, class=0, nrcpts=1, msgid=<[email protected]-successful.com>, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
May 1 06:27:40 pbx1 sendmail[14320]: 141ARdWP014320: to=[email protected], ctladdr=[email protected]-successful.com (998/1001), delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=30824, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (141ARegl014324 Message accepted for delivery)
May 1 06:27:40 pbx1 sm-mta[14326]: STARTTLS=client, relay=smtp.gmail.com., version=TLSv1.3, verify=FAIL, cipher=TLS_AES_256_GCM_SHA384, bits=256/256
May 1 06:27:41 pbx1 sm-mta[14326]: 141ARegl014324: to=<[email protected]>, ctladdr=<[email protected]-successful.com> (998/1001), delay=00:00:01, xdelay=00:00:01, mailer=relay, pri=120951, relay=smtp.gmail.com. [], dsn=5.0.0, stat=Service unavailable
May 1 06:27:41 pbx1 sm-mta[14326]: 141ARegl014324: 141ARfgl014326: DSN: Service unavailable
May 1 06:27:41 pbx1 sm-mta[14326]: 141ARfgl014326: to=<[email protected]-successful.com>, delay=00:00:00, xdelay=00:00:00, mailer=local, pri=32175, dsn=2.0.0, stat=Sent
May 1 06:52:02 pbx1 sendmail[16587]: 141Aq2KC016587: from=[email protected]-successful.com, size=541, class=0, nrcpts=1, msgid=<[email protected]-successful.com>, relay=root@localhost
May 1 06:52:02 pbx1 sm-mta[16598]: 141Aq2EQ016598: from=<[email protected]-successful.com>, size=829, class=0, nrcpts=1, msgid=<[email protected]-successful.com>, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
May 1 06:52:02 pbx1 sendmail[16587]: 141Aq2KC016587: to=<[email protected]-successful.com>, ctladdr=[email protected]-successful.com (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30541, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (141Aq2EQ016598 Message accepted for delivery)
May 1 06:52:02 pbx1 sm-mta[16624]: 141Aq2EQ016598: forward /var/spool/hylafax/.forward.pbx1: Group writable directory
May 1 06:52:02 pbx1 sm-mta[16624]: 141Aq2EQ016598: forward /var/spool/hylafax/.forward: Group writable directory
May 1 06:52:02 pbx1 sendmail[16637]: 141Aq2e6016637: from=[email protected]-successful.com, size=414, class=0, nrcpts=1, msgid=<[email protected]-successful.com>, relay=root@localhost
May 1 06:52:02 pbx1 sm-mta[16624]: 141Aq2EQ016598: to=<[email protected]-successful.com>, ctladdr=<[email protected]-successful.com> (0/0), delay=00:00:00, xdelay=00:00:00, mailer=local, pri=31072, dsn=2.0.0, stat=Sent
May 1 06:52:02 pbx1 sm-mta[16639]: 141Aq2iE016639: from=<[email protected]-successful.com>, size=702, class=0, nrcpts=1, msgid=<[email protected]-successful.com>, proto=ESMTP, daemon=MTA, relay=localhost [127.0.0.1]
May 1 06:52:02 pbx1 sendmail[16637]: 141Aq2e6016637: to=<[email protected]-successful.com>, ctladdr=[email protected]-successful.com (0/0), delay=00:00:00, xdelay=00:00:00, mailer=relay, pri=30414, relay=[127.0.0.1] [127.0.0.1], dsn=2.0.0, stat=Sent (141Aq2iE016639 Message accepted for delivery)
May 1 06:52:02 pbx1 sm-mta[16640]: 141Aq2iE016639: forward /var/spool/hylafax/.forward.pbx1: Group writable directory
May 1 06:52:02 pbx1 sm-mta[16640]: 141Aq2iE016639: forward /var/spool/hylafax/.forward: Group writable directory
May 1 06:52:02 pbx1 sm-mta[16640]: 141Aq2iE016639: to=<[email protected]-successful.com>, ctladdr=<[email protected]-successful.com> (0/0), delay=00:00:00, xdelay=00:00:00, mailer=local, pri=30945, dsn=2.0.0, stat=Sent
 
did you follow this?
# Stop here and edit client-info (nano -w client-info) in all three lines. # Replace user_id with your gMail account name without @gmail.com # Replace password with your real gMail password OR # use your Gmail App Key if 2-step verification is enabled # Be sure to replace the double-quotes shown above if they don't appear in the file!!!

make sure you are using the correct password OR gmail app key(2-step) - this depends on the settings in your gmail account.
verify in /etc/mail/auth/client-info

nothing is arriving because google is rejecting due to 530-5.7.0 Authentication Required
 
Brianmac said:
did you follow this?
# Stop here and edit client-info (nano -w client-info) in all three lines. # Replace user_id with your gMail account name without @gmail.com # Replace password with your real gMail password OR # use your Gmail App Key if 2-step verification is enabled # Be sure to replace the double-quotes shown above if they don't appear in the file!!!

make sure you are using the correct password OR gmail app key(2-step) - this depends on the settings in your gmail account.
verify in /etc/mail/auth/client-info

nothing is arriving because google is rejecting due to 530-5.7.0 Authentication Required
Click to expand...
Where are these instructions?
 
Since you are using Incredible PBX 2021 Debian, I would use the tutorial on nerdvittles for the system you are using. It is easier than the old method.

Happy New Year: Introducing Incredible PBX 2021 for Debian – Nerd Vittles

nerdvittles.com nerdvittles.com

Outbound mail functionality needs to be working so that you can receive voicemail messages and faxes by email. To prevent SPAM, most ISPs and ITSPs block messages from downstream mail servers. That would be you. The easiest way to resolve this is to configure SendMail using Gmail as an SMTP Smarthost. You obviously need a Gmail account to implement this and, if you have turned on two-factor authentication for your Gmail account, you also will need to obtain an App password for your Gmail account, and use that in lieu of your regular Gmail password when configuring SendMail. With your Gmail username and password in hand, log into your server as root and run: /root/enable-gmail-smarthost-for-sendmail.

I have setup multiple systems using the simple instructions above and it works just fine. If you turned on two-factor authentication, follow the link obtain an App password and use it in place of your regular Gmail account password. I would use a normal gmail account not a Google Apps for Business account and get it working.
 
@Brianmac @hawk#1
I have tried following the instructions that are in Configuring SendMail with Incredible PBX 2020.
I have run enable-gmail-smarthost-for-sendmail.

However, my system still does not send out VM or FAX emails.
 
Also, I am on Debian. But in the instructions it says to run:
root@pbx1:/etc/mail $ sed -i 's|sendmail-cf|sendmail/cf|' Makefile make

I receive this message:
root@pbx1:/etc/mail $ sed -i 's|sendmail-cf|sendmail/cf|' Makefile make
sed: can't read make: No such file or directory
WARNING: Always run Incredible PBX behind a secure firewall.
 
Look at post #14 - don't use the script
run each line by hand(copy & paste)and make sure you do not get an error... if you do, stop and reply back
your box is sending, but google is rejecting, there is a conflict somewhere...
 
Generally, if you give the PBX a full TLD domain, with subdomain (pbx.mydomain.net) , and put an A Record for it in a DNS , Gmail will accept it. Microsoft/Outlook/Hotmail, not so much.
 
KNERD said:
Generally, if you give the PBX a full TLD domain, with subdomain (pbx.mydomain.net) , and put an A Record for it in a DNS , Gmail will accept it. Microsoft/Outlook/Hotmail, not so much.
Click to expand...

You really need a PTR as well. MS/Outlook etc will look for SPF, DMARC and DKIM, which gets way more difficult. In these instances there are some mail relay services you can pay a couple dollars a month for which might work as better.
 
You must log in or register to reply here.

Latest Posts

Forum statistics

Threads
26,831
Messages
175,390
Members
20,381
Latest member
kalilinux
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Verify your Email

Check your inbox!

We’ve sent you an email. Click on the button in the email body to verify your email address – (if you can not find it, check your spam folder).

Upon verification you will be directed to the 3CX setup wizard.

Back
Top