Tag Info

New answers tagged

3

Nagios only sends emails once a host or service has entered a 'hard' state. At a basic level to answer your question - a hard state is reached once the host or service has been checked a number of times specified by max_check_attempts. By default, this is 4. Info on soft/hard states: http://nagios.sourceforge.net/docs/3_0/statetypes.html Info on ...


2

I've been asked something vaguely similar, and have Get-MessageTrackingLog -Sender user@example.com -EventID "send" -start '3/1/15' -end '3/5/15' -resultsize unlimited | select-object sender | Group-Object pattern | select count The receive would be: Get-MessageTrackingLog -Recipients user@example.com -EventID "receive" -start '3/1/15' -end '3/5/15' ...


0

Yes, you are right, the MX record is responsible. It tells the mail server to which server he should transfer emails for a particular domain. example.com. 1800 MX mail.example.com. 10 In this case, the server that accepts mails for example.com is mail.example.com. You are free to choose any name, such as hermes.example.com or ...


1

From Wikipedia: A mail exchanger record (MX record) is a type of resource record in the Domain Name System that specifies a mail server responsible for accepting email. MX record just specifies a mail server. which in your case is mail.company.com. Whatever you define in your MX record must exist and resolve to a host which is your mail server. ...


4

Generally there are two types of bounces The bounces caused by directrejection of remote mail server when your postfix deliver the email. The bounces caused by remote server (next-hop server after your postfix) fails to deliver the message to final recipients. The first case was already covered by excellent answer by Esa Jokinen above. Your best bet is ...


6

As RFC3463 explains, status codes beginning with 5 are used for permanent failures and 4 for persistent transient failures. Instead of trying to parse several messages with different formats you could rely on server logs and try something like this: grep " dsn=5." /var/log/mail.log | grep -o -P " to=<(.+?)>" | sort | uniq -c This will find permanent ...


1

It seems you are not enabling SSL on the port 465 nor using different settings for your smtp submission server. This means you might have the same settings on port 465 than on port 25. Thunderbird is then trying to establish SMTPS connection but answered in plain text. Submission is a whole different setup from plain SMTP and certainly needs an ...


1

DKIM does not mitigate this kind of attacks. By checking the DKIM signature it is possible to detect changes to the message on the transport from the original sender to the receiver. It is not possible for the receiver to find out if the message should have a DKIM signature, because it does not know the selector to query the public key. I think you want SPF ...


2

The problem is that your SMART_HOST doesn't trust your server to send mail from an arbitrary sender to an arbitrary recipient, and thinks you're a common-or-garden relayer, so denies you. Either you control ssrs.reachmail.net, in which case you need to tell it that your server is authorized to send mail by listing its IP address in (eg) /etc/mail/access and ...


0

Blacklisting and Rate-limiting do work on IP-basis on most cases. Two criteria (of many others) for being blacklisted or - in general - get a bad reputation are: Amount of emails sent Probability that these emails are spam Mail introspection (analysis of the body) no SPF record for the domain used no DKIM used by the mailserver The latter two are very ...


1

Outlook's built-in encryption uses a simple public/private key exchange scheme. In theory, all you should need to decrypt an email encrypted with Outlook's built-in encryption would be the digital ID (the sender will require your public key to encrypt, you will require the private key to decrypt), and any RFC5652-compliant email client, but as that KB ...


0

Yes, you can. To summrize the steps, you need to: Create a contact inside Exchange. Mail-Enable the contact you just created. Enable mail forward from the users to the newly created contact. The steps are well documented in this Microsoft Knowledge Base: http://support.microsoft.com/kb/281926 Note that there might be some step variations, but the idea ...


0

It may take more than one step to fix this issue Take the step mentioned earlier. Log into your google email account and then go to this link: https://www.google.com/settings/security/lesssecureapps and set "Access for less secure apps" to ON. Test to see if your issue is resolved. If it isn't resolved, as it wasn't for me, continue to Step #2. Go to ...


1

I have found the solution to my own question. Below are the lines 507-513 from program/steps/mail/sendmail.inc. // encoding subject header with mb_encode provides better results with asian characters if (function_exists('mb_encode_mimeheader')) { mb_internal_encoding($message_charset); $headers['Subject'] = mb_encode_mimeheader($headers['Subject'], ...


3

I believe what you are encountering is a Backscatter email, check wikipedia for detailed description. In brief, backscatter happens when someone sends out spam using forged addresses, in this case yours, and the bounce messages send back to your address. Many mail servers resolve this by tagging every email they send out, using a technique called Bounce ...


1

Say, the normal domain is example.com and example.net is the alias which should redirect. In DNS you have to specify the responsible mail server using the MX record, the MX for example.net would be mail.example.com are whatever the MX record for example.com is. Then all mails for example.net get delivered to the same mailserver as for example.com. The ...


