Tag Info

New answers tagged

-2

In my case I had to add a relayhost to my sendmail.cf file. I changed DS to DS relayhost.example.com and restarted sendmail.


0

Connection refused by [127.0.0.1] most likely means your local sendmail daemon is not up and running. Have you tries to start/restart it? service sendmail restart Does it start? Does it report any startup problems in the log file?


1

Finally I found a solution to filter outgoing spam with header_checks, though I do not know how effective and efficient it can be. Warning: this mitigation technique solution does not clean the infection. it is only useful when the attack sends spam by using the real domain name and faked user names or email accounts as senders (From:). when the infection ...


0

For fedora et al. journalctl _COMM=sendmail will show messages from sendmail. I was directed to this answer via a search. /var/log/mail only contains a 'statistics' file on Fedora. And all other mentioned directories are non-existent. journalctl is not intuitive enough if you don't know what parameter to use, ymmv. so I've posted this solution.


2

As I understand this, the problem is that your OpenSSL upgrade has made you intolerant of other's short DH key lengths, in order to protect the conversation against the Logjam attack. That's why increasing your DH key length (openssl dhparam ..., etc.) did nothing to help, whilst turning off TLS did. Obviously, what we'd all like is a flag to OpenSSL like ...


0

I do this in amavisd-new. i have amavis setup to scan all email regardless of where it came from (local or external). These types of spam messages have tons of bad headers witch can easily be caught in amavisd. You will have to disable a few header checks that a lot of mail clients (such as outlook) dont do correctly. This post may also be of use to you if ...


0

You can pipe output of multiple command into sendmail input. If the code below does not work for you the name (command) shell you use. ( # Command 1: "here document with headers and initial body lines cat << END To: toemail Subject: Test X-APP-VOLT: Yes Hope this works! Email Body line 1 END # Command 2: uuencode file cat file | uuencode filename ) ...


1

It is not sendmail.mc changes that you need to track, but sendmail.cf. Sendmail reads sendmail.cf. sendmail.mc is written in m4 and the output is sendmail.cf. So you need to produce it first and then kill -HUP the sendmail process ID. In Debian / Ubuntu systems running sendmailconfig is enough. In CentOS you need something like: cd /etc/mail /etc/mail/make ...


1

The UID and GID for the smmsp user have to be 51/51. My system was set to use 53/53. Why, I don't know, silly. To fix, I had to: change uid/gid in /etc/passwd & /etc/group. Delete old unused "ftp" group 51. chgrp smmsp /usr/sbin/sendmail.sendmail chmod g+s /usr/sbin/sendmail.sendmail chgrp smmsp /var/spool/clientmqueue restart sendmail ...


4

This is because after a recent update to openssl on CentOS 6, openssl-1.0.1e-30.el6.11.x86_64, programs using this library started to refuse connecting to servers vulnerable to Logjam TLS vulnerability. You need to configure sendmail to use stronger temporary Diffie–Hellman key — at least 1024 bit. It is not the same key that you use in your TLS ...


15

sendmail relies on the retry mechanisms in the SMTP protocol for reliability of delivery and does not need to depend on a clever server implementation. Which is why that doesn't exist as far as I know. When you restart sendmail simply aborts any incoming connections with a temporary error and sends a 421 response expecting the delivery to be retried later ...


3

If outgoing port 25 is blocked you cannot send email because you won't be able to connect to the remote MX. What I would do is setup in a different hosting provider a machine that is allowed to send email and set it up to relay from your VPS listening in a different port (e.g.: 1025), then you could configure your sendmail to forward all the emails to that ...


3

When postfix sends email to other server then postfix will act as SMTP client. Therefore the you need to refer to related document about SMTP client and TLS. To activate TLS encryption feature for postfix SMTP client, you need to put this line in main.cf smtp_tls_security_level = may It will put postfix SMTP client into Opportunistic-TLS-mode, i.e. SMTP ...


0

It seems you want to send normal, unencrypted email over a secure, encrypted / authenticated connection. I means: how can check if my smtp server is really talking to let say gmail via TLS channel? Here you say you want to verify that connections made to your MTA really are using your encrypted means of communication. That question has been answered ...


1

You can specify the path to php.ini passing option --php-ini FILENAME to the php executable. Try again giving the path to the php.ini used by the webserver.



Top 50 recent answers are included