New answers tagged

1

In some cases, the 'at' command is missing entirely and the package needs to be installed. Look for the at.x86_64 or at_i386, at_i486, at_i586 packages. Both OEL71 and CentOS can add it with: yum -y install e.g.: yum -y install at.x86_64 If you try copying the commands from another host, you will get pam authentication errors when run by anything ...


2

As @infixed says, the X-Spam-Status header is continued across multiple lines. If you have procmail installed, you can use its formail utility to concatenate continued headers. From man formail: -c      Concatenate continued fields in the header. Might be convenient when postprocessing mail with standard (line oriented) text ...


3

It sounds like that X-Spam-Status line is a 'continued' RFC822 header that spans multiple lines. A header starts with non-whitespace in the first character of a line. A non-blank line with whitespace at the beginning is a continuation of the previous line, and a blank line ends the headers. If you want to filter out a particular header, you are going to ...


1

It seems the error was due to the ipv6 address in /etc/resolv.conf. I removed it and it now works.


0

You may use the table 'generic', provided by postfix to re-write both envolope (smtp) -addresses and mail header addresses. Do that by a) put the address-rewrite rule in a file called /etc/postfix/generic root@your-domain.com someone@anotherdomain.com root someone@anotherdomain.com Postfix then rewrites the two matches above to the someone.. - ...


2

It is not that postdrop does not supports IPv4, it is that it is expecting also IPv6. The machine is obviously using postfix as a mailer daemon. If the sysadmin has disabled IPv6, postfix should give an warning at least each time it is restarted. Furthermore, if your sysadmin disables IPv6, he ought to finish the job and disable IPv6 support in some of the ...


0

The messages you are seeing are explicitly saying that IPv4 is (indeed, is the only) supported protocol. So, yes, and you currently are using a utility which supports IPv4.


2

It sounds like you want Exim's address rewriting. In the rewriting section of your Exim config file, you will probably want something along the lines of this: pi@bar.com foo@bar.com Ffr You may need to adjust the flags ("Ffr") to the specific behavior you want. More generally, see: ...


0

This cron job does what you specified daily at midnight: 0 0 * * * script >/dev/null -c 'env TERM=vt100 mutt -F/dev/null -falerts -e "push <delete-pattern>syscheck@example.com<enter><sync-mailbox>y<enter><exit>"' /dev/null Let's break that down. script -c 'cmd' runs cmd under a fake pseudo-tty (pty) so that cmd thinks it ...


1

The two are not equated in an RFC or other standard, but if you read further, you will notice that searching for the two terms together finds several articles which equate them, as well as pointing out a commonly used different format, maildir. RFC 4155 (written in September 2005, which is recent) says The mbox database format is not documented in an ...


0

Just to expand on Mayey's answer. This will read and delete a message without any side effects (e.g., moving to the next-entry when using tag-prefix, moving to the next-entry when user has resolve set to no): macro index d "<enter-command>set my_old_resolve=\$resolve noresolve<enter>\ ...


2

You could use mutt to do this from cron with expect (or one of its many implementations in many other languages). #!/usr/bin/env expect spawn mutt -f alerts expect -ex "Mutt" # or something if you've customized the display send -- "D" send -- "syscheck@example.com" ... Another option would be to write code that does a similar thing via something like ...



Top 50 recent answers are included