On Mon, 07 Sep 2009, Dave wrote:
> I've got postfix running on CentOS. It's hooked in to amavisd-new
> which is installed as an after-queue content filter. Postfix relays to
> amavisd-new on port 10024 and amavisd-new sends messages back to postfix on
> port 10025. This is all working, now i
Hello,
I've got postfix running on CentOS. It's hooked in to amavisd-new
which is installed as an after-queue content filter. Postfix relays to
amavisd-new on port 10024 and amavisd-new sends messages back to postfix on
port 10025. This is all working, now i want to add dkim signing with
dk
Dave wrote:
> Hello,
> I'm running postfix 2.3 via rpm package. This is on a centos box. I
> know that there are later versions out, and am wondering if there's a
> feature add-ons page, not just a changelog, something very detailed version
> to version, that goes in to detail? I'm trying to
Hello,
I'm running postfix 2.3 via rpm package. This is on a centos box. I
know that there are later versions out, and am wondering if there's a
feature add-ons page, not just a changelog, something very detailed version
to version, that goes in to detail? I'm trying to decide if i should
On Sep 6, 2009, at 11:57 AM, Ralf Hildebrandt wrote:
smtpd_recipient_restrictions =
permit_mynetworks,
permit_sasl_authenticated,
reject_unauth_destination
reject
Got it.
Looks like I have send/receive working again with authentication,
mostly thanks to this thread:
http://www.nabble.co
Hi all!!
I'm proud to announce the new version of Postfix Quota Reject. This
new version enters several improvements over the old code and it's
oriented to ISPs for allowing to reject mail at smtp dialogue from the
own incoming mail scanning machines and avoiding bounces
(backscattering d
Jack Bates:
> How can I configure an LDAP map to use one result attribute if it
> exists, and another if not?
Specify two maps
xxx_maps = ldap:/file/1 ldap:/file/2
where file2 resolves what file1 doesn't.
Wietse
How can I configure an LDAP map to use one result attribute if it
exists, and another if not?
Entries in our LDAP directory have a "uid" attribute, and possibly a
"mail" and/or "mailRoutingAddress" attributes
1) If an entry has neither a "mail" attribute nor a "mailRoutingAddress"
attribute, then
* Paul Beard :
>
> On Sep 6, 2009, at 2:31 AM, Ralf Hildebrandt wrote:
>
> >Because you forgot permit_mynetworks:
> >
> >>smtpd_recipient_restrictions = permit_sasl_authenticated, reject
> >
>
>
> Like this?
>
> smtpd_recipient_restrictions = permit_mynetworks,
> reject_unauth_destination
Yep
On Sep 6, 2009, at 9:17 AM, /dev/rob0 wrote:
That might be because the client was configured to try to AUTH, and
left, when it found that AUTH was not offered. Review my previous
post, wherein it is explained.
All I really wanted to know was why the match list was failing. I am
dismantling
On Sunday 06 September 2009 10:41:54 Paul Beard wrote:
> On Sep 5, 2009, at 11:20 PM, /dev/rob0 wrote:
(A detailed description of the problem, why your host cannot accept
mail at all, which was snipped.)
> > Try giving us the complete, non-verbose logs for a mail that
> > illustrates the problem
On 9/6/2009, Paul Beard (paulbe...@gmail.com) wrote:
>> Try giving us the complete, non-verbose logs for a mail that
>> illustrates the problem you're seeing.
> There aren't any. That's the problem. This looks like all I get.
You're not listening.
Never provide verbose logs unless requested to
On Sep 6, 2009, at 2:31 AM, Ralf Hildebrandt wrote:
Because you forgot permit_mynetworks:
smtpd_recipient_restrictions = permit_sasl_authenticated, reject
Like this?
smtpd_recipient_restrictions = permit_mynetworks,
reject_unauth_destination
On Sep 5, 2009, at 11:20 PM, /dev/rob0 wr
Raimund Eimann:
> Hi,
>
> maybe it's me having completely weird ideas, but the existing Google
> results for "postfix ldap howto" are not very satisfactory for me:
That's because LDAP is not really the right search term. Postfix
can use MySQL, PostgreSQL, and so on for similar purposes.
Informat
Hi!
IMHO, you have two choices:
1. Integrate your OS to LDAP, thus making LDAP users also OS (local)
users, in this case, you should make the shell for every "mail-only"
users to /bin/false, or maybe a "menu-like" shell that only let them
run a mail client or something like that (really old-schoo
* Paul Beard :
> All I really want is to allow clients on my local subnet to be able
> to send mail from within that subnet using only the resources of that
> subnet, no relays, just trusted users. The idea would be that even
> outside the building, users could send mail through this network by
> a
16 matches
Mail list logo
