Tag Info

New answers tagged

3

It seems to be a CR+LF problem. Are you sure you send both control characters for end of lines in DATA? Not every MTA is sensitive to this, AFAIK. I don't think it's Postfix where the change should be made, but rather an original application (the one generating message). Try saving the message in a UNIX (LF-only) file, then run cat file |sendmail -i -t, ...


2

Sendemail is a Perl script, so it is easy to install anywhere there is Perl. The upstream URL is http://www.caspian.dotconf.net/menu/Software/SendEmail/, and they have prepacaged rpms. It has nothing to do with Postfix.


0

I assume that your 'sendEmail' is just Sendmail. Postfix has its own /usr/sbin/sendmail binary, which should work with pretty much any sendmail-compatible package. As I see, you want to forward your mail to a remote SMTP server. Zabbix natively supports SMTP connectivity, so why not use the built-in mechanism instead of calling the sendmail binary?


6

You should install mailx (yum install mailx). It looks like you can probably replace the script with this: #!/bin/sh echo "$3" | /bin/mailx \ -r zabbix@yourdomain.example \ -s "$2" \ -S smtp="yoursmtpserver.example:25" \ -S smtp-auth=login \ -S smtp-auth-user="your-user" \ -S smtp-auth-password="your-password" \ "$1" Consider using port 587 (submission) ...


1

The problem for either approaches is racing condition, i.e. your internet was working A or B acknowledge successful delivery to them but, when A or B trying to forward it to the internet, the connection was gone. Above scenario was possible because how email flows in postfix. Email from client ---> Received ---> Queued -> Sent Postfix in server ...


1

My apologies, but I think @wombies answer is wrong. The more logical answer (to what was probably meant) is this - You can allow SMTP communication on (almost) any port - the security does not come from the port, rather it comes from the access controls in the mail server to ensure only authenticated users can log in (be it by username/password or IP ...


1

Yes, there is. Depending on how much control you're giving the user over the content, it could range from "user can do mischief" to "you're a total open relay". As an example more at the "mischief" end of the spectrum, Redis has a fairly "permissive" command parser. It will ignore any commands it doesn't recognise, and then wait for a command it does. ...


0

Simple. Was looking for the same and it dawned on me. Use another smtp server to drop the eml files into its queue by telling it to send to a non existing smtp relay. Have a bat process or what have you pick them up deleting the failed delivery log and then process them and place into the working smtp servers pickup folder. Done.:)


1

You are overriding local_recipient_maps and unset it: local_recipient_maps = The default value is: local_recipient_maps = proxy:unix:passwd.byname $alias_maps The first part manages the local users, see: $ sudo postmap -q root proxy:unix:passwd.byname root:x:0:0:root:/root:/bin/bash Remove the line cited above to allow root local users recipient or ...


0

There is also a ruby gem called mailcatcher. You can read the emails directly in your browser through the integrated web interface, there's a screenshot from their homepage below.


0

You have to add some outer IPs to the dc_local_interfaces. Now exim hasn't legal way to communicate with other MTAs.


0

Me neither. Your server isn't delivering the email directly. It's passing it >> off to a smarthost for delivery So even if its a smart host delivery, you should not use a .local for helo. .local (.lan) are reserved names for Apple's mDNS. (zeroconf) In you case, you helo is not correct and should always be a resolvable hostname. If an MX ...


0

You'll need to do two things: configure the MTA on your webserver to relay mail to your mail server. Then, make sure your mail server is configured to allow your webserver to relay mail.


1

For people interessed in implementing a similar restriction: This works fine only if an extra file is created, for example /etc/postfix/ldap_virtual_domains_restrict_access.cf with following content bind = yes bind_dn = uid=postfix,ou=service,dc=example,dc=com bind_pw = xxxxxx server_host = ldap://127.0.0.1:389 search_base = ou=domain,dc=example,dc=com ...


1

Given the change in IP address, I'd say the most likely cause is that the reputation of the IP you're now using has been trashed by abuse in the past, and has been comprehensively blacklisted. I'd return it to wherever you got it from, as it is not fit for the purpose to which it is to be put. I'd suggest following the instructions in the e-mail, but in ...


0

Another solution is to tell postfix to not chroot smtp. That is the CentOS 6 default. Find the two lines in /etc/postfix/master.cf that start with smtp. Change the 5th column from the left to an n on each line. Then restart postfix. Of course, only do this if you are comfortable with postfix not running in a chroot'd environment.


4

Does it mean that someone is using my username (MYEMAIL@example.com) to send spam? YES This log line was the proof of it. Aug 4 11:09:17 mail postfix/smtpd[71597]: 1AE3B7EC3D: client=unknown[59.88.35.206], sasl_method=PLAIN, sasl_username=MYEMAIL@example.com As you have permit_sasl_authenticated in main.cf, then you authorize anyone who knows your ...


4

The log shows that someone has obtained the password for the mail account MYEMAIL@MYDOMAIN.COM and is using it to send SPAM through the server. The entry at time 11:09:17 shows a successful SASL authentication from IP address 59.88.35.206 with username MYEMAIL@MYDOMAIN.COM. The entry at 11:09:30 shows reception and queuing of a message with sender address ...


1

Limit access to a relay server that requires authentication and configure the auth data into your Jenkins instance.


1

Faced with same problem, tried many ways such as proposed by bshea, googling and trying. Base: Ubuntu 14.04.2 LTS, postgrey service starts, but doesn't appear in process list, i.e. service starts but quietly drops out. Found solution to change line in /etc/default/postgrey: Change this line: POSTGREY_OPTS="--inet=10023" To this ...



Top 50 recent answers are included