Tag Info

Hot answers tagged

15

sendmail relies on the retry mechanisms in the SMTP protocol for reliability of delivery and does not need to depend on a clever server implementation. Which is why that doesn't exist as far as I know. When you restart sendmail simply aborts any incoming connections with a temporary error and sends a 421 response expecting the delivery to be retried later ...


4

I've been running my own email server for 17 years, including hosting a large mailing list, and although it takes time I find it's perfectly possible, even today. Most of what should be done, you're already doing; but one factor you don't address is what kind of IP address you're using. Many mail providers outright blacklist (or use as a strong marker for ...


3

The obvious solution is put $myhostname or linuxmachine.example.com in mydestination parameter. explanation Before the config modification, here the background event after you send email via mail external Postfix receives email via pickup service. Because the recipient doesn't have domain parts and (by default) parameter append_at_myorigin has value yes, ...


3

You have to create the router that redirect outgoing messages: intercept: driver = redirect domains = !+local_domains data = auditor@local.tld pipe_transport = address_pipe no_more Place that router at the very beginning of begin routers section to ensure each message will be proceeded. When message addressed to the ...


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

Exchange will use TNEF if the message is sent via Rich Text Format (not the same as RTF!). The senders should opt to use HTML or Plain Text when sending you messages, or the admin can generally set this at the domain level e.g in Exchange 2010, Exchange Management Console>Organisation Config>Remote Domains, add your domain and set 'Exchange Rich Text' to ...


2

You can do that via special router, transport and script. First you have to add the router that measure the size of message: slimit: driver = accept condition = ${if >{$message_size}{1M}} transport = size_warning unseen Place that router at the beginning of router section Then add the transport anywhere at the ...


1

This is going to be an incomplete answer but I hope it gets you on track. The transport you specified in your transport table has to point to something Postfix knows about (and a transport has nothing to do with your aliases). That is, "mailman" needs to be defined in master.cf. Most postfix installations come with an example mailman service in master.cf ...


1

I'm not aware of "outlook autodiscovery" working at all without the "proper" DNS TXT and SRV records in your domain. But these are non-standard and may differ depending on how you, your ISP, or your hosting provider have configured your email SERVER and which server it is. here are some samples of ISP, Microsfot , and tech help blogs showing the variety ...


1

Don't give up hope completely. Running your own mail server is sometimes a pain but it sounds like you're doing everything right. Generally I would say if they aren't blocking you outright (i.e. you get bounces back) then it's a content issue. Try adjusting the content somewhat. Microsoft aren't the best at anti-spam but they try hard for their users - ...


1

Your postfix haven't access to the auth-daemon socket because of different uid and strict permissions. The easiest way is to change permissions to the 666 (rw-rw-rw-) and check whether the auth become fixed. Then you have to deal with process UIDs/users to restrict auth to only mail software. service auth { unix_listener /var/spool/postfix/private/auth { ...


1

Generally speaking the receiving server will look at the client that has connected to it and asked to deliver some mail. The first part of the SMTP protocol is a greeting command (HELO or EHLO) where the client can identify itself. Most email servers will take that claimed identity and compare it to the PTR record for the client's IP address. The client ...


1

Disabling ipv6 on centos 6.5 seems to have removed this issues.


1

This question is likely to be too broad for ServerFault, but I'll have a go at pointing you in the right direction. Postfix is an MTA (Mail Transfer Agent) and as such will only transport email between systems - for example, receiving email from either clients and forwarding to destination servers, or receiving email intended for other servers and ...


1

It is not sendmail.mc changes that you need to track, but sendmail.cf. Sendmail reads sendmail.cf. sendmail.mc is written in m4 and the output is sendmail.cf. So you need to produce it first and then kill -HUP the sendmail process ID. In Debian / Ubuntu systems running sendmailconfig is enough. In CentOS you need something like: cd /etc/mail /etc/mail/make ...



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