popbsmtpd-users
Re: Your main.cf
Ahh. Now that I reread the howto, I realized I misunderstood it the first
time. I copied the whole directory to /usr/sbin instead of just the
popbsmtpd. hehe. Thanks again!
----- Original Message -----
From: "Marcus Redivo" <mredivo_at_binarytool.com>
To: <ziddey_at_magnum.ijib.com>
Sent: Saturday, August 24, 2002 12:15 PM
Subject: Re: Your main.cf
> Jibben Nee said:
> > Wow! You rule! I had a feeling that that was the cause but didn't
> > exactly pinpoint it. It's working great now! Thank you for a great
> > program and for taking the time to help me set it up.
> >
> > Thanks,
> > Jibben Nee
>
> My pleasure; you are welcome.
>
> I want to make sure that any problems people have with it are addressed in
> the next version, so I am glad we were able to get it going.
> Good luck with it, and please let me know if any problems arise with
> popbsmtpd.
> Marcus
>
> >
> > On Fri, 23 Aug 2002, Marcus Redivo wrote:
> >
> >> Jibben Nee said:
> >> > Ahhh! Thank you so much. The problem now is that the init.d script
> >> > won't work properly, so I can't start popbsmtpd. I think I can run
> >> > it manually and will attempt that right now. Thanks again!
> >>
> >> I was wondering about that, and I think I figured it out.
> >>
> >> The init script expects the binary to be in /usr/sbin, and bails out
> >> if it is not there. You can fix it in one of two ways; change the
> >> $RUNPATH in the init script to point to where you have it, or move
> >> popbsmtpd to /usr/sbin (disabling LIDS as per the HOWTO).
> >> That should do it.
> >>
> >> Marcus
> >>
> >> >
> >> > ----- Original Message -----
> >> > From: "Marcus Redivo"
> >> > To: "Jibben Nee"
> >> > Sent: Friday, August 23, 2002 12:50 PM
> >> > Subject: Your main.cf
> >> >
> >> >
> >> >> Hi Jibben,
> >> >>
> >> >> I have looked through your main.cf, and I see a couple of things
> >> >> that
> >> > could
> >> >> be changed.
> >> >>
> >> >> First, the only network it acknowledges as being its own is the
> >> >> loopback. You also need to tell it about the 192.168.2 network:
> >> >>
> >> >> mynetworks = 192.168.2.0/24 127.0.0.0/8
> >> >>
> >> >> It will now recognize all your 192.168.2.* machines as being local,
> >> >> and permit relaying.
> >> >>
> >> >> The second item is the order in which your restrictions are listed.
> >> > Postfix
> >> >> has two types of tests it can make in a restriction:
> >> >>
> >> >> 1. A test that gives an unequivocal YES or NO
> >> >> 2. A test that can return with "I DON'T KNOW"
> >> >>
> >> >> Nothing after a test of the first kind matters; the item is either
> >> > accepted
> >> >> or rejected right there. But tests of the second kind only stop the
> >> >> list processing if they return a definite answer. For example,
> >> >> looking up an IP in a blacklist does not mean the mail is
> >> >> acceptable if it is not found in the blacklist; further tests must
> >> >> be made.
> >> >>
> >> >> check_relay_domains is a test of the first kind, and you have it
> >> >> listed first, so none of the other tests ever gets executed. Try
> >> >> this instead:
> >> >>
> >> >> smtpd_recipient_restrictions = permit_mynetworks,
> >> >> check_client_access hash:/etc/postfix/pop-before-smtpd
> >> >> check_relay_domains
> >> >>
> >> >> smtpd_client_restrictions = check_client_access
> >> >> hash:/etc/postfix/pop-before-smtpd
> >> >>
> >> >> Actually, because you have no other smtpd_client_restrictions, you
> >> >> don't need to specify this one either. Other people need it here
> >> >> because they
> >> > have
> >> >> other restrictions that will block the mail unless pop-before-smtpd
> >> >> lets them through.
> >> >>
> >> >> Good luck, and please let me know if this works...
> >> >>
> >> >> Marcus Redivo
> >> >>
> >> >> The Binary Tool Foundry
> >> >> http://www.binarytool.com
>
This archive was generated by hypermail 2.1.6 on 2005-11-05 00:15:04 PST
| |
