# Error with M1 Apple Silicon and wp\_mail

**URL:** <https://community.kinsta.com/t/error-with-m1-apple-silicon-and-wp-mail/898>\
**Category:** Bug Reports\
**Created:** [August 2, 2021, 1:48pm UTC](https://community.kinsta.com/t/error-with-m1-apple-silicon-and-wp-mail/898 "2021-08-02T13:48:59Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marek\_Maurizio](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/marek_maurizio/32/624_2.png) [@Marek\_Maurizio](https://community.kinsta.com/u/Marek_Maurizio)\
**Post date:** [August 2, 2021, 1:48pm UTC](https://community.kinsta.com/t/error-with-m1-apple-silicon-and-wp-mail/898/1 "2021-08-02T13:48:59Z")

</div>

**Q: Date/Time this occurred (Provide your time zone also)**  
**A:**  
GMT+1 02/08/2022

**Q: DevKinsta Version**  
**A:**  
Version 2.1.0 (2.1.0.1899)

**Q: OS Version**  
**A:**  
11.2.3 (20D91)

**Q: Docker Desktop Version**  
**A:**  
3.5.2 66501

**Q: Were any error codes or messages observed? If so, what were they?**  
**A:**

```auto
wp> wp_mail('email@example.com', 'test', 'test')
runtime: failed to create new OS thread (have 2 already; errno=22)
fatal error: newosproc

runtime stack:
runtime.throw(0x6b2000, 0x9)
	/usr/local/Cellar/go/1.6/libexec/src/runtime/panic.go:530 +0x90
runtime.newosproc(0xc820026000, 0xc820035fc0)
	/usr/local/Cellar/go/1.6/libexec/src/runtime/os1_linux.go:149 +0x18c
runtime.newm(0x715c28, 0x0)
	/usr/local/Cellar/go/1.6/libexec/src/runtime/proc.go:1513 +0x135
runtime.main.func1()
	/usr/local/Cellar/go/1.6/libexec/src/runtime/proc.go:125 +0x2c
runtime.systemstack(0x7f3300)
	/usr/local/Cellar/go/1.6/libexec/src/runtime/asm_amd64.s:291 +0x79
runtime.mstart()
	/usr/local/Cellar/go/1.6/libexec/src/runtime/proc.go:1048

goroutine 1 [running]:
runtime.systemstack_switch()
	/usr/local/Cellar/go/1.6/libexec/src/runtime/asm_amd64.s:245 fp=0xc820020770 sp=0xc820020768
runtime.main()
	/usr/local/Cellar/go/1.6/libexec/src/runtime/proc.go:126 +0x62 fp=0xc8200207c0 sp=0xc820020770
runtime.goexit()
	/usr/local/Cellar/go/1.6/libexec/src/runtime/asm_amd64.s:1998 +0x1 fp=0xc8200207c8 sp=0xc8200207c0
=> bool(false)

```

**Q: Detailed Description of the Problem**  
**A:**  
A default DevKinsta/Wordpress installation does not send emails to Mailhog. Mailhog is running, but no email are received. Tested both in the admin interface and WPCLI.

---

<div class="post-metadata">

**Author:** ![michael](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/michael/32/31_2.png) [@michael](https://community.kinsta.com/u/michael)\
**Post date:** [August 2, 2021, 9:28pm UTC](https://community.kinsta.com/t/error-with-m1-apple-silicon-and-wp-mail/898/2 "2021-08-02T21:28:10Z")

</div>

Sorry for the wait here, @Marek_Maurizio . We’re currently reviewing this and will get back to you shortly!

---

<div class="post-metadata">

**Author:** ![Marek\_Maurizio](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/marek_maurizio/32/624_2.png) [@Marek\_Maurizio](https://community.kinsta.com/u/Marek_Maurizio)\
**Post date:** [August 4, 2021, 2:45pm UTC](https://community.kinsta.com/t/error-with-m1-apple-silicon-and-wp-mail/898/3 "2021-08-04T14:45:33Z")

</div>

Thank you @michael. My knowloedge of Docker is very limited, so forgive me if I am mistaken, but I guess a version of the docker images compiled for the arm64 architecture would prevent this error and bring better performances too. Right now I got this message.

 ![Screenshot 2021-08-04 at 16.44.55](https://us1.discourse-cdn.com/flex020/uploads/kinsta/original/1X/548633cba7e266c38b0574425b15a3d06ceb0c8e.jpeg)

---

<div class="post-metadata">

**Author:** ![Marek\_Maurizio](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/marek_maurizio/32/624_2.png) [@Marek\_Maurizio](https://community.kinsta.com/u/Marek_Maurizio)\
**Post date:** [August 12, 2021, 7:03am UTC](https://community.kinsta.com/t/error-with-m1-apple-silicon-and-wp-mail/898/4 "2021-08-12T07:03:29Z")

</div>

Any news on that?  
I used the system for a while developing a website and the email sending problem seems to be the only problem i got for now.

---

<div class="post-metadata">

**Author:** ![michael](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/michael/32/31_2.png) [@michael](https://community.kinsta.com/u/michael)\
**Post date:** [August 12, 2021, 2:11pm UTC](https://community.kinsta.com/t/error-with-m1-apple-silicon-and-wp-mail/898/5 "2021-08-12T14:11:03Z")

</div>

I’m sorry for the wait here @Marek_Maurizio . There does appear to be a bug with M1 machines at the moment that our developers are looking into.

---

<div class="post-metadata">

**Author:** ![michael](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/michael/32/31_2.png) [@michael](https://community.kinsta.com/u/michael)\
**Post date:** [November 10, 2021, 2:32pm UTC](https://community.kinsta.com/t/error-with-m1-apple-silicon-and-wp-mail/898/6 "2021-11-10T14:32:16Z")

</div>

Hi @Marek_Maurizio. We just released [DevKinsta 2.3.0](https://devkinsta.com). Could you give this a test and let me know if this issue continues? Thank you again.