On 12/23/2012 9:57 PM, Alex wrote:
> Hi,
>
>>> I've implemented postscreen with postfix-2.9.4 on fc17 and it is
>>> rejecting mail from alice.it and libero.it, which are apparently two
>>> ISPs in Italy. We receive a large number of messages that are rejected
>>> due to postscreen, but now we have
Hi,
>> I've implemented postscreen with postfix-2.9.4 on fc17 and it is
>> rejecting mail from alice.it and libero.it, which are apparently two
>> ISPs in Italy. We receive a large number of messages that are rejected
>> due to postscreen, but now we have one email address from each domain
>> that
Alex:
> Hi,
>
> I've implemented postscreen with postfix-2.9.4 on fc17 and it is
> rejecting mail from alice.it and libero.it, which are apparently two
> ISPs in Italy. We receive a large number of messages that are rejected
> due to postscreen, but now we have one email address from each domain
>
Am 24.12.2012 02:38, schrieb Alex:
> It also looks like mail originates from IPs other than those listed as
> an MX record for alice.it
MX record has nothing to do with sending IP's
it is only the incoming server
in nearly any larger setup they are different
because you have incoming servers wi
On 12/23/2012 08:03 PM, Wietse Venema wrote:
Robert Moskowitz:
Is there a way to append to a parameter using postconf. If it is only
in a version later than 2.6.6, oh well. But the example is
smtpd_recipient_restrictions which can have a long list and then you
want to add a realtime black lis
Robert Moskowitz:
> Is there a way to append to a parameter using postconf. If it is only
> in a version later than 2.6.6, oh well. But the example is
> smtpd_recipient_restrictions which can have a long list and then you
> want to add a realtime black list check fqdn.
With these parameters i
Is there a way to append to a parameter using postconf. If it is only
in a version later than 2.6.6, oh well. But the example is
smtpd_recipient_restrictions which can have a long list and then you
want to add a realtime black list check fqdn.
Also in this vein, can postconf -e 'parameter= .
On 12/23/2012 12:35 PM, Robert Moskowitz wrote:
On 12/23/2012 12:12 PM, Wietse Venema wrote:
Robert Moskowitz:
postconf debugger_command
returns
postconf: warning: debugger_command: unknown parameter
This is postfix 2.6.6 on Centos 6
Wietse:
Fixed in Postfix 2.9.
Robert Moskowitz:
ARGH!!! :
On 12/23/2012 12:12 PM, Wietse Venema wrote:
Robert Moskowitz:
postconf debugger_command
returns
postconf: warning: debugger_command: unknown parameter
This is postfix 2.6.6 on Centos 6
Wietse:
Fixed in Postfix 2.9.
Robert Moskowitz:
ARGH!!! :)
I will submit this to the Centos list and see
Robert Moskowitz:
> postconf debugger_command
> returns
> postconf: warning: debugger_command: unknown parameter
> This is postfix 2.6.6 on Centos 6
Wietse:
> Fixed in Postfix 2.9.
> Robert Moskowitz:
> ARGH!!! :)
>
> I will submit this to the Centos list and see what they do with it.
> Thanks
On 12/23/2012 11:16 AM, Wietse Venema wrote:
Robert Moskowitz:
postconf debugger_command
returns
postconf: warning: debugger_command: unknown parameter
This is postfix 2.6.6 on Centos 6
Fixed in Postfix 2.9.
ARGH!!! :)
I will submit this to the Centos list and see what they do with it.
On 12/23/2012 09:33 AM, Noel Jones wrote:
On 12/23/2012 8:12 AM, Robert Moskowitz wrote:
In the Centos 6 /etc/postfix/mail.cf there are the lines:
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
ddd $daemon_directory/$process_name $process_id & sleep 5
This par
Robert Moskowitz:
> postconf debugger_command
>
> returns
>
> postconf: warning: debugger_command: unknown parameter
>
> This is postfix 2.6.6 on Centos 6
Fixed in Postfix 2.9.
Wietse
On 12/23/2012 09:33 AM, Noel Jones wrote:
On 12/23/2012 8:12 AM, Robert Moskowitz wrote:
In the Centos 6 /etc/postfix/mail.cf there are the lines:
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
ddd $daemon_directory/$process_name $process_id & sleep 5
This par
On 12/23/2012 8:28 AM, Robert Moskowitz wrote:
>
> On 12/23/2012 09:20 AM, Noel Jones wrote:
>> On 12/23/2012 7:17 AM, Robert Moskowitz wrote:
You can chase these with something like:
# postconf -n | while read parameter equal value; do
default_value=`postconf -d $parame
On 12/23/2012 8:12 AM, Robert Moskowitz wrote:
> In the Centos 6 /etc/postfix/mail.cf there are the lines:
>
> debugger_command =
> PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
> ddd $daemon_directory/$process_name $process_id & sleep 5
>
> This parameter (?) does not show in the po
On 12/23/2012 09:20 AM, Noel Jones wrote:
On 12/23/2012 7:17 AM, Robert Moskowitz wrote:
You can chase these with something like:
# postconf -n | while read parameter equal value; do
default_value=`postconf -d $parameter 2>&1`;
if [ "$value" = "$default_value" ]; then
On 12/23/2012 7:17 AM, Robert Moskowitz wrote:
>> You can chase these with something like:
>>
>> # postconf -n | while read parameter equal value; do
>> default_value=`postconf -d $parameter 2>&1`;
>> if [ "$value" = "$default_value" ]; then
>> echo "NOTICE: Useless setting
In the Centos 6 /etc/postfix/mail.cf there are the lines:
debugger_command =
PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
ddd $daemon_directory/$process_name $process_id & sleep 5
This parameter (?) does not show in the postconf -n listing. Also this
command takes these 3 lines i
John Allen:
> I am using Dovecot as my mail delivery mechanism for both local and
> virtual users, plus using it as my SASL auth agent.
> My setup is for a small business (average 30 users).
> The mail system is on a single server.
> Which would be better unix/pipes and LDA or LMTP.
A resident LM
Am 23.12.2012 16:24, schrieb John Allen:
> I am using Dovecot as my mail delivery mechanism for both local and virtual
> users, plus using it as my SASL auth agent.
> My setup is for a small business (average 30 users).
> The mail system is on a single server.
> Which would be better unix/pipes
I am using Dovecot as my mail delivery mechanism for both local and
virtual users, plus using it as my SASL auth agent.
My setup is for a small business (average 30 users).
The mail system is on a single server.
Which would be better unix/pipes and LDA or LMTP.
TIA
JohnA
--
"He who opens a sch
On 12/14/2012 05:01 PM, mouss wrote:
# postconf -d
shows default settings (builtin defaults).
# postconf -n
shows "local" settings.
that said, some "local" settings may use the same value as the default
config, which is mostly useless. on the url you posted, an example is
inet_interfaces = all
On Sun, 23 Dec 2012, Joey J wrote:
I currently have a transport_map that takes mail for abc.com and send it to
their server mail.abc.com, so I am acting as the gateway for the domain.
My trasport config looks like:
abc.comsmtp:[mail.abc.com]
Now lets say their server is down so we decide to
Thanks Mouss,
Maybe I didn't say this properly to make sense.
I currently have a transport_map that takes mail for abc.com and send it to
their server mail.abc.com, so I am acting as the gateway for the domain.
My trasport config looks like:
abc.comsmtp:[mail.abc.com]
Now lets say their serve
Le 23/12/2012 05:21, Joey J a écrit :
> Hello All,
>
> I have done this previously, but can't find any of my own documentation
> that I make.
>
> I want to configure a transport map, that delivers mail to my server (
> postfix acting as a gateway ) but also deliver every message to a mailbox.
>
>
26 matches
Mail list logo
