Thunderbird problems: “building summary file for Inbox”

Mozilla Thunderbird has trouble downloading new mail. The status bar shows “building summary file for Inbox”. Subsequent attempts to download mail may result in new messages being downloaded that are empty when you try to read them, multiple entries for new messages in the Inbox, or large numbers of reported unread messages that cannot be found. The symptoms may suggest a corrupt Inbox.

Solution

These problems can occur if you do not compact the Inbox. Mozilla Thunderbird mailboxes require periodic maintenance to prevent such problems from occurring. By the time the problems occur, compacting the Inbox, though still required, may not be sufficient to resolve the problem.

Method 1

Compact the Inbox if you have not already done so. Right-click the Inbox and select Compact this folder.

  • Close Mozilla Thunderbird.
  • Using Windows Explorer, navigate to the folder containing the messages for this account. This will be in a location similar to: C:\Documents and Settings\\Application Data\Thunderbird\Profiles\xxxxxx.default\Mail\. If you have multiple accounts on the same mail server then you may need to look at the names of the subfolders to identify which folder belongs to which account.
  • Delete the file named Inbox.msf. (Do not delete the file named Inbox, with no file type extension. This is the file containing your messages, and it will probably be very large.)
  • Restart Mozilla Thunderbird.

If the problem has not been resolved, try Method 2.

Method 2

Recreate the problem account.

  • Select the problem account and click View settings for this account.
  • Change the name of the account to e.g. Old .
  • Select Server Settings, and clear all the options that check for or download new messages.
  • Click Add Account, then create a new account with the same settings as the old one.
  • Select all the messages in the Inbox of the old account and drag and drop them into the Inbox of the new one.
  • Drag and drop any message folders from the old account to the new one.
  • Manually recreate any message filters that existed in the old account.
  • Once you are sure that all your messages have been transferred to the recreated account, delete the old one.

If necessary, you can use the Folderpane Tools extension to change the order of your Thunderbird accounts so that the recreated account appears in the same position as the original.

Compacting the Inbox

To ensure that this problem does not occur, you should configure Thunderbird to automatically compact mail folders. Click on Tools, Options, select Offline & Disc Space, and check Compact folders when it will save over xxxx KB.

Applies to
  • Mozilla Thunderbird 1.0 and up

exim

What are some tools that I can use to troubleshoot mail delivery issues with Exim on my linux / BSD / unix server?

This article will highlight some of the utilities included with the standard exim installation that assist in troubleshooting mail delivery issues.

Exigrep

Exigrep is very useful when you need to search for specific strings in the exim logfile. The reason for this is that it will look for the search string you specify, match that to a message-ID, and then display all the lines pertaining to that message.

Usage: exigrep /path/to/exim/logfile

Examples:
root@cpdemo [~]# exigrep 1BbLM3-0007fA-0v /var/log/exim_mainlog
2004-06-18 10:32:35 1BbLM3-0007fA-0v <= root@cpdemo.example.com U=root P=local S=1037
2004-06-18 10:32:37 1BbLM3-0007fA-0v => /dev/null <
devnull@cpdemo.example.com> R=system_aliases T=**bypassed**
2004-06-18 10:32:37 1BbLM3-0007fA-0v Completed

-OR-

root@cpdemo [~]# exigrep inspirem@cpdemo.example.com /var/log/exim_mainlog
2004-06-14 00:00:00 1BZjZg-000750-Ch <= inspirem@cpdemo.example.com U=inspirem P=local S=597
2004-06-14 00:00:00 1BZjZg-000750-Ch == example
@yahoo.com R=defer_router defer (-1): All deliveries are handled by MailScanner
2004-06-14 00:00:03 1BZjZg-000750-Ch => example
@yahoo.com R=lookuphost T=remote_smtp H=mx1.mail.yahoo.com [64.157.4.78]
2004-06-14 00:00:03 1BZjZg-000750-Ch Completed

2004-06-15 00:00:01 1Ba63E-0004gD-US <= inspirem@cpdemo.example.com U=inspirem P=local S=597
2004-06-15 00:00:01 1Ba63E-0004gD-US == example
@yahoo.com R=defer_router defer (-1): All deliveries are handled by MailScanner
2004-06-15 00:00:04 1Ba63E-0004gD-US => example
@yahoo.com R=lookuphost T=remote_smtp H=mx1.mail.yahoo.com [64.156.215.19]
2004-06-15 00:00:04 1Ba63E-0004gD-US Completed

