I’m excited to give Greylisting a try, however my installation failed with:
.. install complete.
… installation failed!
Trying to enable it produces:
socket failed : Address family not supported by protocol
Any tips on how to proceed?
Brian<br><br>Post edited by: webwzrd, at: 2009/04/23 10:07
Hi Brian,
Is there any chance I could log in and take a look?
It could be a few things, and I’ve love to resolve that before everyone else starts running into that issue as well 
If that’s okay – if you’re a Pro user, you can enable remote access using the support module, or barring that, you can simply email me your login details, using eric@virtualmin.com. Include a link to this forum post if you could.
Thanks!
-Eric
Thanks Eric, I just sent you an email.
Okay, it should be working now.
Give that a try and let us know how it goes!
Thanks,
-Eric
Terrific!
I need to explore this a bit. Looks like this is on server wide, is that right? How long before a typical retry?
Brian
Hi Brian,
By default, it is indeed server-wide.
You can play around with the "Whitelisted Clients" and "Whitelisted Recipients" to prevent certain users or servers from being greylisted.
How long the typical retry is depends on the email server in question, but it’s typically between 5 and 20 minutes.
Also, it only happens once. Once a given user emails someone on your server, and successfully gets through the greylisting, that user won’t be greylisted again when emailing that person on your server.
-Eric
Great - Thanks so much for your help Eric.
Brian
Hey Brian,
I’m trying to help Jamie nail down what went awry during your initial attempt to get this working.
How had you gone about installing the "postgrey" daemon? When you clicked the "Enable Greylisting" button, did Virtualmin attempt to install it for you? Or did you do that from the command line?
-Eric
One other quick question…
I can obviously get to the Email Greylising module by clicking "Try it" under New Virtualmin Features, but where is this nested in the left column menu?
It’s in Email Messages -> Email Greylisting.
Also, how was it that you initially did the install of the greylisting software? Had you attempted to manually install it, or was that Virtualmin installing it for you?
-Eric
I was doing the Virtualmin update and discovered Greylisting was part of it. No other attempts to install.
andreychek wrote:
Just reloading the full page should be all that is needed to update menus.
Looks like this is a Virtualmin bug. However, it’s pretty easy to work around … if you get that error, go to Webmin -> System -> Bootup and Shutdown, check the box next to the postgrey action and click the ‘Start’ button.
Then go back to the ‘Email Greylisting’ page, and click the ‘Enable’ button.
Hi guys,
what was the solution to this error?
My installation was ok with no errors, but enabling it gave me also:
Enabling Postgrey at boot time …
socket failed : Address family not supported by protocol
Never mind, started the service and then enabled it again with no errors…
Yeah, there’s a bug in the current version that causes the error you saw.
It’s fixed in the next version, but as you discovered the solution it to just manually start it.
-Eric
It might not be in GPL. But I can’t think of why it wouldn’t be, as mail processing is not an area we differentiate. It’s probably an oversight in the packaging script.
I’ll ping Jamie. It’ll probably be in 3.69.
I’ve also added postgrey to my linking script for the GPL repositories, so the postgrey package will appear there in the next update, as well.
Yes, the Postgrey feature isn’t in the GPL version of Virtualmin yet … but will be in the next release.
I have a couple of questions about this:
When I attempt to install postgrey on my vm gpl now…
I get:
Is this because it’s not in the gpl version yet?
Or should I be able to install it with this, but it won’t actually show up in the panel?
If it should be installable, would it be in the virtualmin.repo?
Thanks, Chris