1

Your concern was valid because the existence of SPF checker. If you forward an email comes from a domain with proper SPF record your IP doesn't listed in their sender SPF record the receiver use SPF record as a factor to identifying spam then yes, you may have error message SPF fail and the email end up in Spam Folder. SPF community acknowledge this ...


1

You must include the signing table via: refile:/etc/opendkim/SigningTable Refile means that regular expressions get evaluated. When it is included via file:/... regular expressions are not evaluated.


2

Snippet from comment It is a CentOS 5.11 server, there is no newer postfix version available in our repos (CentOS standard repos, epel, FAN, graphviz and remi). So you are stuck in unsupported version of postfix 2.3.3. Well, I understand your case, it's very sad tough :(. Postfix version 2.3.3 was released in August 2006. Although the CentOS team was ...


-2

FYI The difficulty with /24 blacklists is NOT mistakenly punishing innocent senders who happen to have IP allocation separate from the spammers, but which shares the same /24 block. And that is precisely why ivmSIP/24 is so new. For this very reason, we were reluctant to get into this /24 business. Until one day, several “light bulbs” went off ...


2

Finally got my setup to work with postfix multiple instances masegaloeh mentioned. I tried to use exim4, but apt-get install exim4 automatically uninstalled postfix, without even a prompt! Anyways, here is how I got it to work: #Adds some lines to main.cf enabling multiple instance postmulti -e init #Creates a new instance at the directory ...


0

My understanding is that Google Apps is not for transactional mail, but I could be wrong. What may work better is a smart relay that makes use of an API, as this is typically lighter on resources than using a local MTA. Mandrill by Mailchimp is popular, but there is also Amazon SES, Rackspace Mailgun, and others. You can find WordPress plugins for these and ...


0

If it's not a DNS problem, the blacklisted IP may be a 3rd party IP and not yours. Check your routing configuration to see if any packets are redirected via another than default normal path. They may explain why your original IP is clean but mails are still blocked with blacklisted IP.


0

Use this tool http://mxtoolbox.com/supertool.aspx to make sure your server is setup properly. Likely you just missed a DNS record. "If you are on RATS-Dyna, your reverse DNS is probably not set up correctly." http://spamrats.com/removal.php


1

