To:
exigrep ‘=>.*[email protected]’ /var/log/exim/mainlog
From:
exigrep ‘<=.*[email protected]' /var/log/exim/mainlog
exim find all delivered emails to/from email address
Leave a reply
Tag Archives: exim
exim remove received from headers
vi /etc/exim.conf
remote_smtp:
driver = smtp
headers_remove = Received
exim remove all mail spool queue
cd /var/spool
mv exim exim.old
mkdir -p exim/input
mkdir -p exim/msglog
mkdir -p exim/db
chown -R mail:mail exim
/sbin/service exim restart
exiqgrep exit with error “Line mismatch”
exim -bp | grep "4d" | awk '{print $3}' | xargs exim -Mrm
switch postfix with exim or exim with postfix
alternatives –config mta
debugging exim MTA
killall exim
exim -v -bd
Also always useful:
exim -bt
exim -bt
or verbose mail sessions:
exim -v -odf
forwarding mail exim
yum install exim
mkdir /etc/exim/vhosts
vi /etc/exim/vhosts/linuxėyou.tk >>
info: [email protected]
vi /etc/exim/vhosts/linuxėyou.com >>
info: [email protected]
#Add virtual hosts
vi /etc/exim.conf >
domainlist local_domains = @ : localhost : localhost.localdomain : dsearch;/etc/exim/vhosts
#Create new router:
vi /etc/exim.conf >
virtual:
driver = redirect
domains = dsearch;/etc/exim/vhosts
data = ${lookup{$local_part}lsearch{/etc/exim/vhosts/$domain}}
no_more
service exim restart
exim modify a queued message
Modify a queued message # exim -Mar 1G4K8N-0003uY-29 [email protected] # Add recipient
# exim -Mes 1G4K8N-0003uY-29 [email protected] # Edit sender
# exim -Mmad 1G4K8N-0003uY-29 # Mark all delivered
# exim -Mmd 1G4K8N-0003uY-29 [email protected] # Mark delivered (just the address)
exim commands
Print a count of the messages in the queue:
exim -bpc
Print a listing of the messages in the queue (time queued, size, message-id, sender, recipient):
exim -bp
Print a summary of messages in the queue (count, volume, oldest, newest, domain, and totals):
exim -bp | exiqsumm
Print what Exim is doing right now:
exiwhat
Test how exim will route a given address:
root@localhost# exim -bt [email protected] [email protected] <-- [email protected] router = localuser, transport = local_delivery root@localhost# exim -bt [email protected] [email protected] router = localuser, transport = local_delivery root@localhost# exim -bt [email protected] router = lookuphost, transport = remote_smtp host mail.remotehost.com [1.2.3.4] MX=0
Run a pretend SMTP transaction from the command line, as if it were coming from the given IP address. This will display Exim’s checks, ACLs, and filters as they are applied. The message will NOT actually be delivered.
exim -bh 192.168.11.22
Display all of Exim’s configuration settings:
exim -bP
Searching the queue with exiqgrep
Exim includes a utility that is quite nice for grepping through the queue, called exiqgrep. Learn it. Know it. Live it. If you’re not using this, and if you’re not familiar with the various flags it uses, you’re probably doing things the hard way, like piping `exim -bp` into awk, grep, cut, or `wc -l`. Don’t make life harder than it already is.
First, various flags that control what messages are matched. These can be combined to come up with a very particular search.
Use -f to search the queue for messages from a specific sender:
exiqgrep -f [luser]@domain
Use -r to search the queue for messages for a specific recipient/domain:
exiqgrep -r [luser]@domain
Use -o to print messages older than the specified number of seconds. For example, messages older than 1 day:
exiqgrep -o 86400 [...]
Use -y to print messages that are younger than the specified number of seconds. For example, messages less than an hour old:
exiqgrep -y 3600 [...]
Use -s to match the size of a message with a regex. For example, 700-799 bytes:
xiqgrep -s '^7..$' [...]
Use -z to match only frozen messages, or -x to match only unfrozen messages.
There are also a few flags that control the display of the output.
Use -i to print just the message-id as a result of one of the above two searches:
exiqgrep -i [ -r | -f ] ...
Use -c to print a count of messages matching one of the above searches:
exiqgrep -c ...
Print just the message-id of the entire queue:
exiqgrep -i
Managing the queue
The main exim binary (/usr/sbin/exim) is used with various flags to make things happen to messages in the queue. Most of these require one or more message-IDs to be specified in the command line, which is where `exiqgrep -i` as described above really comes in handy.
Start a queue run:
exim -q -v
Start a queue run for just local deliveries:
exim -ql -v
Remove a message from the queue:
exim -Mrm <message-id> [ <message-id> ... ]
Freeze a message:
exim -Mf <message-id> [ <message-id> ... ]
Thaw a message:
exim -Mt <message-id> [ <message-id> ... ]
Deliver a message, whether it’s frozen or not, whether the retry time has been reached or not:
exim -M <message-id> [ <message-id> ... ]
Deliver a message, but only if the retry time has been reached:
exim -Mc <message-id> [ <message-id> ... ]
Force a message to fail and bounce as “cancelled by administrator”:
exim -Mg <message-id> [ <message-id> ... ]
Remove all frozen messages:
exiqgrep -z -i | xargs exim -Mrm
Remove all messages older than five days (86400 * 5 = 432000 seconds):
exiqgrep -o 432000 -i | xargs exim -Mrm
Freeze all queued mail from a given sender:
exiqgrep -i -f [email protected] | xargs exim -Mf
View a message’s headers:
exim -Mvh <message-id>
View a message’s body:
exim -Mvb <message-id>
View a message’s logs:
exim -Mvl <message-id>
Add a recipient to a message:
exim -Mar <message-id> <address> [ <address> ... ]
Edit the sender of a message:
exim -Mes <message-id> <address>
Exim use Smart Host on cPanel
To configure a smart host, create /etc/exim.conf.local on the source server (server1 in this example) and add the following lines. Be sure to change to the hostname or IP of the smart host server.
|
1
2
3
4
5
6
|
@ROUTERSTART@ smart_route: driver = manualroute domains = !+local_domains transport = remote_smtp route_list = * host.name.of.smart.host.server |
Assuming this server (server1) is a cPanel server, next run /scripts/buildeximconf and then /scripts/restartsrv_exim. If not, simply restart your Exim server using normal init scripts.
Smarthost Server Config
Assuming you’re installing the yum version of Exim on a CentOS/RHEL server, you’ll need to make two configuration changes. The first is to allow the IP of the mailserver to relay through the smarthost. Open the configuration at /etc/exim/exim.conf, find the line referenced below and edit it replacing x.x.x.x with your mailserver IP.
|
1
|
hostlist relay_from_hosts = 127.0.0.1 : x.x.x.x |
Second, you’ll need to tell Exim not to listen only on the localhost address for incoming mail, which is the default. Again find the configuration line below and add a hash (#) in front of it to comment it out.
|
1
|
local_interfaces = <; 127.0.0.1 ; ::1 |
Save the modified config file and restart Exim on this server.
That’s it; watch the logs for a bit to make sure it’s working! The easiest way is to just tail -f /var/log/exim_mainlog on both servers and then send a message from server1 to a remote host, and watch for the mail to travel out server2!
Enabling greylisting with directadmin using postgrey
You should download yumdownloader postgrey the you should extract this rpm and take some files for usage:
rpm2cpio postgrey-1.34-4.fc18.noarch.rpm | cpio -idv
the you can need copy some postgrey configuration and executable files from ./usr/sbin:
./usr/sbin/postgrey
./usr/sbin/postgreyreport
to /usr/local/sbin
./etc/postfix/postgrey_whitelist_clients.local
./etc/postfix/postgrey_whitelist_recipients
./etc/postfix/postgrey_whitelist_clients
to /etc folder
then you need create postgrey working folder for postgrey database
mkdir /var/spool/exim/postgrey && chown mailnull.mail /var/spool/exim/postgrey
to start postgrey you can like this:
/usr/local/sbin/postgrey -d –unix=/var/spool/exim/postgrey/socket –exim –syslog-facility=local6 –user=mailnull –group=mail –dbdir=/var/spool/exim/postgrey –delay=60 –max-age=35 –retry-window=12h –greylist-text=Greylisted. Please, try again later. –whitelist-clients=/etc/postgrey_whitelist_clients –whitelist-recipients=/etc/postgrey_whitelist_recipients –whitelist-clients=/etc/postgrey_whitelist_clients.local –auto-whitelist-clients=5
if you can start, you maybe missing some dependencies like:
yum install perl-BerkeleyDB perl-Net-DNS perl-Net-Server perl-Digest-HMAC perl-IO-Multiplex perl-Digest-SHA1
You should create new ACL rule in your exim.conf
begin acl
# ACL that is used after the RCPT command
check_recipient:
# postgrey [TOP]
defer
log_message = greylisted host $sender_host_address
!senders = : postmaster@*
# domains = +local_domains : +relay_to_domains
!hosts = /etc/virtual/domains
!authenticated = *
verify = recipient/callout=20s,use_sender,defer_ok
set acl_m3 = request=smtpd_access_policy\n\
protocol_state=RCPT\n\
protocol_name=${uc:$received_protocol}\n\
instance=${acl_m2}\n\
helo_name=${sender_helo_name}\n\
client_address=${substr_-3:${mask:$sender_host_address/27}}\n\
client_name=${sender_host_name}\n\
sender=${sender_address}\n\
recipient=$local_part@$domain\n\n
set acl_m3 = ${sg{\
${readsocket{ /postgrey/socket/full_address }{$acl_m3}\
{5s}{}{action=DUNNO}}\
}{action=}{}}
message = ${sg{$acl_m3}{^\\w+\\s*}{}}
condition = ${if eq{${uc:${substr{0}{5}{$acl_m3}}}}{DEFER}{true}{false}}
# add “greylisted by ..seconds” header to mail which has successfully
# passed the greylisting.
warn
!senders = : postmaster@*
# domains = +local_domains : +relay_to_domains
!hosts = /etc/virtual/domains
!authenticated = *
message = ${sg{$acl_m3}{^\\w+\\s*}{}}
condition = ${if eq{${uc:${substr_0_7:$acl_m3}}}{PREPEND}{true}{false}}
# postgrey [END]
# to block certain wellknown exploits, Deny for local domains if
# local parts begin with a dot or contain @ % ! / |
deny domains = +local_domains
local_parts = ^[.] : ^.*[@%!/|]
After this you can restart you exim server and check if you exim use greylisting.
421 Unexpected failure, please try later EXIM
It means you should check exim main log and usually it means exim is missing some configuration files from main exim root folder.