Hello,
i would say for *accepting* mail you 'just' have to get the following
working:
- ability to accept tcp connections on port 25
(some public reachable ip, no port 25 filtering by ISP)
- have some dns A/ record(s) pointing to your public reachable
ipv4/ipv6
- have the MX
Hi,
from a SMTP protocol point of view, postfix just ingests mail on the one
end, and hands it over on the other end.
What you are describing is, that postfix will accept any and all mail.
That parts seems easy enough, and does not require any database or
speaking with dovecot (as the
On 25/10/2021 11:35, Vincent Pelletier wrote:
I would rather postfix just stop sending emails altogether in such case,
than send them from an unexpected ip: a delay is preferable to me to
uncertainty as to how the emails were processed by recipient SMTPs.
As a categorical prevention of postfix
Hi there,
always distrusting that my brain remembers documentation correctly, i
checked the meaning of ``unknown_client_reject_code''.
http://www.postfix.org/postconf.5.html#unknown_client_reject_code
Incidentally, i also clicked on the presented link (in html source):
Hi,
did you already ctrl+f for 'reject_sender_login_mismatch' and
'smtpd_sender_login_maps' in http://www.postfix.org/postconf.5.html
?
regards,
Max
On 28/09/2021 13:36, João Silva wrote:
Hi
I need to limit the domains in "mail from" for autenticated users to
prevent sending emails with
If you are only
interested in what mail clients do, and can't find any
online explanation, you could either look at the source
code to some open source ones (probably the easiest
way),
to me, this feels rather the most troublesome way :-)
or set up a mail smarthost with multiple IP
Hi there,
when a user clicks "send", the email client has to make some
tcp-connection to some ip address.
what if the hostname configured at the email client resolves to multiple
ip addresses?
i actually know the theory (either round-robin, or just the first, or
try first and if fail then
On 30/05/2021 12:47, Laura Smith wrote:
It is a fairly recent change, perhaps a year ago, that they return the .254 and
.255
codes rather than just ignoring the request, as a hint that you need to fix your
configuration.
Seems the change is dated 11/2/2021
Hello,
well, as a quick-fix you could always start an additional smtpd service
on a non-standard port (by adding an appropriate line in master.cf) and
configure this additional smtpd in exception ways (by adding "-o
smtpd_tls_FOO" options to the additional smtpd service)
example master.cf line
Hi,
i am guessing, that you have configured maildrop via the
`mailbox_command` configuration parameter? in that case, the theory i
can offer is, the following:
according to http://www.postfix.org/postconf.5.html#home_mailbox the
mailbox_command has higher precedence than home_mailbox:
> The
Hi Mark,
just to rule out any misunderstandings:
According to the logs you posted, the Postfix local mail delivery (and
not dovecot) is used to deliver the mail to some directory on the system.
I think that is what Viktor had in mind, when suggesting you look the
folder returned by the command
> Am 19.12.19 um 10:02 schrieb Viktor Dukhovni:
> [..snipped..]
it's funny, yesterday (and the day before, actually) i double-checked it
from every angle i could think of.
and now? i just cannot reproduce the error now. it just works like you
say. like a charm.
so whatever you did, thanks for
Hi List!
for a particular connection, i always received the error message "Server
certificate not verified". client was postfix, server was postfix. both
as distributed by debian stretch, version 3.1.12-0+deb9u1.
i was using the following settings on the smtp-postfix:
relayhost=[localhost]:24
13 matches
Mail list logo