Also notice that if you are looking for information that is listed in multple email transactions(ie. email addresses, sending hosts, etc …), exigrep will provide a space in between each email transaction.

Exiwhat

The ‘exiwhat’ command displays what each running exim process is doing at that given moment. This can be helpful in tracking down the cause for hanging exim processes or monitoring exim processes while they perform certain functions during testing.

Example:

root@cpdemo [~]# exiwhat
2118 daemon: -q1h, listening for SMTP on port 25 (IPv4)
2130 daemon: no queue runs, listening for SMTPS on port 465 (IPv4)
31640 handling incoming connection from [67.19.0.37]

Exim -bh

This section describes another usage of the exim mail server binary with special arguments that allow you to simulate a mail delivery from an external IP as the sender from the local server with the exim installation. This can be very useful when you need to recreate the mail delivery issue and you don’t have access to the sender’s machine to do so(ex. mail relaying, blacklists, etc.).

Usage: exim -bh

This will create a fake SMTP session which appears to be from . Not only that, but it also displays what exim is doing behind the scenes, and also what it would normally log. Now, bear in mind that this will not actually inject a message into the queue, nor will it actually log anything. This does however require knowledge of SMTP commands, but they are fairly easy. I have highlighted them in bold below for easier reading. Example:

root@cpdemo [/var/spool/exim/input]# exim -bh 216.87.129.155

**** SMTP testing session as if from host 216.87.129.155
**** but without any ident (RFC 1413) callback.
**** This is not for real!

>>> host in host_lookup? no (option unset)
>>> host in host_reject_connection? no (option unset)
>>> host in sender_unqualified_hosts? no (option unset)
>>> host in recipient_unqualified_hosts? no (option unset)
>>> host in helo_verify_hosts? no (option unset)
>>> host in helo_try_verify_hosts? no (option unset)
>>> host in helo_accept_junk_hosts? yes (matched “*”)
220-cpdemo.domain.com ESMTP Exim 4.34 #1 Fri, 18 Jun 2004 16:05:31 -0500
220-We do not authorize the use of this system to transport unsolicited,
220 and/or bulk e-mail.
helo bbozo-2.example.com
>>> bbozo-2.example.com in helo_lookup_domains? no (end of list)
250 cpdemo.domain.com Hello bbozo-2.example.com [216.87.129.155]
mail from: ken@bbozo-2.example.com
250 OK
rcpt to: inspirem@cpdemo.domain.com
>>> using ACL “check_recipient”
>>> processing “accept”
>>> check hosts = :
>>> host in “:”? no (end of list)
>>> accept: condition test failed
>>> processing “warn”
>>> check condition = ${if and {{match{$local_part}{(.*)-bounces+.*}} {exists {/usr/local/cpanel/3rdparty/mailman/lists/${lc:$1}/config.pck}}} {yes}{no}}
>>> = no
>>> warn: condition test failed
>>> processing “accept”
>>> check condition = ${if and {{match{$local_part}{(.*)-bounces+.*}} {exists {/usr/local/cpanel/3rdparty/mailman/lists/${lc:$1}/config.pck}}} {yes}{no}}
>>> = no
>>> accept: condition test failed
>>> processing “warn”
>>> check condition = ${if and {{match{$local_part}{(.*)-bounces+.*}} {exists {/usr/local/cpanel/3rdparty/mailman/lists/${lc:$1}_${lc:$domain}/config.pck}}} {yes}{no}}
>>> = no
>>> warn: condition test failed
>>> processing “accept”
>>> check condition = ${if and {{match{$local_part}{(.*)-bounces+.*}} {exists {/usr/local/cpanel/3rdparty/mailman/lists/${lc:$1}_${lc:$domain}/config.pck}}} {yes}{no}}
>>> = no
>>> accept: condition test failed
>>> processing “require”
>>> check verify = sender
>>> ken@bbozo-2.example.com in “nobody@lsearch;/etc/localdomains“? no (end of list)
>>> ken@bbozo-2.example.com in “cpanel@lsearch;/etc/localdomains“? no (end of list)
>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>> routing ken@bbozo-2.example.com
>>> bbozo-2.example.com in “lsearch;/etc/localdomains”? no (end of list)
>>> bbozo-2.example.com in “! +local_domains”? yes (end of list)
>>> calling lookuphost router
>>> 216.87.129.155 in “0.0.0.0 : 127.0.0.0/8 : 64.94.110.0/24”? no (end of list)
>>> routed by lookuphost router
>>> ———– end verify ————
>>> require: condition test succeeded
>>> processing “accept”
>>> check domains = +local_domains
>>> cpdemo.domain.com in “lsearch;/etc/localdomains”? yes (matched “lsearch;/etc/localdomains”)
>>> cpdemo.domain.com in “+local_domains”? yes (matched “+local_domains”)
>>> check verify = recipient
>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>> routing inspirem@cpdemo.domain.com
>>> cpdemo.domain.com in “! +local_domains”? no (matched “! +local_domains” – cached)
>>> cpdemo.domain.com in “! +local_domains”? no (matched “! +local_domains” – cached)
>>> cpdemo.domain.com in “! +local_domains”? no (matched “! +local_domains” – cached)
>>> cpdemo.domain.com in “lsearch;/etc/userdomains”? no (end of list)
>>> cpdemo.domain.com in “! lsearch;/etc/userdomains”? yes (end of list)
>>> cpdemo.domain.com in “lsearch;/etc/localdomains”? yes (matched “lsearch;/etc/localdomains”)
>>> calling virtual_aliases_nostar router
>>> virtual_aliases_nostar router declined for inspirem@cpdemo.domain.com
>>> cpdemo.domain.com in “lsearch;/etc/userdomains”? no (end of list)
>>> cpdemo.domain.com in “lsearch;/etc/userdomains”? no (end of list)
>>> cpdemo.domain.com in “lsearch;/etc/localdomains”? yes (matched “lsearch;/etc/localdomains”)
>>> cpdemo.domain.com in “lsearch;/etc/localdomains”? yes (matched “lsearch;/etc/localdomains”)
>>> calling virtual_aliases router
>>> virtual_aliases router declined for inspirem@cpdemo.domain.com
>>> calling system_aliases router
>>> system_aliases router declined for inspirem@cpdemo.domain.com
>>> calling local_aliases router
>>> local_aliases router declined for inspirem@cpdemo.domain.com
>>> cpdemo.domain.com in “! lsearch;/etc/userdomains”? yes (end of list)
>>> cpdemo.domain.com in “! lsearch;/etc/userdomains”? yes (end of list)
>>> calling localuser router
>>> routed by localuser router
>>> ———– end verify ————
>>> accept: condition test succeeded
250 Accepted
Data
354 Enter message, ending with “.” on a line by itself
From: Ben bozo <ken@bbozo-2.example.com>
Subject: Test
>>> host in ignore_fromline_hosts? no (option unset)

