Jose Borges Ferreira:
> On Fri, Jul 18, 2014 at 5:05 PM, wrote:
> > So my last questioni is: can I choose smtp transport based on user used for
> > smtpd authentication?
>
> Have you tried to use check_sasl_access table and return a "FILTER
> smtp1:". You will need Postfix version 2.11 or later.
On Fri, Jul 18, 2014 at 5:05 PM, wrote:
> So my last questioni is: can I choose smtp transport based on user used for
> smtpd authentication?
Have you tried to use check_sasl_access table and return a "FILTER
smtp1:". You will need Postfix version 2.11 or later.
http://www.postfix.org/postconf.
i...@itrezero.it:
> So my last questioni is: can I choose smtp transport based on user
> used for smtpd authentication?
There is no such feature, or else it would be documented.
If you don't want to implement multiple MTA personalities with
multiple MTA instances, then there are only partial solu
Many thanks Mr. Venema.
I just tried a "multi instance" solution and it works very well. The problem
is when the number of IPs become very large: what if 20 IPs => 20 Postfix
instances? I believe that this way is resource-consuming and can't be
scalable as I'd like.
I also tried to use sender_dep
--- Original message ---
From: "Wietse Venema"
Date: 18 July 2014, 17:43:34
> Wietse Venema:
> > wishmaster:
> > > Hi!
> > >
> > > I have strange behavior of Postfix (postfix-2.11.1_1,1)
> > >
> > > I use FreeBSD as base system and some jails. Each jail use
> > > virtual network stac
tejas sarade:
> >
> > You mean: no MX records; otherwise this is correct.
>
> Yes, that is what I meant.
>
> And I think that Postfix parameter ignore_mx_lookup_error controls the
> behaviour when there is no response for MX lookup at all.
Indeed. No response is an error.
> I guess that 'no MX'
Am 18.07.2014 16:41, schrieb tejas sarade:
>> You mean: no MX records; otherwise this is correct.
>
> Yes, that is what I meant.
>
> And I think that Postfix parameter ignore_mx_lookup_error controls the
> behaviour when there is no response for MX lookup at all.
> I guess that 'no MX' and 'no r
>
> You mean: no MX records; otherwise this is correct.
Yes, that is what I meant.
And I think that Postfix parameter ignore_mx_lookup_error controls the
behaviour when there is no response for MX lookup at all.
I guess that 'no MX' and 'no response for MX lookup' are handled differently.
Andrea:
> Hello,
> I'm having a problem with header_checks pcre
>
> This rule is working:
>
> # Block mail from xxx.yyy.zzz.www and russian domain
> if /.*xxx\.yyy\.zzz\.www/
> /.*from.*\@.*\.ru.*to.*\@.*/
> reject Mail from russian domain
> endif
>
> This is not:
>
> # Block mail from
On 7/18/2014 9:04 AM, Andrea wrote:
> Hello,
> I'm having a problem with header_checks pcre
>
> This rule is working:
>
> # Block mail from xxx.yyy.zzz.www and russian domain
> if /.*xxx\.yyy\.zzz\.www/
> /.*from.*\@.*\.ru.*to.*\@.*/
> reject Mail from russian domain
> endif
>
I doubt t
Wietse Venema:
> wishmaster:
> > Hi!
> >
> >I have strange behavior of Postfix (postfix-2.11.1_1,1)
> >
> >I use FreeBSD as base system and some jails. Each jail use
> >virtual network stack (vnet). Problem is in latency when
> >connection is outside from the base system only.
> >
Hello,
I'm having a problem with header_checks pcre
This rule is working:
# Block mail from xxx.yyy.zzz.www and russian domain
if /.*xxx\.yyy\.zzz\.www/
/.*from.*\@.*\.ru.*to.*\@.*/
reject Mail from russian domain
endif
This is not:
# Block mail from xxx.yyy.zzz.www with sender differen
wishmaster:
> Hi!
>
>I have strange behavior of Postfix (postfix-2.11.1_1,1)
>
>I use FreeBSD as base system and some jails. Each jail use
>virtual network stack (vnet). Problem is in latency when
>connection is outside from the base system only.
>
> telnet localhost 25 works fin
Hi!
I have strange behavior of Postfix (postfix-2.11.1_1,1)
I use FreeBSD as base system and some jails. Each jail use virtual network
stack (vnet). Problem is in latency when connection is outside from the base
system only.
telnet localhost 25 works fine, but if this connection or fr
Wietse Venema:
> Wietse Venema:
> > i...@itrezero.it:
> > > Good morning.
> > > Maybe I wasn't able to write a clear request :-( I'll try another way.
> > >
> > > I've a set of IPs. I need to authenticate against each of them
> > > (useing different accounts on the same domain: us...@domain.com ,
Wietse Venema:
> i...@itrezero.it:
> > Good morning.
> > Maybe I wasn't able to write a clear request :-( I'll try another way.
> >
> > I've a set of IPs. I need to authenticate against each of them
> > (useing different accounts on the same domain: us...@domain.com ,
> > us...@domain.com , ) and
i...@itrezero.it:
> Good morning.
> Maybe I wasn't able to write a clear request :-( I'll try another way.
>
> I've a set of IPs. I need to authenticate against each of them
> (useing different accounts on the same domain: us...@domain.com ,
> us...@domain.com , ) and want that emails are to be se
Am 18.07.2014 14:28, schrieb tejas sarade:
> As per the RFC 5321 when DNS lookup for recipient domain returns empty MX
> records
> it should try to deliver mail to A record of that domain.
>
> Is there any way in Postfix to disable this behaviour?
just don't do that, even don't try that
not
tejas sarade:
> Hello,
>
> As per the RFC 5321 when DNS lookup for recipient domain returns empty MX
> records it should try to deliver mail to A record of that domain.
You mean: no MX records; otherwise this is correct.
> Is there any way in Postfix to disable this behaviour?
This will not be
Hello,
As per the RFC 5321 when DNS lookup for recipient domain returns empty MX
records it should try to deliver mail to A record of that domain.
Is there any way in Postfix to disable this behaviour?
Good morning.
Maybe I wasn't able to write a clear request :-( I'll try another way.
I've a set of IPs. I need to authenticate against each of them (useing
different accounts on the same domain: us...@domain.com , us...@domain.com , )
and want that emails are to be sent through the same IP.
For
21 matches
Mail list logo
