Re: virtual mailbox domains??

post...@aecperformance.com: > How can I debug/resolve this problem? By sharing Postfix logs, in addition to Postfix configurations. "email to X bounces" is not sufficient to determine *WHY* delivery is failing. Wietse

Re: virtual mailbox domains??

post...@aecperformance.com: > I stopped postfix and dovecot, > cleared the logs, > started postfix and dovecot, > attempted to send an email to smok...@sizzelicks.com (I don't see this in > the logs) and then > attempted to create a mail account in Thunderbird for smok...@sizzelicks.com

Setting up virtual mail users

I stood up my server using these instructions from this website, which have gotten me VERY far. However, I'm at a deviation point. I'd like to have virtual users (and not require local unix accounts for those "users"), and then possibly even forward those emails to a real user, effectively

RE: virtual mailbox domains??

I tried to send the logs and configs. I cleared the logs before I: started postfix & dovecot; attempted to send an email; attempted to create a mail account in Thunderbird. Then I retrieved syslog and mail.log. For configs I did: postconf -n postconf Mf dovecot -n The email bounced

RE: virtual mailbox domains??

postconf n append_dot_mydomain = no biff = no compatibility_level = 2 inet_interfaces = all mailbox_size_limit = 0 mydestination = localhost myhostname = softlinksys.com readme_directory = no recipient_delimiter = + smtpd_banner = $myhostname ESMTP $mail_name (Ubuntu)

RE: virtual mailbox domains??

dovcot -n # 2.3.7.2 (3c910f64b): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.7.2 () # OS: Linux 5.4.0 x86_64 Ubuntu 20.04.3 LTS ext4 # Hostname: softlinksys.com auth_mechanisms = plain login auth_username_format = %n mail_location = maildir:/var/mail/vhosts/%d/%n

RE: virtual mailbox domains??

I stopped postfix and dovecot, cleared the logs, started postfix and dovecot, attempted to send an email to smok...@sizzelicks.com (I don't see this in the logs) and then attempted to create a mail account in Thunderbird for smok...@sizzelicks.com syslog Dec 3 19:26:55 softlinksys

RE: virtual mailbox domains??

Thunderbird -Original Message- From: owner-postfix-us...@postfix.org On Behalf Of Wietse Venema Sent: Friday, December 3, 2021 1:35 PM To: Postfix users Subject: Re: virtual mailbox domains?? post...@aecperformance.com: > How can I

virtual mailbox domains??

VPS Ubuntu 20.04 postfix 3.4.13 and dovecot 2.3.7.2 Virtual Mailboxes MySql Our server hosts multiple mail domains each having multiple email addresses. Domain: sizzelicks.com has an MX record pointing to mail.sizzelicks.com showing the IP: 194:163:45:150 which is our VPS IP.

are my helo restrictions too strict ?

Hello, I have strict helo checks: smtpd_helo_required = yes smtpd_helo_restrictions = reject_non_fqdn_helo_hostname, reject_invalid_helo_hostname, reject_unknown_helo_hostname now I have noticed mails being rejected:

Re: are my helo restrictions too strict ?

Fourhundred Thecat: > Hello, > > I have strict helo checks: > >   smtpd_helo_required = yes >   smtpd_helo_restrictions = reject_non_fqdn_helo_hostname, >     reject_invalid_helo_hostname, >     reject_unknown_helo_hostname Anecdotal: I used to have these exact

Re: are my helo restrictions too strict ?

On 03.12.21 09:14, Fourhundred Thecat wrote: I have strict helo checks: smtpd_helo_required = yes smtpd_helo_restrictions = reject_non_fqdn_helo_hostname, reject_invalid_helo_hostname, reject_unknown_helo_hostname should be

Re: are my helo restrictions too strict ?

> "JR" == Jaroslaw Rafa writes: JR> Dnia 3.12.2021 o godz. 09:14:23 Fourhundred Thecat pisze: >> Hello, >> >> I have strict helo checks: >> >> smtpd_helo_required = yes smtpd_helo_restrictions = >> reject_non_fqdn_helo_hostname, reject_invalid_helo_hostname, >> reject_unknown_helo_hostname

Re: are my helo restrictions too strict ?

Dnia 3.12.2021 o godz. 09:14:23 Fourhundred Thecat pisze: > Hello, > > I have strict helo checks: > > smtpd_helo_required = yes > smtpd_helo_restrictions = reject_non_fqdn_helo_hostname, > reject_invalid_helo_hostname, >

destination_concurrency_limit after while moving from Postfix 3.1.15 to Postfix 3.5.6

Hi folks, I moved from Postfix 3.1.15 to 3.5.6... It was mandatory to upgrade it in order to remove any legacy version (OS and Postfix) ! Before that everything was perfect : respecting the limit of connections for a specific route per IP with connection reuse without TLS ! Since moving from

Re: destination_concurrency_limit after while moving from Postfix 3.1.15 to Postfix 3.5.6

Le 03/12/2021 à 14:48, Yves-Marie Le Pors Chauvel a écrit : Hi folks, I moved from Postfix 3.1.15 to 3.5.6... It was mandatory to upgrade it in order to remove any legacy version (OS and Postfix) ! Before that everything was perfect : respecting the limit of connections for a specific route