Re: 'pkg upgrade -f spamassassin' stops but doesn't restart spamd

[Michael Grimm]

Kevin Oberman  wrote:
> On Sun, Jan 7, 2018 at 7:10 AM, Miroslav Lachman <000.f...@quip.cz> wrote:

>> There are no consensus about what services should do on deinstall or
>> upgrade. That's why there is such a mess in ports / packages.
>> Some did nothing (my preferred way), some stop (but did not start) the
>> service,
[…]
> Beg pardon, but I am aware of this being discussed twice on this list and
> both times there was a clear consensus in both cases that it was
> unacceptable or a port/package upgrade to touch running daemons.  There
> were arguments that some port might make changes in underlying files that
> could break a daemon in some way, though I can't recall any actual examples.
> 
> The only real argument was that leaving a daemon with a serious
> vulnerability running was not acceptable. A competent admin should never
> let this happen, but I'm sure it has.

FTR: I have filed PR 225030 on this.

Thanks and regards,
Michael


___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: 'pkg upgrade -f spamassassin' stops but doesn't restart spamd

[Miroslav Lachman]

Eugene Grosbein wrote on 01/08/2018 13:56:

08.01.2018 18:11, Miroslav Lachman wrote:


PRs are false alibi. Some of my PRs are open for more than 10 years.


So were mine when I could not commit fixes myself. This is not excuse to be 
lazy and not make another one.


For all erroneous port there must be will on maintainer and committer side.
And if "they" think this is not a bug


If we have written policy (and we have in this case), and upgrade really break 
things,
sane committer will not think "this is not a bug".

Again, do you have a PR with "how-to-repeat" scenario and a patch,
so I could take it?


OK, let's move on. I can open PR if you are willing to help and commit some 
fixes. But can we first talk


Relevant discussion should better take place in the PR itself so it's not lost
and easier to point to when asking corresponding parties, f.e. portmgr@

You may open PR without patch too, you know. But it needs clear description of 
the problem
and "how-to-repeat".


I created PR 225005
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=225005

Let me know if I should add some more informations.

Kind regards
Miroslav Lachman

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: 'pkg upgrade -f spamassassin' stops but doesn't restart spamd

[Eugene Grosbein]

08.01.2018 18:11, Miroslav Lachman wrote:

>>> PRs are false alibi. Some of my PRs are open for more than 10 years.
>>
>> So were mine when I could not commit fixes myself. This is not excuse to be 
>> lazy and not make another one.
>>
>>> For all erroneous port there must be will on maintainer and committer side.
>>> And if "they" think this is not a bug
>>
>> If we have written policy (and we have in this case), and upgrade really 
>> break things,
>> sane committer will not think "this is not a bug".
>>
>> Again, do you have a PR with "how-to-repeat" scenario and a patch,
>> so I could take it?
> 
> OK, let's move on. I can open PR if you are willing to help and commit some 
> fixes. But can we first talk 

Relevant discussion should better take place in the PR itself so it's not lost
and easier to point to when asking corresponding parties, f.e. portmgr@

You may open PR without patch too, you know. But it needs clear description of 
the problem
and "how-to-repeat".

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: 'pkg upgrade -f spamassassin' stops but doesn't restart spamd

[Miroslav Lachman]

Eugene Grosbein wrote on 01/07/2018 22:12:

08.01.2018 4:00, Miroslav Lachman wrote:


PRs are false alibi. Some of my PRs are open for more than 10 years.


So were mine when I could not commit fixes myself. This is not excuse to be 
lazy and not make another one.


For all erroneous port there must be will on maintainer and committer side.
And if "they" think this is not a bug


If we have written policy (and we have in this case), and upgrade really break 
things,
sane committer will not think "this is not a bug".

Again, do you have a PR with "how-to-repeat" scenario and a patch,
so I could take it?


OK, let's move on. I can open PR if you are willing to help and commit 
some fixes. But can we first talk about what and how should be done? 
What is the right way to handle Apache module install / deinstall / 
upgrade? Because some modules are using code from Mk/bsd.apache.mk which 
do the wrong thing:


.if defined(AP_FAST_BUILD)
.if !target(ap-gen-plist)
_USES_build+=   490:ap-gen-plist
ap-gen-plist:
.if defined(AP_GENPLIST)
.   if !exists(${PLIST})
@${ECHO} "===>  Generating apache plist"
@${ECHO} "%%APACHEMODDIR%%/%%AP_MODULE%%" >> ${PLIST}
@${ECHO} "@postexec %D/sbin/apxs -e ${AP_MOD_EN} -n %%AP_NAME%% 
%D/%F" >> ${PLIST}
@${ECHO} "@postunexec ${SED} -i '' -E 
'/LoadModule[[:blank:]]+%%AP_NAME%%_module/d' 
%D/%%APACHEETCDIR%%/httpd.conf" >> ${PLIST}
@${ECHO} "@postunexec echo \"Don't forget to remove all 
${MODULENAME}-related directives in your httpd.conf\"">> ${PLIST}

.   endif
.endif
.endif

Some modules did similar thing in Makefile (or they did in the past).

1) Should install put something in to httpd.conf?

2) Should deinstall or upgrade remove something from httpd.conf?

3) Or as I suggested here 
https://lists.freebsd.org/pipermail/freebsd-ports/2017-October/110725.html 
should each module install own sample file in apache24/modules.d/?


Miroslav Lachman

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: 'pkg upgrade -f spamassassin' stops but doesn't restart spamd

[Eugene Grosbein]

08.01.2018 4:00, Miroslav Lachman wrote:

> PRs are false alibi. Some of my PRs are open for more than 10 years.

So were mine when I could not commit fixes myself. This is not excuse to be 
lazy and not make another one.

> For all erroneous port there must be will on maintainer and committer side.
> And if "they" think this is not a bug

If we have written policy (and we have in this case), and upgrade really break 
things,
sane committer will not think "this is not a bug".

Again, do you have a PR with "how-to-repeat" scenario and a patch,
so I could take it?

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: 'pkg upgrade -f spamassassin' stops but doesn't restart spamd

[Miroslav Lachman]

Eugene Grosbein wrote on 2018/01/07 21:47:

08.01.2018 3:36, Miroslav Lachman wrote:


There IS consensus on modifying config files while upgrade and it is written in 
our Porter's Handbook:
only unmodified files may be changes with upgrade. Any other behaviour is a bug 
that should be fixed.


If it is that simple then tell me how it is possible that for many years there 
are repetitive discussions
and many ports with many commits violating this "rule"?


Because:

1) People are lazy and make errors creating ports violating Porter's handbook 
instructions;
2) People are lazy and do not create formal Problem Reports even when they are 
annoyed
hoping that SomeOne (TM) would do that for them.

Where are your PRs?


PRs are false alibi. Some of my PRs are open for more than 10 years.
PRs doesn't solve anything even if they have patches. That's why I tried 
to discuss it publicly. For all erroneous port there must be will on 
maintainer and committer side. And if "they" think this is not a bug, 
than why should I spent my time filling another PR which will be left 
open indefinitely. I will let someone else to fight windmills.
Unluckily it is simpler (for me) to maintain private changes to ports 
tree in local VCS.


Miroslav Lachman

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: 'pkg upgrade -f spamassassin' stops but doesn't restart spamd

[Eugene Grosbein]

08.01.2018 3:36, Miroslav Lachman wrote:

>> There IS consensus on modifying config files while upgrade and it is written 
>> in our Porter's Handbook:
>> only unmodified files may be changes with upgrade. Any other behaviour is a 
>> bug that should be fixed.
> 
> If it is that simple then tell me how it is possible that for many years 
> there are repetitive discussions
> and many ports with many commits violating this "rule"?

Because:

1) People are lazy and make errors creating ports violating Porter's handbook 
instructions;
2) People are lazy and do not create formal Problem Reports even when they are 
annoyed
hoping that SomeOne (TM) would do that for them.

Where are your PRs?

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: 'pkg upgrade -f spamassassin' stops but doesn't restart spamd

[Miroslav Lachman]

Eugene Grosbein wrote on 2018/01/07 17:18:

07.01.2018 22:10, Miroslav Lachman wrote:


I am following 11-STABLE and therefore upgrading my system quite frequently. 
During that process I do recompile all ports installed by poudriere and upgrade 
all ports after reboot.

There are no consensus about what services should do on deinstall or upgrade. 
That's why there is such a mess in ports / packages.
Some did nothing (my preferred way), some stop (but did not start) the service,
some modify user edited config files (removing / disabling modules in 
httpd.conf so Apache is broken on each upgrade of module(s)).


There IS consensus on modifying config files while upgrade and it is written in 
our Porter's Handbook:
only unmodified files may be changes with upgrade. Any other behaviour is a bug 
that should be fixed.


