Tag Info

New answers tagged

0

I had the following bit of perl that strips all attachments from stdin and returns stdout which may be of help: #!/usr/bin/perl -w use strict; use Mail::Audit; use Mail::Audit::Attach qw(Attach); my $mail = Mail::Audit->new; my $attachments = $mail->attachments; foreach (@$attachments) { $_->remove; } $mail->print(); and ...


0

Your ISP may by proxying/caching HTTP requests. But icanhazip.com supports HTTPS which, like SSH, your ISP can't proxy. So try changing the script to curl https://icanhazip.com


0

You can use imapsync for this. You can get the source from fedorahosted.org imapsync page. Zimbra Guide to imapsync has good documentation about this subject.


0

"cp -pr" should do the job. The "r" option in "pr" should take care of both subfolders and any hidden files/directories.


2

Rewriting the From header field would not help with protecting your ip address from getting blacklisted when the receiver of that mail marks it as spam as your ip address will still be the one that transmitted that e-mail, but might make the receiver realize it is being forwarded. You can use postfix header_checks feature to rewrite the From header. 1 ...


1

Judging by aharris88's description, Gmail was blocking access to his account via mutt because mutt is using insecure connections when communicating with Gmail's servers. This means that your username and password are being sent across the local network and the Internet in an unencrypted form; generally a really bad idea, and something to be avoided whenever ...


0

You may have a few options, but they are not universal. If the mail server's logs are world-readable, you can examine them for error messages. If your mail server is exim, look for /var/log/exim/ or perhaps simply /var/log/mail. What exactly gets logged where exactly is ultimately a separate can of worms, where a starting point is the syslog ...


0

Often you can look at the headers of the bounced mail about what has gone (wrong) under way, how far the mail got and which machine rejected it (or was offline). If you have access to the sending and/or receiving machine's /var/log/mail.log check those for messages to make you start looking for possible configuration problems on the right machine. Looking ...


2

If you want to send email to a user at an IP address, you need to enclose the address in brackets, e.g. dest_user@[ip.ad.dr.ess]. Whether that addressing will be accepted by the receiving server is another issue. My mail servers don't accept email addressed to it IP address.


0

The descriptive text in the From: address is taken from the password file. You can use the chfn command to change this. Try the command (change fullname and user ids as appropriate): sudo chfn -f "Contact me" root Ideally, you will have an alias for root in /etc/aliases specifying who should receive mail sent to root. This would likely be your userid, ...


1

You need to tell mail the name you'd like to use (its currently looking it up in /etc/passwd, most likely). Of course, you could also change the user full name in /etc/passwd (e.g., via chfn -f 'New Name' user, and you really ought not be sending the mail as root! For Heirloom mail, you can use either the from environment variable, its mailrc config file, ...


0

Based on those 1st 3 messages it would look like you need to upgrade your version of Perl to at least 5.12.3. Perl version 5.012003 (5.12.3) is at least recommended to run ASSP 2.4.3 (14313) - you are running Perl version 5.010001 - please upgrade Perl Perl version 5.012000 (5.12.0) is at least required to use the unicode Bayesian/HMM engine of ASSP ...


0

You can do the following, but this requires a mailbox, create a dummy mailbox (/home/vmail/domains/mydomain/redir), and create a dot-courier file (/home/vmail/domains/mydomain/redir/.courier) with the following content: dest1@wherever.com dest2@wherever.com And that's it, when you send a mail to redir@mydomain.com, it will be forwarded to ...


2

Following should work for postfix equal or higher than 2.7. You need to modify /etc/postfix/master.cf, change the line smtp inet n - n - - smtpd to something like this: domain1 unix - - n - - smtp -o syslog_name=postfix-mail.example.com -o smtp_helo_name=mail.example.com -o smtp_bind_address=1.1.1.1 ...


2

From RFC 2822 para 3.6.2: When the "Reply-To:" field is present, it indicates the mailbox(es) to which the author of the message suggests that replies be sent. In the absence of the "Reply-To:" field, replies SHOULD by default be sent to the mailbox(es) specified in the "From:" field unless otherwise specified by the person composing the reply. ...


1

The FROM address identifies who is sending the message. Normally this is where someone will send a reply, but you can specify a different address where you want replies to go. This may be useful for example, when posting to a mailing list and you want people replying to your message to send to the mailing list rather than directly to you.


0

It is neither recommended nor common to remove received headers. However, there are cases where it is desirable to remove the headers in an attempt to prevent leakage of your network configuration. (This may not be as successful as intended.). If you are removing headers, it is recommended you keep a record of the removed headers so that they can be ...


1

mail's exit status refers to local processing only. It means: "This mail has been accepted bei the local MTA." It cannot say anything about the success of delivering the mail as that has not even been tried at this point.


2

You can set up the mailbox(es) to use in mutt via ~/.muttrc. It would be something like this (see the manpage for muttrc for the full details): set folder=/var/spool/mail set mbox=+daedalus


0

Turns out that all we had to do was to combine the last 2 steps I had asked in the question. Copy the e-mail file, (ie. 141443305.abc123abc.imap01.xyz.com:2,S) from /home/<user>/Maildir/cur to /home/<user>/Maildir/new and rename it by removing the :2,S suffix. This process marks the read mail as unread.


1

Create directory with below command mkdir /var/spool/mqueue Make sure mqueue directory has correct permission chown root:mail /var/spool/mqueue Then restart Sendmail service sendmail restart


0

One of possible solution is that, create the mqueue drive with root permission in /var/spool hope its may work. best luck. Regards Jaymin D



Top 50 recent answers are included