Ralf Hildebrandt a écrit :
> * Andrew Thompson :
>> I'm a little confused by this entry in my log:
>>
>> Received: from adsl-dynamic-pool-xxx.fpt.vn (unknown [118.71.113.83])
>> by mx.myserver.com (Postfix) with ESMTP id DAB68800D3
>> for <__use...@aktzero.com>; Thu, 23 Jul 2009 18:23:54
> "Clunk" == Clunk Werclick
> writes:
Clunk> I think perhaps 4-12 queries per message is not optimal?
Use proxymap(8) to reduce the number of queries made to the backend
database. It is just as fast in my experience as a hash table.
Basically, everywhere you have mysql:... make it pro
Thanks for the hint Noel.
The problem I found with sender_dependent_relayhost_maps is that
"This information is overruled with relay_transport, default_transport
and with the transport(5) table."
so if you already have a transport map for that particular domain, it
won't work.
I will investiga
Etienne Simard:
> Hi,
>
> I must have been searching at the wrong place or using the wrong
> keywords as I have been trying to find how to correctly transport to a
> particular smtp relay or have postfix do a MX query based on the "from"
> address field. I did look at the postfix doc, in se's and
Rodman Frowert wrote:
> Ahhh, now that makes more sense. I'll check it out.
>
> Thanks Brian!
In addition, the local(8) delivery agent drops privileges to that of the
UNIX user in question.
You can/will hit errors if they do not exist.
The virtual(8) delivery agent can be statically assigned a U
Kenneth Marshall wrote:
On Fri, Jul 24, 2009 at 11:50:19AM -0400, Etienne Simard wrote:
Hi,
I must have been searching at the wrong place or using the wrong
keywords as I have been trying to find how to correctly transport to a
particular smtp relay or have postfix do a MX query based on the "f
Ahhh, now that makes more sense. I'll check it out.
Thanks Brian!
Rodman
- Original Message -
From: "Brian Evans - Postfix List"
To: "Postfix users"
Sent: Friday, July 24, 2009 11:06 AM
Subject: Re: mydomain & alias questions
Rodman Frowert wrote:
Brian,
Unless I am just not se
Rodman Frowert wrote:
> Brian,
>
> Unless I am just not seeing, it, that document describes ONLY virtual
> domains. I want to be able to receieve mail for clients that are in
> "mydomain", yet they are not system user accounts.
>
> For example:
>
> If, in main.cf, my domain is listed as: mydomain
On Fri, Jul 24, 2009 at 11:50:19AM -0400, Etienne Simard wrote:
> Hi,
>
> I must have been searching at the wrong place or using the wrong
> keywords as I have been trying to find how to correctly transport to a
> particular smtp relay or have postfix do a MX query based on the "from"
> address fi
Noel,
I understand that anything for "mydomain" is looked up in /etc/passwd which
is a type of local recipitant table. But what if I want to feed that
"lookup system" another file in addition to the /etc/passwd file? I was
looking at the "local_recipitant_maps" parameter but haven't quite fi
Hi,
I must have been searching at the wrong place or using the wrong
keywords as I have been trying to find how to correctly transport to a
particular smtp relay or have postfix do a MX query based on the "from"
address field. I did look at the postfix doc, in se's and the
postfix-users archives w
Noel Jones wrote:
Jake Vickers wrote:
I also tried these settings (smtpd_tls_mandatory_protocols = !SSLv2)
on a Debian build (running 2.3.8) with a self-signed cert and am
still getting a SSLv2 connection. I'm sure I'm missing something
glaringly obvious...
smtpd_tls_mandatory_protocols o
Brian,
Unless I am just not seeing, it, that document describes ONLY virtual
domains. I want to be able to receieve mail for clients that are in
"mydomain", yet they are not system user accounts.
For example:
If, in main.cf, my domain is listed as: mydomain = xyz.com
And I want to get mail
Jake Vickers wrote:
I also tried these settings (smtpd_tls_mandatory_protocols = !SSLv2) on
a Debian build (running 2.3.8) with a self-signed cert and am still
getting a SSLv2 connection. I'm sure I'm missing something glaringly
obvious...
smtpd_tls_mandatory_protocols only takes effect wh
i use dkimproxy 1.1 , I dont use the beta release on my box
On Fri, 24 Jul 2009 19:36:28 +0530 (IST), Zakir Shaikh
wrote:
> Thanks fakessh,
>
> Dkimproxy did the Magic!
> works gr8.. for both - Domain Keys & DKIM.
>
>
> Thanks & Regards,
> Zakir H. Shaikh
>
>
>
>
> _
On Jul 24, 2009, at 9:45 AM, Jay Kusler wrote:
We currently have a postfix MX front-end that uses MailScanner,
clamav, and spamassassin to preprocess incoming email. We use LDAP
lookups to determine valid recipients. Email that makes it through
all of that gets moved to a Cyrus imap mail
Thanks fakessh,
Dkimproxy did the Magic!
works gr8.. for both - Domain Keys & DKIM.
Thanks & Regards,
Zakir H. Shaikh
From: fakessh
To: Zakir Shaikh
Cc: postfix mailing list ; njo...@megan.vbhcs.org
Sent: Friday, 24 July, 2009 4:34:06 PM
Subject: Re: Domai
Michael Monnerie wrote, at 07/23/2009 10:33 AM:
> I just need a sieve that can call an external program to deliver mails.
> Is that really not existing?
Sieve is deliberately crippled in this way:
http://sieve.info/
One of its design goals was to reduce the chance of users performing
potentia
We currently have a postfix MX front-end that uses MailScanner, clamav,
and spamassassin to preprocess incoming email. We use LDAP lookups to
determine valid recipients. Email that makes it through all of that
gets moved to a Cyrus imap mailstore using LMTP
(mailbox_transport = lmtp:cyrusimap
Rodman Frowert wrote:
> I am wanting to accept mail for "mydomain" but I have users that don't
> need system (unix) accounts and I really don't want to create them
> just for their mail. Is there an easy way to lookup these users
> outside the local table? Also, what happens to my system users if
S. Berch wrote:
>
> smtps inetn - - -- smtpd
Note that this is in chroot mode.
If the rest of your master.cf is not, it should be disabled.
Other than that, good job.
Jake Vickers wrote:
Barney Desmond wrote:
2009/7/24 Jake Vickers :
I ma having a spot of trouble disabling SSLv2 on a Postfix 2.5.1
installation (from Fedora 9 repo). Here is my postconf:
$ postconf -n
smtpd_tls_mandatory_protocols = !SSLv2
As documented, this sh
> This is a Domain Keys issue. See the -i option to dk-filter to add which IPs
> should be signed.
> And note that Domain Keys is less used these days. Consider dropping it and
> using DKIM instead.
Thanks for the suggestion.
But it is Still Not Working. I tried with the " -i filename "opt
Barney Desmond wrote:
2009/7/24 Jake Vickers :
I ma having a spot of trouble disabling SSLv2 on a Postfix 2.5.1
installation (from Fedora 9 repo). Here is my postconf:
$ postconf -n
smtpd_tls_mandatory_protocols = !SSLv2
As documented, this shouldn't be necessary:
On Donnerstag 23 Juli 2009 Mikael Bak wrote:
> Postfix sends the email to amavisd-new
> for processing, and after that the email are pushed back to postfix
> for delivery.
>
> Your "deliver" program will have to be able to push back the email
> into postfix exactly as amavisd-new does. I think you
On Donnerstag 23 Juli 2009 Benny Pedersen wrote:
> sieve is cool yes, but deliver to a mailfolder dont need sieve if you
> add + addressing
Yes, Benny, but
1) I need sieve to *decide* where the mail should be dropped. I receive
mail to x...@y.z, which should go to folder AAA, so I'd need sieve t
On Jul 22, 2009, at 16:51, "Benny Pedersen" wrote:
yes this is clear to me its is so, but i dont know why self signed
ssl is being used so much when there is plenty of good trusted
signers :/
Because a selfsigned cert is good enough and FREE.
2009/7/24 Jake Vickers :
> I ma having a spot of trouble disabling SSLv2 on a Postfix 2.5.1
> installation (from Fedora 9 repo). Here is my postconf:
> $ postconf -n
> smtpd_tls_mandatory_protocols = !SSLv2
As documented, this shouldn't be necessary:
http://www.postfix.org/postconf.5.html#smtpd_
28 matches
Mail list logo