If it is that simple then tell me how it is possible that for many years 
there are repetitive discussions and many ports with many commits 
violating this "rule"?
If it is written somewhere how any committer can allow ports with those 
problems?


For example: "requesting policy for Apache module installation 
(LoadModule manipulation)"

https://lists.freebsd.org/pipermail/freebsd-ports/2017-October/110725.html

Miroslav Lachman
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: 'pkg upgrade -f spamassassin' stops but doesn't restart spamd

[Kevin Oberman]

On Sun, Jan 7, 2018 at 7:10 AM, Miroslav Lachman <000.f...@quip.cz> wrote:

>
> There are no consensus about what services should do on deinstall or
> upgrade. That's why there is such a mess in ports / packages.
> Some did nothing (my preferred way), some stop (but did not start) the
> service, some modify user edited config files (removing / disabling modules
> in httpd.conf so Apache is broken on each upgrade of module(s)).
>
> Miroslav Lachman


Beg pardon, but I am aware of this being discussed twice on this list and
both times there was a clear consensus in both cases that it was
unacceptable or a port/package upgrade to touch running daemons.  There
were arguments that some port might make changes in underlying files that
could break a daemon in some way, though I can't recall any actual examples.

The only real argument was that leaving a daemon with a serious
vulnerability running was not acceptable. A competent admin should never
let this happen, but I'm sure it has.
--
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkober...@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: 'pkg upgrade -f spamassassin' stops but doesn't restart spamd

[Eugene Grosbein]

07.01.2018 22:10, Miroslav Lachman wrote:

>> I am following 11-STABLE and therefore upgrading my system quite frequently. 
>> During that process I do recompile all ports installed by poudriere and 
>> upgrade all ports after reboot.
> There are no consensus about what services should do on deinstall or upgrade. 
> That's why there is such a mess in ports / packages.
> Some did nothing (my preferred way), some stop (but did not start) the 
> service,
> some modify user edited config files (removing / disabling modules in 
> httpd.conf so Apache is broken on each upgrade of module(s)).

There IS consensus on modifying config files while upgrade and it is written in 
our Porter's Handbook:
only unmodified files may be changes with upgrade. Any other behaviour is a bug 
that should be fixed.

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: 'pkg upgrade -f spamassassin' stops but doesn't restart spamd

[Miroslav Lachman]

Michael Grimm wrote on 2018/01/07 15:31:

Hi,

I am following 11-STABLE and therefore upgrading my system quite frequently. 
During that process I do recompile all ports installed by poudriere and upgrade 
all ports after reboot.

Today I stumbled over an IMHO weird behaviour of the spamassassin's 
installation process, that stops a running spamd daemon without restarting. 
Even worse, the user will not be informed about that procedure:

mail> /usr/local/etc/rc.d/sa-spamd status
    spamd is running as pid 13859.

mail> pkg upgrade -fy spamassassin
Updating poudriere repository catalogue...
poudriere repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be REINSTALLED:
spamassassin-3.4.1_11 [poudriere]

Number of packages to be reinstalled: 1
[mail] [1/1] Reinstalling spamassassin-3.4.1_11...
===> Creating groups.
Using existing group 'spamd'.
===> Creating users
Using existing user 'spamd'.
[mail] [1/1] Extracting spamassassin-3.4.1_11: 100%
[*]     Stopping spamd.
Waiting for PIDS: 13859, 13859.
You may need to manually remove 
/usr/local/etc/mail/spamassassin/local.cf if it is no longer needed.
Message from spamassassin-3.4.1_11:


==

You should complete the following post-installation tasks:

1) Read /usr/local/share/doc/spamassassin/INSTALL
   and /usr/local/share/doc/spamassassin/UPGRADE
   BEFORE enabling SpamAssassin for important changes

2) Edit the configuration in /usr/local/etc/mail/spamassassin,
   in particular /usr/local/etc/mail/spamassassin/init.pre
   You may get lots of annoying (but harmless) error messages
   if you skip this step.

    3) To run spamd, add the following to /etc/rc.conf:
   spamd_enable="YES"

4) If this is a new installation, you should run sa-update
   and sa-compile. If this isn't a new installation, you
   should probably run those commands on a regular basis
   anyway.

5) Install mail/spamass-rules if you want some third-party
   spam-catching rulesets

SECURITY NOTE:
    By default, spamd runs as root (the AS_ROOT option). If you wish
to change this, add the following to /etc/rc.conf:

    spamd_flags="-u spamd -H /var/spool/spamd"


==

    mail> /usr/local/etc/rc.d/sa-spamd status
spamd is not running.

Ok, one might notice that the daemon has been stopped [*], but section "You should 
complete …" fails to mention, that one needs to restart the daemon after upgrading.


Please correct me if I am wrong but I have always been under the impression 
that stopping a daemon whilst upgrading violates conventions?


There are no consensus about what services should do on deinstall or 
upgrade. That's why there is such a mess in ports / packages.
Some did nothing (my preferred way), some stop (but did not start) the 
service, some modify user edited config files (removing / disabling 
modules in httpd.conf so Apache is broken on each upgrade of module(s)).


Miroslav Lachman

___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

'pkg upgrade -f spamassassin' stops but doesn't restart spamd

[Michael Grimm]

Hi,

I am following 11-STABLE and therefore upgrading my system quite frequently. 
During that process I do recompile all ports installed by poudriere and upgrade 
all ports after reboot.

Today I stumbled over an IMHO weird behaviour of the spamassassin's 
installation process, that stops a running spamd daemon without restarting. 
Even worse, the user will not be informed about that procedure:

mail> /usr/local/etc/rc.d/sa-spamd status
    spamd is running as pid 13859.

mail> pkg upgrade -fy spamassassin
Updating poudriere repository catalogue...
poudriere repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The following 1 package(s) will be affected (of 0 checked):

Installed packages to be REINSTALLED:
spamassassin-3.4.1_11 [poudriere]

Number of packages to be reinstalled: 1
[mail] [1/1] Reinstalling spamassassin-3.4.1_11...
===> Creating groups.
Using existing group 'spamd'.
===> Creating users
Using existing user 'spamd'.
[mail] [1/1] Extracting spamassassin-3.4.1_11: 100%
[*]     Stopping spamd.
Waiting for PIDS: 13859, 13859.
You may need to manually remove 
/usr/local/etc/mail/spamassassin/local.cf if it is no longer needed.
Message from spamassassin-3.4.1_11:


==

You should complete the following post-installation tasks:

1) Read /usr/local/share/doc/spamassassin/INSTALL
   and /usr/local/share/doc/spamassassin/UPGRADE
   BEFORE enabling SpamAssassin for important changes

2) Edit the configuration in /usr/local/etc/mail/spamassassin,
   in particular /usr/local/etc/mail/spamassassin/init.pre
   You may get lots of annoying (but harmless) error messages
   if you skip this step.

    3) To run spamd, add the following to /etc/rc.conf:
   spamd_enable="YES"

4) If this is a new installation, you should run sa-update
   and sa-compile. If this isn't a new installation, you
   should probably run those commands on a regular basis
   anyway.

5) Install mail/spamass-rules if you want some third-party
   spam-catching rulesets

SECURITY NOTE:
    By default, spamd runs as root (the AS_ROOT option). If you wish
to change this, add the following to /etc/rc.conf:

    spamd_flags="-u spamd -H /var/spool/spamd"


==

    mail> /usr/local/etc/rc.d/sa-spamd status
spamd is not running.

Ok, one might notice that the daemon has been stopped [*], but section "You 
should complete …" fails to mention, that one needs to restart the daemon after 
upgrading.


Please correct me if I am wrong but I have always been under the impression 
that stopping a daemon whilst upgrading violates conventions?

Thanks and with kind regards,
Michael





___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: Spamd

[Matthew D. Fuller]

On Fri, Apr 04, 2014 at 08:52:29AM +0300 I heard the voice of
Esa Karkkainen, and lo! it spake thus:
 On Thu, Apr 03, 2014 at 09:53:10AM +0200, Jos Chrispijn wrote:
 Since my last Spamd port update I get this error when I try to start
 
 Same here, I've had this happen every time when I update
 spamassassin, using portmaster, which is using pkgng.

pkg-plist in spamassassin includes

@unexec rm -rf /var/run/spamd 21 /dev/null || true

so removing the package will blow away the pid file.


-- 
Matthew Fuller (MF4839)   |  fulle...@over-yonder.net
Systems/Network Administrator |  http://www.over-yonder.net/~fullermd/
   On the Internet, nobody can hear you scream.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Spamd