Test.
.
>>> using ACL “check_message”
>>> processing “require”
>>> check verify = header_sender
>>> verifying From: header address Ben bozo <ken@bbozo-2.example.com>
>>> ken@bbozo-2.example.com in “nobody@lsearch;/etc/localdomains“? no (end of list)
>>> ken@bbozo-2.example.com in “cpanel@lsearch;/etc/localdomains“? no (end of list)
>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>>> routing ken@bbozo-2.example.com
>>> bbozo-2.example.com in “lsearch;/etc/localdomains”? no (end of list)
>>> bbozo-2.example.com in “! +local_domains”? yes (end of list)
>>> calling lookuphost router
>>> 216.87.129.155 in “0.0.0.0 : 127.0.0.0/8 : 64.94.110.0/24”? no (end of list)
>>> routed by lookuphost router
>>> require: condition test succeeded
>>> processing “accept”
>>> accept: condition test succeeded
LOG: 1BbQZP-00005P-Gg <= ken@bbozo-2.example.com H=(bbozo-2.example.com) [216.87.129.155] P=smtp S=264
250 OK id=1BbQZP-00005P-Gg

**** SMTP testing: that is not a real message id!

SMTP/Exim debug mode
Description

To test verbose mail-delivery and debugging via the Exim SMTP server in @Mail, you can use the following command:

/usr/local/atmail/mailserver/bin/exim -d -v ‘user@localdomain.com’
^D ( control D )

This will step through each router in Exim, until the message is delivered or bounced.

This command can be useful for debugging, ( to test why a message cannot be delivered, database connection details, exim router reports, aliases and catch-all delivery )

For a more simple version use the command:

