Tag Info

Hot answers tagged

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) ...


4

Anything using port 25 should be a verified SMTP program that you both know about - and have authorized. In your case, that is ONLY postfix. You should know that having an open relay can also cause you to send spam unwittingly. Check this out to determine which programs are using which ports: ...


3

You need to distinguish between local and remote ports, and between incoming and outgoing connections. Only one process can listen on local port 25 at a time, and hence only one program can accept incoming SMTP connections. If you try to start another one it will abort with a "port already in use" error. (I'm neglecting the possible exception of different ...


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, ...


3

You're not using the virtual_mailbox_base parameter like you're supposed to. A prefix that the virtual(8) delivery agent prepends to all pathname results from $virtual_mailbox_maps table lookups. This is a safety measure to ensure that an out of control map doesn't litter the file system with mailboxes. This is only a safety measure and isn't designed ...


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.


2

EDIT: reading that reject_unverified_sender could cause blacklisting i've removed id, and now the problem is back I think i've resolved this using this restrictions: smtpd_client_restrictions = permit_sasl_authenticated, permit_mynetworks #smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_non_fqdn_helo_hostname, ...


2

It is fairly common that mail servers require a valid e-mail address and reject invalid ones. noreply@example.com (Ryan) is not a valid e-mail address. The wikipedia entry has some useful pointers, as well as references to the relevant RFC's. In practice you use either a bare email address: noreply@example.com or whatever display name followed by a ...


1

For the sasl credentials in postfix where you have 'AK...:34.../...' you need to use SMTP username and password not an AWSAccessKeyId and AWSSecretKey. See "Obtaining Your Amazon SES SMTP Credentials" at http://docs.aws.amazon.com/ses/latest/DeveloperGuide/smtp-credentials.html


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

the answer for your question is yes only postfix or similar mail transfer agent MTA, should listen on port 25 which is dedicated port for incoming mail. Whenever your server being used to send out spam, it's not using your incoming port, it makes an outgoing connections.



Only top voted, non community-wiki answers of a minimum length are eligible