[Jos Chrispijn]

   Since my last Spamd port update I get this error when I try to start
   spamd:
   spamd not running? (check /var/run/spamd/spamd.pid).
   Starting spamd.
   server socket setup failed, retry 1: spamd: could not create
   IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
   server socket setup failed, retry 2: spamd: could not create
   IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
   server socket setup failed, retry 3: spamd: could not create
   IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
   server socket setup failed, retry 4: spamd: could not create
   IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
   server socket setup failed, retry 5: spamd: could not create
   IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
   server socket setup failed, retry 6: spamd: could not create
   IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
   server socket setup failed, retry 7: spamd: could not create
   IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
   server socket setup failed, retry 8: spamd: could not create
   IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
   server socket setup failed, retry 9: spamd: could not create
   IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
   spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783:
   Address already in use
   ./sa-spamd: WARNING: failed to start spamd
   SpamAssassin version 3.4.0
 running on Perl version 5.16.3
   nmap -v localhost:
   Starting Nmap 6.40 ( [1]http://nmap.org ) at 2014-04-03 09:44 CEST
   Initiating SYN Stealth Scan at 09:44
   Scanning localhost (127.0.0.1) [1000 ports]
   Discovered open port 25/tcp on 127.0.0.1
   Discovered open port 587/tcp on 127.0.0.1
   Discovered open port 993/tcp on 127.0.0.1
   Discovered open port 995/tcp on 127.0.0.1
   Increasing send delay for 127.0.0.1 from 0 to 5 due to 11 out of 21
   dropped probes since last increase.
   Discovered open port 143/tcp on 127.0.0.1
   Discovered open port 3306/tcp on 127.0.0.1
   Discovered open port 110/tcp on 127.0.0.1
Discovered open port 783/tcp on 127.0.0.1 
   Increasing send delay for 127.0.0.1 from 5 to 10 due to 43 out of 142
   dropped probes since last increase.
   Increasing send delay for 127.0.0.1 from 10 to 20 due to
   max_successful_tryno increase to 4
   --- cut ---
   /letc/services file no port 783 reserved:
   multiling-http  777/tcp#Multiling HTTP
   multiling-http  777/udp#Multiling HTTP
   wpgs780/tcp
   wpgs780/udp
   mdbs_daemon 800/tcp
   mdbs_daemon 800/udp
   Can you tell me if this is a ports issue or how I could solve this?
   Thanks!
   Jos

References

   1. http://nmap.org/
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Spamd

[Sergey V. Dyatko]

В Thu, 03 Apr 2014 09:53:10 +0200
Jos Chrispijn po...@webrz.net пишет:

Since my last Spamd port update I get this error when I try to start
spamd:
spamd not running? (check /var/run/spamd/spamd.pid).
Starting spamd.
server socket setup failed, retry 1: spamd: could not create
IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 2: spamd: could not create
IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 3: spamd: could not create
IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 4: spamd: could not create
IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 5: spamd: could not create
IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 6: spamd: could not create
IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 7: spamd: could not create
IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 8: spamd: could not create
IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 9: spamd: could not create
IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
spamd: could not create IO::Socket::IP socket on [127.0.0.1]:783:
Address already in use
./sa-spamd: WARNING: failed to start spamd
SpamAssassin version 3.4.0
  running on Perl version 5.16.3
nmap -v localhost:

use `sockstat -l4 -p783` instead.
It show you what user-command-pid listen that port 

Starting Nmap 6.40 ( [1]http://nmap.org ) at 2014-04-03 09:44 CEST
Initiating SYN Stealth Scan at 09:44
Scanning localhost (127.0.0.1) [1000 ports]
Discovered open port 25/tcp on 127.0.0.1
Discovered open port 587/tcp on 127.0.0.1
Discovered open port 993/tcp on 127.0.0.1
Discovered open port 995/tcp on 127.0.0.1
Increasing send delay for 127.0.0.1 from 0 to 5 due to 11 out of 21
dropped probes since last increase.
Discovered open port 143/tcp on 127.0.0.1
Discovered open port 3306/tcp on 127.0.0.1
Discovered open port 110/tcp on 127.0.0.1
 Discovered open port 783/tcp on 127.0.0.1 
Increasing send delay for 127.0.0.1 from 5 to 10 due to 43 out of 142
dropped probes since last increase.
Increasing send delay for 127.0.0.1 from 10 to 20 due to
max_successful_tryno increase to 4
--- cut ---
/letc/services file no port 783 reserved:
multiling-http  777/tcp#Multiling HTTP
multiling-http  777/udp#Multiling HTTP
wpgs780/tcp
wpgs780/udp
mdbs_daemon 800/tcp
mdbs_daemon 800/udp
Can you tell me if this is a ports issue or how I could solve this?
Thanks!
Jos
 
 References
 
1. http://nmap.org/
 ___
 freebsd-ports@freebsd.org mailing list
 http://lists.freebsd.org/mailman/listinfo/freebsd-ports
 To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org




--
wbr, tiger

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Spamd

[Jos Chrispijn]

Sergey V. Dyatko:
use `sockstat -l4 -p783` instead. It show you what user-command-pid 
listen that port


USER COMMANDPID   FD PROTO  LOCAL ADDRESS FOREIGN ADDRESS
root perl   1404  5  tcp4   127.0.0.1:783 *:*
root perl   1403  5  tcp4   127.0.0.1:783 *:*
root perl   1402  5  tcp4   127.0.0.1:783 *:*

Is this Perl itself or is this a program that uses Perl for this port?

wbr, Jos


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Spamd

[Jos Chrispijn]

Sergey V. Dyatko:
use `sockstat -l4 -p783` instead. It show you what user-command-pid 
listen that port


I killed process 1402 and started Spamd. That did the trick, thanks!

I am very curious:

a. why Perl occupied that port.
Tried to retrieve this information from logfiles in /var/log but no 
success. May that be an inward traffic issue on port 783 that triggered 
Perl and kept it occupied for Spamd?


b. Is it unsafe or possible to let spamd use another port if 783 is 
occupied. May that be a security risk?


T|hanks for your help,
Jos Chrispijn


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Spamd

[RW]

On Thu, 03 Apr 2014 14:48:25 +0200
Jos Chrispijn wrote:

 
 Sergey V. Dyatko:
  use `sockstat -l4 -p783` instead. It show you what user-command-pid 
  listen that port
 
 USER COMMANDPID   FD PROTO  LOCAL ADDRESS FOREIGN
 ADDRESS root perl   1404  5  tcp4   127.0.0.1:783 *:*
 root perl   1403  5  tcp4   127.0.0.1:783 *:*
 root perl   1402  5  tcp4   127.0.0.1:783 *:*
 
 Is this Perl itself or is this a program that uses Perl for this port?

It'll be  the spamassassin master process and default of two children.

By the look of it the rc.d script couldn't find a spamassassin perl
process that matched the PID in the pid file so couldn't shut the old
version down before starting the new. This is commonly because the pid
file isn't writeable, but using port 783 implies that it started as
root.

Check that the current pid file contains a correct value.  
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Spamd

[Matthew Seaman]

On 04/03/14 13:57, Jos Chrispijn wrote:
 Sergey V. Dyatko:
 use `sockstat -l4 -p783` instead. It show you what user-command-pid
 listen that port
 
 I killed process 1402 and started Spamd. That did the trick, thanks!
 
 I am very curious:
 
 a. why Perl occupied that port.
 Tried to retrieve this information from logfiles in /var/log but no
 success. May that be an inward traffic issue on port 783 that triggered
 Perl and kept it occupied for Spamd?
 
 b. Is it unsafe or possible to let spamd use another port if 783 is
 occupied. May that be a security risk?

Assuming 'spamd' here is part of spamassassin then it is a daemon
written in perl, and the command name will show up as perl in sockstat
listings.

In my experience, it is quite common for this daemon to end up running
under a different PID than the one recorded under /var/run -- so the
system initialization scripts 'sa-spamd' think it isn't running, and
then you get the fight over access to port 783 the OP saw.  Killing the
processes using port 783 and restarting spamd should work.

The situation is complicated by the /other/ spamd -- which is an OpenBSD
thing which works via pf to implement greylisting, teergrube and various
other anti-spam things.  Meaning the SpamAssassin 'sa-spamd' startup
script can't simply kill anything called spamd.

Cheers,

Matthew




signature.asc
Description: OpenPGP digital signature

Re: Spamd

[RW]

On Thu, 03 Apr 2014 15:49:47 +0100
Matthew Seaman wrote:

 On 04/03/14 13:57, Jos Chrispijn wrote:
  Sergey V. Dyatko:
  use `sockstat -l4 -p783` instead. It show you what user-command-pid
  listen that port
  
  I killed process 1402 and started Spamd. That did the trick, thanks!
  
  I am very curious:
  
  a. why Perl occupied that port.
  Tried to retrieve this information from logfiles in /var/log but no
  success. May that be an inward traffic issue on port 783 that
  triggered Perl and kept it occupied for Spamd?
  
  b. Is it unsafe or possible to let spamd use another port if 783 is
  occupied. May that be a security risk?
 
 Assuming 'spamd' here is part of spamassassin then it is a daemon
 written in perl, and the command name will show up as perl in sockstat
 listings.
 
 In my experience, it is quite common for this daemon to end up running
 under a different PID than the one recorded under /var/run -- so the
 system initialization scripts 'sa-spamd' think it isn't running, and
 then you get the fight over access to port 783 the OP saw.  Killing
 the processes using port 783 and restarting spamd should work.
 
 The situation is complicated by the /other/ spamd -- which is an
 OpenBSD thing which works via pf to implement greylisting, teergrube
 and various other anti-spam things.  Meaning the SpamAssassin
 'sa-spamd' startup script can't simply kill anything called spamd.

Support for pid files is built into rcng and used a combination of pid
and name, sa-spamd uses this and correctly passes the expected pid
file path to spamd. 

In my experience it does normally work, unless spamd is started as an
unprivileged user via the spamd_user variable in rc.conf, rather
dropping privileges - that's not happening here because the existing
process used port 783.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Spamd

[Jos Chrispijn]

   Thank you for the informative responses - I learned a lot.
   Best regards.
   Jos Chrispijn:

   Since my last Spamd port update I get this error when I try to start
   spamd:
   spamd not running? (check /var/run/spamd/spamd.pid).
   Starting spamd.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Spamd

[John Marshall]

On 04/04/2014 05:13, Jos Chrispijn wrote:
Since my last Spamd port update I get this error when I try to start
spamd:
spamd not running? (check /var/run/spamd/spamd.pid).
Starting spamd.

For SpamAssassin, you need to provide the pidfile specification in
/etc/rc.conf.

  mta4# grep pidfile /etc/rc.conf
  spamd_pidfile=/var/run/spamd/spamd.pid

-- 
John Marshall



signature.asc
Description: OpenPGP digital signature

Re: Spamd

[RW]

On Fri, 04 Apr 2014 06:57:29 +1100
John Marshall wrote:

 On 04/04/2014 05:13, Jos Chrispijn wrote:
 Since my last Spamd port update I get this error when I try to
  start spamd:
 spamd not running? (check /var/run/spamd/spamd.pid).
 Starting spamd.
 
 For SpamAssassin, you need to provide the pidfile specification in
 /etc/rc.conf.
 
   mta4# grep pidfile /etc/rc.conf
   spamd_pidfile=/var/run/spamd/spamd.pid


That's already the default.
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Spamd

[John Marshall]

On 04/04/2014 09:26, RW wrote:
 On Fri, 04 Apr 2014 06:57:29 +1100
 John Marshall wrote:
 For SpamAssassin, you need to provide the pidfile specification in
 /etc/rc.conf.

   mta4# grep pidfile /etc/rc.conf
   spamd_pidfile=/var/run/spamd/spamd.pid
 
 
 That's already the default.

Hmmm. So it is, and all still works fine when I remove spamd_pidfile
from rc.conf. I wonder why I did that? My recollection was that I had
done that many years ago to fix a problem like the OP's. Sorry for the
noise.

-- 
John Marshall



signature.asc
Description: OpenPGP digital signature

Re: Spamd

[Esa Karkkainen]

On Thu, Apr 03, 2014 at 09:53:10AM +0200, Jos Chrispijn wrote:
Since my last Spamd port update I get this error when I try to start

Same here, I've had this happen every time when I update spamassassin,
using portmaster, which is using pkgng.

This was taken after I had updated spamassassin

# /usr/local/etc/rc.d/sa-spamd status
spamd is not running.
# /usr/local/etc/rc.d/sa-spamd start
Starting spamd.
server socket setup failed, retry 1: spamd: could not create
IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 2: spamd: could not create
IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 3: spamd: could not create
IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
server socket setup failed, retry 4: spamd: could not create
IO::Socket::IP socket on [127.0.0.1]:783: Address already in use
^C
# sockstat -l4 -p783
USER COMMANDPID   FD PROTO  LOCAL ADDRESS FOREIGN ADDRESS
root perl   988   5  tcp4   127.0.0.1:783 *:*
root perl   987   5  tcp4   127.0.0.1:783 *:*
root perl   986   5  tcp4   127.0.0.1:783 *:*
# kill 986
# sockstat -l4 -p783
USER COMMANDPID   FD PROTO  LOCAL ADDRESS FOREIGN ADDRESS
# /usr/local/etc/rc.d/sa-spamd start
Starting spamd.
# /usr/local/etc/rc.d/sa-spamd status
spamd is running as pid 57023.
# portmaster spamassassin-3.4.0_9

[ building of spamassassin-3.4.0_9 removed ]

=== Re-installation of spamassassin-3.4.0_9 complete

=== Exiting
# /usr/local/etc/rc.d/sa-spamd status
spamd is not running.
# sockstat -l4 -p783
USER COMMANDPID   FD PROTO  LOCAL ADDRESS FOREIGN ADDRESS
root perl   57025 5  tcp4   127.0.0.1:783 *:*
root perl   57024 5  tcp4   127.0.0.1:783 *:*
root perl   57023 5  tcp4   127.0.0.1:783 *:*
# ls -l /var/run/spamd/spamd.pid
ls: /var/run/spamd/spamd.pid: No such file or directory
# printf '57023'  /var/run/spamd/spamd.pid
# /usr/local/etc/rc.d/sa-spamd status
spamd is running as pid 57023.
# /usr/local/etc/rc.d/sa-spamd restart
Stopping spamd.
Waiting for PIDS: 57023.
Starting spamd.
# /usr/local/etc/rc.d/sa-spamd status
spamd is running as pid 66760.
# sockstat -l4 -p783
USER COMMANDPID   FD PROTO  LOCAL ADDRESS FOREIGN ADDRESS
root perl   66762 5  tcp4   127.0.0.1:783 *:*
root perl   66761 5  tcp4   127.0.0.1:783 *:*
root perl   66760 5  tcp4   127.0.0.1:783 *:*

So IMHO either portmaster or pkgng just removes the spamd.pid file, and
in reality does not stop spamd.

# grep HANDLE_RC_SCRIPTS /usr/local/etc/pkg.conf
#HANDLE_RC_SCRIPTS  : NO

I changed HANDLE_RC_SCRIPTS from NO to YES, and removed the comment from
the beginning of the line.

# grep HANDLE_RC_SCRIPTS /usr/local/etc/pkg.conf
HANDLE_RC_SCRIPTS  : YES

# portmaster spamassassin-3.4.0_9

[ building of spamassassin-3.4.0_9 removed ]

=== Re-installation of spamassassin-3.4.0_9 complete

=== Exiting
# /usr/local/etc/rc.d/sa-spamd status
spamd is not running.
# sockstat -l4 -p783
USER COMMANDPID   FD PROTO  LOCAL ADDRESS FOREIGN ADDRESS
# /usr/local/etc/rc.d/sa-spamd start
Starting spamd.
# sockstat -l4 -p783
USER COMMANDPID   FD PROTO  LOCAL ADDRESS FOREIGN ADDRESS
root perl   71309 5  tcp4   127.0.0.1:783 *:*
root perl   71308 5  tcp4   127.0.0.1:783 *:*
root perl   71307 5  tcp4   127.0.0.1:783 *:*
# /usr/local/bin/sa-check_spamd
SPAMD OK: 0.101 second ping repsonse time
# ps -U root -o pid,args|grep spam
71307 /usr/local/bin/spamd -c -d -r /var/run/spamd/spamd.pid (perl)
71308 spamd child (perl)
71309 spamd child (perl)
#

So now the spamassassin is stopped correctly, but it is not started
automatically.

-- 
In the beginning the Universe was created. This has made a lot of
people very angry and been widely regarded as a bad move.
-- Douglas Adams 1952 - 2001
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org

Re: Bug in OpenBSD spamd

[Jeremy Chadwick]

On Thu, Oct 16, 2008 at 09:43:49PM -0700, Doug Hardie wrote:
 There is a bug in OpenBSD's spamd.  The value for the whitelist  
 expiration that can be set with the arguments to spamd is not used by  
 spamlogd.  It uses the hard-coded value of 36 days in grey.h.  As a  
 result if you think you are changing the time a whitelist entry is  
 retained, you are actually not.  It will always be 36 days.  The easiest 
 way to correct this is to add an argument to spamlogd with the desired 
 value and overwrite the default.

Have you reported this up-stream to the OpenBSD folks?

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Bug in OpenBSD spamd

[Doug Hardie]

There is a bug in OpenBSD's spamd.  The value for the whitelist  
expiration that can be set with the arguments to spamd is not used by  
spamlogd.  It uses the hard-coded value of 36 days in grey.h.  As a  
result if you think you are changing the time a whitelist entry is  
retained, you are actually not.  It will always be 36 days.  The  
easiest way to correct this is to add an argument to spamlogd with the  
desired value and overwrite the default.

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: spamd port

[eculp]

Quoting Doug Hardie [EMAIL PROTECTED]:

I am trying to get the port mail/spamd to work on FreeBSD 6.2.   
There is not a lot of information on actually using spamd.  So far I  
have figured out that I have to kldload pf and then a pfctl -e  
before attempting to start spamd.  However, spamd-setup actually  
does nothing.  pfctl -s rules shows an error message:


No ALTQ support in kernel
ALTQ related functions disabled

I have no idea what ALTQ is (or if its even required) since I can  
find no references to it in the kernel config files or kld modules.   
There is a page on setting up spamd at  
http://www.bgnett.no/~peter/pf/en/spamd.setup.html but it doesn't  
address this issue or have any extra steps that need to be done.   
Any ideas what is going on here?


I would start by getting pf running as expected and do some rule  
changing and testing to understand it a bit better and THEN I would  
look at spamd which I found a bit confusing although well worth the  
effort.


My salvation in spamd was a an excellent,common sense write-up by  
Jeremy Chadwick [EMAIL PROTECTED] that you can find at:  
http://jdc.parodius.com/freebsd/openbsd-spamd.txt


You can use Peter´s excellent work from the beginning to get pf going  
or by using the samples in /usr/share/examples/pf


enjoy,

ed

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]




___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

spamd port

[Doug Hardie]

I am trying to get the port mail/spamd to work on FreeBSD 6.2.  There  
is not a lot of information on actually using spamd.  So far I have  
figured out that I have to kldload pf and then a pfctl -e before  
attempting to start spamd.  However, spamd-setup actually does  
nothing.  pfctl -s rules shows an error message:


No ALTQ support in kernel
ALTQ related functions disabled

I have no idea what ALTQ is (or if its even required) since I can find  
no references to it in the kernel config files or kld modules.  There  
is a page on setting up spamd at http://www.bgnett.no/~peter/pf/en/spamd.setup.html 
 but it doesn't address this issue or have any extra steps that need  
to be done.  Any ideas what is going on here?

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Do SpamAssassin spamd and Obspamd play nicely together?

[Alex Zbyslaw]

Jeremy Chadwick wrote:


Here's an example of one which I should probably track down in our SMTP
logs to see if the delay was caused by something other than redelivery
time on the remote SMTP server:

 X-Greylist: delayed 16000 seconds by postgrey-1.30 at mx01.sc1.parodius.com; 
Mon, 07 Jan 2008 10:33:09 PST
 

Obviously, I can't tell you if this particular entry has legitimate 
reasons or not.  However, I think you mentioned in an earlier message 
that you didn't believe that a delay of the magnitude of 19 hours ought 
to be possible.   From a competent mail service, one would hope not, but 
some months ago I found myself completely unable to send messages to 
most FreeBSD mailing lists and debugged this with sterling help from 
[EMAIL PROTECTED]


My email provider could wait *days* before retrying an email which was 
greylisted.  It took four days for a message to arrive in test@ and the 
mail logs clearly showed them failing to retry at any kind of acceptable 
interval.


For the record, this was my broadband provider blueyonder.co.uk - now 
owned by Virgin - who were *no help whatsoever*.  Luckily, I have kept 
up a dial-in provider as well and always used my email address from 
them; they provide an authenticated SMTP gateway, so I'm not 
disenfranchised any longer :-)  (They've recently been taken over by 
Tiscali, so I hope that their previous standard of service keeps up).