# /usr/local/atmail/mailserver/bin/exim -bt ‘username@localdomain.com’

username@localdomain.com
router = spamcheck_router, transport = spamcheck

This will emulate message-delivery and report which router can handle the message. The above message reports the message is accepted within @Mail.

For accounts that do not exist the following is returned:

username@localdomain.com is undeliverable:
Unrouteable address

Asagidaki howto bu adresden alintidir.
tarafimdan bir takim ekler yapilmistir.

1) Create a mysql db via direct admin. I called mine admin_webmail (you should all know how to do this!)

2) Download and unpack the package:

code:

cd /var/www/html

wget http://easynews.dl.sourceforge.net/...20051007.tar.gz

tar xvfz roundcube_webmail_0.1-20051007.tar.gz

EK: bu versyon turkce kullanmaya kalkinca pek cok sorun cikartiyor.
O yuzden SVN versyonunu tercih etmeli
SVN versyonuna su sekilde sahip oluyoruz:

Linux konsolumuzda:

svn checkout https://svn.roundcube.net/trunk

————–


3) Ensure proper permissions of the folders:

code:
chown -R root.root roundcubemail

cd roundcubemail

chown -R apache logs temp

4) Import their SQL file:

code:
cd SQL

//replace the following with the database
username and password you created in step 1

mysql -u admin_webmail -p
Enter Password: *******

Once in, import their SQL file:

code:
use admin_webmail

SOURCE mysql.initial.sql

EK: mysql5 icin farkli bir dosyamiz var

SOURCE mysql5.initial.sql
—-
now the import should be complete.

5) Setup db config variables

code:
cd ../config/

nano db.inc.php


all you have to do here is change the “$rcmail_config[‘db_dsnw’] = ” config information, mine looks like this:

code:
$rcmail_config['db_dsnw'] =
'mysql://admin_webmail:myPasswordHere@localhost/admin_webmail';

the format is: mysql://:

@host/database_namesave that file and close it.

6) Setup the application config:

code:
nano main.inc.php

find this line:

code:
$rcmail_config['enable_caching'] = TRUE;

Replace with:

code:
$rcmail_config['enable_caching'] = FALSE;

next find:

code:
$rcmail_config['default_host'] = '';

replace with:

code:
$rcmail_config['default_host'] = 'localhost';

EK: Turkce destegi icin main.inc.php nin en altina

php tagindan once

$rcmail_config[‘charset’] = ‘ISO-8859-9’;

eklememiz lazim

———

7) *optional* you may want to setup an apache alias, you can overwrite your current webmail one with the following:

Edit httpd.conf:

code:
nano /etc/httpd/conf/httpd.conf

Find this line:

code:
Alias /webmail /var/www/html/webmail/

Replace with:

code:
Alias /webmail /var/www/html/roundcubemail/

then restart apache

code:
/usr/sbin/service httpd restart

You are done!

Login @ http://www.domain.com/webmail/

My Install Guide V4 – Debian 3.1 (VHCS2.4.7.1)

Install Steps Debian 3.1 base install – manual and clean
Follow these instructions exactly with a clean install and you can’t go wrong.

On install of Debian, select no packages to be installed, allow it to connect to the internet and let it download anything
it needs, usually its libs etc. Exim is most likely installed at this point so dont worry it will be removed shortly.

I would at this stage edit your host file to so that it picks up everything during install

vi /etc/hosts and add your server hostname with the IP, example

Code:

192.168.1.1       myhostname.domain.com myhostname

Lets being the install
———————————————————-

1.vi /etc/apt/sources.list (add the following sources, ive had no problems with this mirror)

Code:

deb ftp://ftp.uk.debian.org/debian/ stable main
deb-src ftp://ftp.uk.debian.org/debian/ stable main
deb http://security.debian.org/ stable/updates main

2. apt-get install postfix postfix-tls proftpd-mysql courier-authdaemon courier-base courier-imap courier-maildrop courier-pop libberkeleydb-perl libc-dev libcrypt-blowfish-perl libcrypt-cbc-perl libcrypt-passwdmd5-perl libdate-calc-perl libdate-manip-perl libdbd-mysql-perl libdbi-perl libio-stringy-perl libmail-sendmail-perl libmailtools-perl libmd5-perl libmime-perl libnet-dns-perl libnet-netmask-perl libnet-perl libnet-smtp-server-perl libperl5.8 libsnmp-session-perl libterm-readkey-perl libtimedate-perl perl perl-base perl-modules bind9 diff gzip iptables libmcrypt4 mysql-client-4.1 mysql-common-4.1 mysql-server-4.1 patch php4 php4-mcrypt php4-mysql php4-pear procmail libterm-readpassword-perl libsasl2-modules libsasl2 sasl2-bin apache2 apache2-common apache2-mpm-prefork libapache2-mod-php4 gawk libgd1g bzip2 wget make gcc

