|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: POP before SMTP
From: Ralf Hildebrandt (news-list.postfix.users
innominate.de)Date: Tue Jun 13 2000 - 02:01:21 CDT
- Next message: Leif Nixon: "Re: mail deliveries to NFS mount (sort of)"
- Previous message: Matthew Hawkins: "Re: Is postfix vulnerable to the Linux setcap bug?"
- In reply to: Dave Stewart: "POP before SMTP"
- Reply: Ralf Hildebrandt: "Re: POP before SMTP"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 12 Jun 2000 20:30:51 +0200, Dave Stewart <dbs
dbscom.com> wrote:
>I've got qpopper on another machine, and when a user checks mail, their IP
>address is dutifully place on the Postfix machine, in
>/etc/postfix/access.db (which is a hash database)
So you have a patched qpopper.
>Postfix seems to only read this on startup - if I SIGKILL master and
>restart it, it allows relay from the clients listed in the database. But
Argh. You don't SIGKILL master, but use "postfix reload"
>it does not appear to re-read the database, or reference it in any way,
>after startup.
It does, believe me.
>Here's the relevant (I think) part of main.cf:
>
>smtpd_recipients_restrictions = permit_mynetworks, check_client_access
>hash:/etc/postfix/access
>smtpd_senders_restrictions = permit_mynetworks, check_client_access
>hash:/etc/postfix/access
If the permit_mynetworks matches, you'll never see an access to
hash:/etc/postfix/access
-- Ralf.Hildebrandtinnominate.de innominate AG networking people fon: +49.30.308806-44 fax: -77 web: http://innominate.de pgp: /pgp/rh
- Next message: Leif Nixon: "Re: mail deliveries to NFS mount (sort of)"
- Previous message: Matthew Hawkins: "Re: Is postfix vulnerable to the Linux setcap bug?"
- In reply to: Dave Stewart: "POP before SMTP"
- Reply: Ralf Hildebrandt: "Re: POP before SMTP"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]