Just a data point for the archives.  Great obspamd write-up too!

--Alex

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Do SpamAssassin spamd and Obspamd play nicely together?

[Peter Jeremy]

On Wed, Feb 06, 2008 at 11:15:30AM +, Alex Zbyslaw wrote:
My email provider could wait *days* before retrying an email which was 
greylisted.  It took four days for a message to arrive in test@ and the 
mail logs clearly showed them failing to retry at any kind of acceptable 
interval.

SingTel Optus Pty Limited (the second largest ISP in Australia)
provide a similar service.  Last time I raised the issue with them,
they claimed that they retried at 4 hour intervals - despite me
providing them with evidence to the contrary - but refused to provide
any evidence to backup their claim.  They insisted that the delivery
problems were the fault of the recipient and I should contact the
recipients ISP to get it fixed.

-- 
Peter Jeremy
Please excuse any delays as the result of my ISP's inability to implement
an MTA that is either RFC2821-compliant or matches their claimed behaviour.


pgpolaUNunGSp.pgp
Description: PGP signature

Re: Do SpamAssassin spamd and Obspamd play nicely together?

[eculp]

Quoting Jeremy Chadwick [EMAIL PROTECTED]:


On Mon, Feb 04, 2008 at 02:13:16PM -0600, eculp wrote:

