Sorry for following up on my own post, but I want to correct the record.
Please disregard my previous email. I realize now I made a blunder
during the analysis, since I was working on two similar questions one
unrelated to postfix and I mixed up the data sets without realizing it.
Sorry for the
I thought that may be right, but if I comment out the "inet_interfaces" it
fails to take mail from the main server for outbound delivery.
Sent with Proton Mail secure email.
On Friday, May 31st, 2024 at 1:32 PM, Wietse Venema via Postfix-users
wrote:
> Mailman29 via Postfix-users:
>
> >
> On 31 May 2024, at 16:13, Wietse Venema via Postfix-users
> wrote:
>
> Gerben Wierda via Postfix-users:
>>> On 31 May 2024, at 14:53, Wietse Venema wrote:
>>>
>>> Gerben Wierda via Postfix-users:
> On 31 May 2024, at 13:20, pat...@patpro.net wrote:
>
> Hello,
>
>
Mailman29 via Postfix-users:
> I have changed the $myhostname string and it still says it loops
> back to myself. Port 25 must be forwarded for incoming mail. Postfix
> isn't supposed to be listening to any ports. In fact, I only have
> smtpd enabled, and not smtp. This is very confusing. :(
To in
I have changed the $myhostname string and it still says it loops back to
myself. Port 25 must be forwarded for incoming mail. Postfix isn't supposed to
be listening to any ports. In fact, I only have smtpd enabled, and not smtp.
This is very confusing. :(
Sent with Proton Mail secure email.
Gerben Wierda via Postfix-users:
> > On 31 May 2024, at 14:53, Wietse Venema wrote:
> >
> > Gerben Wierda via Postfix-users:
> >>
> >>> On 31 May 2024, at 13:20, pat...@patpro.net wrote:
> >>>
> >>> Hello,
> >>>
> >>> Any sign of postfix 3.9 blacklisting HAproxy because of SMTP
> >>> errors/a
> On 31 May 2024, at 14:53, Wietse Venema wrote:
>
> Gerben Wierda via Postfix-users:
>>
>>> On 31 May 2024, at 13:20, pat...@patpro.net wrote:
>>>
>>> Hello,
>>>
>>> Any sign of postfix 3.9 blacklisting HAproxy because of SMTP
>>> errors/abuse/half-baked connections?
>>
>> Not blacklisting
On Fri, May 31, 2024 at 8:01 AM Wietse Venema via Postfix-users
wrote:
>
> Greg Sims via Postfix-users:
> > I set the following in main.cf
> >
> > mydestination = localhost
> >
> > and received the following in our logs:
> >
> > May 31 04:42:27 mail01.raystedman.org postfix/local[3978]:
> > 7CE5
Viktor Dukhovni via Postfix-users:
> On Fri, May 31, 2024 at 02:01:50PM +0200, Gerben Wierda via Postfix-users
> wrote:
>
> > It sends: "PROXY TCP4 192.168.2.2 192.168.2.2 65535 587\r\nQUIT\r\n"
> > It expects a response that matches regex ^220
>
> Don't send "QUIT\r\n", just send the PROXY hand
Greg Sims via Postfix-users:
> I set the following in main.cf
>
> mydestination = localhost
>
> and received the following in our logs:
>
> May 31 04:42:27 mail01.raystedman.org postfix/local[3978]:
> 7CE5C30F558E: to=, orig_to=,
> relay=local, delay=0, delays=0/0/0/0, dsn=5.1.1, status=bounce
Gerben Wierda via Postfix-users:
>
> > On 31 May 2024, at 13:20, pat...@patpro.net wrote:
> >
> > Hello,
> >
> > Any sign of postfix 3.9 blacklisting HAproxy because of SMTP
> > errors/abuse/half-baked connections?
>
> Not blacklisting as I understand it, but as HAproxy makes a connection to
On 31.05.24 12:19, Gerben Wierda via Postfix-users wrote:
smtpd_milters =
unix:/opt/local/var/spool/postfix/opt/local/var/run/rspamd/milter.sock
But it gets greylisted anyway:
May 31 12:02:13 hermione smtp/smtpd[58412]: connect from
66-220-155-148.mail-mail.facebook.com[66.220.155.148]
May
I set the following in main.cf
mydestination = localhost
and received the following in our logs:
May 31 04:42:27 mail01.raystedman.org postfix/local[3978]:
7CE5C30F558E: to=, orig_to=,
relay=local, delay=0, delays=0/0/0/0, dsn=5.1.1, status=bounced
(unknown user: "bounce-local")
May 31 04:4
On Fri, May 31, 2024 at 02:01:50PM +0200, Gerben Wierda via Postfix-users wrote:
> It sends: "PROXY TCP4 192.168.2.2 192.168.2.2 65535 587\r\nQUIT\r\n"
> It expects a response that matches regex ^220
Don't send "QUIT\r\n", just send the PROXY handshake and wait for 220,
and then drop the connecti
I have a whitelist file rna_rbl_whitelist_clients that contains:
# Part of smtpd_recipient_restrictions (greylisting is managed per recipient)
# These are the CLIENTS that are allowed to bypass greylisting
/\.facebook\.com$/ OK
/\.facebookmail\.com$/ OK
and th
On Fri, May 31, 2024 at 01:06:20PM +0200, Gerben Wierda via Postfix-users wrote:
> Hmm, I just noticed (all outgoing smtp was going to a backup server
> that works) that one of my postfix instances cannot send mail (smtp
> doesn't work, postscreen and smtpd work fine).
What *exactly* do you mean
> On 31 May 2024, at 13:20, pat...@patpro.net wrote:
>
> Hello,
>
> Any sign of postfix 3.9 blacklisting HAproxy because of SMTP
> errors/abuse/half-baked connections?
Not blacklisting as I understand it, but as HAproxy makes a connection to test
if the service is up and then breaks the conne
Gerben Wierda via Postfix-users:
> Hmm, I just noticed (all outgoing smtp was going to a backup server that
> works) that one of my postfix instances cannot send mail (smtp doesn't work,
> postscreen and smtpd work fine).
>
> # submission (587)
> submission inet n - n - -
Hello,
Any sign of postfix 3.9 blacklisting HAproxy because of SMTP
errors/abuse/half-baked connections?
May 31, 2024 1:06 PM, "Gerben Wierda via Postfix-users"
wrote:
Hmm, I just noticed (all outgoing smtp was going to a backup server that works)
that one of my postfix instances cannot send m
Hmm, I just noticed (all outgoing smtp was going to a backup server that works)
that one of my postfix instances cannot send mail (smtp doesn't work,
postscreen and smtpd work fine).
# submission (587)
submission inet n - n - - smtpd
-o smtpd_tls_security_level=en
On Fri, May 31, 2024 at 12:33:34AM +, Mailman29 via Postfix-users wrote:
> Yeah, so even changing the domain name on the server (Ubuntu) itself
> doesn't fix the issue. It must be ip based. Since the proxy and
> Postfix share an IP address, Postfix will always think it's looping
> back to itse
21 matches
Mail list logo
