source

source

# vi /etc/mail/sendmail.cf
DSsmtpgateway.xyz.com.au
# refresh -s sendmail

To log Sendmail activity, place the following entry in the /etc/syslog.conf file, create the log file, and refresh the syslog daemon:

# grep mail /etc/syslog.conf
mail.debug /var/log/maillog rotate time 7d files 4 compress
# touch /var/log/maillog
# refresh -s syslogd

source
.forward+: world writable directory:

The biggest surprise is likely to come from .forward and :include: files in unsafe directory paths (directory paths which are group or world writable). This is no longer allowed. This would mean that if user joe’s home directory was writable by group staff, sendmail would not use his .forward file. This behavior can be altered, at the possible expense of system security, by setting the DontBlameSendmail option. Items from these unsafe .forward and :include: files will be marked as unsafe addresses – the items can not be deliveries to files or programs. This behavior can also be altered via DontBlameSendmail.

I’ve set:

O DontBlameSendmail=forwardfileinunsafedirpath, forwardfileinunsafedirpathsafe

The first flag allows the forward file to be read, the second allows the items in the file to be marked as safe for file and program delivery.

source

How do I start/stop sendmail on AIX?

 source

Purging a sendmail mailqueue on AIX

# ps -ef | grep sendmail

# kill -9 SENDMAIL_PIDS

Then, stop sendmail cleanly (the commands depend of your OS. This one works only on IBM AIX).

# stopsrc -s sendmail

You may check the number of messages that are in the queue, which will give you an idea of the time it will take to process the queue:

# sendmail -bp


Check that there are no longer any sendmail processes running:

# ps -ef | grep sendmail

# kill -9 SENDMAIL_PIDS

Rename the current mailqueue to another directory:

# mv /var/spool/mqueue /var/spool/omqueue 

Restart sendmail

# startsrc -s sendmail
0513-059 The sendmail Subsystem has been started. Subsystem PID is 62118
Now process the old queue (may take time, depending upon the number of messages to process):

# /usr/sbin/sendmail -oQ/var/spool/omqueue -q -v

Running /var/spool/omqueue/m7HKkOM60666 (sequence XXXX of XXXXX)
Running /var/spool/omqueue/m7HKkOM60666 (sequence XXXX+1 of XXXXX)...
etc... 

Now, you may safely delete all messages in the old queue:

# rm -rf /var/spool/omqueue

Create a new mailqueue directory.

# mkdir /var/spool/mqueue

Stop and start sendmail:

# stopsrc -s sendmail


# startsrc -s sendmail

source

Kill all sendmail processes

for i in `ps -ef |grep sendmail|awk '{ print $2 }'`; do kill -9 $i; done

To insert an image into your signature in Mozilla Thunderbird:

• Start with a new, empty message using HTML formatting.
• In the message’s body, create your signature the way you want it to look.
• Insert the image.
  • Go to the image insertion dialog’s Link tab to link your image to a web page.
• Select File | Save As | File… from the message’s menu.
• Make sure HTML Files is selected under Format:.
• Enter “signature.html” (or something similar) under Save As:.
• Click Save.
• Close the message window, not saving the draft.
• Select Tools | Account Settings… from the Mozilla Thunderbird menu.
• For all desired accounts:
  • Go to the account’s root item.
  • Make sure Attach this signature: is checked.
  • Click Choose….
  • Find and highlight the “signature.html” file just created.
  • Click Open.
• Click OK.

source

cd /etc/mail
m4 sendmail.mc > sendmail.cf
service sendmail restart

source

http – http only, the user would browse to http://zimbra.domain.com
https – https only, the user would browse to https://zimbra.domain.com http:// is denied.
both – A user can go to http:// or https:// and will keep that mode for their entire session.
mixed – If the user goes to http:// it will switch to https:// for the login only, then will revert to http:// for normal session traffic. If they browse to https:// then they will stay https://
redirect – Like mixed if the user goes to http:// it will switch to https:// but they will stay https:// for their entire session.

source

close evolution
$ killall gconfd-2
rm /home/user/.gconf/apps/evolution/shell/network_config/%gconf.xml

This is expected behavior. The scrubber saves attachments in
the archives/private/<listname>/attachments/ directory. This
happens for all messages if scrub_nondigest is Yes, and for
all plain digests in any case even if the list does not do
archiving.

If you allow attachments at all, the only way to avoid this
is to set both scrub_nondigest and digestable to No. I.e,
don’t scrub individual messages and don’t allow digests.

source

source

source