* Stan Hoeppner [2012-07-30 14:35]:
> On 7/29/2012 6:57 PM, Engin qwert wrote:
>
> > Actually it is not router. It is only BPL modem. After Static IP hiring the
> > ISP send me an email how to configure the server with this IP addresses
> > information. The 10.138.9.201 internal IP address sele
Hello,
We are setting up a gateway server (mx.example.com) to serve as primary
MX (for domain example.com).
It will receive mail from the Internet and forward (relay) it using:
transport_maps = hash:/etc/postfix/transportmap
where: /etc/postfix/transportmap
example.com relay:[ma
On Tue, Aug 07, 2012 at 03:24:37PM +0300, Nikolaos Milas wrote:
> I was wondering whether we could set up this server in a way so it
> can forward (relay) all mail to mail.example.com AND, if (and only
> if) this is temporarily down, then:
>
> 1. Keep incoming mail in queue until it can contact ma
Hi there,
I'm trying to implement always_bcc to send a copy of all received messages to
another server.
My idea is disable any notification messages back in the second server (if
something goes wrong) and discard all messages after received.
This way is like the "clean" solution to ensure th
email builder:
> I read in http://www.postfix.org/mysql_table.5.html for the %d
> substitution in the query if the lookup is not a full email address
> with domain, the entire query is not even executed? Is this right?
If postfix does not work as documented, please post a bug report.
Wiet
Hi, there. The problem has solved by itself or maybe the ISP has made a
change or an improvement due to my request after you captured that the problem
is the "router or upstream". Thank you for your great support, and sparing me
your valuable time.
Engin YILMAZ
Hello,
I setup procmail. I have a system wide config:
LOGFILE=/var/log/procmail.log
VERBOSE=on
:0B:
* (://[A-Za-z0-9.-]+\.ru)
/dev/null
:0:
* ^Subject: (Rolex)
/dev/null
:0
* ^Subject: (anoncvs)
! m...@server1.com some...@server2.com
I checked the log and it is putting spam in /dev/null, but
Hello
let me explains
Reading the manual, it explain that
sender_dependent_default_transport_maps override default_transport
first I want to white-list sender address allow to sender mail to other
domain
so fisrt I did that
in main.cf
default_transport = error:error message
sender
On Tue, Aug 07, 2012 at 05:51:43PM +0200, zorg wrote:
> Reading the manual, it explain that
> sender_dependent_default_transport_maps override default_transport
Which selects the delivery agent and nexthop for *external* recipients
based on the sender. This is NOT an access control mechanism.
>
Hi list,
I'm currently doing some brainstorming on how to protect backup-mx
servers from being directly contacted by clients. I found that
postscreen can do this, but as far as I read only if the backup runs on
the same machine.
Another idea that came in my mind is that the backup-mx checks the
po
On Tue, Aug 7, 2012 at 9:45 AM, tobi wrote:
> Hi list,
>
> I'm currently doing some brainstorming on how to protect backup-mx
> servers from being directly contacted by clients.
Why would you want to protect your clients from your backup mx?
On 2012-08-07 Al Zick wrote:
> I setup procmail. I have a system wide config:
>
> LOGFILE=/var/log/procmail.log
> VERBOSE=on
>
> :0B:
> * (://[A-Za-z0-9.-]+\.ru)
> /dev/null
>
> :0:
> * ^Subject: (Rolex)
> /dev/null
>
> :0
> * ^Subject: (anoncvs)
> ! m...@server1.com some...@server2.com
>
> I
On 2012-08-07 tobi wrote:
> I'm currently doing some brainstorming on how to protect backup-mx
> servers from being directly contacted by clients.
That kinda defeats the purpose of having a backup MX in the first place.
Regards
Ansgar Wiechers
--
"Abstractions save us time working, but they don'
On 8/7/2012 11:45 AM, tobi wrote:
> Hi list,
>
> I'm currently doing some brainstorming on how to protect backup-mx
> servers from being directly contacted by clients. I found that
> postscreen can do this, but as far as I read only if the backup runs on
> the same machine.
> Another idea that cam
- Original Message -
> From: Wietse Venema
> To: Postfix users
> Cc:
> Sent: Tuesday, August 7, 2012 8:26 AM
> Subject: Re: mysql query suppressed?
>
> email builder:
>> I read in http://www.postfix.org/mysql_table.5.html for the %d
>> substitution in the query if the lookup is no
>> Probably the best lesson to learn from postfixadmin is: you can have
>> more than one lookup table in postfix per main.cf directive.
>> Postfixadmin uses 2 separate queries for "regular" aliases and
>> domain
>> aliases.
>>
>> from main.cf:
>> virtual_alias_maps = /etc/postfix/mysql_vir
Em 07-08-2012 15:04, Stan Hoeppner escreveu:
On 8/7/2012 11:45 AM, tobi wrote:
Hi list,
I'm currently doing some brainstorming on how to protect backup-mx
servers from being directly contacted by clients. I found that
postscreen can do this, but as far as I read only if the backup runs on
the s
Am 07.08.2012 20:04, schrieb Stan Hoeppner:
> The first thing you need to do is define for us what "protect
> backup-mx servers" means. What, exactly, do you want to protect
> them from?
>
Sorry if my intention was only clear to myself ;-)
I want to prevent clients from connecting my backup-mx
Am 07.08.2012 22:03, schrieb tobi:
>
> Am 07.08.2012 20:04, schrieb Stan Hoeppner:
>> The first thing you need to do is define for us what "protect
>> backup-mx servers" means. What, exactly, do you want to protect
>> them from?
>>
>
> Sorry if my intention was only clear to myself ;-)
> I wan
On 2012-08-07 tobi wrote:
> Am 07.08.2012 20:04, schrieb Stan Hoeppner:
>> The first thing you need to do is define for us what "protect
>> backup-mx servers" means. What, exactly, do you want to protect
>> them from?
>
> Sorry if my intention was only clear to myself ;-)
> I want to prevent clie
On Aug 7, 2012, at 1:18 PM, Ansgar Wiechers wrote:
On 2012-08-07 Al Zick wrote:
I setup procmail. I have a system wide config:
LOGFILE=/var/log/procmail.log
VERBOSE=on
:0B:
* (://[A-Za-z0-9.-]+\.ru)
/dev/null
:0:
* ^Subject: (Rolex)
/dev/null
:0
* ^Subject: (anoncvs)
! m...@server1.com som
Al Zick:
> >> I checked the log and it is putting spam in /dev/null, but there are
> >> errors in procmail.log when ever it tries to forward the emails:
> >>
> >> sendmail: warning: the Postfix sendmail command has set-uid root file
> >> permissions
> >> sendmail: warning: or the command is run fro
email builder:
>it says if you use "%d" in your query and the lookup key is not in
>the form of "u...@domain.tld" (ie local part only), then the query
>is "suppressed".?
What is not clear about that?
Wietse
On 7/8/2012 3:48 μμ, Viktor Dukhovni wrote:
This is difficult to automate reliably...
Thank you Victor for all the valuable info. I see.
A question: Could we use the format:
/etc/postfix/transportmap
example.com relay:[mail.example.com], relay:[mail2.example.com]
to force relaying to *both*
I recently switched from using flat virtual files to using mysql to manage a
virtual table.
Email addresses that were set up prior to the switchover can be reached. But
emails set up afterwards can't.
I added verbose logging to the smtp processes by adding the -v parameter in
master.cf
With
On Wed, Aug 08, 2012 at 12:58:41AM +0300, Nikolaos Milas wrote:
> A question: Could we use the format:
>
> /etc/postfix/transportmap
> example.com relay:[mail.example.com], relay:[mail2.example.com]
No. As documented.
> to force relaying to *both* those servers (mail AND mail2) at the
> same ti
On Tue, Aug 07, 2012 at 03:28:45PM -0700, Scott Brown wrote:
> I recently switched from using flat virtual files to using mysql
> to manage a virtual table.
http://www.postfix.org/DEBUG_README.html#mail
> Aug ?7 17:52:13 miltermatic postfix/smtpd[15169]: resolve_clnt: `' ->
> `sbr...@ol
Hello,
today I noticed I don;t have orig_to in my log file even that the address
is rewrited.
I googled this problem with no luck.
According to what Viktor wrote in this message
http://www.mail-archive.com/postfix-users@postfix.org/msg08917.html
orig_to should appear in case of virtual_alias_m
On Tue, Aug 07, 2012 at 03:28:45PM -0700, Scott Brown wrote:
> I recently switched from using flat virtual files to using mysql
> to manage a virtual table.
http://www.postfix.org/DATABASE_README.html#preparing is worth a
read.
> Email addresses that were set up prior to the switchover can be
>
On 8/7/2012 5:32 PM, Viktor Dukhovni wrote:
> On Wed, Aug 08, 2012 at 12:58:41AM +0300, Nikolaos Milas wrote:
...
>> A second question: Is anyone aware of any (Linux) "smart" script
>> automating (at least to some extent) reliably enough detection of a
>> mail server failure (to avoid re-inventing
Michal Lipka:
> Hello,
> today I noticed I don;t have orig_to in my log file even that the address
> is rewrited.
Incorrect. Postfix logs orig_to only if the address is rewritten
before it is delivered.
For example Postfix does not log orig_to AFTER a content filter, when
virtual alias expansion
> email builder:
>> it says if you use "%d" in your query and the lookup key is not in
>> the form of "u...@domain.tld" (ie local part only), then the query
>> is "suppressed".?
>
> What is not clear about that?
1) the word "suppressed" is only slightly unclear. I just want to make sure I
und
On Tue, Aug 07, 2012 at 09:17:48PM -0700, email builder wrote:
> > email builder:
> >> it says if you use "%d" in your query and the lookup key is not in
> >> the form of "u...@domain.tld" (ie local part only), then the query
> >> is "suppressed".?
> >
> > What is not clear about that?
>
>
> 1)
> This feature is not going to change. Over and out.
I merely asked (politely I think) for confirmation that I understood the
documentation correctly.
Why do you have to use such unfriendly language in your responses?
34 matches
Mail list logo
