Hi,
I manage a web site that sends price change alerts to subscribers using
postfix with VERP to detect failed deliveries. When a bounce comes in it
is fed to a perl script (through procmail) which increments the email's
error count in the database until that count reaches 4 and the email is
Hi,
I have a virtual_alias_maps with a pcre entry like
/^(info|contact|etc)@/ localuser
and it delivers i...@anydomain.com to localuser even though
'anydomain.com' is not in virtual_alias_domains, is that normal?
On Thu, Oct 24, 2013 at 10:42:07AM +0200, Ralf Hildebrandt wrote:
* Louis-David Mitterrand vindex+lists-postfix-us...@apartia.org:
Hi,
I have a virtual_alias_maps with a pcre entry like
/^(info|contact|etc)@/ localuser
and it delivers i...@anydomain.com to localuser even
On Thu, Oct 24, 2013 at 10:04:08AM -0500, /dev/rob0 wrote:
On Thu, Oct 24, 2013 at 10:00:00AM -0500, /dev/rob0 forgot to
terminate a PCRE expression:
if /@example\.(com|net|org)$/
/^(info|contact|etc)@ localuser@mydestination.domain
endif
if /@example\.(com|net|org)$/
Hi,
Why is this accepted e-mail from=double-bounce@ instead of the real
sender address?
[later] Ah, maybe I understand... Is it a probe postfix sends to verify
the recipient (LDM@ in uppercase, which normally is always lowercas)?
May 9 10:38:03 zenon postfix/smtpd[26553]: connect from
On Tue, Jul 20, 2010 at 12:29:09PM -0400, Victor Duchovni wrote:
On Tue, Jul 20, 2010 at 10:14:01AM +0200, Louis-David Mitterrand wrote:
I can't seem to get postfix to match that header:
Subject: =?UTF-8?Q?Vos_Factures_arrivant_a_=C3=A9ch=C3=A9ance_-_FR0905249?=
with this /etc
Hi,
Can I select a specific transport depending on the envelope sender?
On Thu, Sep 02, 2010 at 08:21:06AM -0400, Wietse Venema wrote:
Louis-David Mitterrand:
Hi,
Can I select a specific transport depending on the envelope sender?
No, that would break mail delivery with local recipients.
You can have sender-dependent relayhost or default_transport
On Thu, Sep 02, 2010 at 09:01:44AM -0400, Wietse Venema wrote:
Louis-David Mitterrand:
On Thu, Sep 02, 2010 at 08:21:06AM -0400, Wietse Venema wrote:
Louis-David Mitterrand:
Hi,
Can I select a specific transport depending on the envelope sender?
No, that would break mail
Hi,
I can't seem to get postfix to match that header:
Subject:
=?UTF-8?Q?Vos_Factures_arrivant_a_=C3=A9ch=C3=A9ance_-_FR0905249?=
with this /etc/postfix/header_check entry (PCRE):
/^(Subject:
=\?UTF-8\?Q\?Vos_Factures_arrivant_a_=C3=A9ch=C3=A9ance_-_FR0905249\?=)/ REJECT
yet a:
On Wed, May 05, 2010 at 01:44:54PM -0400, Brian Evans - Postfix List wrote:
You could try this in /etc/postfis/header_checks
if
/^(Received|X-((Origin(ating)?|Client|MDRemote|Sender)-?IP|(Client|Remote_)Addr|PHP-Script)):/
if
On Thu, May 06, 2010 at 11:15:21AM +0200, Tom Hendrikx wrote:
On 06/05/10 10:58, Louis-David Mitterrand wrote:
On Wed, May 05, 2010 at 01:44:54PM -0400, Brian Evans - Postfix List wrote:
You could try this in /etc/postfis/header_checks
if
/^(Received|X-((Origin(ating)?|Client
On Wed, May 05, 2010 at 07:00:37PM +0200, Laurent CARON wrote:
Hi,
I'm basically trying to protect my users from the following:
Spam
- Sent from accounts hosted on freemail providers (yahoo, ...)
- Originating from AfriNIC ranges
- Tergetted at several dozen of users
The headers look
Hi,
I am using an (insanely) long pcre (see below) to reject
african/chinese/etc. spam that relays through large ISP's. An now it
seems I have reached a limit. When trying to add a single more
expression with a set of () parens I get this error:
postmap: warning: pcre map
On Mon, Mar 29, 2010 at 04:38:17PM +0200, Steve wrote:
Ohhh boy. Now looking at the regexp I see an error. Every line
starting with /[^:]*.+ should be replaced by /[^:]*:.+. Sorry for
that.
Hi Steve,
You if/endif suggestion for the prefix is interesting.
For added safety, the
On Mon, Mar 29, 2010 at 04:55:19PM +0200, Steve wrote:
You if/endif suggestion for the prefix is interesting.
For added safety, the individual rules should be anchored with ^ and the
bracketed atom plussed, no?
/^[^:]+:.+
Yes. You are right. But to be honest this should be enough
On Mon, Mar 29, 2010 at 05:16:39PM +0200, Steve wrote:
Ach. Again. I made errors. Sorry. It's hard to write here in such a
small edit box in a web interface. The above is not 100% correct. What
I wanted to write is:
You need the 'itsalltext' firefox extension to edit any web textarea
with
Hi,
A lot of spam comes from certain ip ranges (e.g. west africa) through
relays (large ISPs) that would be too onerous to block. To filter these
I am presently matching:
/^((Received|X-Originating-IP):.+\b(124\.120\.1\.(IP RANGE IN
REGEX)\b/
in pcre:/etc/postfix/header_access. But
Hi,
I'd like to implement an automatic whitelisting of outgoing addresses
(people I write to should be able to pass my heavy spam filter).
For a year I've been testing a minimal, proof-of-concept, whitelisting
script (see below) but haven't maintained or improved it. What I'd like
ideally is
19 matches
Mail list logo
