Tag Info

New answers tagged

0

I know it's not e-mail only, but Microsoft's Exchange Online plans (basically hosted Exchange direct from MS) may be worth some serious consideration. The price means that it's not necessarily a concern that you have other bells and whistles. Fully supports IMAP (no need to use Outlook if you don't want to), plus ActiveSync push to mobile devices. Regarding ...


0

I've changed my blockreportlist.txt to: *@mydomain.com Now, It works.


0

Is there any chance your messages are queueing up and then going out in bursts? We had that problem with some of our production servers; when a huge queue of emails goes out at once, some of the spam filters will detect that as problematic behavior. I assume you're using Spamhaus to check their listings: we found ourselves on their lists whenever there ...


0

If you place another gateway device between your Ironport and the Internet, then your only option is to disable SenderBase and any other IP-based authorisation in your Incoming Policy definitions in the HAT. You cannot tell the Ironport to obtain the previous-hop IP address from any other method than the incoing TCP connection itself (for obvious reasons - ...


3

If your email is S/MIME signed, you cannot add a disclaimer after signing the message. Adding a disclaimer after signing the message either invalidates the signature (i.e., the signature no longer validates) or the message is no longer a valid S/MIME message. One possible solution would be that the disclaimer service extracts the signed message and adds it ...


0

I think you can use auth-passwdfile.conf.ext with users file. passdb { driver = passwd-file args = scheme=CRYPT username_format=%u /my/file/path/dovecot.users } Syntax: user@domain.tld:{passwdtype}password:uid:gid::::


0

We have a similar setup. In our case Logwatch, Fail2Ban, our Rails apps all send email seamlessly. The short answer is use Postfix to relay your emails. The long answer: (using Sendgrid as an example) 1) Sign up an account from email providers like Sendgrid, Mailgun, etc. All of them have free plans and paid plans. 2) Setup the /etc/postfix/main.cf. The ...


0

You can install postfix with apt-get install postfix and select 'Internet Site' in configuration dialog. Then create one mail alias in /etc/aliases for root pointing to your gmail address: root: youraddress@gmail.com Run newaliases and you'll start receiving mails from daemons like logwatch, fail2ban etc in your gmail.


0

One option is save it on HOLD queue. On your smtpd_recipient_restriction, insert two lines. check_sender_access hash:/etc/postfix/supportteam, hash:/etc/postfix/latepayingcustomers_outgoing check_recipient_access hash:/etc/postfix/supportteam, hash:/etc/postfix/latepayingcustomers_incoming Content of /etc/postfix/latepayingcustomers_outgoing example.org ...


2

A domain name, say example.com, is registered to company ONE. The Address record of the DNS for that domain has been changed, to map example.com with an IP of a server of company TWO. It doesn't matter to whom a domain name is registered. The registrant is simply responsible (among other matters) for setting the nameservers, the machine(s) which are ...


1

Fixed the problem by going here: https://accounts.google.com/DisplayUnlockCaptcha


0

If autodiscover works correctly then I find just not creating any accounts and letting the wizard take care of it works 95% in my environment. The wizard is more user friendly than 07/10 and should prompt for name, primary email address and password, then autoconfig and launch ok. This is with Office 365 / Outlook 2013 32 bit, both c2r and msi on RDP ...


0

After following the instructions here, as mentioned above, I changed my autoconfig server template under System Settings > Server Templates (and under the dropdown menu "Edit template section") > Mail client auto-configuration. In the section Thunderbird auto-configuration XML, under the heading outgoingServer, I changed the port from $SMTP_PORT to ...


0

Whatever service you configured to run on port 10024 is not running. Inspect your /etc/postfix/master.cf to find out what service it is, if you don't already know, and then start the service.


1

Yes, if the applications are hard-coded to connect by name, you can do something like: emailserver IN A 192.168.0.5 oldserver1 IN CNAME emailserver oldserver2 IN CNAME emailserver and that way you keep one live emailserver name with one address (for ease of management in future), and redirect the old servers to point to it. Or ...


1

An iptables PREROUTING rule will not show up in a standard netstat listing, as in NAT mode, it operates at the kernel level, therefore does not register as a process that's listening. The best way for you to diagnose this is to monitor all traffic on that machine on port 25 to see how it behaves with the rules you have in place; tcpdump -nn -i eth0 port 25 ...


