Thanks again for the quick answer.
Le 03/12/2014 17:56, Wietse Venema a écrit :
> Running one process per email address lookup would be expensive.
I know, that's what I explained in my original post, it's only for
testing purposes, I wouldn't use that on production servers; the whole
Postfix->DSP
On Wed, Dec 03, 2014 at 04:55:47PM +, Viktor Dukhovni wrote:
> On Wed, Dec 03, 2014 at 04:36:12PM +, James Bailey wrote:
>
> > is it possible to use a non fully qualified host name as relayhost?
>
> Not by default. And it is generally not a good idea to change this.
>
> However, if you
On Wed, 3 Dec 2014 16:55:47 +
Viktor Dukhovni wrote:
> On Wed, Dec 03, 2014 at 04:36:12PM +, James Bailey wrote:
>
> > is it possible to use a non fully qualified host name as relayhost?
>
> Not by default. And it is generally not a good idea to change this.
>
> However, if you replac
Rapha?l Halimi:
> Le 03/12/2014 15:51, Wietse Venema a ?crit :
> > You may be able to use the reject_unverified_sender/recipient feature
> > (which is implemented by the verify(8) daemon).
> >
> > The recursion that you refer to is not implemented in a single
> > program, but by a different progra
On Wed, Dec 03, 2014 at 04:36:12PM +, James Bailey wrote:
> is it possible to use a non fully qualified host name as relayhost?
Not by default. And it is generally not a good idea to change this.
However, if you replace the relayhost setting with:
# Default empty value
# relayhost
Hello,
is it possible to use a non fully qualified host name as relayhost?
My client has a number of different relay hosts in DCs globally these
are marked for example us1, us2, in1, au2. So a relay-host. I would
simple like to be able roll out a default single main.cf globally with
relayhost
On Wed, Dec 03, 2014 at 01:40:12PM +0100, mancyb...@gmail.com wrote:
> Hi, my whole 'smtpd_recipient_restrictions' is:
>
> smtpd_recipient_restrictions =
> permit_mynetworks,
> check_policy_service inet:127.0.0.1:10031,
> check_sender_access hash:/etc/postfix/sender_access,
Note, "check_sende
Le 03/12/2014 15:51, Wietse Venema a écrit :
> You may be able to use the reject_unverified_sender/recipient feature
> (which is implemented by the verify(8) daemon).
>
> The recursion that you refer to is not implemented in a single
> program, but by a different programs (cleanup(8), local(8)) at
Rapha?l Halimi:
> So the question is: is there a way to call one of Postfix binaries with
> a recipient e-mail address as input, and get the final e-mail address as
> output after it has done the recursive lookups on the relevant tables
> (or no output at all if the address doesn't resolve to any k
Wietse Venema:
> Jose Borges Ferreira:
> > On Wed, Dec 3, 2014 at 1:51 PM, Wietse Venema wrote:
> > > Jose Borges Ferreira:
> > >> This is the scenario.
> > >> Box 1 : just receive email from "outside" - inbound flow.
> > >> Box 2 : used to sent email to the "outside" - oubound flow.
> > >
> > > I
Hi,
I'm trying to use DSPAM's external lookups engine to validate e-mail
addresses before creating an UID in its database. This engine has only
two backends for now: ldap, and "program".
Even if I won't end up using this (the setup I have right now works
correctly; mails are sent to DSPAM only af
Jose Borges Ferreira:
> On Wed, Dec 3, 2014 at 1:51 PM, Wietse Venema wrote:
> > Jose Borges Ferreira:
> >> This is the scenario.
> >> Box 1 : just receive email from "outside" - inbound flow.
> >> Box 2 : used to sent email to the "outside" - oubound flow.
> >
> > Inbound MTA: primary MX for your
Am 03.12.2014 um 14:41 schrieb mancyb...@gmail.com:
On Wed, 03 Dec 2014 14:11:44 +0100
"li...@rhsoft.net" wrote:
Am 03.12.2014 um 13:40 schrieb mancyb...@gmail.com:
On Wed, 03 Dec 2014 13:18:45 +0100
"li...@rhsoft.net" wrote:
put the exchange host in "mynetworks" and just add "permit_myne
On Wed, Dec 3, 2014 at 1:51 PM, Wietse Venema wrote:
> Jose Borges Ferreira:
>> This is the scenario.
>> Box 1 : just receive email from "outside" - inbound flow.
>> Box 2 : used to sent email to the "outside" - oubound flow.
>
> Inbound MTA: primary MX for your domain(s). If mail can't be
> deliv
Jose Borges Ferreira:
> This is the scenario.
> Box 1 : just receive email from "outside" - inbound flow.
> Box 2 : used to sent email to the "outside" - oubound flow.
Inbound MTA: primary MX for your domain(s). If mail can't be
delivered, use Postfix's relayhost feature to deliver outbound mail
v
On Wed, 03 Dec 2014 14:11:44 +0100
"li...@rhsoft.net" wrote:
>
> Am 03.12.2014 um 13:40 schrieb mancyb...@gmail.com:
> > On Wed, 03 Dec 2014 13:18:45 +0100
> > "li...@rhsoft.net" wrote:
> >> put the exchange host in "mynetworks" and just add "permit_mynetworks"
> >> *before* "reject_authenticat
Am 03.12.2014 um 14:32 schrieb Jose Borges Ferreira:
2) I want to forward bounces to a specific host. I was looking for a
way to specify a relayhost or a transport for that class of messages
and couldn't find a way to achieve that.
There is no RFC that requires this. I am highly-suspicious wh
ferriswheel:
> the current options on http://www.postfix.org/lists.html are limited
> to sub-scribe or un-sub-scribe.
These are the available options (i.e. the documentation is accurate).
I do not run the mialing list manager on my own system.
Wietse
On Wed, Dec 3, 2014 at 12:28 PM, Wietse Venema wrote:
> Jose Borges Ferreira:
>> Hi,
>>
>> I'm looking deeper into bounce handling in Postfix and cam across 2 issues:
>>
>> 1) The default From: header, "MAILER-DAEMON (Mail Delivery System)",
>> is not RFC valid.
>
> YOU create a non-compliant co
Am 03.12.2014 um 13:40 schrieb mancyb...@gmail.com:
On Wed, 03 Dec 2014 13:18:45 +0100
"li...@rhsoft.net" wrote:
put the exchange host in "mynetworks" and just add "permit_mynetworks"
*before* "reject_authenticated_sender_login_mismatch"
Hi, my whole 'smtpd_recipient_restrictions' is:
smtpd
On Wed, 03 Dec 2014 13:18:45 +0100
"li...@rhsoft.net" wrote:
>
> Am 03.12.2014 um 13:06 schrieb mancyb...@gmail.com:
> > Hi, I'm currently the following two parameters:
> >
> > reject_authenticated_sender_login_mismatch,
> > reject_unauthenticated_sender_login_mismatch,
> >
> > under 'smtpd_
Jose Borges Ferreira:
> Hi,
>
> I'm looking deeper into bounce handling in Postfix and cam across 2 issues:
>
> 1) The default From: header, "MAILER-DAEMON (Mail Delivery System)",
> is not RFC valid.
YOU create a non-compliant configuration when YOU disable
append_at_myorigin for local submis
Am 03.12.2014 um 13:06 schrieb mancyb...@gmail.com:
Hi, I'm currently the following two parameters:
reject_authenticated_sender_login_mismatch,
reject_unauthenticated_sender_login_mismatch,
under 'smtpd_recipient_restrictions'
to enforce sasl username+password authentication.
As you may k
Hi, I'm currently the following two parameters:
reject_authenticated_sender_login_mismatch,
reject_unauthenticated_sender_login_mismatch,
under 'smtpd_recipient_restrictions'
to enforce sasl username+password authentication.
As you may know, M$ Exchange, when using an external SMTP, can't send
Am 03.12.2014 um 12:43 schrieb Jose Borges Ferreira:
I'm looking deeper into bounce handling in Postfix and cam across 2 issues:
1) The default From: header, "MAILER-DAEMON (Mail Delivery System)",
is not RFC valid.
a bounce has no envelope sender (null sender) and so no from-address
2) I
Hi,
I'm looking deeper into bounce handling in Postfix and cam across 2 issues:
1) The default From: header, "MAILER-DAEMON (Mail Delivery System)",
is not RFC valid.
It can change, though.
in ubuntu install the postfix-doc package, then
cat /usr/share/doc/postfix-doc/exampl
26 matches
Mail list logo
