troy Posted July 20, 2018 Share Posted July 20, 2018 Have factory reset several times, nothing else installed and configured - can't email with Gmail. Are there any workarounds for the current firmware? Link to comment Share on other sites More sharing options...
b0N3z Posted July 21, 2018 Share Posted July 21, 2018 you need to allow less secure apps to login to your gmail for this to work Link to comment Share on other sites More sharing options...
troy Posted July 21, 2018 Author Share Posted July 21, 2018 Apologies - should have already clarified - it is turned on. Link to comment Share on other sites More sharing options...
Foxtrot Posted July 21, 2018 Share Posted July 21, 2018 What are the settings you are using in the module? Link to comment Share on other sites More sharing options...
troy Posted July 21, 2018 Author Share Posted July 21, 2018 3 minutes ago, Foxtrot said: What are the settings you are using in the module? From: [redacted]@gmail.com To: [redacted]@gmail.com SMTP Server: smtp.gmail.com SMTP Port: 587 (also tried 485) Domain: gmail.com Username: [redacted]@gmail.com Password: [redacted] Use TLS: Unchecked Use STARTTLS: Checked Link to comment Share on other sites More sharing options...
Just_a_User Posted July 21, 2018 Share Posted July 21, 2018 5 hours ago, troy said: From: [redacted]@gmail.com To: [redacted]@gmail.com SMTP Server: smtp.gmail.com SMTP Port: 587 (also tried 485) Domain: gmail.com Username: [redacted]@gmail.com Password: [redacted] Use TLS: Unchecked Use STARTTLS: Checked That looks good to me. With only one last thing to check the report configuration as below: - As @b0N3z said I had to lower the security for the gmail account to get mine to work on other networks, VPN etc. https://support.google.com/accounts/answer/6010255?hl=en Also i made a pineapple account just for that, not lowering the security of my account ? works well for me. Link to comment Share on other sites More sharing options...
troy Posted July 21, 2018 Author Share Posted July 21, 2018 It's all configured correctly. I think ssmtp is seg faulting when trying to send - at least it does on the command line. I can't see where there is any logging or output when I click test send - so I've go no idea where to look. Does anybody else use gmail SMTP with the current firmware? The account works with SMTP sending, just not from the pinapple Link to comment Share on other sites More sharing options...
Just_a_User Posted July 21, 2018 Share Posted July 21, 2018 10 minutes ago, troy said: Does anybody else use gmail SMTP with the current firmware? The account works with SMTP sending, just not from the pinapple Like I said im using gmail smtp on 2.2.0 and its working well. Link to comment Share on other sites More sharing options...
troy Posted July 21, 2018 Author Share Posted July 21, 2018 Apologies @Just_a_User I didn't see you clarify you were using the current firmware. I'm not sure what else to do then, it is not working here. Link to comment Share on other sites More sharing options...
The Power Company Posted July 23, 2018 Share Posted July 23, 2018 May sound like a dumb question, but is your pineapple connected to the internet? Either through WiFi client mode or an Ethernet cable? (you can check by trying to load the news on the dashboard or checking for updates) Link to comment Share on other sites More sharing options...
troy Posted July 23, 2018 Author Share Posted July 23, 2018 It's connected. SSMTP seg faults when trying to send. Link to comment Share on other sites More sharing options...
Just_a_User Posted July 23, 2018 Share Posted July 23, 2018 1 minute ago, troy said: It's connected. SSMTP seg faults when trying to send. Its definitely a Wifi pineapple right? not a Raspberry Pi or anything else? A Firmware recovery should clear anything like this up. Not a factory reset but a firmware recovery. Link to comment Share on other sites More sharing options...
troy Posted July 23, 2018 Author Share Posted July 23, 2018 Firmware recovery and upgraded to 2.2.0 Still getting a Seg fault when trying to send via gmail root@Pineapple:/pineapple/modules/Reporting/files# ./reporting getPineAPReport uci: Entry not found getClientReport uci: Entry not found getTrackedclients getSiteReport OK OK Reloaded PineAP config machine : WiFi Pineapple TETRA Running scan type 2 for 15 seconds New scan id: scan Waiting for scan to finish Retrieving scan results, appending to debug log tar Segmentation fault Link to comment Share on other sites More sharing options...
b0N3z Posted July 23, 2018 Share Posted July 23, 2018 I think you have a setting off or something. Use your personal email to send and receive and allow less secure apps for the test. This setup took me some time to figure out because I have never used smtp and the settings really throw me for a loop. Once you figure out how it works like that then move forward with a "pineapple email" so your not compromising your own email with less security. Link to comment Share on other sites More sharing options...
Foxtrot Posted July 24, 2018 Share Posted July 24, 2018 4 hours ago, troy said: Firmware recovery and upgraded to 2.2.0 Still getting a Seg fault when trying to send via gmail root@Pineapple:/pineapple/modules/Reporting/files# ./reporting getPineAPReport uci: Entry not found getClientReport uci: Entry not found getTrackedclients getSiteReport OK OK Reloaded PineAP config machine : WiFi Pineapple TETRA Running scan type 2 for 15 seconds New scan id: scan Waiting for scan to finish Retrieving scan results, appending to debug log tar Segmentation fault I wasn't able to reproduce this segfault, a screenshot of your full settings would be very useful. I did just find a couple issues that were introduced with the new firmware though, and have since been fixed for the next version. Link to comment Share on other sites More sharing options...
troy Posted July 24, 2018 Author Share Posted July 24, 2018 I've not been able to attach screenshots (or even reply because of rate limiting).. but now i can - here's my settings (attached) Link to comment Share on other sites More sharing options...
Zylla Posted July 24, 2018 Share Posted July 24, 2018 If you're getting segfaults, remember to check dmesg right afterwards. Then copy/paste the output here, or better: to pastebin. ? Makes debugging stuff like this SOOO MUCH EASIER. ? EDIT: I was also unable to reproduce this segfault. Here's my settings: Link to comment Share on other sites More sharing options...
troy Posted July 25, 2018 Author Share Posted July 25, 2018 HI @Zylla - thank you for trying to reproduce. I'm not sure what help dmesg will be / is of. The seg fault is not generating any diagnostic messages. @Foxtrot do you mean that the fix you have applied to a future version is intended to resolve the issue I have - or you are not sure? Is this because there is no ca-certs bundle anywhere possibly? Link to comment Share on other sites More sharing options...
Zylla Posted July 25, 2018 Share Posted July 25, 2018 14 hours ago, troy said: HI @Zylla - thank you for trying to reproduce. I'm not sure what help dmesg will be / is of. The seg fault is not generating any diagnostic messages. @Foxtrot do you mean that the fix you have applied to a future version is intended to resolve the issue I have - or you are not sure? Is this because there is no ca-certs bundle anywhere possibly? dmesg displays the kernel buffer, so if anything goes *DERP'' and segfaults, that's the place to look for any verbose output / error messages. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.