I have sa-spamd running and I just installed obspamd or pfspamd what ever
it should be called and the spamd log file seems taken over by spamasassin.
 Are there any other conflicts or changes that should be made to use both.


Funny, since I indirectly touched on this problem many moons ago when
writing a document on issues we encountered when attempting to migrate
from postgrey to OpenBSD spamd.  See section Issues with OpenBSD spamd
on FreeBSD:


http://jdc.parodius.com/freebsd/openbsd-spamd.txt

Jeremy,

Your link should be included everywhere.  This is a logical,[all too  
uncommon in today's world] common sense approach that answered all the  
additional questions that I had not even asked yet because I was first  
doing tests with the recommended (published) information yet without  
success.  Within 10 minutes after opening your link, I have it  
running, hopefully as I expect, at least based on the multiple input  
spamd log file ;) Now only time will tell but at least debugging my  
configuration will now be easy.


http://jdc.parodius.com/freebsd/openbsd-spamd.txt

--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |





___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Do SpamAssassin spamd and Obspamd play nicely together?

[eculp]

Quoting Jeremy Chadwick [EMAIL PROTECTED]:


On Mon, Feb 04, 2008 at 02:13:16PM -0600, eculp wrote:

I have sa-spamd running and I just installed obspamd or pfspamd what ever
it should be called and the spamd log file seems taken over by spamasassin.
 Are there any other conflicts or changes that should be made to use both.


Funny, since I indirectly touched on this problem many moons ago when
writing a document on issues we encountered when attempting to migrate
from postgrey to OpenBSD spamd.  See section Issues with OpenBSD spamd
on FreeBSD:

http://jdc.parodius.com/freebsd/openbsd-spamd.txt


Jeremy,

Sorry, but I have one other question.  Are you still using obspamd on  
the machines you set up when you wrote the above link?  Your reasons  
on why or why not would be greatly appreciated.


Thanks again for the information,

ed

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Do SpamAssassin spamd and Obspamd play nicely together?

[Jeremy Chadwick]

On Tue, Feb 05, 2008 at 09:51:46AM -0600, eculp wrote:
 Your link should be included everywhere.  This is a logical,[all too 
 uncommon in today's world] common sense approach that answered all the 
 additional questions that I had not even asked yet because I was first 
 doing tests with the recommended (published) information yet without 
 success.  Within 10 minutes after opening your link, I have it running, 
 hopefully as I expect, at least based on the multiple input spamd log 
 file ;) Now only time will tell but at least debugging my configuration 
 will now be easy.

Glad something I wrote up long ago came in handy!  All the questions in
the document were ones I had, and the answers I had to figure out for
myself.  It makes me feel good knowing I'm not the only one who was
confused by the existing documentation!  :-)

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Do SpamAssassin spamd and Obspamd play nicely together?

[Jeremy Chadwick]

On Tue, Feb 05, 2008 at 09:54:40AM -0600, eculp wrote:
 Quoting Jeremy Chadwick [EMAIL PROTECTED]:
 http://jdc.parodius.com/freebsd/openbsd-spamd.txt

 Sorry, but I have one other question.  Are you still using obspamd on the 
 machines you set up when you wrote the above link?  Your reasons on why or 
 why not would be greatly appreciated.

No, we're not.  The main reason we reverted back to postgrey was because
OpenBSD spamd cannot add an SMTP header to mails detailing how long the
mail was delayed for.  postgrey, since it's a postfix policy service,
adds an X-Greylist header to mails allowing users to see just how long
the greylisting delay was.  This feature has come in handy for tracking
down greylisting problems.  An example header:

  X-Greylist: delayed 360 seconds by postgrey-1.30 at mx01.sc1.parodius.com; 
