Tag Info

Hot answers tagged

3

When postfix receives incoming email, basically it can be divided into three processes: Receive email by doing SMTP transaction with sender mail server and apply SMTP restrictions, for example: check if recipient exist Store email by sending it into one of delivery agents (dovecot, local, virtual) Based on two processes above, parameter ...


3

In the event of a remote server being unreachable, Postfix (and any such MTA) will just queue/spool the message and keep retrying - you can configure the threshold/duration of the retries by changing the maximal_queue_lifetime, maximal_backoff_time, minimal_backoff_time and queue_run_delaysettings. If you don't want to force global values, a quite hacky ...


2

Every system has a hostname, it is given by the administrator when the system is installed/set up. It is used by all installed network-related software to identify the machine . To get the current set hostname, you can just call hostname or look in /etc/hosts, as the hostname always points to localhost. The hostname is essential as all network related ...


2

Here the extended version of @sebix's comment above. This untested solution taken directly from dovecot 2 wiki: Pigeonhole Sieve examples. You need subaddress extension from dovecot sieve to do it. Put it in sieve script. Here the simple example to put email foo+spam@example.org to Spam folder. require ["fileinto", "envelope", "subaddress"]; if envelope ...


2

Here is the email journey across postfix daemon before you put spamassassin stuff Email for a@example.com -> aliased to a@example.com and b@example.com -> final destination After you put spamassassin stuff, basically you put content filter in postfix stack, thus the email journey becomes Email for a@example.com -> aliased to a@example.com and ...


1

Some documentation is more verbose [1]: -u domain (default: system FQDN hostname) Use domain to set user domain property (realm). SASL can be used for authenticating users with different realms (domains, FQDN, servers ...). You can think of it as an email address, which consist of user and domain. This is required to cover some authentication methods ...


1

Sender dependent authentication can help. There is good example in official documentation. Postfix supports different ISP accounts for different sender addresses (version 2.3 and later). This can be useful when one person uses the same machine for work and for personal use, or when people with different ISP accounts share the same Postfix server. To ...


1

You can specify many mysql maps in virtual_mailbox_maps parameter. For your example case, here the configuration virtual_mailbox_maps = mysql:/etc/postfix/example1,mysql:/etc/postfix/example2 Then in both maps specify the different parameters #/etc/postfix/example1 user = someone password = some_password hosts = foo.example1.org dbname = foodb query = ...


1

The remote SMTP client doesn’t even try to authenticate and makes no attempt to send a message. Your log file shows that it simply QUITs after it receives a response to its EHLO User command: < s72-38-252-2.static.datacom.cgocable.net[72.38.252.2]: EHLO User ... < s72-38-252-2.static.datacom.cgocable.net[72.38.252.2]: QUIT I’d suspect that the ...


1

Each time you have modified /etc/aliases you have to launch newaliases command.


1

The alias file is used for routing of incoming emails. It does not affect the envelope sender of outgoing emails. That's something you need to set in whatever it is you're using to send the emails.


1

Don't use virtual_alias_maps, use alias_maps instead. Parameter virtual_alias_maps match all address classes Parameter alias_maps match only local address class i.e. address defined in mydestination parameter See Address Class README for more information. So, the parameter of alias_maps would become #main.cf alias_maps = ...


1

It appears postfix completely ignores /etc/hosts. If the setting relayhost = FQDN instead of an IP address, it will try to resolv the FQDN for its IP address and will not use /etc/hosts to find it. It will use the system configured resolv.conf file if smtp_host_lookup is set to native. Since it could not resolve my relay host it instead just attempted to ...



Only top voted, non community-wiki answers of a minimum length are eligible