Hot answers tagged smtp
7
There are several choices of minimal, relay-only mail transfer agents (MTAs, or "mail servers"), some of which have been mentioned in other answers:
esmtp http://esmtp.sourceforge.net/
nullmailer http://untroubled.org/nullmailer/ (my personal favourite)
sSMTP http://packages.debian.org/source/sid/ssmtp (development has stopped, i think)
For either of ...
7
I would suggest Postfix, especially on Debian where postfix is split into several packages. You can choose and trim features as necessary.
Postfix is powerful, modular, highly secure, lightweight, extensible and easy to configure.
On my VPS with 256MB of RAM, the postfix daemons collectively use about 6.5MB of resident memory which includes TLS and PCRE ...
5
RFC 5321 defines this in section 3.2:
So basically you can send
EHLO which should be answered by the mailserver with a list of extended capabilities, including valid encryption algorithms.
Should the server not understand EHLO, it is propably an older system, that just accepts HELO. I did not read any further than this, whether the old systems can be asked ...
5
While it isn't SSH's pubkey authentication (which is something that only exists in the SSH protocol, not SMTP), you could set up TLS Client certificates. This will require a valid SSL certificate on the client side.
Also, if you must use SSH's pubkeys, you could simply allow all mail connections from localhost on your personal SMTP server, and set up an ...
5
smtpd is executed by Postfix to handle incoming mail (either locally, or remotely). If you have 100 running at a time, I suggest your server is handling a lot of mail. If you don't believe you're generating that much mail, it's possible your server is either receiving a lot of mail it bounces, or it's sending a lot of mail you're not aware of.
The default ...
4
Honestly, this sounds like a sendmail.cf problem, as if it's not configured for non-local email, or it's misconfigured.
The file /var/log/maillog.3 is almost certainly an "old" log file, and therefore, nothing new will get written to it. You didn't mention what Linux distro, BSD or Unix you're using, but the current log file, the one sendmail currently ...
4
IMHO, the easiest way to do this is to install postfix (if debconf asks you questions, pick "internet site"), then run these commands:
postconf -e relayhost=other.mailserver.com
postconf -e mailname=my.domainname.com
As long as the SMTP server specified in relayhost doesn't require authentication, allows you to relay or is a valid destination for the ...
4
In the Unix/Linux world you won't find tools that "do everything", as that violates the single responsibility principle. However, to "orchestrate" all the tools together in a single configuration panel, there are projects like Webmin that provide this functionality. For this specific task of mail/groupware, I have the following suggestion.
You could look at ...
3
The error you quoted from the error log indicates that Postfix is unable to connect to the MySQL server on 127.0.0.1. This is because you told the MySQL server not to listen on 127.0.0.1. The high process count is probably due to repeated failed attempts to query MySQL for virtual-mailbox lookups.
You need to tell Postfix to try to connect to the MySQL ...
3
127.0.0.1 is not the "outside world", it is looking around inside the house.
Check your firewall configuration (iptables in Linux today), most of them shouldn't be accessible from the ouside.
Don't run services you don't need. Uninstall all not required software.
Change passwords to be stronger. Check your usage of the system, don't go chasing any ...
3
What you're actually doing is asking how to set the ports used Postfix so that it is also listening on tcp/587, which is the "submission" port.
I have the following in my /etc/postfix/master.cf:
submission inet n - n - - smtpd
-o smtpd_tls_security_level=encrypt
-o smtpd_sasl_auth_enable=yes
-o ...
3
Check out this tool Fail2Ban, it scans log files for malicious activity and fires off an event. There is bottled event handlers like creating a firewall to reject the offending IP, or you can make your own custom event handlers.
3
You could switch to esmtp, there it is pretty trivial:
identity myself@gmail.com
hostname smtp.googlemail.com:25
username "myself@gmail.com"
password "secret"
starttls enabled
default
identity mysecondaccount@gmail.com
hostname smtp.googlemail.com:25
username "mysecondaccount@gmail.com"
...
3
For postfix:
Add the IP for your external mail-relay to /etc/hosts and add an alias mailrelay to it.
Modify the postfix configuration:
relayhost = [mailrelay]
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/smtp_auth
smtp_sasl_security_options = noanonymous
Edit /etc/postfix/smtp_auth
mailrelay login:password
Convert into ...
3
In order to forward root's e-mails to another e-mail address, you could change the line related to root in the file /etc/aliases. For instance:
root: myname@myemail.com
To forward e-mails of a UNIX user (let say myuser) to another e-mail address (myname@myemail.com), had the file .forward in the home folder of myuser. This file should contain one line ...
2
I am not sure, but a quick search turned up this which says (emphasis mine):
To be able to send to (or receive from) those MTAs, the ruleset
try_tls (srv_features) can be used that work together with the access
map. Entries for the access map must be tagged with Try_TLS
(Srv_Features) and refer to the hostname or IP address of the
connecting ...
2
My favorite is the email (github) client. It's really simple, no complex configuration needed, no dependencies needed. And you can specify smtp-server argument via command line, which means it's more suitable for scripting. The only pity is that most linux distributions does not contains this tool, so you need to compile it yourself.
Quotes from email ...
2
I found much simpler the use of sSMTP
In debian systems:
apt-get install ssmtp
Then edit the configuration file in /etc/ssmtp/ssmtp.conf
A sample configuration to use your gmail for sending e-mails:
# root is the person who gets all mail for userids < 1000
root=your@email.com
# Here is the gmail configuration (or change it to your private smtp ...
2
The headers are initially generated by the Mail User Agent (MUA, i.e., your mail client) and contain very little information. It depends on the MUA being used, but will usually include at a minimum From, To, Subject and Date. Using the Unix mail command you can specify additional headers to be added with the -a flag.
Example:
mail -a "X-foo: bar" ...
1
The configuration file is OK except you're missing a reference to the aliases table in your accept rules:
accept from any for domain mydomain.com alias <aliases> deliver to mbox
You can run with smtpd -dv -T smtp to get incoming session tracing and see where it fails ;-)
1
You've given the answer in your question. When you use the EHLO command, the server will respond with all the SMTP extensions that it supports. So the server you are connecting to supports these extensions:
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE
250-DSN
250-ETRN
250-STARTTLS
250-DELIVERBY
250 HELP
The only extension related to ...
1
Set up a local exim SMTP server by following the instructions on this page, but choose the "mail sent by smarthost; no local mail" option from the first screen of the Exim configuration. This will set up an SMTP server on your box that can receive mail from the "mail" or "mailx" commands and will forward all messages to the smarthost (a Gmail server in your ...
1
I prefer Aaron's answer but just in case someone else stumbles across this, there's an alternate method of doing this.
Locate the CLIENT_OPTIONS part of a sendmail.mc file and add M=S.
So for example, if you had something like:
CLIENT_OPTIONS(`Family=inet, Addr=1.2.3.4’)dnl
You could change it to:
CLIENT_OPTIONS(`Family=inet, M=S, Addr=1.2.3.4’)dnl
...
1
Nothing prevents networked application to use ssh keys for authentication/encryption, except these applications have to be written to support this (i.e. by using libssh). You don't say what mail user agent you use, nor what SMTP server it connects to, but it is not very likely they support ssh natively.
But of course, you can use a normal ssh connection to ...
1
You will need to have Postfix relay the messages to the remote server. This will require a change to the Postfix configuration. You'll need to enable Postfix's SASL authentication to handle the authentication. Once configured, you can use your local SMTP server as you did with local addresses, and the local server will relay them on the the remote server.
1
Do you need to use exim4?
I recommend using postfix. This guide helps you do this with encrypted password
http://www.marksanborn.net/linux/send-mail-postfix-through-gmails-smtp-on-a-ubuntu-lts-server/
1
Based on the title, I think the bounce_size_limit option might help. Try setting it to 0.
Based on the question body, I think you need something else.
Is this what's happening?
1. hMail ---> Postfix (OK)
2. Postfix ---> BlackBerry (Fails)
3. Postfix ---> hMail (OK)
4. hMail ---> Postfix (loop)
etc.
If so, you could append a header to the ...
1
I'm assuming that you are using a Debian based derivative given that you mentioned apt-get in your question.
This can be done fairly simply using the exim4 mail package. A simple
apt-get install exim4 exim4-config
Will install everything that you need to send mail via smtp. Note you need to be root or use sudo for the apt-get command to work.
During ...
1
You may find sSMTP suitable for your needs. Read this article on it and its limitations.
Honestly though, I wouldn't be too stressed about installing postfix or exim, even if it is only for sending emails. Just stay the hell away from sendmail. :-)
Only top voted, non community-wiki answers of a minimum length are eligible