(when you get to the courier screen screen select no to web directories)
(when you get to the postfix screen select internet site and then type root for mail. If you set debian up correctly on install your domain should be already on screen. Select no to force sync updates.)
(when you get to the proftpd screen, select standalone)

3. mysql -u root (no password at this stage, change it later!)

Code:


create database vhcs2;
use vhcs2; grant all privileges on *.* to 'vhcs2'@'localhost' identified by 'vhcs2' with grant option;
\q (quit program)

4. apt-get remove apache-common (if installed – not needed)

5. wget http://kent.dl.sourceforge.net/sourceforge/vhcs/vhcs2-2.4.7.1.tar.bz2

6. tar -xjvf vhcs2-2.4.7.1.tar.bz2

7. cd vhcs2-2.4.7.1

8. cd configs

9. vi vhcs2.conf (make the changes to match your requirements, dont forget to change database name, username and password, these are what you need to change)

Code:


DEFAULT_ADMIN_ADDRES = your email
SERVER_HOSTNAME = your hostname
BASE_SERVER_IP = your ip
DATABASE_TYPE = mysql
DATABASE_HOST = localhost
DATABASE_NAME = vhcs2
DATABASE_PASSWORD = vhcs2
DATABASE_USER = vhcs

10. cd .. (back to the root of the vhcs2 directory)

11. make install (if command not found run ‘apt-get install make’)

12. cd /tmp/vhcs*

13. cp -R * /

14. cd /var/www/vhcs2/engine/setup

15. ./vhcs2-setup (install script)

Code:


Wlecome to VHCS2 '2.4 Spartacus' Setup Dialog.
This program will set up VHCS2 system on your server.
Please press 'Enter' to continue.
Please enter system hostname (Enter for defaults) [debian]: yourhostname
Please enter system network address (Enter for defaults) [192.168.0.128]: your ipaddress
Please enter SQL server host (Enter for defaults) [localhost]:
Please enter system SQL database (Enter for defaults) [vhcs2]: vhcs2
Please enter system SQL user (Enter for defaults) [root]: vhcs2
Please enter system SQL password (Enter for defaults) [none]: vhcs2
Please repeat system SQL password: vhcs2
Please enter VHCS ftp SQL user (Enter for defaults) [vftp]: vftp
Please enter VHCS ftp SQL user password (Enter for defaults) [none]: vftp
Please repeat VHCS ftp SQL user password: vftp
Please enter administrator login name (Enter for defaults) [admin]:
Please enter administrator password: your password
Please repeat administrator password: your password
Please enter admininistrator email address: your email address

16.

Code:

echo "Include /etc/apache2/sites-available/vhcs2.conf" >> /etc/apache2/httpd.conf


(forgotten in install script)

17. sh /etc/init.d/apache2 restart

18. vi /etc/init.d/courier-authdaemon

(change this line) ${libexecdir}/authlib/authdaemon stop

Code:

killall authdaemond.plain


19. sh /etc/init.d/courier-authdaemon restart

21. vi /etc/resolv.conf (and add to the top)

add this

Code:

nameserver your ip


(this removes errors about virtual hosts when starting apache)

22 Vhcs2 does not start automatically on reboot so we need to add it as a startup script.

First, you must get the startup runlevel by the command “runlevel” in the bash. You’ll get something like N 2, N means there was no previous runlevel, 2 is the actual runlevel.

For those who don’t have an N, you know what you’re doing, simply look in your inittab, then go in the folder /etc/rc2.d (if 2 is your startup runlevel)

Make an ls -al to see how it works, it isn’t hard to understand. At startup everthing from S01xx to S99xx is started in that order.

This should do most people for runlevel 2, replace rc.2 with rc.3 if on runlevel 3

Code:

ln -s /etc/init.d/vhcs2_daemon /etc/rc2.d/S98vhcs

23. (You may need to change permissions on the tools folder)

Code:


