Tag Info

New answers tagged

2

It's not completely clear what your overall plan entails but here are some clarifications about how wildcard records work in general. I think this should clarify what may potentially be a problem. Wildcard records do not cover the base name (ie *.example.com. does not cover example.com.). Wildcard records never overlap with anything, whether CNAME or any ...


1

The target server name is not used in the SMTP request. There is no equivalent of the HTTP Host: header. If you want to use an IP address instead of a DNS name, I'd recommend that you talk to the email service provider to verify which IP address they'd prefer you to use. (And, for $DEITY's sake, don't hard code the IP address - use a config file or put it ...


-1

I have found a solution : Open a cmd on the server type the following commands : set timeout = 55 That's worked for me.


0

The reason for the problem was the "DelayedAck" setting on the Exchange transport. The receiving server on the "other side" of the relay was taking too long to respond (more than 30 secs) and so the connection we were making timed out and SMTP conversation never completed. (se url I added in the question). The Exchange admin turned off DelayedAck on the ...


0

I would recommend setting up an additional mailbox with a rule that sends a message back stating that the address is out of date and that the new format should be used. If you can, make this generic - eg Our new address takes the format firstname.lastname@....Then assign all of the old email addresses to this mailbox.If you need to set up a custom reply for ...


0

Tips to make sure your mail doesn't go to spam: Make sure the plain text and html mail contain the same content Use DKIM Don't use "test" in the body/title (I've noticed from personal experience this does not help your spam score) To test, create a new gmail account and see if the message gets into the spambox Send real messages when testing, short ...


2

I discovered the following documented under ACL return codes: If the ACL for MAIL returns “discard”, all recipients are discarded, and no ACL is run for subsequent RCPT commands.


2

Basically they perform a query for MX record of the domain, following your question, for gmail.com: alphamikevictor@ges01:~ > nslookup -query=mx gmail.com Server: 194.179.1.100 Address: 194.179.1.100#53 Non-authoritative answer: gmail.com mail exchanger = 30 alt3.gmail-smtp-in.l.google.com. gmail.com mail exchanger = 40 ...


4

This problem can be tackled either by postfix or dovecot. In dovecot, you should set the LMTP service to reply with temporary reject 4XX (for your "special" domain) when postfix send email. In postfix, you need to configure postfix so it must defer the email if the recipient domain match your "special" domain. Option 1 isn't possible because -unlike ...


1

In general, I agree that #1 is probably the best solution, you can just discard any returns at the server. Install a .forward that sends messages to /dev/null. It's unlikely your bandwidth bill will hurt. To the wider discussion as to whether you should care about messages not being delivered, I don't really know anyone processing their own returns at any ...


3

Using option #1 is always the better solution. Think of it like paper mail; a functioning return address is mandatory. Email is only getting more restricted (DMARC, etc) due to spamers taking advantage of the open policy. It's really not that hard to automate dealing with replys you don't care about. But likely less than 10% of email servers are that ...


2

It seems that sometimes your application sends QUIT command before receiving reply for the "the final dot" of the message (250 for OK). It seems that the MTA (MS Exchange) ignores commands received before it sends the reply. Suggested Fixes: 1) Increase timeout for waiting for the reply, do not send QUIT before receiving it (even when PIPELINING extension ...


1

Your DNS server isn't authoritative for the ip address that your server is using, your ISP is authoritative for the ip address. You need your ISP to create the PTR record for your server in their Reverse Lookup zone.


0

Starting from the default configuration of MDaemon "POP before SMTP" you will be unable to receive mails from Office 365 disabling Account Verification settings. The best way (more secure) is to add all EOP IPs to the Trusted IPs list on MDaemon and then flag the options to disable account verification for trusted IPs only: EOP IPs are available at ...


0

IISRESET fixed this for me. I believe it is similar to the solution of resetting the SMTP service since this service depends on IIS. After it restarted the mail inside C:\inetpub\mailroot\Queue started to disappear!


2

Your DNAT rule will route all TCP traffic, received by your KVM host, on port 25, to KVM guest, no matter the interface or destination. You should add either interface or destination IP (or both) in that DNAT: iptables -t nat -A PREROUTING -i your_pub_if -p TCP --dport 25 -j DNAT --to-destination 192.168.122.201:25 or iptables -t nat -A PREROUTING -d ...


2

Did you look in /etc/hosts.deny ?


4

Long waiting for SMTP greeting How long do you wait to get SMTP greeting message? Exact duration in seconds may provide very important hint. AFAIR some servers issue SMTP greeting message after doing DNS lookups (IP address -> DNS name -> IP address). Typical DNS timeout is 75s. DNS is not the only suspect.


3

To test an ip in senderbase.org database you have to query their dns server for a txt record with a specially constructed domain name. It should be a sequence of bytes in reverse order representing an IPv4 address, encoded as decimal numbers, separated by dots with the suffix .query.senderbase.org. In your particular case: dig txt ...


2

Most setups include the domain in the username. (At least most of mine.) Try: echo -ne '\0username@domain.com\0password!'|base64 You could also try the PERL approach: perl -MMIME::Base64 -e 'print encode_base64("\000user\@domain.com\000password")'


2

You are mixing up smtpd_sasl and smtp_sasl, the first is for users authenticating on your server to submit emails for delivery, the latter is used when postfix does not deliver directly but also through a relay and postfix itself authenticates. Unfortunately, when connecting to my server with the username and password, I keep getting authentication ...


2

Use error:nouser 550 ... or error:5.1.1:550 ... as virtusertable value as suggested in virtusertable section of cf/README. info@example.com error:nouser 550 No such user here info@example.net error:5.1.1:550 No such user here RFC5321 describes (subtle) difference between the two error codes. 550 Requested action not taken: mailbox unavailable (e.g., ...


1

You've got Yourself a SSL certificate for your domain, I think you have exported certificate without private key. A ".cert" (or ".cer" or ".crt") file usually contains a single certificate, alone and without any wrapping (no private key, no password protection, just the certificate). Ex- Some CAs store the certificate's private key in a Private Key (.pvk) ...


1

Either you or the CA had to create a private/public key pair, before the CA signed the public key. You need the private key in order to decrypt the TLS traffic. If you created the key pair, then you have the private key file. If the CA created it, then they have it and you need to get it from them.



Top 50 recent answers are included