@lbutlr:
> if !/backup.*@/
> /^([^+_]*).*@(.*)/ backup+${1}.${2}@domain.tld
> endif
>
> I currently have the above in recipient_bbc
>
> /etc/postfix/main.cf:
>
> recipient_bcc_maps =3D pcre:$config_directory/recipient_bcc.pcre
>
> And this works perfectly and stores a copy of all email (sent
if !/backup.*@/
/^([^+_]*).*@(.*)/ backup+${1}.${2}@domain.tld
endif
I currently have the above in recipient_bbc
/etc/postfix/main.cf:
recipient_bcc_maps = pcre:$config_directory/recipient_bcc.pcre
And this works perfectly and stores a copy of all email (sent and received) in
a backup accoun
Stephan:
> Hi list,
>
> I am having a bad time setting up a postifx configuration that allows
> sending mails only when the sender actually "owns" the "From:"-address.
There is no such feature in Postfix. Postfix can control the MAIL FROM
address in SMTP commands, not the From header.
Wi
Hi list,
I am having a bad time setting up a postifx configuration that allows
sending mails only when the sender actually "owns" the "From:"-address.
I manage multiple domains the the login names are full qualified email
addresses as well. My "alias" table looks like this (goto is the login name
Thank you very much, sir. Much appreciated.
Süleyman Düzdaban
Ankara Üniversitesi
Bilgi İşlem Daire Başkanlığı - Sistem Grubu
0312 215 90 01 (Dahili: 3033)
On 02/07/2017 05:03 PM, Viktor Dukhovni wrote:
>> On Feb 7, 2017, at 7:59 AM, Süleyman Düzdaban
>> wrote:
>>
>> When I remove the record (
> On Feb 7, 2017, at 7:59 AM, Süleyman Düzdaban
> wrote:
>
> When I remove the record (For example, @ankara.edu.tr) from "alias"
> table then I can get "Recipient address rejected: User unknown in
> virtual mailbox table" message and that's what I want.
> So I can remove all of that records fro
Yes, you're right sir, we have for all of our domains ("postmap -q
@ankara.edu.tr(or other subdomains)
mysql:$config_directory/maps/sql-valiases.cf" yields some return value).
When I remove the record (For example, @ankara.edu.tr) from "alias"
table then I can get "Recipient address rejected: User
Hi Istvan,
> Noel Jones wrote:
> > Remember that header_checks won't match encoded subjects
We need to see the raw Subject header from the email that failed to
match. It was probably encoded.
$ scan -forma '%{subject}' .
=?UTF-8?B?VGhpcyBpcyBzcGFtLgo=?=
$ scan -forma '%(decode{subje
On 2017-02-06 23:19, Noel Jones wrote:
On 2/6/2017 3:23 PM, Istvan Prosinger wrote:
Hi All, and Happy New Year with a little delay :)
Comming to spam, header checks are one tool that I use frequently to
prevent it.
So, amongst all, I have this:
if !/^Subject: (.*)[Aa]liexpress/
/^Subject:(.*)
On 2017-02-06 22:56, Dominic Raferd wrote:
On 6 February 2017 at 21:23, Istvan Prosinger
wrote:
Hi All, and Happy New Year with a little delay :)
Comming to spam, header checks are one tool that I use frequently to
prevent it.
So, amongst all, I have this:
if !/^Subject: (.*)[Aa]liexpress/
10 matches
Mail list logo