Mon, 04 Feb 2008 21:02:35 PST

Here's an example of one which I should probably track down in our SMTP
logs to see if the delay was caused by something other than redelivery
time on the remote SMTP server:

  X-Greylist: delayed 16000 seconds by postgrey-1.30 at mx01.sc1.parodius.com; 
Mon, 07 Jan 2008 10:33:09 PST

I would love to try OpenBSD spamd again, but it's not a policy service
service like postgrey is -- OpenBSD spamd has absolutely no way of
inserting any data into delivered mail, because it's implemented with
pf(4) and is not a policy service.

It's quite possible to make a piece of software that would act as a
policy service for postfix which could get details of greylisted mails
and when they were actually delivered by OpenBSD spamd.  Just thinking
about it makes me consider writing it.  :-)  Would be quite useful...

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Do SpamAssassin spamd and Obspamd play nicely together?

[eculp]

Quoting Jeremy Chadwick [EMAIL PROTECTED]:


On Tue, Feb 05, 2008 at 09:54:40AM -0600, eculp wrote:

Quoting Jeremy Chadwick [EMAIL PROTECTED]:

http://jdc.parodius.com/freebsd/openbsd-spamd.txt


Sorry, but I have one other question.  Are you still using obspamd on the
machines you set up when you wrote the above link?  Your reasons on why or
why not would be greatly appreciated.


No, we're not.  The main reason we reverted back to postgrey was because
OpenBSD spamd cannot add an SMTP header to mails detailing how long the
mail was delayed for.  postgrey, since it's a postfix policy service,
adds an X-Greylist header to mails allowing users to see just how long
the greylisting delay was.  This feature has come in handy for tracking
down greylisting problems.  An example header:

  X-Greylist: delayed 360 seconds by postgrey-1.30 at  
mx01.sc1.parodius.com; Mon, 04 Feb 2008 21:02:35 PST


Here's an example of one which I should probably track down in our SMTP
logs to see if the delay was caused by something other than redelivery
time on the remote SMTP server:

  X-Greylist: delayed 16000 seconds by postgrey-1.30 at  
mx01.sc1.parodius.com; Mon, 07 Jan 2008 10:33:09 PST


I would love to try OpenBSD spamd again, but it's not a policy service
service like postgrey is -- OpenBSD spamd has absolutely no way of
inserting any data into delivered mail, because it's implemented with
pf(4) and is not a policy service.

It's quite possible to make a piece of software that would act as a
policy service for postfix which could get details of greylisted mails
and when they were actually delivered by OpenBSD spamd.  Just thinking
about it makes me consider writing it.  :-)  Would be quite useful...


It would be very nice to have and useful information.  Especially now  
that I am impatiently watching my tables grow and waiting for emails  
that I have seeded from many other sources, I am far from comfortable  
with pfspamd but seeing that I have received almost no spam since I  
started the test, is currently compensating.  I would give postgray a  
try but don't have a server running postfix right now and don't have a  
lot of time and for now am going to set up pfspamd on all unless I  
find some major issue.


Thanks again for all the useful information.

ed


--
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |





___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Do SpamAssassin spamd and Obspamd play nicely together?

[eculp]

I have sa-spamd running and I just installed obspamd or pfspamd what  
ever it should be called and the spamd log file seems taken over by  
spamasassin.  Are there any other conflicts or changes that should be  
made to use both.


Thanks,

ed

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Do SpamAssassin spamd and Obspamd play nicely together?

[Jeremy Chadwick]

On Mon, Feb 04, 2008 at 02:13:16PM -0600, eculp wrote:
 I have sa-spamd running and I just installed obspamd or pfspamd what ever 
 it should be called and the spamd log file seems taken over by spamasassin. 
  Are there any other conflicts or changes that should be made to use both.

Funny, since I indirectly touched on this problem many moons ago when
writing a document on issues we encountered when attempting to migrate
from postgrey to OpenBSD spamd.  See section Issues with OpenBSD spamd
on FreeBSD:

http://jdc.parodius.com/freebsd/openbsd-spamd.txt

-- 
| Jeremy Chadwickjdc at parodius.com |
| Parodius Networking   http://www.parodius.com/ |
| UNIX Systems Administrator  Mountain View, CA, USA |
| Making life hard for others since 1977.  PGP: 4BD6C0CB |

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

mail/spamd - inactive maintainer

[Alex Samorukov]

Please, reset maintainer of the mail/spamd.

Version in the ports is buggy and outdated, and my PR`s are just ignored.

See:
http://www.freebsd.org/cgi/query-pr-summary.cgi?category=severity=priority=class=state=sort=nonetext=spamdresponsible=multitext=originator=release=

--
Best regards,
Alex Samorukov, SAMM1-RIPE
Zend Certified PHP Engineer

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: mail/spamd - inactive maintainer

[Hans F. Nordhaug]

* Alex Samorukov [EMAIL PROTECTED] [2007-03-20]:
 Please, reset maintainer of the mail/spamd.
 
 Version in the ports is buggy and outdated, and my PR`s are just ignored.
 
 See:
 http://www.freebsd.org/cgi/query-pr-summary.cgi?category=severity=priority=class=state=sort=nonetext=spamdresponsible=multitext=originator=release=

Yes, please get these spamd issues resolved - I'm really
looking forward to see your patches being commited. In particular the
conflict with SA is annoying.

Regards
Hans
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: ports/108657: [PATCH] mail/spamd: core dump on spamd-setup with -t key

[Xin LI]

Synopsis: [PATCH] mail/spamd: core dump on spamd-setup with -t key

Responsible-Changed-From-To: delphij-freebsd-ports
Responsible-Changed-By: delphij
Responsible-Changed-When: Tue Mar 20 14:03:55 UTC 2007
Responsible-Changed-Why: 
Return to pool.

http://www.freebsd.org/cgi/query-pr.cgi?pr=108657
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: ports/105277: [UPDATE] mail/spamd - improvements and clean up

[Xin LI]

Synopsis: [UPDATE] mail/spamd - improvements and clean up

Responsible-Changed-From-To: delphij-freebsd-ports
Responsible-Changed-By: delphij
Responsible-Changed-When: Tue Mar 20 14:16:31 UTC 2007
Responsible-Changed-Why: 
Return to pool.

http://www.freebsd.org/cgi/query-pr.cgi?pr=105277
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: ports/108663: [PATCH] mail/spamd: resolv conflict with sa-spamd and add pfspamd_setup_flags

[Xin LI]

Synopsis: [PATCH] mail/spamd: resolv conflict with sa-spamd and add 
pfspamd_setup_flags

Responsible-Changed-From-To: delphij-freebsd-ports
Responsible-Changed-By: delphij
Responsible-Changed-When: Tue Mar 20 14:17:01 UTC 2007
Responsible-Changed-Why: 
Return to pool.

http://www.freebsd.org/cgi/query-pr.cgi?pr=108663
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: mail/spamd - inactive maintainer

[LI Xin]

