On 05-18-2021 2:12 pm, Matus UHLAR - fantomas wrote:
so, you have multiple instances?
On 18.05.21 14:37, post...@ptld.com wrote:
No, i don't have multiple instances of a postfix install. Postfix has
multiple instances as in:
in your other mail you still refer to them as two separate servers
-
Dnia 18.05.2021 o godz. 16:26:03 post...@ptld.com pisze:
> End game goals:
>
> Server 1 is the MX server to accept mail for domain. It should not
> be tasked with submissions, relays, etc. Keep it available for one
> purpose only for balancing purposes.
>
> Server 2 is to cater to the end user, t
> On May 18, 2021, at 4:26 PM, post...@ptld.com wrote:
>
> Server 1 is the MX server to accept mail for domain. It should not be tasked
> with submissions, relays, etc. Keep it available for one purpose only for
> balancing purposes.
>
> Server 2 is to cater to the end user, to handle their nee
On 05-18-2021 3:36 pm, Jaroslaw Rafa wrote:
Before writing my previous mail, I read exactly the same documentation
as
you linked above and for me it says something exactly opposite: Dovecot
submission service needs real MTA as a "backend" to relay mail onto the
Internet. By itself it can only se
>
>
> The issue im trying to avoid is that when postfix/submission accepts a
> message meant for another user on the same domain, it delivers it
> directly to maildir and does not put that message through the same
> filters, milters, policy servers as if the message was accepted by
> smtp:25.
You
Perhaps the OP should explain the *actual* problem he's trying to
solve, rather than the artificial goal of routing inbound mail
via a second SMTP hop, while outbound mail goes direct.
End game goals:
Server 1 is the MX server to accept mail for domain. It should not be
tasked with submissions
Viktor Dukhovni:
> > On May 18, 2021, at 3:02 PM, Wietse Venema wrote:
> >
> > What about using this to send only local recipients to the MX host,
> > and all other recipients directly.
> >
> > master.cf:
> >submission .. .. ... . smtpd
> > -o { smtpd_recipient_restrictions =
> >
> On May 18, 2021, at 3:02 PM, Wietse Venema wrote:
>
> What about using this to send only local recipients to the MX host,
> and all other recipients directly.
>
> master.cf:
>submission .. .. ... . smtpd
> -o { smtpd_recipient_restrictions =
> check_recipient_access
>
Dnia 18.05.2021 o godz. 15:28:28 post...@ptld.com pisze:
> >what would send the mail out to the Internet after being accepted
> >by Dovecot
> >submission service? Dovecot is not a MTA, it's submission service
> >needs to
> >pass mail to a real MTA to be sent out further.
>
> Not anymore. Dovecot a
On 05-18-2021 3:14 pm, Jaroslaw Rafa wrote:
So where is the maildir actually located? On server X or on server Y?
If it is located on server Y, how Dovecot on server X accesses it? NFS
or
some other kind of shared storage?
Yes, both servers are sharing NFS storage.
And, if there were no Post
Dnia 18.05.2021 o godz. 13:47:15 post...@ptld.com pisze:
> >On 05-18-2021 12:36 pm, Jaroslaw Rafa wrote:
> >If Postfix on server X is only for submission, then how does Postfix on
> >server Y deliver mail to server X?
>
> It doesn't because as you said, server X is only for submission.
> Nothing s
What about using this to send only local recipients to the MX host,
and all other recipients directly.
master.cf:
submission .. .. ... . smtpd
-o { smtpd_recipient_restrictions =
check_recipient_access
inline:{{example.com = filter smtp:mx.example.com}}
On 05-18-2021 2:32 pm, IL Ka wrote:
Think about postfix as about some kind of router.
It has several "input channels" like smtpd server or sendmail command.
All messages go to the queue and routed by "qmgr" regardless the way
they got to the system
http://www.postfix.org/OVERVIEW.html
I have
On 05-18-2021 2:12 pm, Matus UHLAR - fantomas wrote:
so, you have multiple instances?
No, i don't have multiple instances of a postfix install. Postfix has
multiple instances as in:
01: /usr/libexec/postfix/master -w
02: \_ pickup -l -t unix -u
03: \_ qmgr -l -t unix -u
04: \_ smtpd -n sub
>
> And i know you all keep politely telling me im crazy for not
> understanding postfix wants to deliver to user's mailboxes. I get that.
> Not knowing the inner workings of postfix, from a logical point of view,
> submission isn't smtp:25, it has its own service spawn, it works on its
> own port,
On 05-18-2021 12:41 pm, Jaroslaw Rafa wrote:
This gets more and more confusing. I understand what you are trying to
achieve in two-server setup, but in case there is only one server,
where do
you want to send the local mail if not deliver it locally? Where
else can it
be delivered if there is o
On 05-18-2021 12:41 pm, Jaroslaw Rafa wrote:
This gets more and more confusing. I understand what you are trying to
achieve in two-server setup, but in case there is only one server,
where do
you want to send the local mail if not deliver it locally? Where else
can it
be delivered if there is o
On 05-18-2021 12:36 pm, Jaroslaw Rafa wrote:
If Postfix on server X is only for submission, then how does Postfix on
server Y deliver mail to server X?
It doesn't because as you said, server X is only for submission. Nothing
should ever be delivered to X. Server Y is the destination and Y shoul
Dnia 18.05.2021 o godz. 11:45:53 post...@ptld.com pisze:
>
> Yes, i understand the logic of what is happening. The only behavior
> im trying to change is for the submission service, because on a
> single server setup (in my perfect world) postfix is the destination
> for mail received via smtp:25
Dnia 18.05.2021 o godz. 11:45:53 post...@ptld.com pisze:
>
> Yes, and postfix X is not the MX server for the recipient domain. If
> you didn't get the beginning of this thread, the purpose of postfix
> X is to be only a submission service for dovecot/imap. I wouldn't
> even use postfix if possible
On 05-18-2021 11:17 am, Matus UHLAR - fantomas wrote:
So, you want postfix X to deliver mail to whatever server is MX for the
recipient domain.
On 18.05.21 11:45, post...@ptld.com wrote:
Yes, and postfix X is not the MX server for the recipient domain.
no mailservers I know care about MX serv
On 05-18-2021 12:00 pm, Viktor Dukhovni wrote:
A multi-instance configuration can do what you ask and more.
I believe this is the third time I've said that that's the main
way (likely the only way) to do this.
Yes, i understand and heard you. In the same email you replied to at the
bottom i ac
> On May 18, 2021, at 11:45 AM, post...@ptld.com wrote:
>
> Yes, and postfix X is not the MX server for the recipient domain. If you
> didn't get the beginning of this thread, the purpose of postfix X is to be
> only a submission service for dovecot/imap. I wouldn't even use postfix if
> possib
On 05-18-2021 11:17 am, Matus UHLAR - fantomas wrote:
So, you want postfix X to deliver mail to whatever server is MX for the
recipient domain.
Yes, and postfix X is not the MX server for the recipient domain. If you
didn't get the beginning of this thread, the purpose of postfix X is to
be on
On 05-18-2021 10:51 am, Wietse Venema wrote:
You want Postfix X to forward a recipient to Postfix Y (the MX).
You want Postfix Y to deliver that recipient to Postfix X.
That is a loop. It can be broken with multiple instances,
content_filter,
or smtpd_proxy_filter.
On 18.05.21 11:11, post...
On 05-18-2021 10:51 am, Wietse Venema wrote:
You want Postfix X to forward a recipient to Postfix Y (the MX).
You want Postfix Y to deliver that recipient to Postfix X.
That is a loop. It can be broken with multiple instances,
content_filter,
or smtpd_proxy_filter.
Not exactly.
Yes i want p
post...@ptld.com:
> I do not understand how what im asking would cause a loop issue. If mail
> received by submission service uses transport smtp: which then connects
> to smtp:25 and smtpd service by default uses transport=virtual it would
> never loop. Unless again the answer is postfix isn't
On 05-18-2021 9:45 am, Viktor Dukhovni wrote:
As I already noted in this thread, doing this on a single machines is
typically best accomplished via a MULTI-INSTANCE configuration, with
separate submission and relay instances.
I read over multi instance and it feels heavy handed / overkill for wh
Wietse Venema:
Actually, here is a simpler one, that uses content_filter.
master.cf:
submission .. .. .. .. smtpd
-o { content_filter = smtp:[mxhost.example.com] }
In my situation this did not give the behavior i was looking for. It
sends all mail to the smtp:host, including mail g
On Tue, May 18, 2021 at 09:26:40AM -0400, post...@ptld.com wrote:
> But for the single all in one server configuration, i tried:
>
> main.cf:
> virtual_transport=virtual
>
> master.cf:
> submission inet n - n - - smtpd
> -o virtual_transport=smtp:mxhost.example.com
>
> However the -o option
On 05-18-2021 8:53 am, Wietse Venema wrote:
Wietse Venema:
Remove the recipient domain from main.cf:mydestination and
main.cf:virtual_mailbox_domains.
Add the recipient domain to main.cf:relay_domains.
Actually, here is a simpler one, that uses content_filter.
master.cf:
submission .. ..
Wietse Venema:
> post...@ptld.com:
> > If i send mail to submission:587 addressed to another user on the same
> > server, postfix instead of sending the mail to the mx records for that
> > domain, and connecting to postfix on smtp:25 it bypasses all of that and
> > delivers directly into that us
post...@ptld.com:
> If i send mail to submission:587 addressed to another user on the same
> server, postfix instead of sending the mail to the mx records for that
> domain, and connecting to postfix on smtp:25 it bypasses all of that and
> delivers directly into that users inbox. This avoids al
On Mon, May 17, 2021 at 11:02:35PM -0400, post...@ptld.com wrote:
> If I send mail to submission:587 addressed to another user on the same
> server, postfix instead of sending the mail to the mx records for that
> domain, and connecting to postfix on smtp:25 it bypasses all of that and
> delive
34 matches
Mail list logo
