On 2015-01-19 13:32, wie...@porcupine.org wrote:
m...@ruggedinbox.com:
[sendmail -f]
This solved the issue.
As you can see it was under your nose all the time but you were
too busy insulting us:
Postfix has hundreds of parameters and dozens of comand-line options.
Figuring which of these was i
m...@ruggedinbox.com:
[sendmail -f]
> This solved the issue.
> As you can see it was under your nose all the time but you were
> too busy insulting us:
Postfix has hundreds of parameters and dozens of comand-line options.
Figuring which of these was in error was non-trivial, especially
with someon
Am 19.01.2015 um 11:49 schrieb Michael Ströder:
wie...@porcupine.org (Wietse Venema) wrote:
m...@ruggedinbox.com:
and the header is still there.
By default, Postfix REMOVES Return-Path headers from email messages.
The default setting is:
message_drop_headers = bcc, content-length, rese
wie...@porcupine.org (Wietse Venema) wrote:
> m...@ruggedinbox.com:
>> and the header is still there.
>
> By default, Postfix REMOVES Return-Path headers from email messages.
> The default setting is:
>
> message_drop_headers = bcc, content-length, resent-bcc, return-path
From http://www.pos
On 2015-01-19 01:36, wie...@porcupine.org wrote:
m...@ruggedinbox.com:
Perhaps we could pass ${sender} to our custom script
and then use sendmail's -f argument to change the Return-Path header ?
The -f argument IS THE RETURN-PATH ADDRESS.
SENDMAIL(1)
m...@ruggedinbox.com:
> Perhaps we could pass ${sender} to our custom script
> and then use sendmail's -f argument to change the Return-Path header ?
The -f argument IS THE RETURN-PATH ADDRESS.
SENDMAIL(1)SENDMAIL(1)
NAME
sendmail -
On 2015-01-19 00:53, wie...@porcupine.org wrote:
m...@ruggedinbox.com:
> By default, Postfix REMOVES Return-Path headers from email messages.
> The default setting is:
>
> message_drop_headers = bcc, content-length, resent-bcc, return-path
That is the default setting.
We tried to use the
m...@ruggedinbox.com:
> > By default, Postfix REMOVES Return-Path headers from email messages.
> > The default setting is:
> >
> > message_drop_headers = bcc, content-length, resent-bcc, return-path
That is the default setting.
> We tried to use the 'message_drop_headers' parameter in both m
On 2015-01-18 23:51, wie...@porcupine.org wrote:
m...@ruggedinbox.com:
and the header is still there.
By default, Postfix REMOVES Return-Path headers from email messages.
The default setting is:
message_drop_headers = bcc, content-length, resent-bcc, return-path
You claim that you remove
On 2015-01-18 23:35, Christian Rößner wrote:
Am 18.01.2015 um 23:27 schrieb m...@ruggedinbox.com:
Return-Path:
Delivered-To: m...@ruggedinbox.com
Received: from localhost (localhost.localdomain [127.0.0.1])
by ruggedinbox.com (Postfix) with ESMTP id 7693331405C7
for ; Sun, 18 Ja
m...@ruggedinbox.com:
> and the header is still there.
By default, Postfix REMOVES Return-Path headers from email messages.
The default setting is:
message_drop_headers = bcc, content-length, resent-bcc, return-path
You claim that you removed all the pipe "R" flags. You can verify
that by t
> Am 18.01.2015 um 23:27 schrieb m...@ruggedinbox.com:
>
> Return-Path:
> Delivered-To: m...@ruggedinbox.com
> Received: from localhost (localhost.localdomain [127.0.0.1])
> by ruggedinbox.com (Postfix) with ESMTP id 7693331405C7
> for ; Sun, 18 Jan 2015 23:23:03 +0100 (CET)
At this
On 2015-01-18 22:01, wie...@porcupine.org wrote:
m...@ruggedinbox.com:
Ok the new rule is:
spamassassin unix - n n - - pipe
user=debian-spamd argv=/usr/bin/spamc -e /usr/sbin/sendmail -oi -f
-G
${sender} -- ${recipient}
You can't put -G between -f and sender. I assumed that you would be
On 2015-01-18 22:17, KSB wrote:
On 19.01.2015. 0:01, Wietse Venema wrote:
m...@ruggedinbox.com:
did a postfix restart (of course) and sent a test email:
There is no such thing as "postfix restart". In other words,
Postfix keeps using the old configuration.
Wietse
Probably ML used
On 19.01.2015. 0:01, Wietse Venema wrote:
m...@ruggedinbox.com:
did a postfix restart (of course) and sent a test email:
There is no such thing as "postfix restart". In other words,
Postfix keeps using the old configuration.
Wietse
Probably ML used init.d script restart facility, w
m...@ruggedinbox.com:
> Ok the new rule is:
>
> spamassassin unix - n n - - pipe
>user=debian-spamd argv=/usr/bin/spamc -e /usr/sbin/sendmail -oi -f -G
> ${sender} -- ${recipient}
You can't put -G between -f and sender. I assumed that you would be
familiar with the way UNIX command-line synt
On 2015-01-18 21:17, wie...@porcupine.org wrote:
m...@ruggedinbox.com:
>> spamassassin unix - n n - - pipe
>>user=debian-spamd
>>argv=/usr/bin/spamc -e /usr/sbin/sendmail -oi -f ${sender} --
>> ${recipient}
>
> This is better, without "R" flags and with -- before the recipients.
>
> The
m...@ruggedinbox.com:
> >> spamassassin unix - n n - - pipe
> >>user=debian-spamd
> >>argv=/usr/bin/spamc -e /usr/sbin/sendmail -oi -f ${sender} --
> >> ${recipient}
> >
> > This is better, without "R" flags and with -- before the recipients.
> >
> > The Postfix FILTER_README also recomme
On 2015-01-18 20:48, wie...@porcupine.org wrote:
m...@ruggedinbox.com:
>> spamassassin unix - n n - - pipe
>> flags=R user=debian-spamd argv=/usr/bin/spamc -e /usr/sbin/sendmail
>> -oi -f
>> ${sender} ${recipient}
>
> This is not final delivery, don't use "R" here. And don't forget "--"
> bef
m...@ruggedinbox.com:
> >> spamassassin unix - n n - - pipe
> >> flags=R user=debian-spamd argv=/usr/bin/spamc -e /usr/sbin/sendmail
> >> -oi -f
> >> ${sender} ${recipient}
> >
> > This is not final delivery, don't use "R" here. And don't forget "--"
> > before the recipient list.
...
> About
On 2015-01-18 19:53, Viktor Dukhovni wrote:
On Sun, Jan 18, 2015 at 07:41:15PM +, m...@ruggedinbox.com wrote:
Hi ok we double checked and this is the source of an email sent from
m...@ruggedinbox.com to m...@ruggedinbox.com:
Return-Path:
Delivered-To: m...@ruggedinbox.com
[...]
so it lo
On Sun, Jan 18, 2015 at 07:41:15PM +, m...@ruggedinbox.com wrote:
> Hi ok we double checked and this is the source of an email sent from
> m...@ruggedinbox.com to m...@ruggedinbox.com:
>
>
> Return-Path:
> Delivered-To: m...@ruggedinbox.com
> [...]
>
> so it looks like 'Return-Path: ' is a
On 2015-01-18 18:43, wie...@porcupine.org wrote:
m...@ruggedinbox.com:
Hi!
At the end of the /etc/postfix/master.cf file (Debian Wheezy)
we have a nice custom PHP script which checks and limits outgoing
emails:
outCustomFilter unix - n n - - pipe
flags=F user=vmail:vmail argv=/etc/postfix/ou
m...@ruggedinbox.com:
> Hi!
> At the end of the /etc/postfix/master.cf file (Debian Wheezy)
> we have a nice custom PHP script which checks and limits outgoing
> emails:
>
> outCustomFilter unix - n n - - pipe
>flags=F user=vmail:vmail argv=/etc/postfix/outCustomFilter.php
> ${recipient}
>
Am 18.01.2015 um 19:36 schrieb m...@ruggedinbox.com:
At the end of the /etc/postfix/master.cf file (Debian Wheezy)
we have a nice custom PHP script which checks and limits outgoing emails:
outCustomFilter unix - n n - - pipe
flags=F user=vmail:vmail argv=/etc/postfix/outCustomFilter.php
${re
Hi!
At the end of the /etc/postfix/master.cf file (Debian Wheezy)
we have a nice custom PHP script which checks and limits outgoing
emails:
outCustomFilter unix - n n - - pipe
flags=F user=vmail:vmail argv=/etc/postfix/outCustomFilter.php
${recipient}
This script does its checks and if eve
26 matches
Mail list logo
