Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Email notofication and gmail smtp

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    19 Posts 8 Posters 25.4k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • R
      rilles
      last edited by

      Still doesn't work for me using my ISP (Rogers - which uses Yahoo email servers).

      On port 25 with all the correct settings it still fails with "Error: 530 authentication required"… seems pfense 2.0 is not sending the credentials.  My email client (Thunderbird) has no issues.

      1 Reply Last reply Reply Quote 0
      • johnpozJ
        johnpoz LAYER 8 Global Moderator
        last edited by

        On this document it clearly states to use port 587

        http://www.rogershelp.com/yahoo/mail/settings.html

        Outgoing (SMTP) Port Number: 587

        An intelligent man is sometimes forced to be drunk to spend time with his fools
        If you get confused: Listen to the Music Play
        Please don't Chat/PM me for help, unless mod related
        SG-4860 24.11 | Lab VMs 2.8, 24.11

        1 Reply Last reply Reply Quote 0
        • R
          rilles
          last edited by

          Highly amusing, they have changed all their web pages to port 587 from port 25 from 2 years ago. But not relevant, my email client works fine on port 25 and I can telnet there and test without issue.  Changing it to port 587 in any case does not help with the pfsense error.

          1 Reply Last reply Reply Quote 0
          • johnpozJ
            johnpoz LAYER 8 Global Moderator
            last edited by

            Well I just tested using another smtp server, and yup it fails.

            I know for a fact that have the correct username and password, since I just tested the auth from command line

            250 homiemail-a48.g.dreamhost.com
            auth login
            snipped
            235 2.7.0 Authentication successful

            To test from telnet you need to base64 your email address and password, send base64 encoded emailaddress, then enter then base64 encoded password.  And this works fine, but put the same info into pfsense and yup it fails.

            But if you have telnet access off your network, then just send directly to the mail server for the domain your wanting to sent email too.

            But they need to correct this, think I will do a sniff and see what its doing wrong.

            edit: Ok from a capture it never sends the auth command, nor the info.. So yeah its broke!

            capture.jpg
            capture.jpg_thumb

            An intelligent man is sometimes forced to be drunk to spend time with his fools
            If you get confused: Listen to the Music Play
            Please don't Chat/PM me for help, unless mod related
            SG-4860 24.11 | Lab VMs 2.8, 24.11

            1 Reply Last reply Reply Quote 0
            • jimpJ
              jimp Rebel Alliance Developer Netgate
              last edited by

              Some commits happened for this over the weekend, can you try a new snapshot and see if it works?

              Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

              Need help fast? Netgate Global Support!

              Do not Chat/PM for help!

              1 Reply Last reply Reply Quote 0
              • L
                ldpaniak
                last edited by

                Just upgraded tested e-mail on the latest snapshot (Mon Jan 3 03:26 2011)

                I get an error:

                Warning: require_once(sasl.inc): failed to open stream: No such file or directory in /etc/inc/notices.inc on line 286 
                Fatal error: require_once(): Failed opening required 'sasl.inc' (include_path='.:/etc/inc:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg') in /etc/inc/notices.inc on line 286
                
                1 Reply Last reply Reply Quote 0
                • jimpJ
                  jimp Rebel Alliance Developer Netgate
                  last edited by

                  Here is the open ticket for that, the error messages would be useful to the person working on the issue: http://redmine.pfsense.org/issues/1141

                  Remember: Upvote with the 👍 button for any user/post you find to be helpful, informative, or deserving of recognition!

                  Need help fast? Netgate Global Support!

                  Do not Chat/PM for help!

                  1 Reply Last reply Reply Quote 0
                  • johnpozJ
                    johnpoz LAYER 8 Global Moderator
                    last edited by

                    yup getting the same error when try to change the notification section to use auth.

                    Warning: require_once(sasl.inc): failed to open stream: No such file or directory in /etc/inc/notices.inc on line 286 Fatal error: require_once(): Failed opening required 'sasl.inc' (include_path='.:/etc/inc:/usr/local/www:/usr/local/captiveportal:/usr/local/pkg') in /etc/inc/notices.inc on line 286

                    On the latest snap

                    2.0-BETA5 (i386)
                    built on Mon Jan 3 03:26:07 EST 2011

                    edit:
                    Ok, tested the lastest snap and still not working
                    2.0-BETA5 (i386)
                    built on Mon Jan 3 13:22:20 EST 2011

                    now bug says it was fixed because he did not include the sasl.inc or sasl.php from the class – but that was still missing after the update..  But I grabbed the file from the links in the bug, renamed to .inc and then changed the names for the other files to be .inc vs .php and its working.. I would assume the next snap will include file?

                    But if not you can always make it work on your own.. Just grab from the link in the bug.

                    I tested sending to my dreamhost server authing, and its send to my gmail address just fine.

                    As you can see from capture its sending auth now ;)  I'll the file I added and edited before I upgrade to the next snap to verify its now included, etc.

                    authworking.png
                    authworking.png_thumb

                    An intelligent man is sometimes forced to be drunk to spend time with his fools
                    If you get confused: Listen to the Music Play
                    Please don't Chat/PM me for help, unless mod related
                    SG-4860 24.11 | Lab VMs 2.8, 24.11

                    1 Reply Last reply Reply Quote 0
                    • P
                      ppomes
                      last edited by

                      Hi all,

                      Yeah, I made only a partial operation with git and I forgot to add /etc/inc/sasl.inc :-(

                      The file should now be in the lastest snapshot, can you just try again to validate all is ok ?

                      Many thanks,
                      Pierre

                      1 Reply Last reply Reply Quote 0
                      • L
                        ldpaniak
                        last edited by

                        Works for me now with latest snap.

                        Thanks!

                        1 Reply Last reply Reply Quote 0
                        • R
                          rilles
                          last edited by

                          Working for me now also with 1/5/11 snapshot.

                          1 Reply Last reply Reply Quote 0
                          • T
                            TheAngryPenguin
                            last edited by

                            I just joined the 2.x revolution and was unable to get e-mail notifications working as previously described in this post.  For one reason or another, my pfSense is unable to authenticate against smtp.gmail.com:587.  Since I use Google Apps to host my domain's e-mail, I decided to extend the guidance above by performing a lookup on my domain (http://www.mxtoolbox.com is a handy tool), and I used the resulting hostname in my config.  Same deal – use port 25, no need for AUTH, the From: address can even be 'spoofed'.  Hope this helps anyone who may run into the same problem!

                            1 Reply Last reply Reply Quote 0
                            • johnpozJ
                              johnpoz LAYER 8 Global Moderator
                              last edited by

                              Guess Im going to sound like a dick no matter how I say this - but no shit you would not be able to connect to gmail.com on port 25 - nobody ever suggested that you do such a thing.. I clearly pointed out the MX records for gmail.com – why would you have tried to use gmail.com??

                              But yes as already went over you could send directly to the smtp server for you domain, and would have no need to auth..  But as also went over they corrected the issue and now you can auth to whatever smtp server you want to use to send email to your notification address.

                              An intelligent man is sometimes forced to be drunk to spend time with his fools
                              If you get confused: Listen to the Music Play
                              Please don't Chat/PM me for help, unless mod related
                              SG-4860 24.11 | Lab VMs 2.8, 24.11

                              1 Reply Last reply Reply Quote 0
                              • T
                                TheAngryPenguin
                                last edited by

                                My bad.  I was trying so many different configs – meant to note that my pfSense was unable to auth against smtp.gmail.com:587.

                                1 Reply Last reply Reply Quote 0
                                • P
                                  photonman
                                  last edited by

                                  gmail smtp requires ssl so use port 587 or 465

                                  1 Reply Last reply Reply Quote 0
                                  • First post
                                    Last post
                                  Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.