* [gentoo-user] Trying to debug postgrey
@ 2014-10-22 5:12 Ajai Khattri
2014-10-22 10:30 ` thegeezer
2014-10-24 14:37 ` Michael Orlitzky
0 siblings, 2 replies; 5+ messages in thread
From: Ajai Khattri @ 2014-10-22 5:12 UTC (permalink / raw
To: gentoo-user
Ive been running postgrey for years without any problems but today I
noticed I hadn't gotten email for awhile and realized upon investigation
that postgrey wasnt running so postfix was rejecting mail.
What's maddening is that I can run postgrey quite happily from the command
line in the foregorund, but if I try to use the init script or otherwise
try to daemonize it, it silently crashes:
# /etc/init.d/postgrey start
* Starting Postgrey ...
[ ok ]
# pgrep -af postgrey
Its not running.
The logs dont show anything useful. If I ask the init script to be verbose
I see this:
# /etc/init.d/postgrey start --verbose
* Caching service dependencies ...
[ ok ]
* Starting Postgrey ...
* start-stop-daemon: fopen `/var/run/postgrey.pid': No such file or
directory
[ ok ]
#
which doesn't make much sense.
--
Ajai Khattri
Systems Admin | Web / Mobile Developer
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-user] Trying to debug postgrey
2014-10-22 5:12 [gentoo-user] Trying to debug postgrey Ajai Khattri
@ 2014-10-22 10:30 ` thegeezer
2014-10-22 16:10 ` Ajai Khattri
2014-10-24 14:37 ` Michael Orlitzky
1 sibling, 1 reply; 5+ messages in thread
From: thegeezer @ 2014-10-22 10:30 UTC (permalink / raw
To: gentoo-user
On 22/10/14 06:12, Ajai Khattri wrote:
>
> Ive been running postgrey for years without any problems but today I
> noticed I hadn't gotten email for awhile and realized upon
> investigation that postgrey wasnt running so postfix was rejecting mail.
>
> What's maddening is that I can run postgrey quite happily from the
> command line in the foregorund, but if I try to use the init script or
> otherwise try to daemonize it, it silently crashes:
>
> # /etc/init.d/postgrey start
> * Starting Postgrey ...
> [ ok ]
> # pgrep -af postgrey
>
> Its not running.
>
> The logs dont show anything useful. If I ask the init script to be
> verbose I see this:
>
> # /etc/init.d/postgrey start --verbose
> * Caching service dependencies ...
> [ ok ]
> * Starting Postgrey ...
> * start-stop-daemon: fopen `/var/run/postgrey.pid': No such file or
> directory
> [ ok ]
> #
>
> which doesn't make much sense.
>
>
i had this happen the other day, it's an issue with postgrey + perl 5.18
https://bugs.gentoo.org/show_bug.cgi?id=521912
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-user] Trying to debug postgrey
2014-10-22 10:30 ` thegeezer
@ 2014-10-22 16:10 ` Ajai Khattri
0 siblings, 0 replies; 5+ messages in thread
From: Ajai Khattri @ 2014-10-22 16:10 UTC (permalink / raw
To: gentoo-user
On Wed, 22 Oct 2014, thegeezer wrote:
> i had this happen the other day, it's an issue with postgrey + perl 5.18
> https://bugs.gentoo.org/show_bug.cgi?id=521912
I had a feeling that the recent Perl updates may have borked it. Good to
know its not just me. Just did a sync - hopefully the new packages will
fix it.
--
Ajai Khattri
Systems Admin | Web / Mobile Developer
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-user] Trying to debug postgrey
2014-10-22 5:12 [gentoo-user] Trying to debug postgrey Ajai Khattri
2014-10-22 10:30 ` thegeezer
@ 2014-10-24 14:37 ` Michael Orlitzky
2014-10-24 20:26 ` thegeezer
1 sibling, 1 reply; 5+ messages in thread
From: Michael Orlitzky @ 2014-10-24 14:37 UTC (permalink / raw
To: gentoo-user
On 10/22/2014 01:12 AM, Ajai Khattri wrote:
>
> Ive been running postgrey for years without any problems but today I
> noticed I hadn't gotten email for awhile and realized upon investigation
> that postgrey wasnt running so postfix was rejecting mail.
For what it's worth, recent versions of postfix ship with a
pre-screening daemon called postscreen. It has a suite of tests that
work after the initial greeting, and thus have the "negative" side
effect that the client must be disconnected (temporarily) if it passes:
http://www.postfix.org/POSTSCREEN_README.html#after_220
The main limitation of "after 220 greeting" tests is that a new
client must disconnect after passing these tests (reason: postscreen
is not a proxy). Then the client must reconnect from the same IP
address before it can deliver mail.
In other words, it greylists them. So if you're already running a
separate greylisting daemon, it's safe for you to enable postscreen and
turn on the "deep protocol tests" (see the README). That way you get
postscreen's benefit for free and don't need to worry about running a
separate greylisting daemon any more.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [gentoo-user] Trying to debug postgrey
2014-10-24 14:37 ` Michael Orlitzky
@ 2014-10-24 20:26 ` thegeezer
0 siblings, 0 replies; 5+ messages in thread
From: thegeezer @ 2014-10-24 20:26 UTC (permalink / raw
To: gentoo-user
On 24/10/14 15:37, Michael Orlitzky wrote:
> On 10/22/2014 01:12 AM, Ajai Khattri wrote:
>> Ive been running postgrey for years without any problems but today I
>> noticed I hadn't gotten email for awhile and realized upon investigation
>> that postgrey wasnt running so postfix was rejecting mail.
> For what it's worth, recent versions of postfix ship with a
> pre-screening daemon called postscreen. It has a suite of tests that
> work after the initial greeting, and thus have the "negative" side
> effect that the client must be disconnected (temporarily) if it passes:
>
> http://www.postfix.org/POSTSCREEN_README.html#after_220
>
> The main limitation of "after 220 greeting" tests is that a new
> client must disconnect after passing these tests (reason: postscreen
> is not a proxy). Then the client must reconnect from the same IP
> address before it can deliver mail.
>
> In other words, it greylists them. So if you're already running a
> separate greylisting daemon, it's safe for you to enable postscreen and
> turn on the "deep protocol tests" (see the README). That way you get
> postscreen's benefit for free and don't need to worry about running a
> separate greylisting daemon any more.
>
>
very good, after looking up postscreen i went through a phase of wow,
how did i miss this, and then even went so far to check when all this
came about (2011 it seems)
definitely a good one to know about, for the greylisting and for the
other tests too.
one to investigate more, thanks for the tip !
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2014-10-24 20:27 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-10-22 5:12 [gentoo-user] Trying to debug postgrey Ajai Khattri
2014-10-22 10:30 ` thegeezer
2014-10-22 16:10 ` Ajai Khattri
2014-10-24 14:37 ` Michael Orlitzky
2014-10-24 20:26 ` thegeezer
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox