Policyd-spf and RBL white listing

2016-04-18 Thread lists
 >From what I can tell, if you whitelist a domain, the policyd-spf check is skipped. Now I white listed domains to stop the RBL from blocking them, but it would be nice to see if SPF passes. Am I right about the SPF being skipped? While I'm at it, can you whitelist specific users at a domain, that is the full email address, or only the domain itself. 


Re: Autoresponder

2016-04-18 Thread Gao

Hi Dave,

Here is the copy of the autoresponder 1.6.3 Perl script.

Gao

On 16-04-15 11:59 AM, David Mehler wrote:

Hello,

I'm looking for an autoresponder, free, and one that does not rely on
postfixadmin.

I saw one featured in a howtoforge article called Autoresponse 1.6.3
but that has been taken down, which is unfortunate, because how it
worked, sending an email to an address sounded great for my needs.

If anyone has this, or has any suggestions i'd appreciate them. I have
looked on the postfix page and the autoresponders there are paid
products, and the one that isn't uses an LDAP format which I am not
using.

Thanks.
Dave.




autoresponse-1.6.3.tar.gz
Description: application/gzip


Re: Content Filter only for incoming mails

2016-04-18 Thread Thomas Leuxner
* BP20  2016.04.18 10:41:

> Thank you, can you please explain it a bit more with an example?
> What do you mean with "dedicated submission instance"?

1.2.3.4:submission inet n   -   -   -   -   smtpd
-o syslog_name=postfix/submission
...


signature.asc
Description: Digital signature


Re: reject empty sender address for authenticated users

2016-04-18 Thread Michael D. Sofka

On 04/15/2016 05:42 PM, Noel Jones wrote:

On 4/15/2016 4:02 PM, Michael D. Sofka wrote:

I would like to be able to reject the empty envelope-sender, <>, for
authenticated email to our submission and smtps ports.  That is, I
want to stop:

235 2.7.0 Authentication successful
mail from:<>
250 2.1.0 Ok
rcpt to:
250 2.1.5 Ok


...

It's pretty easy to block the null sender on port 587, and I don't
think that's an unreasonable request.  I'll hope/assume you don't
allow AUTH on port 25 since that complicates this.



SMTP-AUTH is allowed on port 25, but it is only available on these 
servers on-campus, and restricted to a few, known, server.  So this 
restriction meets our needs.



All you need to do is add a check_sender_access map to the master.cf
submission service. Simple (incomplete?) example:

# main.cf
submission_sender_checks =
check_sender_access hash:/etc/postfix/reject_null_sender

# master.cf
#  existing submission entry
submission ... smtpd
   ... other options ...
#  add sender restrictions
   -o smtpd_sender_restrictions=$submission_sender_checks


# reject_null_sender
<>  REJECT null sender not allowed


And that works!  Thank you!!

Mike

--
Michael D. Sofka   sof...@rpi.edu
C&MT Sr. Systems Programmer,   Email, TeX, Epistemology
Rensselaer Polytechnic Institute, Troy, NY.  http://www.rpi.edu/~sofkam/


Re: BURL

2016-04-18 Thread Charles Marcus
On 4/18/2016 11:46 AM, wie...@porcupine.org (Wietse Venema)
 wrote:
> Charles Marcus:
>> I would s love to be able to uncheck the 'Save copy to Sent folder'
>> for my postfix+dovecot accounts.
> What client would do this?

Also, just noticed that there is apparently one MUA (work in progress)
that supports BURL:

https://docs.kde.org/trunk4/en/extragear-pim/trojita/using-kapp.html

Main page here:

http://trojita.flaska.net/


Re: BURL

2016-04-18 Thread Charles Marcus
On 4/18/2016 11:46 AM, wie...@porcupine.org (Wietse Venema)
 wrote:
> Charles Marcus:
>> I would s love to be able to uncheck the 'Save copy to Sent folder'
>> for my postfix+dovecot accounts.
> What client would do this?

Thunderbird (alluded to this in my OP, as this was a result of a
question on the Thunderbird list)...

Although, if you recall, there was a short conversation between you and
Timo (dovecot author) about him implementing this in dovecot, which
required a little help on the postfix side - one of you said something
about 20 lines or so of code - or, whatever, it appeared to be
relatively trivial and you didn't seem averse to doing it.

Copying Timo in in case he wants to add anything...

Thanks as always Wietse for postfix!

Charles


Re: Decoding base64 emails for content filtering

2016-04-18 Thread Viktor Dukhovni
On Mon, Apr 18, 2016 at 07:45:01AM -0700, BP20 wrote:

> Does anyone have an idea for how to decode base64 encoded
> emails (Content-Transfer-Encoding: base64) in order to filter the
> content?
> http://www.postfix.org/FILTER_README.html#simple_filter
>   

Base64 decoding is the easy part, the tricky part is MIME parsing,
and then deciding which MIME parts one wants to (base64) decode.

-- 
Viktor.


Re: Decoding base64 emails for content filtering

2016-04-18 Thread Michael J Wise

> On 2016-04-18 16:45, BP20 wrote:
>> Does anyone have an idea for how to decode base64 encoded
>> emails (Content-Transfer-Encoding: base64) in order to filter the
>> content?
>> http://www.postfix.org/FILTER_README.html#simple_filter
>> 
>
> As the content filter can be any file you can execute, several in fact.

Perl has a very nice Base64 decoder module.

If someone wanted to start off running, I'd look sample Policy Daemon
source code that comes with Postfix.

Aloha mai Nai`a.
-- 
" So this is how Liberty dies ...  http://kapu.net/~mjwise/
" To Thunderous Applause.




Re: too many connections

2016-04-18 Thread Viktor Dukhovni
On Mon, Apr 18, 2016 at 12:15:13PM +0200, Thomas kinghorn wrote:

> In master.cf
> 
> transport_maps = hash:/etc/postfix/vox_transport
> vox_destination_concurrency_limit = 20
> vox_destination_rate_delay = 2s

Setting a rate delay reduces the concurrency to 1.

> vox_destination_recipient_limit = 6

Setting a low recipient limit causes multi-recipient mesages to
split into more parts and consume more connections.

So if the destination accepts more than 6 recipients at a time,
use a larger limit.

The best way to resolve your issue is to get whitelisted by the
receiving system.

You may be able to reduce the impact of downstream connection limits
by slowing down positive and negative feedback:

smtp_destination_initial_concurrency = 2
smtp_destination_concurrency_positive_feedback = 0.2 / concurrency
smtp_destination_concurrency_negative_feedback = 0.5 / concurrency

This will grow the concurrency for each destination more slowly
and and will avoid throttling too quickly.

-- 
Viktor.


Re: BURL

2016-04-18 Thread Wietse Venema
Charles Marcus:
> I would s love to be able to uncheck the 'Save copy to Sent folder'
> for my postfix+dovecot accounts.

What client would do this?

Wietse


Re: too many connections

2016-04-18 Thread Wietse Venema
Thomas kinghorn:
> Good morning List.
> 
> I have a problem where Vox Telecoms is temp rejecting our mail stating "too
> many connections".
> 
> I was thinking of a transport_map to delay control the connection rate but
> Vox hosts the email for many domains, so it would be impossible to create
> an accurate list.
> 
> Is there an easier way?

Alas, not. 

Scheduling the concurrency by (primary) MX host(s) requires that
the scheduler (queue manager) knows the MX hosts for recipient
destination. As long as different destinations have overlap in the
sets of (primary) MX hosts, those destinations should be scheduled
together.

It is not impossible but it would require splitting the SMTP client
into two parts: one that looks up MX hosts, and one part that
delivers mail.

Postfix copies this behavior from qmail.

> in vox_transport
> 
> 
> domain1vox:
> domain2vox:
> domain3vox:

Yes.

Wietse


Re: Decoding base64 emails for content filtering

2016-04-18 Thread Sven Schwedas
On 2016-04-18 16:45, BP20 wrote:
> Does anyone have an idea for how to decode base64 encoded
> emails (Content-Transfer-Encoding: base64) in order to filter the
> content?
> http://www.postfix.org/FILTER_README.html#simple_filter
>   

As the content filter can be any file you can execute, several in fact.

You can take a look at base64-de/encoding in bash (will most likely
involve perl or python), or write the filter in a real language to begin
with.

All your program needs is to take a mail from stdin, do things,
re-inject the mail if appropriate, and set a proper status code.


-- 
Mit freundlichen Grüßen, / Best Regards,
Sven Schwedas
Systemadministrator
TAO Beratungs- und Management GmbH | Lendplatz 45 | A - 8020 Graz
Mail/XMPP: sven.schwe...@tao.at | +43 (0)680 301 7167
http://software.tao.at



signature.asc
Description: OpenPGP digital signature


Decoding base64 emails for content filtering

2016-04-18 Thread BP20
Does anyone have an idea for how to decode base64 encoded
emails (Content-Transfer-Encoding: base64) in order to filter the
content?
http://www.postfix.org/FILTER_README.html#simple_filter
  



--
View this message in context: 
http://postfix.1071664.n5.nabble.com/Decoding-base64-emails-for-content-filtering-tp83449.html
Sent from the Postfix Users mailing list archive at Nabble.com.


“smtp_generic_maps” and “smtp_sender_dependent_authentication”

2016-04-18 Thread Postfix User
I have a question regarding “smtp_generic_maps” and
“smtp_sender_dependent_authentication” with
“sender_dependent_relayhost_maps”.

I have some users who have addresses in the form of:
“u...@localdomain.com” whose name should be rewritten to
u...@newdomain.com. The “new” name should then be looked up using the
setting in “sender_dependent_relayhost_maps”.

Will this actually work? I wanted to get some confirmation before I
actually tried it. Also, this should only act on addresses used when
sending email, not when email is received.

Thanks!


Re: SV: domain rewrite/redirect [SOLVED]

2016-04-18 Thread Matteo Cazzador

I'v solved , i made a configuration error.

Thanks


Il 18/04/2016 14:02, Matteo Cazzador ha scritto:


Hi thanks but this not solve my problem maybe because i use virtualmin 
with virtual host.


I need that mail.example.com will be consider like example.com in 
receiving mail


Thanks


Il 18/04/2016 13:35, Sebastian Nielsen ha scritto:


Simplest way is to add mail.example.com to your mydomains. Then mails 
both to t...@mail.example.com  and 
t...@example.com  will arrive to the account 
“test” on your server. Same is for example recommended to do with 
domain literals (IP addresses like test@[123.123.123.123 
] where 123.123.123.123 is your 
mailserver IP)


*Från:*owner-postfix-us...@postfix.org 
[mailto:owner-postfix-us...@postfix.org] *För *Matteo Cazzador

*Skickat:* den 18 april 2016 12:44
*Till:* postfix-users@postfix.org
*Ämne:* domain rewrite/redirect [invalid signature!]

Hi, i 've a question, which is the better way to do this please:

i've a virtual domain "example.com" on this server i receive mail too 
from mail.example.com


An example

any mail receive from t...@mail.example.com 
 must redirect to t...@example.com 



I try with canonical maps but i obtain relay access denied when i 
receive mail from t...@mail.example.com 


Can someone help me please.

Thanks



--
Rispetta l'ambiente: se non ti è necessario,  non stampare questa mail.
Le informazioni contenute in questa e-mail e nei files eventualmente
allegati sono destinate unicamente ai destinatari della stessa
e sono da considerarsi strettamente riservate.
E' proibito copiare, salvare, utilizzare,  inoltrare a terzi e diffondere
il contenuto della presente senza il preventivo consenso, ai sensi
dell'articolo 616 c.p. e della Legge n. 196/2003.
Se avete ricevuto questo messaggio per errore siete pregati di comunicarlo
immediatamente all'indirizzo mittente, nonché di cancellarne il contenuto
senza procedere ad ulteriore o differente trattamento.
**
Ing. Matteo Cazzador
NetLite snc di Cazzador Gagliardi
Corso Vittorio Emanuele II, 188 37069
Villafranca di Verona VR
Tel 0454856656
Fax 0454856655
Email:mat...@netlite.it 
Web:http://www.netlite.it
**


--

Rispetta l'ambiente: se non ti è necessario,  non stampare questa mail.


Le informazioni contenute in questa e-mail e nei files eventualmente
allegati sono destinate unicamente ai destinatari della stessa
e sono da considerarsi strettamente riservate.
E' proibito copiare, salvare, utilizzare,  inoltrare a terzi e diffondere
il contenuto della presente senza il preventivo consenso, ai sensi
dell'articolo 616 c.p. e della Legge n. 196/2003.
Se avete ricevuto questo messaggio per errore siete pregati di comunicarlo
immediatamente all'indirizzo mittente, nonché di cancellarne il contenuto
senza procedere ad ulteriore o differente trattamento.


**
Ing. Matteo Cazzador
NetLite snc di Cazzador Gagliardi
Corso Vittorio Emanuele II, 188 37069
Villafranca di Verona VR
Tel 0454856656
Fax 0454856655
Email:mat...@netlite.it
Web:http://www.netlite.it
**


--

Rispetta l'ambiente: se non ti è necessario,  non stampare questa mail.


Le informazioni contenute in questa e-mail e nei files eventualmente
allegati sono destinate unicamente ai destinatari della stessa
e sono da considerarsi strettamente riservate.
E' proibito copiare, salvare, utilizzare,  inoltrare a terzi e diffondere
il contenuto della presente senza il preventivo consenso, ai sensi
dell'articolo 616 c.p. e della Legge n. 196/2003.
Se avete ricevuto questo messaggio per errore siete pregati di comunicarlo
immediatamente all'indirizzo mittente, nonché di cancellarne il contenuto
senza procedere ad ulteriore o differente trattamento.


**
Ing. Matteo Cazzador
NetLite snc di Cazzador Gagliardi
Corso Vittorio Emanuele II, 188 37069
Villafranca di Verona VR
Tel 0454856656
Fax 0454856655
Email: mat...@netlite.it
Web: http://www.netlite.it
**



smime.p7s
Description: Firma crittografica S/MIME


Re: BURL

2016-04-18 Thread Charles Marcus
On 4/18/2016 9:42 AM, Charles Marcus  wrote:
> I also found this email from Mike Abbot in April 2010 announcing
> Apple's contribution of a patch for both postfix and dovecot for BURL
> support, and for CATENATE and URLAUTH support for dovecot too, so I'm
> confused about the comment about Apple not supporting it:

Sorry, forgot the link:

http://opensource.apple.com//source/postfix/postfix-229/patches/burl.patch

>
> So... anyone know what happened here?
>
> I would s love to be able to uncheck the 'Save copy to Sent
> folder' for my postfix+dovecot accounts.
>
>
> */Charles/*/*
> */
>



Re: BURL

2016-04-18 Thread Charles Marcus
On 3/31/2014 7:22 AM, wie...@porcupine.org (Wietse Venema)
 wrote:
> Viktor Dukhovni:
>> On Sun, Mar 30, 2014 at 09:13:19PM -0400, Wietse Venema wrote:
>>
>>> Viktor Dukhovni:
 Postfix does not yet support Apple's BURL SMTP extension.  With
 Apple as the only MUA that supports BURL, it probably does not make
 sense for Postfix to support BURL.
>>> Last time I asked (late 2013) Apple currently does not support BURL.
> I was looking for client software so that I could test Postfix
> BURL support without having to implement my own mail client first.
> I saw no BURL activity from iPhone or iPad with Apple's patch for
> Postfix, and the author of the patch confirmed that IOS had no BURL
> support. If anyone knows of a real client that implements BURL (not
> some unmaintained beta) then I am interested.

I guess maybe this is sort of a 'chicken and egg' conundrum? Why would a
client implement something that has no server side support? It seems to
me that it would make more sense for servers to be the first to add
support for things like this. Label it experimental of course
unless/until there is at least one client that can be used for real
world testing, but somebody has to go first...

A question came up recently on the Thunderbird list about BURL support,
and I did some checking and found this as the only message in the
postfix archives with BURL in the subject...

I also found this email from Mike Abbot in April 2010 announcing Apple's
contribution of a patch for both postfix and dovecot for BURL support,
and for CATENATE and URLAUTH support for dovecot too, so I'm confused
about the comment about Apple not supporting it.

So... anyone know what happened here?

I would s love to be able to uncheck the 'Save copy to Sent folder'
for my postfix+dovecot accounts.


*/Charles/*/*
*/



Re: SV: domain rewrite/redirect [invalid signature!]

2016-04-18 Thread Matteo Cazzador
Hi thanks but this not solve my problem maybe because i use virtualmin 
with virtual host.


I need that mail.example.com will be consider like example.com in 
receiving mail


Thanks


Il 18/04/2016 13:35, Sebastian Nielsen ha scritto:


Simplest way is to add mail.example.com to your mydomains. Then mails 
both to t...@mail.example.com  and 
t...@example.com  will arrive to the account 
“test” on your server. Same is for example recommended to do with 
domain literals (IP addresses like test@[123.123.123.123 
] where 123.123.123.123 is your 
mailserver IP)


*Från:*owner-postfix-us...@postfix.org 
[mailto:owner-postfix-us...@postfix.org] *För *Matteo Cazzador

*Skickat:* den 18 april 2016 12:44
*Till:* postfix-users@postfix.org
*Ämne:* domain rewrite/redirect [invalid signature!]

Hi, i 've a question, which is the better way to do this please:

i've a virtual domain "example.com" on this server i receive mail too 
from mail.example.com


An example

any mail receive from t...@mail.example.com 
 must redirect to t...@example.com 



I try with canonical maps but i obtain relay access denied when i 
receive mail from t...@mail.example.com 


Can someone help me please.

Thanks



--
Rispetta l'ambiente: se non ti è necessario,  non stampare questa mail.
Le informazioni contenute in questa e-mail e nei files eventualmente
allegati sono destinate unicamente ai destinatari della stessa
e sono da considerarsi strettamente riservate.
E' proibito copiare, salvare, utilizzare,  inoltrare a terzi e diffondere
il contenuto della presente senza il preventivo consenso, ai sensi
dell'articolo 616 c.p. e della Legge n. 196/2003.
Se avete ricevuto questo messaggio per errore siete pregati di comunicarlo
immediatamente all'indirizzo mittente, nonché di cancellarne il contenuto
senza procedere ad ulteriore o differente trattamento.
**
Ing. Matteo Cazzador
NetLite snc di Cazzador Gagliardi
Corso Vittorio Emanuele II, 188 37069
Villafranca di Verona VR
Tel 0454856656
Fax 0454856655
Email:mat...@netlite.it 
Web:http://www.netlite.it
**


--

Rispetta l'ambiente: se non ti è necessario,  non stampare questa mail.


Le informazioni contenute in questa e-mail e nei files eventualmente
allegati sono destinate unicamente ai destinatari della stessa
e sono da considerarsi strettamente riservate.
E' proibito copiare, salvare, utilizzare,  inoltrare a terzi e diffondere
il contenuto della presente senza il preventivo consenso, ai sensi
dell'articolo 616 c.p. e della Legge n. 196/2003.
Se avete ricevuto questo messaggio per errore siete pregati di comunicarlo
immediatamente all'indirizzo mittente, nonché di cancellarne il contenuto
senza procedere ad ulteriore o differente trattamento.


**
Ing. Matteo Cazzador
NetLite snc di Cazzador Gagliardi
Corso Vittorio Emanuele II, 188 37069
Villafranca di Verona VR
Tel 0454856656
Fax 0454856655
Email: mat...@netlite.it
Web: http://www.netlite.it
**



smime.p7s
Description: Firma crittografica S/MIME


SV: domain rewrite/redirect [invalid signature!]

2016-04-18 Thread Sebastian Nielsen
Simplest way is to add mail.example.com to your mydomains. Then mails both
to t...@mail.example.com   and
t...@example.com   will arrive to the account
“test” on your server. Same is for example recommended to do with domain
literals (IP addresses like test@[123.123.123.123
 ] where 123.123.123.123 is your mailserver
IP)

 

Från: owner-postfix-us...@postfix.org
[mailto:owner-postfix-us...@postfix.org] För Matteo Cazzador
Skickat: den 18 april 2016 12:44
Till: postfix-users@postfix.org
Ämne: domain rewrite/redirect [invalid signature!]

 

Hi, i 've a question, which is the better way to do this please:

i've a virtual domain "example.com" on this server i receive mail too from
mail.example.com

An example

any mail receive from t...@mail.example.com 
must redirect to t...@example.com  

I try with canonical maps but i obtain relay access denied when i receive
mail from t...@mail.example.com  

Can someone help me please.

Thanks





-- 
 
Rispetta l'ambiente: se non ti è necessario,  non stampare questa mail. 
 
 
Le informazioni contenute in questa e-mail e nei files eventualmente 
allegati sono destinate unicamente ai destinatari della stessa 
e sono da considerarsi strettamente riservate. 
E' proibito copiare, salvare, utilizzare,  inoltrare a terzi e diffondere 
il contenuto della presente senza il preventivo consenso, ai sensi 
dell'articolo 616 c.p. e della Legge n. 196/2003. 
Se avete ricevuto questo messaggio per errore siete pregati di comunicarlo 
immediatamente all'indirizzo mittente, nonché di cancellarne il contenuto 
senza procedere ad ulteriore o differente trattamento.
 
 
**
Ing. Matteo Cazzador
NetLite snc di Cazzador Gagliardi
Corso Vittorio Emanuele II, 188 37069
Villafranca di Verona VR
Tel 0454856656
Fax 0454856655
Email: mat...@netlite.it  
Web: http://www.netlite.it
**


smime.p7s
Description: S/MIME Cryptographic Signature


domain rewrite/redirect

2016-04-18 Thread Matteo Cazzador

Hi, i 've a question, which is the better way to do this please:

i've a virtual domain "example.com" on this server i receive mail too 
from mail.example.com


An example

any mail receive from t...@mail.example.com must redirect to 
t...@example.com


I try with canonical maps but i obtain relay access denied when i 
receive mail from t...@mail.example.com


Can someone help me please.

Thanks


--

Rispetta l'ambiente: se non ti è necessario,  non stampare questa mail.


Le informazioni contenute in questa e-mail e nei files eventualmente
allegati sono destinate unicamente ai destinatari della stessa
e sono da considerarsi strettamente riservate.
E' proibito copiare, salvare, utilizzare,  inoltrare a terzi e diffondere
il contenuto della presente senza il preventivo consenso, ai sensi
dell'articolo 616 c.p. e della Legge n. 196/2003.
Se avete ricevuto questo messaggio per errore siete pregati di comunicarlo
immediatamente all'indirizzo mittente, nonché di cancellarne il contenuto
senza procedere ad ulteriore o differente trattamento.


**
Ing. Matteo Cazzador
NetLite snc di Cazzador Gagliardi
Corso Vittorio Emanuele II, 188 37069
Villafranca di Verona VR
Tel 0454856656
Fax 0454856655
Email: mat...@netlite.it
Web: http://www.netlite.it
**



smime.p7s
Description: Firma crittografica S/MIME


too many connections

2016-04-18 Thread Thomas kinghorn
Good morning List.

I have a problem where Vox Telecoms is temp rejecting our mail stating "too
many connections".

I was thinking of a transport_map to delay control the connection rate but
Vox hosts the email for many domains, so it would be impossible to create
an accurate list.

Is there an easier way?

My current solution is:

In master.cf

transport_maps = hash:/etc/postfix/vox_transport
vox_destination_concurrency_limit = 20
vox_destination_rate_delay = 2s
vox_destination_recipient_limit = 6

In *master.cf *

vox unix  -   -   n   -   -   smtp -o
syslog_name=postfix-vox

in vox_transport


domain1vox:
domain2vox:
domain3vox:
...
...
domain100vox:


The problem is that there are hundreds of domains and its impossible to
keep track of which domains deliver to vox.

Many thanks
Tom


Re: Content Filter only for incoming mails

2016-04-18 Thread BP20
Thank you, can you please explain it a bit more with an example?
What do you mean with "dedicated submission instance"?



--
View this message in context: 
http://postfix.1071664.n5.nabble.com/Content-Filter-only-for-incoming-mails-tp83437p83439.html
Sent from the Postfix Users mailing list archive at Nabble.com.


Re: Content Filter only for incoming mails

2016-04-18 Thread Patrick Ben Koetter
* BP20 :
> Hello,
> 
> i am new to this.
> I am trying to set up a content filter for incoming postfix mails.
> I am using this instruction: 
> http://www.postfix.org/FILTER_README.html#simple_filter
>   
> 
> --- master.cf snippet ---
> smtp  inet  n   -   -   -   -   smtpd
>  -o content_filter=filter:dummy
> filterunix  -   n   n   -   10  pipe
>   flags=Rq user=filter null_sender=
>   argv=/var/spool/filter/afterqueue.sh -f ${sender} -- ${recipient}
> 
> 
> The problem is, that the filter is also applied to outgoing mails.
> I don't really understand that "-o content_filter=filter:dummy" line. Should
> "filter:dummy" be replaced?

Nope.

Your problem very likely is that your Postfix server currently is unaware of
directions. It can't tell what is incoming nor can it tell what is outgoing.

> So how can i set it up, so that it is only used for incoming mails?

Use a dedicated submission instance (master.cf) to submit outbound mail.

p@rick


-- 
[*] sys4 AG
 
https://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München
 
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Marc Schiffbauer
Aufsichtsratsvorsitzender: Florian Kirstein
 


Content Filter only for incoming mails

2016-04-18 Thread BP20
Hello,

i am new to this.
I am trying to set up a content filter for incoming postfix mails.
I am using this instruction: 
http://www.postfix.org/FILTER_README.html#simple_filter
  

--- master.cf snippet ---
smtp  inet  n   -   -   -   -   smtpd
 -o content_filter=filter:dummy
filterunix  -   n   n   -   10  pipe
  flags=Rq user=filter null_sender=
  argv=/var/spool/filter/afterqueue.sh -f ${sender} -- ${recipient}


The problem is, that the filter is also applied to outgoing mails.
I don't really understand that "-o content_filter=filter:dummy" line. Should
"filter:dummy" be replaced?

So how can i set it up, so that it is only used for incoming mails?
Thanks



--
View this message in context: 
http://postfix.1071664.n5.nabble.com/Content-Filter-only-for-incoming-mails-tp83437.html
Sent from the Postfix Users mailing list archive at Nabble.com.