0

This most probably is not a replication issue. Either the index of your inbox on one server is corrupt, or you have two folders named inbox in that database, and one server shows the "right" one, and the other the "wrong" one. You can rebuild the index of inbox using updall with -R (rebuild) and -T (define view) options: lo updall mail\db.nsf -R -T ($Inbox) ...


3

As has been noted, your domain registrar likely can forward email for you. If you are sending email from your domain, you will want some basic email setup including an MX. Adding SPF, and DKIM signatures may increase your delivery success. You will want your MX to accept (and possibly forward) email sent to the sending address, as well as mail sent to ...


2

Quite a few domain name registrars offer e-mail forwarding as a free feature. Typically the interface for managing regular DNS records is used to create a custom record type indicating an email (or URL) forward. In the background that forces the domain registrar's mailservers as the MX servers for the domain, but since you don't want to run your own ...


3

Whenever your restriction can't be applied globally to all cases, you can use Postfix restriction classes. The idea is excluding some domains to separate restrictions. I reorder your current configuration on following principles "lightweight checks should executed before heavy ones". So, I suggest the configuration became smtpd_recipient_restrictions = ...


1

Just sort your smtpd_recipient_restrictions accordingly. This list is processed from front to back. Some filters can return a reject or nothing (blacklists, spf; either it's a malicious sender or we don't know) or a permit (SASL, Networks, if they don't match, continue) In your case it would be: smtpd_recipient_restrictions = permit_mynetworks ...


3

Better is to create a virtual alias file: In /etc/postfix/main.cf: virtual_alias_maps = pcre:/etc/postfix/virtual In /etc/postfix/virtual: /.*@.*/ root You can replace root with whichever user you'd like to receive all the outgoing e-mail. This pattern can be tweaked if you want local mail to be delivered normally (without redirection): ...


0

If the example.com and mail.example.com DNS records point to the same IP address (which is generally the case with shared hosting setups), then yes, it will work without the mail subdomain. To check, run the following commands: nslookup mail.example.com nslookup example.com However, you may want to take advantage of SSL encryption on the connections, ...


1

Your /etc/hosts file should have a separate line defining the system's IP and fully-qualified domain name and the short name on the same line. Remove the "mail.website1.com" and "mail" from the line with 127.0.0.1. 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 ...


0

You have to use doveadm utility to add manually copied messages to the maildir index: doveadm [-Dv] index [-S socket_path] -u user [-q] [-n max_recent] mailbox Further reading can be found here: http://wiki2.dovecot.org/Tools/Doveadm/Index


1

If your mail servers are down, senders will keep trying for 3 to 5 days before returning the mail to sender. This includes most mailing lists. While this value is customizable, I've never seen any mail server return mail for a temporary failure like that in less than 24 hours. Sendmail and Postfix both default to 5 days, exim (which is often used by cheap ...


3

Your understanding of how SMTP works will help you understand what's going on here. The website is submitting the forms to an SMTP server. That SMTP server is returning the error messages you're seeing. Don't think about MX records and DNS-- you're concerned with the SMTP server that the form processing script is using. MX records and DNS are irrelevant at ...


0

Your provided information is very lean, not enough to accurately debug the problem, but I can make a few educated guesses and give you some places to look. Are you sure that the failed attemp was connecting to smtp.sendgrid.com:587? It's acting like your exim connected to port 25, and didn't use a user/pass to try to send, which sendgrid rejected. It very ...


1

And added to that we see that in the the non-active server in the cluster, the inbox is not empty. Basically, that sounds like replication isn't working between your two Domino servers. Sure, the Notes Inbox view can get corrupted (as can any view or database), and there are tools and commands to repair corrupt databases, such as fixup and updall, but ...


1

I think that contactgroups must be contact_groups


0

Redmine offers you a solution which should work for your need: http://www.redmine.org/projects/redmine/wiki/RedmineReceivingEmails


1

You can use a procmail and a postfix.


1

Turns out there doesn't seem to be anything wrong with my configuration. What's happening is that my messages are being processed by mailman correctly, and being relayed out to the list. There are a couple of receivers however which (for whatever reason is unique to them) reject the message. Because I have actually correctly configured SPF, I'm seeing the ...


4

E-Mail security sucks. So in the end, you're probably going to be faced with a decision where all your options are terrible, and break different things for different reasons. As for SPF specifically, a mailing list will cause a failure if it forwards a message, without rewriting the headers. A list can configure itself to work however it pleases, so there ...


0

You didn't setup virtual domains or users. Unless you want that explicitly, you probably forgot it.


1

I've not looked at the DKIM part. Concerning the SPF record I see the following used in most example: v=spf1 mx -all This is documented here: http://www.openspf.org/SPF_Record_Syntax However "+mx" should also be correct according to RFC 7208 (Thanks Chris for pointing this out). Maybe it is stil worth a try... I really don't know what to suggest ...


0

It can be done by using Virtual Channel. There is a free tool that's called Remote Executer for Terminal Server that can do the trick. It can forward commamd line, internet link (http, ftp), mailto to the client side.


0

This script works for restarting the service. I'm having the same issue with the transport service. I have to do this every hour now. sc stop MSExchangeTransport sc stop MSExchangeEdgeSync timeout /t 10 sc start MSExchangeEdgeSync sc start MSExchangeTransport


0

PHPList will work but if you don't want to use existing infrastructure, which I'd recommend to keep any possibilities of being flagged as a spam server, you can use a commercial mailing service such as mailjet.com I personally try to separate mass mailing from my production infrastructure.


2

I am using Ubuntu Server 12.04 and I tried the above solutions. However, I found that simplest and easiest way was in 10-auth.conf to set auth_username_format = %n I use PAM for the authentication which is the default in Ubuntu 12.04.


0

According to the not accepted answers to a similar question it depends on which version of cron you're running. Check man 5 crontab if setting the CONTENT_TYPE and/or CONTENT_TRANSFER_ENCODING variables is supported to change from the default plain text. AFAIK in cronie on RHEL 6 it is and if the output from script is HTML formatted the following should ...


1

The auth_http does two main things: It authenticates users (including various options to effectively delay users on failed authentication). And it determines which backend to use (and which username and password to use in backend authentication, if at all). While in some cases authentication can be handled directly by a backend, it's not something always ...


1

Your first example sends both stderr and stdout to the file (2>&1) ; the MAILTO variable set in the cron will capture any output that is not redirected, and this combined with directing the output to the file means that no output is available for the cron to email. I'd suggest using tee to append the output to the file as well as sending it to stdout; ...


4

No, this is not necessary. Only if you send bulk mail, but then you're better off handing that to a service provider for sending it out, as they have far more experience in making sure that your e-mail reaches the target mailboxes. Also, just changing domain/subdomain does usually not work, as BAN's are largely based on IP addresses as well, or only on ...


5

If DNS resolution simply times out and a response never comes back from the DNS server at all, or the return is SERVFAIL, then the message is supposed to be queued and tried again later. If DNS resolution returns NXDOMAIN (the name doesn't exist) then the message is supposed to be returned immediately. See RFC 5321, section 5.1: The lookup first ...


2

A quick & dirty way might be to check if they have an SMTP server running by banner grabbing or nmap'ing to see if the port open - but that's a guaranteed to prove that they still run in the same way as they did before.


0

After several hours of working in circles I stumbled upon the answer that worked for me. It didn't matter how many permutations of dpkg-reconfigure exim4-config I tried, adding in entries for dc_relay_nets or dc_relay_domains or direct edits of exim4-local-domains.txt. It turns out there is a file named exim4-relay-mail-from-this-list-of-ip-addresses.txt in ...


6

We mitigated the same issue by using an outside vendor as our e-mail gateway (in our case, Exchange Online Protection but there's many other comparable services). We then configured all our e-mail sending services to use that as the smarthost. Now, all our outgoing messages are associated with the reputation of the external e-mail gateway. Because of that, ...


15

I'm looking forward to seeing other answers to this question, but my feeling is that if you're catching compromised mail accounts after only 40 spams have got through, you're doing really well. I'm not sure I could detect similar abuse so quickly, and the prospect worries me. But I'm appalled that seven sets of credentials were stolen in the past week ...


-1

I am pretty sure you need only adjust the mynetworks key in your postfix config. Change it to use the catch all addresses instead of only the local host ones. So: mynetworks = 0.0.0.0/32 [::]/128



Top 50 recent answers are included