SMTP "Other" Configuration Does Not Work

[Revo2Maxx]

I asked in PM for that info to be in PM and not posted if it wasn't related to what I thought was the post in Question. So Yes it was removed as it wasn't needed or part of helping answer the issue and hand.

[GaryOkie]

ok, got it! If a post contains any information deemed not relevant to the question at hand it is subject to being removed. Wow.

Sorry that I missed answering the PM's. There was TMI in there that I hadn't fully processed.

[sickroachman]

Is this really still not fixed?

[bleeper]

i have the ipm-721 camera and no luck with this. same smtp settings work nicely with an older foscam. it appears that the amcrest mail settings require user authentication even with the anonymous setting and simple mail submission to port 25 isn't supported. no diagnostics either to figure out where things are going wrong. just a simple failed message. sucks.

edit: seems to work ok with smtp.office365.com and user auth over port 587. so the smtp port 25 submission error is def a firmware bug that probably is in a wide variety of amcrest products. like the op mentioned, the system doesn't even try to send the email. it just fails out of the gate.

[CommanderData]

Well, I recently purchased two more Amcrest 4K cameras, Amcrest 4K - IP8M-2779EW-AI, believing that their simple SMTP email problem has been solved.

Well, I now have 3 different models and NONE of them work with a simple, no-authentication required on-site SMTP server that has been working fine with other devices for years (NAS, UPS, etc).

I'm surprised that the most basic email setup does not work with Amcrest devices. Even worse, these two new cameras do not even save the Other SMTP IP Server address, Authentication type (None, SSL, TLS), or the connection port settings. After "save success", leaving that page and returning to it shows the default options as "none", "TLS", and "25" no matter what I try.

I'm once again saddened by Amcrest and continue to recommend other cameras to my clients, which has been well over 1,000 site installs over the past 5 years (over 25,000 cameras). I work with larger organizations to install camera systems, sometimes dozens or hundreds in a single location. They all have an extensive networks and on-site (local network) SMTP servers.

I'm out of gas, and will permanently abandon Amcrest for this one simple, yet extremely important reason.

[Revo2Maxx]

Only thing it don't retain and will need to be entered each time is the password if you need to make changes.. About the other settings.. Yeah you are kind of right moving from default area to Other changes things back to 25 and so on.. You see that Refresh button on the bottom, Pressing that will return the entered items from before as long as they were saved..

I don't understand why someone would want to use No Auth for a user? Main issue with that is there is no Email server that I know of that supports such user.. Then for the Local servers that are connected as a relay or even a real email server with a MX record that option normally has been removed because of others abusing the option..

Have no issues setting up email to my email servers.. I mean last year my Network Solutions server aka host changed the way it runs the mail server and now some of my devices no longer connect to that mostly only NVRs.. So I hosted a different server from Inmotion hosting and that one works fine on both IP cameras and DVR/NVRs..

I am all for the security of my security system.. IF there was room for abuse then others would exploit that.. I want the end users to be safe not open for issues.. Anything that isn't secure with a camera system then what is the sense of owning one?

Main issue isn't the login to the local server, the real issue is setting it up without auth and sending as many emails as I get a day from my 1 camera, If it was not setup for a real account my incoming email server would Block the incoming mail as it would be considered Spam.. With the device logging into a real server using TLS the incoming server understands that the outgoing server has a real user and the email most likely is ok.

[CommanderData]

Revo2Maxx:

I setup local on-site SMTP servers where the authentication to the "real" email servers (eg: gmail, Yahoo, etc) is built-into the SMTP server itself so that all of these so-called "smart" devices don't need to know anything about any real email server, MX records, or passwords that can be hacked.

When one of my UPSes goes on battery, it simply opens a connection to a local SMTP server with NO authentication over port 25 and drops an email message to whatever address I want. Then the SMTP server takes that and relays it to gmail (for example) and uses the authentication I have given it for the gmail account. The only thing that "knows" this gmail account is the SMTP server itself.

As for "real" servers, when the IP address of the sending SMTP server is a business, those restrictions you mention about the number of emails is moot. Those restrictions are for typically for IP addresses that are homes, not businesses.

I appreciate your quick response, but it still doesn't explain why the simplest email function in so many Amcrest camera models doesn't work. Why have "Other" if it will never work in the first place?