TIPS Incredible PBX 13-12 No Email & Knock App

[Twilight Sparkle]

Specs:
Google Cloud VM Compute Engine ( Free $300 Trial 60 Days )
Installed: Incredible PBX 13-12 with Incredible GUI for the Ubuntu 14 Platform
From: http://nerdvittles.com/?p=14183
WGET:
wget http://incrediblepbx.com/incrediblepbx13-12.2-ubuntu14.tar.gz

so after i got it installed and setup i notice that i cant get emails for anything.
this also means i dont get fax's sent to email but i can see them online so no issue there...

i just want emails for Voicemail and other things like caller id.

i setup everything like i did in the past no luck?

Dose it have something to do with Knock or Firewall ot TM4?

Oh yeah... TM4 or Knock or the same i dont know... i cant get KNOCK to work on phone...

i installed the app and still dose not grant access, i have used it for a while on other VM and CLoud like digital ocean but on Google CLoud no luck or is it the PBX i installed...

what do you suggest i do

 

[KevinW]

I just got done loading Incredible on a Rasberry Pi 2 B+. My email didn't work either. I did 3 things if I recall correctly. I had to set the hostname to a fully qualified domain name. I made it match DNS I had set for the old box that it's replacing. I also had to go into the sendmail config and remove a domain alias that was manually set as that made mail appear to come from root@raspberrypi. I also set it up so it forwarded all email to my existing mail server so I didn't need to bother with setting it up with a relay server or anything like that. I made all the sendmail changes in Webmin. I found it pretty simple to do.

The way I found out what needed to change was by sending test emails from the command line and watching the response from the server. That's how I figured out the server was rejecting emails without fully qualified domain info.

HTH

 

[Twilight Sparkle]

I just got done loading Incredible on a Rasberry Pi 2 B+. My email didn't work either. I did 3 things if I recall correctly. I had to set the hostname to a fully qualified domain name. I made it match DNS I had set for the old box that it's replacing. I also had to go into the sendmail config and remove a domain alias that was manually set as that made mail appear to come from root@raspberrypi. I also set it up so it forwarded all email to my existing mail server so I didn't need to bother with setting it up with a relay server or anything like that. I made all the sendmail changes in Webmin. I found it pretty simple to do.

The way I found out what needed to change was by sending test emails from the command line and watching the response from the server. That's how I figured out the server was rejecting emails without fully qualified domain info.

HTH

i discover if i did a static ip the emails got sent but ended up in SPAM box which is not bad as long as they are sent.

but if their is away to make it into the inbox that would be better

 

[KevinW]

i discover if i did a static ip the emails got sent but ended up in SPAM box which is not bad as long as they are sent.

but if their is away to make it into the inbox that would be better

That will depend on what is managing your spam filter. There is normally a way in most systems to either whitelist the sending email address, or to mark the message as not spam so the system learns how to properly mark the message.

 

[chris_c_]

@Twilight Sparkle
For email delivery, it's best you setup as follows:

1. use a fully qualified domain name which you own,
   
2. add an SPF record in your domain name's DNS,
   
3. activate DNSSEC in your BIND9 DNS server (paste DS record to your DNS registrar etc),
   
4. DKIM records in DNS (open-dkim),
   
5. install a real, free TLS cert from letsencrypt with your fully qualified domain name on it,
   
6. TLSA records in DNS,

If you use webmin then most of this is taken care of semi automatically.

 

[jerrm]

If you're not trying to overcome negative scoring from being on a dynamic IP, proper SPF and PTR records with matching fqdn is usually enough.

DKIM is almost never needed. There will be occasional exceptions, but we have many Exchange servers sending mail all over the place without DKIM and without issue.

For any hosted service, always check the IP against blacklists, you don't know what the guy before you was doing.

 

[Twilight Sparkle]

If you're not trying to overcome negative scoring from being on a dynamic IP, proper SPF and PTR records with matching fqdn is usually enough.

DKIM is almost never needed. There will be occasional exceptions, but we have many Exchange servers sending mail all over the place without DKIM and without issue.

For any hosted service, always check the IP against blacklists, you don't know what the guy before you was doing.

good info i keep forget-in that IP's are all Recycled.
- my last IP that i loved was taken cuz it was not staic and poof next i know it was used for a stupid spam site....

makes since.
-- nest time before i do a server ill run a check on it if possible to see...