chmod -R 766 /var/www/vhcs2/gui/tools


24. Thats about it, your should be ready to go

Original URL of this Document: http://vhcs.net/new/modules/newbb/viewtopic.php?topic_id=6840&forum=2

<font size="-1"><font face="Tahoma">Buda uzaktan yazma denemesi 2 olsun<br /> gmailden attigim mesajin nedense icerigi gozukmedi.<br /> sakin, ogrenicez.</font></font></p> <p><font size="-1"><font face="Tahoma">mail gonderirken plain text gondermeli..<br /> ..<br /> </font></font></p> </div> </article> <article itemscope itemtype="http://schema.org/Article" id="post-3" class="post-3 post type-post status-publish format-standard hentry category-kategerisiz"> <header class="entry-header"> <h2 class="entry-title" itemprop="name"> <a itemprop="url" href="https://www.shukko.com/x3/2007/01/11/merhaba-x3-x3-evo-d/" title="Merhaba X3! – x3 evo – :D için kalıcı bağlantı" rel="bookmark">Merhaba X3! – x3 evo – :D</a> </h2> <div class="entry-meta"><span class=“entry-date”><a href=“https://www.shukko.com/x3/2007/01/11/merhaba-x3-x3-evo-d/” rel=“bookmark”><time class=“entry-date published” datetime=“2007-01-11T23:56:19+02:00” itemprop=“datepublished”>11 Oca 2007</time></a></span, <span class=“author vcard” itemscope itemprop=“author” itemtype=“http://schema.org/Person”><a class=“url fn n” href=“https://www.shukko.com/x3/author/admin/” rel=“author” itemprop=“url”><span itemprop=“name”>shukko</span></a></span><span class="sep">·</span><span class="comments-link"><a href="https://www.shukko.com/x3/2007/01/11/merhaba-x3-x3-evo-d/#respond" itemprop="discussionUrl">0 yorum</a></span></div> </header> <div class="entry-content" itemprop="articleBody"> <p>Merhaba, bugün simplephpblogdan wordpresse geçiş yapmaya karar verdim.</p> <p>Zaten ne zamandır kullanmakta olduğum simplephpblogun /x ne kadarda kullanışsız olduğunu düşünmekteydim. Birden gaza geldim ve ta ta! wordpress oldu canım 😀 . Şimdi eski simplephpblogdan wordpresee eski içeriğimi aktarmaya çalışacağım. Başarılı olurum diye umuyorum. Yoksa orda bi link burda eski link şurda eski ziyaretçi defteri orda eski bilmemne ruhum daralıyor. Derli toplu olsun herşey. Buda herhalde Türkçe karakter kullanarak yazdığım son yazı olacak. Alışkanlıklarım benim efendimdir…</p> <p>Not: bu arada neden /x dide blog değildi veya /x3 düde root dizininde değildi site için diyeceğim x evolusyonlarının ( x-evolotion * kendi kendimi eğlendirdim 😀 ) 3 cüsü bu olucak…</p> <p>ek – güzel bir fullscreen tema bulmam lazım …</p> </div> </article> <nav class="navigation pagination" aria-label="Yazılar"> <h2 class="screen-reader-text">Yazı gezinmesi</h2> <div class="nav-links"><a class="prev page-numbers" href="https://www.shukko.com/x3/page/43/"><i class="fa fa-chevron-left"></i></a> <a class="page-numbers" href="https://www.shukko.com/x3/">1</a> <span class="page-numbers dots">…</span> <a class="page-numbers" href="https://www.shukko.com/x3/page/43/">43</a> <span aria-current="page" class="page-numbers current">44</span> <a class="page-numbers" href="https://www.shukko.com/x3/page/45/">45</a> <span class="page-numbers dots">…</span> <a class="page-numbers" href="https://www.shukko.com/x3/page/48/">48</a> <a class="next page-numbers" href="https://www.shukko.com/x3/page/45/"><i class=“fa fa-chevron-right”></i></a></div> </nav> </div> <footer class="site-info" itemscope itemtype="http://schema.org/WPFooter"> <a href="http://wordpress.org/" title="Anlamlı kişisel yayınlama platformu">WordPress gururla sunar</a>. Tema: Flat 1.7.11, <a rel="nofollow" href="https://themeisle.com/themes/flat/" title="Flat WordPress Theme">Themeisle</a>. </footer> </div> </div> </div> </div> </body> </html>