-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I had this working, at least sort of, on my old Arch Linux system. I'm
migrating to a new one, also Arch Linux. Copying the configuration and
just modifying it for new hostnames (and IP addresses?) didn't work.
Here's postconf -n:
address_ve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 04/23/2013 10:42 AM, Steve Jenkins wrote:
>
> This setup has been working pretty well for me, and reduces false
> positives by not allowing any single DNSBL to block an incoming
> connection without concurrence from at least one other DNSBL.
>
F
time, possibly in another galaxy, it would have been 2.01
rather than 2.1. I'm not advocating one way or the other on this, but
I would be a little slower to declare that "if they can't figure it
out, they shouldn't be running a mail server."
- --
David Benfell / be
ouched the
configuration in a few weeks. The only significant system
configuration change has been an Arch Linux upgrade that consolidated
executables from /sbin, /bin, and /usr/sbin into /usr/bin
Help!
Thanks!
- --
David Benfell / benf...@parts-unknown.org
Please see https://parts-unknown.org/
Hi all,
I'm trying to move my maildirs to a non-standard location (trying to
balance disk activity) and there's something I think I'm missing. Here's
what I tried:
home_mailbox = /Maildir/$user/
But when I ran 'postfix check' it said, several times:
/usr/bin/postconf: warning: /etc/postfix/main
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/06/2013 08:53 AM, /dev/rob0 wrote:
> On Tue, Aug 06, 2013 at 12:27:04PM +0530, The_Ace wrote:
>> On Tue, Aug 6, 2013 at 10:10 AM, David Benfell
>> wrote:
>>> I'm trying to move my maildirs to a non-standard locatio
ll what. This is a StartSSL.com certificate so
there's an intermediate key as well as the certificate itself and the
certificate authority key. The chain should be complete. I've just
checked my work; I think I did this right.
So how do I tell what's going wrong?
Thanks!
- --
Da
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/23/2013 12:55 AM, DTNX Postmaster wrote:
> On Aug 23, 2013, at 09:20, David Benfell
> wrote:
>
>> Unfortunately, I'm finding this singularly unhelpful:
>>
>> - Original Message Subject: Pos
- local
virtualunix - n n - - virtual
lmtp unix - - n - - lmtp
anvil unix - - n - 1 anvil
scache unix - - n - 1 scache
What else do I need to s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/21/2013 07:36 AM, Scott Kitterman wrote:
> On Saturday, September 21, 2013 03:34:57 David Benfell wrote:
>> Hi all,
>>
>> As near as I can tell debian's clamav is just broken. It keeps
>> whining about clamd.c
r (which is remote, by the way).
At this point, my first priority has to be just getting mail back up.
I've had a lot of these domains for a decade or more. I get a lot of
spam, hence the postscreen stuff, but I also get a lot of mail. Then,
maybe, I can think about reimplementing clamav.
think I'm now using a distribution that is, at least for me,
sabotaging postfix. Which means I'll need to use something else.
That's not a knock on postfix, but rather a critique of Debian on this
particular package.
- --
David Benfell
see https://parts-unknown.org/node/2 if you don&#
mail server:
May 25 07:52:18 home postfix/smtpd[55825]: NOQUEUE: reject: RCPT from
unknown[50.250.218.164]: 454 4.7.1 : Relay access
denied; from= to=
proto=ESMTP helo=
Both systems are FreeBSD, running postfix from the port, version
postfix-3.1.1,1.
What other information do I need to supply? W
Hello /dev/rob0 ,
Yup, this seems to have been it. Thanks very much for your eyes.
On 05/25/2016 03:34 PM, /dev/rob0 wrote:
> 50.250.218.164 is not in 50.250.218.0/28 ... not in $mynetworks
--
David Benfell, Ph.D.
benf...@parts-unknown.org
signature.asc
Description: OpenPGP digi
me spam will always get through. The war
on spam is ongoing with each side continuing to develop in an attempt to
evade their opponents' efforts. It will probably never be won, at least
with SMTP.
--
David Benfell, Ph.D.
benf...@parts-unknown.org
signature.asc
Description: OpenPGP digital signature
elf, but I
believe it would then be possible to reject spoofed IP addresses because
they would be on the wrong interface.
--
David Benfell, Ph.D.
benf...@parts-unknown.org
signature.asc
Description: OpenPGP digital signature
Hi,
Thinking that OpenBSD's packages incorporated assumptions that are
inapplicable to how I use postfix, I am attempting to build it myself.
Based on what I saw in the READMEs and what I found on the system, I am
using:
make tidy \
&& make makefiles CCARGS="-DUSE_TLS -I/usr/include/open
lt;
postfix-us...@dukhovni.org> wrote:
> On Tue, Aug 23, 2016 at 11:10:38AM -0700, David Benfell wrote:
>
> > Thinking that OpenBSD's packages incorporated assumptions that are
> > inapplicable to how I use postfix, I am attempting to build it myself.
> >
> >
I'm insufficiently familiar with gmail's web interface (g!) and it
appears I sent my last only to Wietse, not the list.
-- Forwarded message ------
From: David Benfell
Date: Tue, Aug 23, 2016 at 12:42 PM
Subject: Re: OpenBSD build 'OPENSSL_VERSION' u
Hi,
My saga continues (the earlier thread had to do with linking to openssl
correctly under OpenBSD). As before, this is OpenBSD 5.9 and postfix 3.1.1.
I have built dovecot 2.2.24 from the upstream source and gotten it working
(hello, file descriptor limits! hello, user authentication weirdness!)
smtpd.c:5799: error: for each function it appears in.)
*** Error 1 in src/smtpd (Makefile:73 'smtpd.o')
*** Error 1 in /home/benfell/postfix-3.1.1 (Makefile:93 'update')
Thanks!
On Tue, Aug 23, 2016 at 5:21 PM, Wietse Venema wrote:
> David Benfell:
> > make tidy \
On Wed, 2016-08-24 at 06:57 -0400, Wietse Venema wrote:
> David Benfell:
> >
> > make tidy \
> > && make makefiles CCARGS="-DUSE_TLS
> > -I/usr/local/include/eopenssl
> INSTALL says:
>
> make makefiles CCARGS=' ... -Dthis=\&qu
22 matches
Mail list logo
