# Postgrey - should it be using a Unix Socket

**URL:** <https://forum.virtualmin.com/t/postgrey-should-it-be-using-a-unix-socket/126946>\
**Category:** Virtualmin\
**Created:** [May 26, 2024, 10:34am UTC](https://forum.virtualmin.com/t/postgrey-should-it-be-using-a-unix-socket/126946 "2024-05-26T10:34:25Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![shoulders](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/shoulders/32/10086_2.png) [@shoulders](https://forum.virtualmin.com/u/shoulders)\
**Post date:** [May 26, 2024, 10:34am UTC](https://forum.virtualmin.com/t/postgrey-should-it-be-using-a-unix-socket/126946/1 "2024-05-26T10:34:25Z")

</div>

| SYSTEM INFORMATION | |
| --- | --- |
| OS type and version | Ubuntu Linux 22.04.4 |
| Webmin version | 2.111 |
| Usermin version | 2.010 |
| Virtualmin version | 7.10.0 |
| Theme version | 21.10 |
| Package updates | 85 package updates are available |

My understanding it is better to use a unix socket where possible (Windows Guy Alert).

When you enable greylisting `Virtualmin --> Email Settings --> Email Greylisting` the following policy:

`check_policy_service inet:127.0.0.1:10023`

gets added to :

`Webmin --> Servers --> Postfix Mail Server --> SMTP Server Options --> Restrictions on recipient addresses: `

I have come across these policy socket declarations people are using instead:

```auto
check_policy_service unix:/var/spool/postfix/postgrey/socket 
check_policy_service unix:postgrey/socket

```

- Are these a better way to do things?
- Does using the `127.0.0.1` method allow for better compatibility between the Linux distros?

---

<div class="post-metadata">

**Author:** ![Joe](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/joe/32/9_2.png) [@Joe](https://forum.virtualmin.com/u/Joe)\
**Post date:** [May 28, 2024, 2:39am UTC](https://forum.virtualmin.com/t/postgrey-should-it-be-using-a-unix-socket/126946/2 "2024-05-28T02:39:05Z")

</div>

Sockets are generally better. I don’t know why we use a port. This is pretty old code.

It’s not about compatibility; all Linux versions going back many years support named sockets. @Jamie is there a reason other than historical baggage we’re using a port for the greylisting policy server rather than a named socket? Maybe it’s what ships in the package?

---

<div class="post-metadata">

**Author:** ![Jamie](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/jamie/32/8589_2.png) [@Jamie](https://forum.virtualmin.com/u/Jamie)\
**Post date:** [May 28, 2024, 5:07am UTC](https://forum.virtualmin.com/t/postgrey-should-it-be-using-a-unix-socket/126946/3 "2024-05-28T05:07:08Z")

</div>

Currently we just follow the default port as set in `/etc/default/postgrey` by the distro packages, but if that’s not found we do fall back to using a TCP port. We could change that though…

---

<div class="post-metadata">

**Author:** ![Joe](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/joe/32/9_2.png) [@Joe](https://forum.virtualmin.com/u/Joe)\
**Post date:** [May 28, 2024, 5:13am UTC](https://forum.virtualmin.com/t/postgrey-should-it-be-using-a-unix-socket/126946/4 "2024-05-28T05:13:47Z")

</div>

I can’t really think of any security reason it’d be necessary/useful, so I don’t think it’s urgent, But doing things in the usual way (whatever the project maintainers recommend or what’s the default in the package, when reasonable) is always good.

---

<div class="post-metadata">

**Author:** ![shoulders](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/shoulders/32/10086_2.png) [@shoulders](https://forum.virtualmin.com/u/shoulders)\
**Post date:** [May 28, 2024, 6:26am UTC](https://forum.virtualmin.com/t/postgrey-should-it-be-using-a-unix-socket/126946/5 "2024-05-28T06:26:09Z")

</div>

Shall I do a github issue (another one 😄 ) so it can be stuck on this list at some point.

---

<div class="post-metadata">

**Author:** ![Joe](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/joe/32/9_2.png) [@Joe](https://forum.virtualmin.com/u/Joe)\
**Post date:** [May 28, 2024, 7:49am UTC](https://forum.virtualmin.com/t/postgrey-should-it-be-using-a-unix-socket/126946/6 "2024-05-28T07:49:35Z")

</div>

I think this one is mostly a preference thing, I’m unaware of security or performance concerns here; a port and a named socket behave the same. The only benefit to a socket is a user can’t squat on it…but that’s unlikely to happen with a service that starts at boot, and there are no security implications I can think of to doing so even if they could.

---

<div class="post-metadata">

**Author:** ![Shirehosting](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/s/eb8c5e/32.png) [@Shirehosting](https://forum.virtualmin.com/u/Shirehosting)\
**Post date:** [May 28, 2024, 9:46am UTC](https://forum.virtualmin.com/t/postgrey-should-it-be-using-a-unix-socket/126946/7 "2024-05-28T09:46:26Z")

</div>

Yes please …

---

<div class="post-metadata">

**Author:** ![Joe](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/joe/32/9_2.png) [@Joe](https://forum.virtualmin.com/u/Joe)\
**Post date:** [May 28, 2024, 7:43pm UTC](https://forum.virtualmin.com/t/postgrey-should-it-be-using-a-unix-socket/126946/8 "2024-05-28T19:43:50Z")

</div>

I think I’m missing something. Why would this be an important/urgent change?

---

<div class="post-metadata">

**Author:** ![shoulders](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/shoulders/32/10086_2.png) [@shoulders](https://forum.virtualmin.com/u/shoulders)\
**Post date:** [May 28, 2024, 8:26pm UTC](https://forum.virtualmin.com/t/postgrey-should-it-be-using-a-unix-socket/126946/9 "2024-05-28T20:26:53Z")

</div>

For me it is not important, I just wanted to point it out just incase it was. So I am all good.

---

<div class="post-metadata">

**Author:** ![Shirehosting](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/s/eb8c5e/32.png) [@Shirehosting](https://forum.virtualmin.com/u/Shirehosting)\
**Post date:** [May 29, 2024, 1:05am UTC](https://forum.virtualmin.com/t/postgrey-should-it-be-using-a-unix-socket/126946/10 "2024-05-29T01:05:13Z")

</div>

Howdi Joe

Its not urgent nor important, but it should be listed that way when you get sick of working so hard on the cloudmin install script you promised us 2 years ago, you have a record of things that should be looked at given extra time.

That is why you have a github page isn’t it so people can list things that need/want to be changed ?

Thanks  
Michael

---

<div class="post-metadata">

**Author:** ![Shirehosting](https://cdn.forum.virtualmin.com/letter_avatar_proxy/v4/letter/s/eb8c5e/32.png) [@Shirehosting](https://forum.virtualmin.com/u/Shirehosting)\
**Post date:** [May 29, 2024, 1:06am UTC](https://forum.virtualmin.com/t/postgrey-should-it-be-using-a-unix-socket/126946/11 "2024-05-29T01:06:13Z")

</div>

Post it shoulders good to have a list of things to be done.

---

<div class="post-metadata">

**Author:** ![shoulders](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/shoulders/32/10086_2.png) [@shoulders](https://forum.virtualmin.com/u/shoulders)\
**Post date:** [May 29, 2024, 7:16am UTC](https://forum.virtualmin.com/t/postgrey-should-it-be-using-a-unix-socket/126946/12 "2024-05-29T07:16:20Z")

</div>

Does using a Unix socket skip using the TCP/IP stack?

---

<div class="post-metadata">

**Author:** ![Stegan](https://cdn.forum.virtualmin.com/user_avatar/forum.virtualmin.com/stegan/32/6860_2.png) [@Stegan](https://forum.virtualmin.com/u/Stegan)\
**Post date:** [May 29, 2024, 7:40am UTC](https://forum.virtualmin.com/t/postgrey-should-it-be-using-a-unix-socket/126946/13 "2024-05-29T07:40:38Z")

</div>

> [@Shirehosting](#):
>
> need/want

or even “would like” someday when you have nothing more adventurous to do with your life?

---

<div class="post-metadata">

**Author:** ![system](https://cdn.forum.virtualmin.com/uploads/default/original/2X/c/cd96d761e326db4b2bef94886a639109bd7a8e76.svg) [@system](https://forum.virtualmin.com/u/system)\
**Post date:** [July 28, 2024, 7:41am UTC](https://forum.virtualmin.com/t/postgrey-should-it-be-using-a-unix-socket/126946/14 "2024-07-28T07:41:27Z")

</div>

Closed on July 28, 2024, 7:41am UTC

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