Alex Samorukov wrote:
 Please, reset maintainer of the mail/spamd.
 
 Version in the ports is buggy and outdated, and my PR`s are just ignored.
 
 See:
 http://www.freebsd.org/cgi/query-pr-summary.cgi?category=severity=priority=class=state=sort=nonetext=spamdresponsible=multitext=originator=release=

I've dropped maintainership.  Good job you guys blocking my e-mails just
because I live in China and simply claim that I'm inactive, and no, I
no longer have any interest to take care for the port.

My apologies to: Max.

Cheers,
-- 
Xin LI [EMAIL PROTECTED]  http://www.delphij.net/
FreeBSD - The Power to Serve!



signature.asc
Description: OpenPGP digital signature

Looking for new mail/spamd maintainer

[LI Xin]

Hi,

I'd like to look for a new maintainer for mail/spamd.  I have a tarball
which consists checked out version (i.e. have CVS/ directories to make
it easier for future updates) which may be useful for its new maintainer.

Please contact me off-list for this.

Cheers,
-- 
Xin LI [EMAIL PROTECTED]  http://www.delphij.net/
FreeBSD - The Power to Serve!



signature.asc
Description: OpenPGP digital signature

Re: ports/97579: [patch] ports mail/spamd to reflect the public hostname in helo dialog

[Xin LI]

Synopsis: [patch] ports mail/spamd to reflect the public hostname in helo dialog

Responsible-Changed-From-To: delphij-freebsd-ports
Responsible-Changed-By: delphij
Responsible-Changed-When: Tue Mar 20 14:21:23 UTC 2007
Responsible-Changed-Why: 
Return to pool.

http://www.freebsd.org/cgi/query-pr.cgi?pr=97579
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: ports/108663: [PATCH] mail/spamd: resolv conflict with sa-spamd and add pfspamd_setup_flags

[Alex Samorukov]

The following reply was made to PR ports/108663; it has been noted by GNATS.

From: Alex Samorukov [EMAIL PROTECTED]
To: [EMAIL PROTECTED],  [EMAIL PROTECTED]
Cc:  
Subject: Re: ports/108663: [PATCH] mail/spamd: resolv conflict with sa-spamd
 and add pfspamd_setup_flags
Date: Tue, 20 Mar 2007 16:50:29 +0200

 Please, commit this patch. Also, i want to take maintainership for this 
 project.
 
 -- 
 Best regards,
 Alex Samorukov, SAMM1-RIPE
 Zend Certified PHP Engineer
 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: ports/108663: [PATCH] mail/spamd: resolv conflict with sa-spamd and add pfspamd_setup_flags

[Xin LI]

Synopsis: [PATCH] mail/spamd: resolv conflict with sa-spamd and add 
pfspamd_setup_flags

State-Changed-From-To: open-closed
State-Changed-By: delphij
State-Changed-When: Tue Mar 20 15:16:59 UTC 2007
State-Changed-Why: 
Committed, thanks!

http://www.freebsd.org/cgi/query-pr.cgi?pr=108663
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

trouble running spamass-milter as spamd

[Peter Losher]

I am integrating spamass-milter into my postfix-based MX's, and while
mail to me works and is processed by spamd (as I have an account on the
box), mail to non-existant users throws up errors when it's invoked:

-=-
Mar 13 08:48:20 no-mx spamd[657]: spamd: handle_user unable to find
user: 'boom'
Mar 13 08:48:20 no-mx spamd[657]: spamd: still running as root: user not
specified with -u, not found, or set to root, falling back to nobody at
/usr/local/bin/spamd line 1144, GEN192 line 4.
-=-

Now in /etc/rc.conf I have -u set to spamd:

-=-
spamass_milter_enable=YES
spamass_milter_socket=/var/run/spamass-milter.sock
spamass_milter_flags=-f -p ${spamass_milter_socket} -r 10 -m -u spamd
-=-

and ps verifies this:

-=-
root   620  0.0  0.7  3640  1652  ??  Ss1:08AM   0:01.38
/usr/local/sbin/spamass-milter -f -p /var/run/spamass-milter.sock -r 10
-m -u spamd
-=-

and spamd is a valid user on this system; I even gave it a proper shell
in case that was the problem:

-=-
% finger spamd
Login: spamdName: SpamAssassin user
Directory: /var/spool/spamd Shell: /bin/csh
Never logged in.
No Mail.
No Plan
-=-

So am I missing something here?

Best Wishes - Peter
-- 
[ http://www.plosh.net/ ] - Earth Halted: Please reboot to continue



signature.asc
Description: OpenPGP digital signature

Re: trouble running spamass-milter as spamd

[Chuck Swiger]

On Mar 13, 2007, at 2:04 AM, Peter Losher wrote:

I am integrating spamass-milter into my postfix-based MX's, and while
mail to me works and is processed by spamd (as I have an account on  
the

box), mail to non-existant users throws up errors when it's invoked:

-=-
Mar 13 08:48:20 no-mx spamd[657]: spamd: handle_user unable to find
user: 'boom'
Mar 13 08:48:20 no-mx spamd[657]: spamd: still running as root:  
user not
specified with -u, not found, or set to root, falling back to  
nobody at

/usr/local/bin/spamd line 1144, GEN192 line 4.


I don't believe that Postfix's milter implementation is as robust as  
integrating spam/AV filtering via the native content-filter  
mechanism.  Try using Amavisd-new+SpamAssassin+ClamAV with Postfix  
instead...works well.


--
-Chuck

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: SpamAssassin (spamd) eating a lot of CPU....

[Stephen Montgomery-Smith]

Forrest Aldrich wrote:

Since a recent update of Spamassassin to:

PORTVERSION=3.1.7
PORTREVISION=   3

I've noticed that each email that gets scanned causes the process to eat 
up 80+% of the CPU time, and it's slow...


I'm not really sure what changed.

Likewise, when I start it up for the first time, I see:

[ top output ]
49106 root1 1060   290M   267M RUN0   0:17 *98.52%* 
perl5.8.8


I have a Dell system here, and it cranks up the fan every time a message 
comes in now, with the recent spamd.


Curious if anyone else has had these issues, etc.

The system is not otherwise active, so I'm certain it's not a resource 
issue (or constraint thereof).



Thanks.


We had this issue.  But we assumed that it was an increase in spam on 
the internet (perhaps recent MS worms).



___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: SpamAssassin (spamd) eating a lot of CPU....

[Jeremy Chadwick]

On Tue, Jan 23, 2007 at 11:02:34PM -0500, Forrest Aldrich wrote:
 Since a recent update of Spamassassin to:
 
 PORTVERSION=3.1.7
 PORTREVISION=   3
 
 I've noticed that each email that gets scanned causes the process to eat 
 up 80+% of the CPU time, and it's slow...
 
 I'm not really sure what changed.
 
 Likewise, when I start it up for the first time, I see:
 
 [ top output ]
 49106 root1 1060   290M   267M RUN0   0:17 *98.52%* 
 perl5.8.8
 
 I have a Dell system here, and it cranks up the fan every time a message 
 comes in now, with the recent spamd.
 
 Curious if anyone else has had these issues, etc.
 
 The system is not otherwise active, so I'm certain it's not a resource 
 issue (or constraint thereof).

I've seen this happen before, although with older SpamAssassin
releases (though I have no proof the problem got fixed at all).
At that time, we were using mail/spamass-rules as well.

Since, we've removed using mail/spamass-rules, and haven't seen
this problem.  Possibly there's some SpamAssassin rule which causes
the daemon to spin when certain regexs are matched.  Not sure.
Ours (note the much smaller memory footprint):

root 58179  2.2  5.2 28088 27084  ??  S 3:58am   1:44.79 spamd child 
(perl5.8.8)
root 65228  0.0  5.0 27172 26128  ??  S 5:58am   0:23.17 spamd child 
(perl5.8.8)
root   313  0.0  4.3 23812 22176  ??  Ss2Jan07  11:40.79 
/usr/local/bin/spamd -c -d -r /var/run/spamd/spamd.pid (perl5.8.8)

It may be worth truss'ing the perl process and opening a Bug with
the SpamAssassin team.

-- 
| Jeremy Chadwick jdc at parodius.com |
| Parodius Networkinghttp://www.parodius.com/ |
| UNIX Systems Administrator   Mountain View, CA, USA |
| Making life hard for others since 1977.   PGP: 4BD6C0CB |

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: SpamAssassin (spamd) eating a lot of CPU....

[Forrest Aldrich]

(see below)

Jeremy Chadwick wrote:

On Tue, Jan 23, 2007 at 11:02:34PM -0500, Forrest Aldrich wrote:
  

Since a recent update of Spamassassin to:

PORTVERSION=3.1.7
PORTREVISION=   3

I've noticed that each email that gets scanned causes the process to eat 
up 80+% of the CPU time, and it's slow...


I'm not really sure what changed.

Likewise, when I start it up for the first time, I see:

[ top output ]
49106 root1 1060   290M   267M RUN0   0:17 *98.52%* 
perl5.8.8


I have a Dell system here, and it cranks up the fan every time a message 
comes in now, with the recent spamd.


Curious if anyone else has had these issues, etc.

The system is not otherwise active, so I'm certain it's not a resource 
issue (or constraint thereof).



I've seen this happen before, although with older SpamAssassin
releases (though I have no proof the problem got fixed at all).
At that time, we were using mail/spamass-rules as well.

Since, we've removed using mail/spamass-rules, and haven't seen
this problem.  Possibly there's some SpamAssassin rule which causes
the daemon to spin when certain regexs are matched.  Not sure.
Ours (note the much smaller memory footprint):

root 58179  2.2  5.2 28088 27084  ??  S 3:58am   1:44.79 spamd child 
(perl5.8.8)
root 65228  0.0  5.0 27172 26128  ??  S 5:58am   0:23.17 spamd child 
(perl5.8.8)
root   313  0.0  4.3 23812 22176  ??  Ss2Jan07  11:40.79 
/usr/local/bin/spamd -c -d -r /var/run/spamd/spamd.pid (perl5.8.8)

It may be worth truss'ing the perl process and opening a Bug with
the SpamAssassin team.

  


Thanks for the replies.

I did clean up the extra rules (dujor and others) and that seems to have 
resolved the problem... for now.


It's worth noting that I've had these extra rules in there for a while, 
and only recently has this caused the high CPU consumption.  So I would 
tend to wonder if there's a bug somewhere.


Might be more resource friendly if this were in C, but I don't want to 
go there ;-)



Thanks,

Forrest

___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

SpamAssassin (spamd) eating a lot of CPU....

[Forrest Aldrich]

Since a recent update of Spamassassin to:

PORTVERSION=3.1.7
PORTREVISION=   3

I've noticed that each email that gets scanned causes the process to eat 
up 80+% of the CPU time, and it's slow...


I'm not really sure what changed.

Likewise, when I start it up for the first time, I see:

[ top output ]
49106 root1 1060   290M   267M RUN0   0:17 *98.52%* 
perl5.8.8


I have a Dell system here, and it cranks up the fan every time a message 
comes in now, with the recent spamd.


Curious if anyone else has had these issues, etc.

The system is not otherwise active, so I'm certain it's not a resource 
issue (or constraint thereof).



Thanks.




___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: SpamAssassin (spamd) eating a lot of CPU....

[Alex Dupre]

Forrest Aldrich wrote:
 Since a recent update of Spamassassin to:
 
 PORTVERSION=3.1.7
 PORTREVISION=   3
 
 I've noticed that each email that gets scanned causes the process to eat
 up 80+% of the CPU time, and it's slow...
 
 Curious if anyone else has had these issues, etc.

No, it's working fine here. Are you using custom ruleset?

--
Alex Dupre
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Is syslog() reentrant? Was: OpenBSD's spamd.

[Christopher Hilton]

Christopher Hilton wrote:
Has anyone gotten a newer version of OpenBSD's spamd than the one in 
ports going? I'm cvsupping my ports tree now but since I didn't see an 
update on the cvs server I'm assuming 3.7 is the latest version.


Between OpenBSD 3.7 and 3.8 spamd gained the ability to tarpit or 
stutter at all connections for a configurable period of time. I 
understand that stuttering for the first few seconds of the SMTP dialog 
causes many spammers to go away before even generating a greylisting 
tuple. It's something I'd like to try and see for myself and it will be 
fairly easy since my primary MX is behind an OpenBSD firewall. However, 
my secondary MX is a FreeBSD box with no such protection and I fear that 
the spammers will just take advantage of the fact that my secondary MX 
has weaker protections than my primary.




A casual attempt to compile a fresher copy of the software shows that 
spamd is using the OpenBSD's reentrant syslog functions (syslog_r, 
openlog_r, etc) Is FreeBSD's syslog already reentrant?


-- Chris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Is syslog() reentrant? Was: OpenBSD's spamd.

[Dan Nelson]

In the last episode (Dec 19), Christopher Hilton said:
 Christopher Hilton wrote:
 Has anyone gotten a newer version of OpenBSD's spamd than the one in
 ports going? I'm cvsupping my ports tree now but since I didn't see
 an update on the cvs server I'm assuming 3.7 is the latest version.
 
 Between OpenBSD 3.7 and 3.8 spamd gained the ability to tarpit or
 stutter at all connections for a configurable period of time. I
 understand that stuttering for the first few seconds of the SMTP
 dialog causes many spammers to go away before even generating a
 greylisting tuple. It's something I'd like to try and see for myself
 and it will be fairly easy since my primary MX is behind an OpenBSD
 firewall. However, my secondary MX is a FreeBSD box with no such
 protection and I fear that the spammers will just take advantage of
 the fact that my secondary MX has weaker protections than my
 primary.
 
 
 A casual attempt to compile a fresher copy of the software shows that
 spamd is using the OpenBSD's reentrant syslog functions (syslog_r,
 openlog_r, etc) Is FreeBSD's syslog already reentrant?

It is, as of FreeBSD 5.4.  In previous versions only openlog() and
syslog(%m) with an invalid errno were non-reentrant.

http://www.freebsd.org/cgi/query-pr.cgi?pr=72394

-- 
Dan Nelson
[EMAIL PROTECTED]
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Is syslog() reentrant? Was: OpenBSD's spamd.

[Christopher Hilton]

Dan Nelson wrote:

In the last episode (Dec 19), Christopher Hilton said:



A casual attempt to compile a fresher copy of the software shows that
spamd is using the OpenBSD's reentrant syslog functions (syslog_r,
openlog_r, etc) Is FreeBSD's syslog already reentrant?


It is, as of FreeBSD 5.4.  In previous versions only openlog() and
syslog(%m) with an invalid errno were non-reentrant.



Awesome. Then all I have to do to get the fresher code is either wrap 
the openlog_r and syslog_r calls in the spamd.c or write local functions 
which do the same. From the point of style which is preferable? Is it 
even possible to #define a C function to get around an argument? E.g. 
The openbsd syslog_r function has this call sequence:


 void
 syslog_r(int priority, struct syslog_data *data,
  const char *message,
  ...);



IIRC there isn't a way to get around the '...' argument with #define and 
deal with the extra argument.


-- Chris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: Is syslog() reentrant? Was: OpenBSD's spamd.

[Clint Olsen]

On Dec 19, Christopher Hilton wrote:
 Awesome. Then all I have to do to get the fresher code is either wrap the
 openlog_r and syslog_r calls in the spamd.c or write local functions
 which do the same. From the point of style which is preferable? Is it
 even possible to #define a C function to get around an argument? E.g.
 The openbsd syslog_r function has this call sequence:
 
  void
  syslog_r(int priority, struct syslog_data *data,
   const char *message,
   ...);
 
 
 
 IIRC there isn't a way to get around the '...' argument with #define and
 deal with the extra argument.

Only C99 allows macros with variable arguments.  But you can attempt to
just replace the function identifier (name) if the function's arguments are
otherwise in the same order.

-Clint
-- 
Clint Olsen. -- .  
clint at NULlsen dot net .'  ,-. `.
 ;_,' (   ;
