New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add com.project.materialmessaging to the by default #302

Eugene-Savenko opened this Issue Jan 29, 2016 · 2 comments


None yet
3 participants

Eugene-Savenko commented Jan 29, 2016


The customer couldn't send MMS. Adding into exclusions makes it work fine.

"Thanks, that fixed it!

My mobile carrier is Cricket - an AT&T MVNO. Regarding other apps, Google
Messenger does not work, even without Adguard.

There is a known issue with both Cricket's DNS entries and server
configuration for their MMS proxy servers. DNS resolves to different
addresses depending on whether the device is connected to WiFi or mobile
data, and the servers at the addresses resolved via WiFi don't have the
proper ports open. It appears that when connecting to the MMS proxy fails
via WiFi, some messaging apps fail to re-resolve the proxy address after
switching to mobile data, causing them to fail, while other apps do
re-resolve the address, allowing them to succeed.

However, with a workaround implemented (that correctly resolves the proxy
address over WiFi), Material Messaging still fails with Adguard enabled."

@ameshkov ameshkov added this to the 2.5 milestone Feb 1, 2016

@ameshkov ameshkov added Compatibility and removed Enhancement labels Feb 1, 2016


This comment has been minimized.


ameshkov commented Feb 1, 2016

We should add this app to the default exclusions list.


This comment has been minimized.


Revertron commented Mar 11, 2016


@Revertron Revertron closed this Mar 11, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment