1 2 3 4 Previous Next 118 Replies Latest reply on Nov 19, 2011 8:09 AM by !Real Go to original post
      • 15. Re: ESVA 1.6
        robert.perry Lurker

        Hi,

        Is it the greylisting that is causing this error?  Also, your configuration sounds similar to mine.  Have you got the 1.6 to work at all, from outside?  Or, is everything failing with that error?

         

        bob

        • 16. Re: ESVA 1.6
          griff158 Novice

          It's works, i commented out in main.cf.

           

          \# smtpd_recipient_restrictions = reject_non_fqdn_recipient,reject_unknown_recipient_domain,

          permit_mynetworks,reject_unauth_destination,check_recipient_access hash:/etc/postfix/recipient_access,check_policy_service inet:127.0.0.1:60000

           

          Just like rooter_c suggested

           

          Message was edited by:

                  ken.cline@hp.com to narrow the display. I split the "reject" between "domain," and "permit_" - it should be just one line

          • 17. Re: ESVA 1.6
            Shamrock Lurker

            Hi Andy

             

            Love your work!

             

            I'm very enthousiastic about the new Mailwatch-feature however I do have 2 problems with it.

             

            My smtp traffic arrives at a webserver in my DMZ that has Trend Micro's IMSS installed. Before you came up with ESVA all mails were relayed to my Exchange server on the intranet directly. So now my Webserver sends al mail to ESVA which in turn relays to my exchange. So far so good; All mails that should arrive, do. When I open Mailwatch and look at the quarantine-list, they're all there but when I try to release a message I get : "Result Messages: Release: message released to xxxxxxx@xxxxx.xxx Error:  N" but nothing happens.

            My second problem has to do with blacklisting. When I try to blacklist a message, the IP-adres of my webserver is blacklisted and not that of the original sender and obviously blocking my webserver would block all my mail.

             

            I hope you can point me in the right direction 'cause I'm really anxious to use it.

            • 18. Re: ESVA 1.6
              bchau1 Lurker

              HI Andy,

               

              First, thanks for this great vm appliance.  1.5 worked great.  I updated to 1.6 but postgrey doesn't seem to work or may be broken.  I start up the service but when I run a status of it, it says, postgrey dead but subsys locked

               

              Hope you can help find out why postgrey isn't working. 

               

              Thanks for all the great work!

              • 19. Re: ESVA 1.6
                yjchung Novice

                Postgrey is crashing at startup.  It's not a port issue as far as I can tell.  I even tried to start it using sockets and still doesn't start.  Guess I'll have to have 1.5.1 running until this is resolved.

                 

                I'm gonna try to reinstall postgrey later today and see what happens.

                • 20. Re: ESVA 1.6
                  griff158 Novice

                  Andy,

                   

                  I love your product (forgot to mention this earlier). Postgrey isn't starting either for me, i tried reinstalling but to no avail. If anyone comes up with a solution it would be greatly appreciated.

                   

                  My workaround for now is that i just commented out the check_policy_service inet:127.0.0.1:60000 in smtpd_recipient_restrictions in the main.cf of postfix

                  • 21. Re: ESVA 1.6
                    andy.mac Hot Shot

                    Sorry I've taken so long to get back to you...

                     

                    I need to have a good look at this - I'll make some time this evening - I have an idea, but i'll let you know when I know for sure.

                     

                    In the mean-time a work-around is to disable postfix by commenting the line that contains check_policy_service inet:127.0.0.1:60000 and uncommenting the alternative version of the line above (that doesn't contain check_policy_service inet:127.0.0.1:60000).

                     

                    The side-effect of this will be that you might get a little more spam through, but a more likely consequence is that you will eat more processor time as MailScanner/SA/Clamav etc processes every inbound message.

                     

                    Sorry again for the inconvenience - It's actually quite embarrassing...

                     

                    -Andy

                    • 22. Re: ESVA 1.6
                      LogIQ Novice

                      Hi Andy,

                       

                      Nothing to be embarrassed over, I bet you will get it working in no time...

                       

                      I am a little confused about your work-around; I can not find a line above the line check_policy_service inet:127.0.0.1:60000 that I can uncomment.

                       

                      \- Ulrich

                      • 23. Re: ESVA 1.6
                        DaleMontgomery Lurker

                        For now I also commented out this line in main.cf  (added the # in the font)

                         

                        \# smtpd_recipient_restrictions = reject_non_fqdn_recipient,reject_unknown_recipient_domain,

                        permit_mynetworks,reject_unauth_destination,check_recipient_access hash:/etc/postfix/recipient_access,check_policy_service inet:127.0.0.1:60000

                         

                        (Just like rooter_c suggested)

                         

                         

                        The quarantine with release option part of 1.6 makes it so much better!

                         

                        Message was edited by:

                                ken.cline@hp.com to narrow the display. I split the "reject" between "domain," and "permit_" - it should be just one line

                        • 24. Re: ESVA 1.6
                          emporio Novice

                          I did same thing and its working fine>

                           

                          Andy 1.6 is great. I haven't got to explore it fully but quarantine, reporting, graph and rest is awesome. Very professional

                           

                          thx gain for ESVA, it rocks

                          -emp

                          • 25. Re: ESVA 1.6
                            rooter_c Novice

                            I agree It Rocks!

                            • 26. Re: ESVA 1.6
                              LogIQ Novice

                              Hi Andy,

                               

                              While doing some testing og ESVA 1.6 I have encountered some problems. I have been sending test-emails from my hotmail, my yahoo-mail and from my gmail, and they do not arrive in my mailbox.

                              My Hotmail was caught by ESVA, so I whitelisted it and then I received the e-mail.

                              The e-mails from the other two are listed as clean in MailWatch, although the do not get through to my mailbox.

                              I am suspecting it beeing because I forward all mails from the receiving mailbox to another, but should that really cause a problem?

                               

                              Also quite a few e-mail are believed to be clean by ESVA, but are in fact spam. I would say that 1 out of every 5-8 spam are found clean, is there a way to get it more precise?

                              Could I teach ESVA manually to get better? I have been running ASSP, and I have some 50000 spam and about 10000 ham mails there, could I feed those to ESVA to make it better?

                               

                              ESVA is a very nice product, but I need it to be more precise before putting it into production.

                               

                              Also I have a suggestion or a request for a solution. I want to run 2 ESVA on 2 different servers in 2 different datacenters, one for MX 10, and another for MX20 for failover.

                              Is there a way to replicate all the users settings and the SA database etc. between 2 servers automatically?

                               

                              Thx Andy for doing a good job!

                               

                              \- Ulrich

                              • 27. Re: ESVA 1.6
                                emporio Novice

                                Is anyone using ESVA also as Outgoing Mail gateway?

                                • 28. Re: ESVA 1.6
                                  rooter_c Novice

                                  I just found another issue, the user gets a spam notification email, but when they click the link to release the mail, it sends it back to the original sender instead of releasing it to the user.  I can release it manually ok?  Where do I look for the config for that function?

                                   

                                  ta.

                                  • 29. Re: ESVA 1.6
                                    rooter_c Novice

                                    Actually, I just tried it on another email and it worked ok?  Must be something in the message format maybe?

                                     

                                    ta

                                    1 2 3 4 Previous Next