I am Dick Lexic of Borg.  Prepare to be ass-laminated. `.``;'
-- Styx Allum  ` -- '  
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

OpenBSD's spamd.

[Christopher Hilton]

Has anyone gotten a newer version of OpenBSD's spamd than the one in 
ports going? I'm cvsupping my ports tree now but since I didn't see an 
update on the cvs server I'm assuming 3.7 is the latest version.


Between OpenBSD 3.7 and 3.8 spamd gained the ability to tarpit or 
stutter at all connections for a configurable period of time. I 
understand that stuttering for the first few seconds of the SMTP dialog 
causes many spammers to go away before even generating a greylisting 
tuple. It's something I'd like to try and see for myself and it will be 
fairly easy since my primary MX is behind an OpenBSD firewall. However, 
my secondary MX is a FreeBSD box with no such protection and I fear that 
the spammers will just take advantage of the fact that my secondary MX 
has weaker protections than my primary.


-- Chris


___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: OpenBSD's spamd.

[Peter Matulis]

--- Christopher Hilton [EMAIL PROTECTED] wrote:

 Has anyone gotten a newer version of OpenBSD's spamd than the one in 
 ports going? I'm cvsupping my ports tree now but since I didn't see
 an 
 update on the cvs server I'm assuming 3.7 is the latest version.
 
 Between OpenBSD 3.7 and 3.8 spamd gained the ability to tarpit or 
 stutter at all connections for a configurable period of time. I 
 understand that stuttering for the first few seconds of the SMTP
 dialog 
 causes many spammers to go away before even generating a greylisting 
 tuple. It's something I'd like to try and see for myself and it will
 be 
 fairly easy since my primary MX is behind an OpenBSD firewall.
 However, 
 my secondary MX is a FreeBSD box with no such protection and I fear
 that 
 the spammers will just take advantage of the fact that my secondary
 MX 
 has weaker protections than my primary.

Yes, best practice is to configure all MX servers in the same way. 
Especially so if you plan to give spam servers a punch in the face
(stuttering, greylisting, etc).  I am also interested in spamd but will
not use it because I do not have control of the other mailservers.


__
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]

Re: OpenBSD's spamd.

[Christopher Hilton]

Peter Matulis wrote:

[ snip ]


 my secondary MX is a FreeBSD box with no such protection and I fear
that 
the spammers will just take advantage of the fact that my secondary
MX 
has weaker protections than my primary.


Yes, best practice is to configure all MX servers in the same way. 
Especially so if you plan to give spam servers a punch in the face

(stuttering, greylisting, etc).  I am also interested in spamd but will
not use it because I do not have control of the other mailservers.




Well, I found out the hard way. I configured my primary mailserver to 
use a few of the less political rbls and found that the spammers adapted 
by hitting my secondary MX


-- Chris
___
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to [EMAIL PROTECTED]