I installed Declude (which is free) and Message Sniffer (which isn't) and over the past 4 days I've seen one spam message come in my test email account, as opposed to the dozens it was getting per day. As far as I can tell, we haven't had good email filtered out. Spamassassin would probably also be a good solution although I didn't have any luck with it ...


7

This quesiton is so broken that I'm going to break with ServerFault protocol here and respond to the question with some of my own questions to point out 1) How it could be improved, and 2) why control panels and web host helper applications are bad. Title: Individual accounts being spammed on server, even though DNS not hosted What do you mean "DNS not ...


0

This is not possible using Exchange transport rules. You will need a third party product. I use Exclaimer Signature Manager (manages Outlook signatures) and Exclaimer Mail Disclaimers (adds signatures at the transport level). I highly recommend them both.


1

I contacted my hosting provider to help me resolve the issue. For those who are seeking answer for similar issue, I suggest to contact their hosting provider. In my case, this was the reply from hostgator (my hosting provider). "The mails were being blocked due to Commtouch blacklisting as the mail patterns were considered suspcious by Commtouch. We ...


2

I believe your issue here is SPF. You need to designate your hosting IP as a permitted sender of email for your domain when you have SPF on. You would do this from your domain registrar. Create a new TXT record to add your IP as a permitted sender. TXT mydomain.com "v=spf1 ip4:192.168.0.x mx -all" Where the 192.168.0.x is replaced with your hosting IP. ...


0

That log is controlled with config/main.inc.php directive: // Log sent messages to <log_dir>/sendmail or to syslog $rcmail_config['smtp_log'] = true;


1

For postfix version 2.6 and later, you can use postmulti shipped by postfix. Excerpt from man 1 postmulti: The postmulti(1) command allows a Postfix administrator to manage multiple Postfix instances on a single host. postmulti(1) implements two fundamental modes of operation. In iterator mode, it executes the same command for multiple Postfix ...


2

This error message: Feb 21 15:52:46 server dovecot: auth-worker(3609): Error: pam(test,<myip>): pam_authenticate() failed: Authentication failure can be caused by several reasons such as: User didn't exist Incorrect password Based on above useradd command useradd --shell /bin/bash --create-home --password <password> <username> I ...


2

Firstly, so long as you have OpenDKIM specified in non_smptd_milters as well as smptd_milters in Postfix's main.cf, outgoing mail sent through PHP mail() should still be signed. The Received headers are not signed by default, and nothing much else should have been rewritten by cleanup. If you want an alternative method, you could DKIM sign using Amavis and ...


0

Setup a relay host to your isp smtp server, in: /etc/postfix/main.conf then reload: sudo service postfix reload


3

Form my understanding I could use PHP mail() function or even Swift Mailer's Swift_SendmailTransport class and deliver the messages directly to Postfix queue. That's true But if so, how can we ensure DKIM? Will changing the "FROM" header to the email accounts on the local server be enough? You doesn't specify your DKIM signer, so I assume that you ...


1

Your Outlook mail client, as shown in your image: is not set to use SASL authentication. Outlook's "Outgoing Server" dialogue may not be self-explanatory: "Log on to incoming mail server before sending mail" means do not SASL authenticate, but POP first. However, your Postfix settings require SASL: smtpd_client_restrictions = permit_sasl_authenticated ...


0

What you need to do is first setup aliasing that address. You can do this with the aliases plugin (or the plugin you listed in your question). See the documentation here: http://haraka.github.io/manual/plugins/aliases.html (and add the plugin to config/plugins). Secondly you need to set things up to relay everything outbound, since you want everything to go ...


1

The first thing I would do before proceeding further would be to test port 25 end to end with a tool like netcat. The tool comes standard with most linux distros. For example on CentOS I would stop postfix to release port 25. Then I would start netcat like this: # nc -l 25 Then on the remote client I would start it like this: # nc {ip of remote ...


3

According to the nmap docs: filtered Nmap cannot determine whether the port is open because packet filtering prevents its probes from reaching the port. The filtering could be from a dedicated firewall device, router rules, or host-based firewall software. These ports frustrate attackers because they provide so little information. Sometimes they respond ...


0

Use spamhole: https://sourceforge.net/projects/spamhole/ From the website: spamhole is a fake sopen SMTP relay, intended to stop (some) spam by convincing spammers that it is delivering spam messages for them, when in fact it is not.


1

The problem was the line -o smtpd_sender_login_maps=hash:/etc/postfix/virtual in master.cf. I forgot to look there, because this exact configuration was running fine for months on another my server.


0

This could be unrelated but I'm going to post it here because I had a hard time finding the answer to my question. I was able to get outbound email working from a vagrant virtual box by editing my /etc/resolv.conf to use Google's nameserver rather than the 10.0.x.x IP it was set to: sudo vi /etc/resolv.conf Change the nameserver IP: nameserver 8.8.8.8 ...


0

The solution is buried in the comments and not explained well. Here is the full solution from Micheal Hampton: Setup a CNAME from www.flyh2.com to flyh2.elasticbeanstalk.com. When using www. this will redirect web requests to the Amazon web server. Setup an A Record from flyh2.com to 174.129.25.170. That IP has a web server that redirects naked domains to ...


3

Most MTAs will go to nearly any end to avoid dropping a message on the floor. Typically a bounce will be generated (either by the receiving MTA, or, for better-behaved MTAs, the receiving MTA will refuse with a 5xx fatal error code and the sending MTA will convert the outbound message into a bounce). If that bounce is itself undeliverable, the MTA holding ...


2

Choose a domain name for your mail server. The MX record should point to the FQDN (Fully Qualified Dommain Name) of the mail server, shuch as smtp.example.com. All domains should use this FQDN in their MX. Use a priority higher than 1 so that you can add servers with both higher and lower priority. Something like: example.com. mx 10 ...


1

An MX record for a domain can "point" to any host, so having them all "point" to the same server is fine. As for the preference, you can set it to whatever you like. If you add servers in the future you can add them with a higher or lower preference, dependent upon your needs.


6

There is no connection between them, as SPF records are set per domain, not per sending host. If several different domains each send email coming only from one host, say mail.example.com, then each should have an SPF record like a:mail.example.com -all. Note that each makes no reference to the other domains sending from mail.example.com. It is only ...


1

I'm reporting back here in case anyone else encounters this. It turned out that mike@foobar.com actually had used Rackspace (via a reseller) before he switched email services over to Microsoft's Hosted Exchange. The Rackspace reseller with whom Mike was dealing apparently never completely deleted Mike's account from their Control Panel. So when my ...


0

RFC 3848 transmission types included commands such as EHLO and a few others that you might see today. ESMTPA introduced EHLO as a command that it was an SMTP server that could handle additional commands compared to standard SMTP, this command is now required per RFC 5321. The ESMTP format was restated in RFC 2821 (superseding RFC 821) and updated to the ...


4

Based upon the error message it would appear that you need to configure reverse DNS lookups for the host. This is normally done with a PTR record. For example you might have a host mail.example.com mail.example.com IN A 192.0.2.1 and a PTR record 1.2.0.192.in-addr.arpa. IN PTR mail.example.com



Top 50 recent answers are included