Hi all,
I did setup a postfix - amavis - etc. system and its a pleasure to work
with.
Thanks everybody who has parts on it!
There is a tiny problem I have, where I'm sure that the solution is already
here somewhere...
I just can not find it...
I'm looking for a way to simple map a fixed username
Hi all
Just curiosity: it's not unwanted to check postscreen_dnsbl for an IP
which is blacklisted in postscreen_access_list?
Nov 12 12:18:40 srv1 postfix/postscreen[26755]: CONNECT from
[94.177.23.227]:50497 to [176.223.199.54]:25
Nov 12 12:18:40 srv1 postfix/postscreen[26755]: BLACKLISTED
[
extremum:
> Hi all,
>
> I did setup a postfix - amavis - etc. system and its a pleasure to work
> with.
> Thanks everybody who has parts on it!
>
> There is a tiny problem I have, where I'm sure that the solution is already
> here somewhere...
> I just can not find it...
> I'm looking for a way
Birta Levente:
> Hi all
>
> Just curiosity: it's not unwanted to check postscreen_dnsbl for an IP
> which is blacklisted in postscreen_access_list?
That would be a waste of Postfix resources. It would make Postfix less
resistant against abuse from a known-bad netblock.
Wietse
> Nov 12 1
as mentioned here:
http://postfix.1071664.n5.nabble.com/Virtual-domains-virtual-mailboxes-and-catch-all-td15461.html
i have to write a Perl string to achieve that functionality...
lets see...
--
View this message in context:
http://postfix.1071664.n5.nabble.com/direction-needed-tp72410p72413
Wietse Venema wrote
> I suppose that you are not maintaining every domain by hand. In
> that case, your "add a new domain" procedure should create not only
> main.cf entries but also the postmaster virtual alias.
not sure what you mean,
but im using no gui or something.
up there the http://www.p
Am 12.11.2014 um 13:37 schrieb extremum:
Wietse Venema wrote
I suppose that you are not maintaining every domain by hand. In
that case, your "add a new domain" procedure should create not only
main.cf entries but also the postmaster virtual alias.
not sure what you mean,
but im using no gui o
Hi,
Messages with a certain content type should be bcc'd to an additional
address for my use-case at hand.
I guess I could do this in two rounds:
1) with header_checks relay to itself on a different port (FILTER)
2) on that secondary smtpd, I could use the
http://www.postfix.org/postconf.5.html#
On 12/11/2014 14:21, Wietse Venema wrote:
Birta Levente:
Hi all
Just curiosity: it's not unwanted to check postscreen_dnsbl for an IP
which is blacklisted in postscreen_access_list?
That would be a waste of Postfix resources. It would make Postfix less
resistant against abuse from a known-bad
yes managing my virtual file with scripts is something i haven't thought
yet
but sure...thats possible (talking about <20 domains )
for now I did add the required users by hand, which does what I wanted now.
Just thought that there is a simpler way to handle that default accounts
by doing a
Birta Levente:
> Just curiosity: it's not unwanted to check postscreen_dnsbl for an IP
> which is blacklisted in postscreen_access_list?
Note: don't use no double negatives.
Wietse:
> That would be a waste of Postfix resources. It would make Postfix less
> resistant against abuse from a known-bad
On 12/11/2014 15:53, Wietse Venema wrote:
Birta Levente:
Just curiosity: it's not unwanted to check postscreen_dnsbl for an IP
which is blacklisted in postscreen_access_list?
Note: don't use no double negatives.
Wietse:
That would be a waste of Postfix resources. It would make Postfix less
re
Ralf Hauser:
> Hi,
>
> Messages with a certain content type should be bcc'd to an additional
> address for my use-case at hand.
That is currently not built into Postfix, but it could be done with
a Milter: in the header and body event handlers look at the content,
and in the end-of-message handle
Wietse Venema:
> Ralf Hauser:
> > Hi,
> >
> > Messages with a certain content type should be bcc'd to an additional
> > address for my use-case at hand.
>
> That is currently not built into Postfix, but it could be done with
> a Milter: in the header and body event handlers look at the content,
>
wietse:
/^(RCPT\s+TO:<.*>.*\s+NOTIFY=.*)/ $1
/^(RCPT\s+TO:<.*>.*)/ $1 NOTIFY=SUCCESS,DELAY,FAILURE
the regex above don't match on 'RCPT TO: ' ( SPACE
after colon )
I use now:
/^(RCPT\s+TO:\s*<.*>.*\s+NOTIFY=.*)/ $1
/^(RCPT\s+TO:\s*<.*>.*)/ $1 NOTIFY=SUCCESS,DELAY,FAILURE
Andreas
On Wed, Nov 12, 2014 at 05:56:38PM +0100, A. Schulze wrote:
>
> wietse:
> >/^(RCPT\s+TO:<.*>.*\s+NOTIFY=.*)/ $1
> >/^(RCPT\s+TO:<.*>.*)/ $1 NOTIFY=SUCCESS,DELAY,FAILURE
>
> the regex above don't match on 'RCPT TO: ' ( SPACE after
> colon )
Note the extra space violates RFCs 5321, 2821, 821. How
Viktor Dukhovni:
> On Wed, Nov 12, 2014 at 05:56:38PM +0100, A. Schulze wrote:
> >
> > wietse:
> > >/^(RCPT\s+TO:<.*>.*\s+NOTIFY=.*)/ $1
> > >/^(RCPT\s+TO:<.*>.*)/ $1 NOTIFY=SUCCESS,DELAY,FAILURE
> >
> > the regex above don't match on 'RCPT TO: ' ( SPACE after
> > colon )
>
> Note the extra spac
A. Schulze:
>
> wietse:
> > /^(RCPT\s+TO:<.*>.*\s+NOTIFY=.*)/ $1
> > /^(RCPT\s+TO:<.*>.*)/ $1 NOTIFY=SUCCESS,DELAY,FAILURE
>
> the regex above don't match on 'RCPT TO: ' ( SPACE
> after colon )
That is invalid syntax. What software (other than home-grown
scripts) sends commands like that?
On Wed, Nov 12, 2014, Wietse Venema wrote:
> A. Schulze:
> > the regex above don't match on 'RCPT TO: ' ( SPACE
> That is invalid syntax. What software (other than home-grown
> scripts) sends commands like that?
Last time I looked: at least cashedge.com, used by several US
banks(?) :-(
Probab
Claus Assmann:
> On Wed, Nov 12, 2014, Wietse Venema wrote:
> > A. Schulze:
>
> > > the regex above don't match on 'RCPT TO: ' ( SPACE
>
> > That is invalid syntax. What software (other than home-grown
> > scripts) sends commands like that?
>
> Last time I looked: at least cashedge.com, used
20 matches
Mail list logo
