Tag Info

New answers tagged

0

The exact message I got was: Insufficient system storage. The server response was: 4.3.1 Out of memory Stopping the service by right-clicking here and Stop then Start fixed it for me. This needs to be done on the IIS6 console which is still available on later editions as a separate component, but you won't find SMTP on the main IIS console for newer ...


-1

add permit_sasl_authenticated to smtpd_client_restrictions and see whether it works.


2

It's normal. If domain1.com and domain2.com are hosted at google, you can't write them in your server virtual_alias_domains. If you put them there in the virtual_alias_domains you tell your postfix he is responsible for this domains and then he see that he has to send any email that has destination domain1.com or domain2.com to catch@mail.mainserver.com ...


0

1) Do SendGrid, Mailjet, or Mandrill have a web client like Outlook.com where I can manually send and reply to customer e-mails? Replies from customers to your e-mail are send to the From and/or Reply-To: address which is typically your existing e-mail address for customer support, your sales office etc. 2) Should I stick with Outlook.com to ...


0

I uninstalled the SmtpReceiveAgent from the mailbox server and installed it on the Client Access Server instead and now the given "RemoteIdentityName" is correct


1

Your mynetworks directive is not valid. This setting controls which IP address ranges Postfix will allow relaying from. It should consist only of your internal servers and networks. It reads: mynetworks = all,localhost This is obviously not a list of IP addresses or CIDR ranges. Change it to reflect the actual addresses of the servers/networks which ...


2

So, As I understand here your email flowing diagram wsX.example.com --> smtp.mandrillapp.com --> external mailserver Now, spam checker on external mailserver usually use the last smtp server reputation to help determining if this email was spam or not. So, in this case the external mailserver just checks smtp.mandrillapp.com reputation ignore what ...


-1

As envelope sender or "sender" is the e-mail address referred to during an SMTP handshake according to RFC 5321 as a parameter of MAIL FROM: is passed. The term envelope is chosen based on the envelope. As in the letter post is just what it says on the cover, crucial for transport. The envelope sender matches the sender, the envelope To the receiver. As ...


1

From your headers it appears that your server uses IPv6 to send email to the gmail server. Received: from scalpello.info ([2607:5300:100:200::693]) and you have not configured a reverse DNS record for your IPv6 address. And there is no forward IPv6 record for mail.scalpello.info either. Additionally there's a lot of information in the Canonical ...


0

Turned out to be much simpler than I initially thought. Just ensure you have the following in your sendmail.cf: FEATURE(access_db, `hash -o -T<TMPF> /etc/mail/access' `relaytofulladdress') FEATURE(blacklist_recipients) Note the relaytofulladdress. Now you can selectively accept specific addresses and reject the rest in access: Connect:[127.0.0.1] ...


1

You can set your default relayhost using the relayhost configuration parameter, and then override this per sender using sender_dependent_relayhost_maps configuration parameter. Notice that the last one is a lookup table. Finally, you will need to set smtp_sasl_password_maps to configure per relayhost smtp credentials. Remember you probably need to enable ...


0

As previously discussed in the comments, I am writing this answer for others who may come across this problem. Adding a Windows Firewall rule to open port 25 will rectify this problem as the connection was rejecting the connection thus not allowing telnet to establish.


0

This is reasonable behavior from your mail server. You didn't give it any commands, so it closed the connection. If you want to talk to the server over telnet, try telling it the following after you connect: EHLO user where user is your username, and see if you get a set of status code 250 responses. This guide has other examples of how to talk to an ...


1

You have to configure so-called "reverse zone" for your domain name. Usually VPS control panel have DNS-related tools where you have to set PTR record pointing to your IP-address. While you do not set PTR record properly other mail servers will treat you as spammer and reject messages from you.


5

It appears that your test email to port25.com arrived through an IPv6 connection (or IPv6 source), so the SPF client looked up DNS AAAA RRs, instead of the A RRs normally used with IPv4 sources. This is how SPF is supposed to work (see RFC7208 Section 5.5), but as your domain lacks AAAA records, neither the "mx", nor the "a" mechanism matched and the SPF ...


1

Most likely cause is that your library is missing Authen::SASL::Perl::NTLM Please refer to https://bugzilla.mozilla.org/show_bug.cgi?id=625781 for details.


0

Most likely it's because of Yandex anti-spam policy. They assume that everyone without verified mobile number assigned to their mail account is spammer and should be barred from using SMTP.


1

From your comments "A middle machine that simply forwards an SMTP connection to some external MTA" and "My vps will listen on myip:25 and redirect it to external ip:2525" i assume this is what you need to do on your SMTP forwarding middle machine: iptables -t nat -A PREROUTING -p tcp --dport 25 -j DNAT --to-destination IP_OF_EXTERNAL_MTA:2525 iptables -t ...


3

Postfix can be easily configured to do that, but in other mail servers I am not sure. On my experience, most of them isn't really good in flexibility. An iptables-based solution were very simple, similar as we can read in this question as well: iptables -t nat -A OUTPUT -d ip.of.target.mx -p tcp --dport 25 -j DNAT --to-destination ip.of.target.mx:2525 ...


1

Looks like your situation looks similar to scenario in this article: postfix in dialup machine. Taken from that article, here some consideration. Disable spontaneous SMTP mail delivery (if using on-demand dialup IP only). With below parameter, postfix won't attempt to send email unless you run postqueue -f manually. Place this parameter in main.cf. More ...


2

chroot is defnitely the reason, however for my case, copying to /var/spool/postfix/etc did not work. So I just got rid of chroot and that works for me. n order to do that you will need to edit /etc/postfix/master.cf locate the following line: smtp inet n - - - - smtpd and modify it as follows: smtp inet n ...


0

Testing Haraka for a while now and I would recommend nothing else but this. Haraka is actually a framework where everything is a module. Very easy to use, source code is readable, available on github, no magic. DKIM/SPF support included over plugins. I don't have speed tests for now but so far I don't have any serious issues. I wrote a working production app ...


1

Run get-messagetracking on the Exchange server. Or have the admin of that system do it, if you can't. If it's Microsoft, open a ticket with them. SMTP 250 is a success code, so something in their system is dropping the ball, from your perspective. There's literally nothing you can do about it, from a technical perspective, if you don't manage the system ...


1

Postfix supports a subset of SMTPUTF8 since version 2.12: http://www.postfix.org/SMTPUTF8_README.html


3

If I'm understanding things correctly, mail for mysite.com is handled by Google Apps. Is this correct? If so, you should not have mysite.com in your mydestination list. Per postfix documentation, entries in that list will be delivered locally, not relayed out to other mail systems.



Top 50 recent answers are included