HI All,
on one of my servers I`m planning to migrate very old Postfix 2.0 to quite
new one 2.6.6.
I migrated already all Postfix instances, so all Postfix configuration
files are already on the new machine (/etc/postfix*). Now its time to
migrate /var/spool/postfix and all other Postfix data files
On Fri, 20 Feb 2015 09:14:37 +0100
Zalezny Niezalezny wrote:
> - zip all /var/spool/postfix* and /var/spool/mail/*
>
don't use zip, it didn't save uid.gid owner...
On 20 Feb 2015, at 09:14, Zalezny Niezalezny
wrote:
> on one of my servers I`m planning to migrate very old Postfix 2.0 to quite
> new one 2.6.6.
> I migrated already all Postfix instances, so all Postfix configuration files
> are already on the new machine (/etc/postfix*). Now its time to mig
Thanks for Your explanation. I see that Postfix community is very strong
and fast :) Its good to know :)
Back to subject.
We are using Red Hat distro so I`m not planning to use Postfix version
higher than its in the repository. What can I say, RHEL is crap if we are
talking about updates for the
What about just routing messages from old server to the new one with
relayhost? We are just talking about messages in queue right?
2015-02-20 10:54 GMT+01:00 Zalezny Niezalezny
:
> Thanks for Your explanation. I see that Postfix community is very strong
> and fast :) Its good to know :)
>
> If
I dont want to route any E-mails. I simply would like to stop old server,
tar everything in the proper way and migrate on the new host. This is my
target.
On Fri, Feb 20, 2015 at 11:05 AM, Test wrote:
> What about just routing messages from old server to the new one with
> relayhost? We are just
Quoting Zalezny Niezalezny :
I dont want to route any E-mails. I simply would like to stop old server,
tar everything in the proper way and migrate on the new host. This is my
target.
Then just block all incoming traffic on port 25 and 587 (or whatever
your users are using).
After everything
I will simply stop postfix and copy all files. I dont see any other
solution here.We will see if it will work properly.
On Fri, Feb 20, 2015 at 11:28 AM, Michael wrote:
> Quoting Zalezny Niezalezny :
>
> I dont want to route any E-mails. I simply would like to stop old server,
>> tar everything
Greetz to all and thanks for Your efficient support!
Its perfect community :)
On Fri, Feb 20, 2015 at 12:30 PM, Zalezny Niezalezny <
zalezny.niezale...@gmail.com> wrote:
> I will simply stop postfix and copy all files. I dont see any other
> solution here.We will see if it will work properly.
>
Hi,
due to problem to send to outlook.com domains with my postfix, i'd like postfix
act as smtp client with my email provider smtp server using the sender
credentials.
For example:
1) pi...@mydomain.com -> u...@anydomain.com, send directly
2) pi...@mydomain.com -> u...@outlook.com, send thr
Viktor Dukhovni:
> On Thu, Feb 19, 2015 at 04:20:17PM -0600, List wrote:
>
> > We would like to use the Cassandra database to persist the state of abusive
> > IPs which we would block from connecting in one of the
> > smtpd_xxx_restrictions clauses. We have systems that exist in multiple data
> >
Gianluca Gargiulo:
> Hi,
>
> due to problem to send to outlook.com domains with my postfix, i'd
> like postfix act as smtp client with my email provider smtp server
> using the sender credentials.
Maybe you can store the credential in smtp_sasl_password_maps and
set "smtp_sender_dependent_authen
Wietse Venema:
> Gianluca Gargiulo:
> > Hi,
> >
> > due to problem to send to outlook.com domains with my postfix, i'd
> > like postfix act as smtp client with my email provider smtp server
> > using the sender credentials.
>
> Maybe you can store the credential in smtp_sasl_password_maps and
>
but i want that postfix acts as smtp client only for outlook.com domains, not
ever.
Where i set this conditions?
- Messaggio originale -
Da: "Wietse Venema"
A: "Postfix users"
Inviato: Venerdì, 20 febbraio 2015 14:29:46
Oggetto: Re: conditional relay with credential based on domain
Gianluca Gargiulo:
> but i want that postfix acts as smtp client only for outlook.com
> domains, not ever. Where i set this conditions?
Set up an "smtp-auth" delivery agent that is used for outlook.com.
and enable client-side SASL for the "smtp-auth" delivery agent only.
/etc/postfix/main.cf:
smtpd_data_restrictions fixed my issue and I see the header now.
Thank you.
On Thu, Feb 19, 2015 at 7:05 PM, Wietse Venema wrote:
> Dave Jones:
> > Feb 19 16:55:12 smtp1 postfwd[27034]: [RULES] rule=4, id=RCPTCNT1,
> > queue=C2B7433E7CE, client=unknown[172.27.0.203], sender=<
> > r...@server1.ex
On Fri, Feb 20, 2015 at 11:15:58AM +0100, Zalezny Niezalezny wrote:
> I dont want to route any E-mails. I simply would like to stop old server,
> tar everything in the proper way and migrate on the new host. This is my
> target.
Letting the legacy queue drain, either to the users mailboxes or
to
Good afternoon all,
I am considering setting up a nolisting postfix server on a spare static IP
so as to study the effects of nolisting for some heavy domains we host (3k
total msgs/day, 200 legit). This server will sit at both the highest
priority and the lowest priority, with the real MX in the
Hi,
I am using a postfix as relay for email sent from an hoster that close
the port 25, so I send the mail to the relayer through the 10025 port.
but the IP of the originating server appear in the header of the mail
and I would like to remove it :
source server ---10025---> relayer ---25--->
On 2/20/2015 5:12 PM, Stéphane MERLE wrote:
> Hi,
>
> I am using a postfix as relay for email sent from an hoster that
> close the port 25, so I send the mail to the relayer through the
> 10025 port.
> but the IP of the originating server appear in the header of the
> mail and I would like to remo
On Fri, Feb 20, 2015 at 05:05:50PM -0600, Isaac Grover wrote:
> I am considering setting up a nolisting postfix server on a spare static IP
> so as to study the effects of nolisting for some heavy domains we host (3k
> total msgs/day, 200 legit). This server will sit at both the highest
> priority
21 matches
Mail list logo
