Tag Info

Hot answers tagged

14

The whole idea behind the MX record is to specify a host or hosts which can accept mail for a domain. As specified, the MX record must therefore point to a host which itself can be resolved in the DNS. The reasons for this in the 1980s, when the specs were originally written, are almost the same as the reasons for it today: A host may be connected to ...


6

To execute your filters on your existent mailbox you can manually run sieve-filter from the command line. To (dry) run the sieve-script example.sieve as user test on the mailbox INBOX use the following command: sieve-filter -v -C -u test /path/to/sieve/example.sieve 'INBOX' Once you like the actions sieve would perform you can execute the script with ...


4

Your reject_rbl_client declaration goes into the smtpd_recipient_restrictions declaration found in main.cf. For my CentOS machines, that's in /etc/postfix/. The code you posted tends to show up in master.cf. That's a different file all-together. This is what my smtpd_recipient_restrictions definition looks like: smtpd_recipient_restrictions = ...


3

I also changed the MX Records for the email service. I am able to send mails but not receive any mails. When I check on a MX lookup service I see my new records when I prefix www (www.abc.com) to the domain but just the domain name (abc.com) it throws up blank results. If you want to receive email for domain.com, the MX records need to be under ...


3

Yes, you can set up a separate SMTP mail server on separate machines. Many bulk mail programs have the option to distribute mail to each individual server. If the goal is to have separate IP addresses, you can set up virtual box to have the updates sent with the same IP address. There is nothing extra you have to do than configure the mail servers. ...


3

Thia maillog line Jan 19 13:45:13 mydomain postfix/smtpd[2361]: fatal: unexpected command-line argument: ### was clear indicator that something wrong on master.cf syntax. You already confirmed this in your answer. In this part, I will try to explain why mail go through when you requeue them. When you issue command postsuper - r to requeue message, ...


3

In amavisd.conf there is a line up at the top of the file $log_templ= you will want to add %b to that, it will include the MD5 hash of the email in the log. You will probably want to read the README.customize a bit more, because you will be redefining how amavisd logs. This is one I've found, it's not impossible to understand, you'd just need to add the %b ...


3

This is somewhat up to your applications and what you want to do exactly, but most likely it would work. However, you would still need a local relay server, but not necessarily a full blown Postfix instance - a relay-only server like nullmailer might be sufficient.


3

If you want to get standard in your MTA, then you can read all links in the RFCs. As postfix built upon this standard, then default value in postfix configuration should be standard. In your case, maximal_queue_lifetime default value is 5d (5 days), you can check it yourself via run postconf -d maximal_queue_lifetime Above configuration derived from RFC ...


3

As you write, it had to work. user1316146 is also right: gethostbyaddr is doing reverse ip lookups, which aren't needed for mail sending. The problem isn't here, on my opinion. I think, you have simply a noisy network or a not really reliable local dns. You had to configure your sendmail to try to get its target address more agressively, and many times. ...


3

gethostbyaddr is performing reverse DNS, so you need to have PTR records set up for the IP addresses in question. You also needs to have that address range delegated to you for public address. If you're using 8.8.8.8 as your DNS for the box, you're not going to be able to have PTR records for the 10.0.0.0/8 network. This lookup usually only occurs for ...


2

I found out the solution. First you have to check that in /etc/hosts file, your hostname is mapped to your IPv4 and IPv6 address. Then you can can use this in /etc/postfix/master.cf: ... yourhostname:submission inet n - n - - smtpd ...


2

Can this work? Yes. Do you want to do it this way? No. Gmail is not meant to be used in this way. They have somewhat arbitrary restrictions and limits on what can be sent, and how many emails can be sent. If you run into these restrictions, they'll gladly cut you off without warning. Belive me, I've had personal experience with this. Instead of Gmail, ...


2

It would have been good if the output included the connecting address but based on the provided report it would appear that you connected via IPv6. The reason why I say this is that, when processing the a directive in the SPF record, it looked up example.com.au. AAAA instead of example.com.au. A. If the client connected via IPv6 there is no chance that ...


2

As the others said, you put reject_rbl_client in wrong place. Set it in smtpd line master.cf or in main.cf. If your postfix has version 2.8 higher, you can put the RBL checking in postscreen. You can get more info in Postscreen Howto page. For example, the equivalent config of reject_rbl_client sbl-xbl.spamhaus.org, reject_rbl_client bl.spamcop.net in ...


2

I'll throw this out as a guess. Course, I'm home with the flu so maybe I'm loopy. RFC 974 states: The first step for the mailer at LOCAL is to issue a query for MX RRs for REMOTE. It is strongly urged that this step be taken every time a mailer attempts to send the message. The hope is that changes in the domain database will rapidly ...


1

IN RFC 1025 MX records only point to a RR (resource record) of an A Record or a CNAME. So the mail server sending the mail asks for the RR of an MX record, the mx record lists A records of servers, the mail server does a forward lookup to get an A record and then forwards the mail via smtp to the service host listed as a mail server 'willing' to receive ...


1

DNS as a protocol has some different types of values, these are not interchangable. It's important to note that DNS is a binary protocol with strict mappings between the type of record and the type of data that such a record holds. For example: An A record holds an IPv4 address (4 bytes of data, fixed length). An AAAArecord holds an IPv6 address (16 bytes ...


1

Some email servers (like exim) specifically do not allow sending to MX records that point to a pure IP address, so you're required to use a FQDN for it instead to be compliant. This is because most servers expect the MX record to contain a hostname, not an IP (that's what A records are for). Edit: To elaborate, in DNS each record has strict requirements for ...


1

The problem lies in your costumer. Your server expect that the client (costumer) will sent email content after 354 Enter mail, end with "." on a line by itself. Unfortunately the client doesn't send any data after 5 minutes (09:33:04 -- 09:38:04) thus exceeding timeout from the server. Because server doesn't want to spend their resources on silent (and ...


1

Oh I feel just so stupid... found the mistake. masegaloeh thx for your hint and sorry for everyone who wasted time cause of my stupidness... I just had a wrong placed comment in my master.cf which I deleted before I posted the content here so my original master.cf file locked like this: ##### Amavis inbound properties ###### 127.0.0.1:10025 inet n - n - - ...


1

OK looks like there are too many mismatch in your postfix, roundcube and dovecot configuration. Let's break it down one by one. STARTTLS error This log line warning: TLS library problem: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca:s3_pkt.c:1293:SSL alert number indicated that PHP fails to verify peer certificate because unknown ...


1

As far as I can see you just want to send mails. In this case you must not set an MX record for the server, as your mail server is not responsible for any domain. If I understand your problem, you really just want an MTA that relays your mails. Setting up a full fledged mail server for this purpose is overkill; so first here are a few alternatives: ...



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