Re: about MTA's 4xx response code
Hi, Here's an extract from a site about 421: SMTP Error 421 421 Temporary System Problem. Try again later. 421 Try again later, closing connection. 421 Server busy, try again later. The SMTP error 421 is normally used for temporary problems on the mail server or a problem with the recipients email account. Some mail providers might also return 421 after you reached a limit (restriction) on your mail account (see SMTP Error 451 below). Does this help? Suggesting the RFC be modified is off the table, because that is not the problem. RFC's are very seriously thought out and hugely important documents, tested and approved by serious committees. Looking. Sure, they get updated, but not for reasons related to issues like this. Andrew On 29/8/19 12:36 pm, Eliza wrote: I know postfix returns 4xx Response Code for Temporarily Deferred, as below: - The following addresses had fatal errors - [Status: Error, Address: , ResponseCode 421, 4.7.0 Temporarily Deferred] Message will be retried for 4 more day(s) I don't like every MTA returns this 4xx code, that would make the incoming messages delay a lot time. How do you think of this? should RFC reconsider to disable 4xx code?
Re: Postfix for three domains on one host
Now am I further confused. What is $myorigin used for then? Andrew On 16/8/19 12:04 pm, Ralph Seichter wrote: The "From" header is usually provided by the MUA. According to your message headers, you are using Thunderbird, so that's where you define your desired sender address(es). Postfix won't overwrite that header. -Ralph
Re: Postfix for three domains on one host
HI Raplh, Does this cover the case where each domain has its own header showing origin from each distinct domain? When I tried your suggestion they all come out from $myorigin. What am I missing? Inbound works fine to any number of virtual domains for me. It's outbound that has me perplexed. On 16/8/19 11:20 am, Ralph Seichter wrote: Yes, a single Postfix instance with one IP address can easily handle multiple domains. http://www.postfix.org/VIRTUAL_README.html should get you started.
Postfix for three domains on one host
I want to use my single VPS for three distinct domains. Simple for webservers. I would also want to be able to send and receive email on the three domains using Postfix. I understand there is postfix-multi. Everything I have read so far uses separate IP addresses for this scenario. Most VPS providers are loath to assign more than one or at most two IPV4 address to a VPS, due to the global shortage. I have been unable to get three at Linode. Not just subdomains, but quite distinct ones. For example (just abstract names) ab.space cd.space zx.com The obvious solution is to run three VPS's. But this adds expense and triples the admin overhead. is there any way to configure Postfix to act for three separate domains without the necessity of separate IP's? Pardon me if this is a stupid newbie question, but it seems to me that Postfix is enormously powerful and can do pretty much anthing if you know how. Andrew
Re: Format of ip address in /etc/postfix/access
Hello Durga, I think that's a strange way to write an IP address. If you do man 3 inet_addr the format for the dotted address is explained. As stated in that man page: In all of the above forms, components of the dotted address can be specified in decimal, octal (with a leading 0), or hexadecimal, with a leading 0X). Addresses in any of these forms are collectively termed IPV4 numbers-and-dots notation. The form that uses exactly four decimal numbers is referred to as IPv4 dotted-decimal notation (or sometimes: IPv4 dotted-quad notation). An example is given: $ ./a.out 226.000.000.037 # Last byte is in octal So 037 is octal not decimal. Because 6 is less than 7 you can get away with it, but not for long with other numerical values that exceed octal. I think its inviting trouble for maintainers of your code. Andrew On 11/8/19 2:59 am, Durga Prasad Malyala wrote: I am curious what is the format of IP addresses in /etc/postfix/access. i.e. will it understand 006.45.023.230 instead of the common 6.45.23.230 ?
